Deprecated features

This section summarizes deprecated features in the product offerings comprising WebSphere Process Server version 6.0, which include the WebSphere Business Integration Server Foundation version 5.1 and WebSphere Application Server Enterprise Edition version 5.0. Deprecated features from other WebSphere Application Server version 5.x and 6.x product offerings are described in the documentation for those products. As they become available, links to additional information will be provided to help you migrate from deprecated features.

Related concepts
Migration overview

Deprecation list

The following tables summarize what is deprecated, by version and release. Each table reflects the version and release where the deprecation took effect and lists what is being deprecated, such as features, APIs, scripting interfaces, tools, wizards, publicly exposed configuration data, naming identifiers, and constants. Where possible, a recommended migration action is provided.

Deprecated features in WebSphere Process Server version 6.0.2

Human Task Manager
The task context variable %htm:task.clientDetailURL% is no longer required, and thus has been deprecated.

Recommended migration action:

No action is required.

The standard e-mail implementation used for all escalation e-mails in TEL has been deprecated, and replaced by native support for defining e-mails in TEL.

Recommended migration action:

Use the new customizeable e-mail feature for escalations.

The following Task object methods that were deprecated in version 6.0 are no longer deprecated:
  • getInputMessageTypeName()
  • getOutputMessageTypeName()

Recommended migration action:

You can now use these methods.

Business Process Choreographer

The method getProcessAdministrators() in the Generic Business Process EJB API interfaces ActivityInstanceData, ProcessInstanceData, and ProcessTemplateData are deprecated:

Recommended migration action:

Use these corresponding new methods:

  • getProcessAdminTaskID() in combination with method getUsersInRole() of the HumanTaskManagerService interface, as follows:
    • htm.getUsersInRole(actInstData.getProcessAdminTaskID(), WorkItem.REASON_ADMINISTRATOR)
  • getAdminTaskID() in combination with method getUsersInRole() of the HumanTaskManagerService interface, as follows:
    • htm.getUsersInRole(procInstData.getAdminTaskID(), WorkItem.REASON_ADMINISTRATOR)
  • getAdminTaskTemplateID()in combination with method getUsersInRole() of the HumanTaskManagerService interface, as follows:
    • htm.getUsersInRole(procTemplData.getAdminTaskTemplateID(), WorkItem.REASON_ADMINISTRATOR )
The following methods are deprecated for the BusinessFlowManagerService interface in Generic Business Process EJB API and the HumanTaskManagerService interface in the Generic Task EJB API:
  • query(String storedQueryName, Integer skipTuples)
  • query(String storedQueryName, Integer skipTuples, Integer threshold)

Recommended migration action:

Use these corresponding new methods:
  • query(String storedQueryName, Integer skipTuples, List parameters)
  • query(String storedQueryName,Integer skipTuples, Integer threshold, List parameters)
The following JACL scripts are deprecated:
  • deleteAuditLog.jacl
  • deleteInvalidProcessTemplate.jacl
  • deleteInvalidTaskTemplate.jacl
  • queryNumberOfFailedMessages.jacl
  • replayFailedMessages.jacl
  • cleanupUnusedStaffQueryInstances.jacl
  • refreshStaffQuery.jacl

Recommended migration action:

For each deprecated JACL scripts, a corresponding Jython script is now provided. Use the Jython scripts (*.py), which can be found in the <install_root>/ProcessChoreographer/admin directory.

SCA Admin Commands
The following commands (used via wsadmin) are deprecated:
  • configSCAForServer
  • configSCAForCluster

Recommended migration action:

You should to use these two commands in place of configSCAForServer for equivalent function. :
  • configSCAAsyncForServer
  • configSCAJMSForServer
You should use these two commands in place of configSCAForCluster for equivalent function:
  • configSCAAsyncForCluster
  • configSCAJMSForCluster
Note: The configSCAAsync* commands are mandatory, because SCA modules will not deploy successfully to a server or cluster that has not been configured by this command. The configSCAJMSForServer and configSCAJMSForCluster commands are optional, however, and you are required to use these commands only if you need SCA JMS functionality.
WebSphere InterChange Server

The APIs (application programming interfaces) listed in Supported WebSphere InterChange Server APIs (WebSphere Process Server 6.0.2) are deprecated.

Recommended migration action:

New code written for WebSphere Process Server should not use these interfaces.

IBM WebSphere InterChange Server Access for Enterprise JavaBeans (EJB) support is deprecated.

Recommended migration action:

New applications developed for use with WebSphere Process Server should not use Access for Enterprise JavaBeans.

Deprecated features in WebSphere Process Server version 6.0.1

WebSphere Process Server version 6.0.1 has no deprecated features.

Deprecated features in WebSphere Process Server version 6.0

Application programming model and container support features
The BRBeans component is deprecated, and is being replaced with the new business rules.

Recommended migration action:

You must manually remove all usages of BRBeans and move to the new business rules.

Some BPEL business process modeling constructs have been syntactically changed in version 6. Only the new syntax is supported by WebSphere Integration Developer version 6.0. Migration is available for these constructs.

Recommended migration action:

Use the migration wizard provided by WebSphere Integration Developer to migrate WebSphere Business Integration Server Foundation version 5.1 service projects (including process definitions) to WebSphere Process Server version 6.0. After the migration wizard has finished, you must carry out some manual steps to complete the migration. For more information about migrating service projects, refer to the information center for WebSphere Integration Developer version 6.0.

In WebSphere Business Integration Server Foundation version 5.1, there is an option for the input of an undo service to implicitly provide a message that results from the merge of the input data of the compensable service overlaid by its output data . Given the enhanced compensation support provided by BPEL this functionality is deprecated.

Recommended migration action:

Use BPEL compensation for new business processes.

Because of changes in the Business Flow Manager functionality In WebSphere Process Server version 6.0, the following methods are deprecated in the generic process API:
  • The WorkList object has been renamed to StoredQuery; consequently, the following methods are deprecated on the BusinessFlowManager bean, and, if applicable, the methods you should now use WebSphere Process Server version 6.0 are given:
    • newWorkList( String workListName, String selectClause, String whereClause, String orderByClause, Integer threshold, TimeZone timezone )
      • Replace with: createStoredQuery( String storedQueryName, String selectClause, String whereClause, String orderByClause, Integer threshold, TimeZone timezone )
    • getWorkListNames()
      • Replace with: getStoredQueryNames()
    • deleteWorkList( String workListName )
      • Replace with: deleteStoredQuery( String storedQueryName )
    • getWorkList( String workListName )
      • Replace with: getStoredQuery( String storedQueryName )
    • executeWorkList( String workListName )
      • Replace with: query( String storedQueryName, Integer skipTuples )
    • getWorkListActions()
      • not supported.
  • The WorkListData object is deprecated.
    • Use StoredQueryData instead.
  • The following methods of the ProcessTemplateData object are no longer supported:
    • getInputMessageTypeTypeSystemName()
    • getOutputMessageTypeTypeSystemName()
  • The following methods of the ProcessInstanceData object are no longer supported:
    • getInputMessageTypeTypeSystemName()
    • getOutputMessageTypeTypeSystemName()
  • The following methods of the ActivityInstanceData object are no longer supported:
    • getInputMessageTypeTypeSystemName()
    • getOutputMessageTypeTypeSystemName()
  • The following methods of the ActivityServiceTemplateData object are no longer supported:
    • getInputMessageTypeTypeSystemName()

Recommended migration action:

Use the replacement methods, if any, that are given.

Because of changes in the Human Task Manager functionality In WebSphere Process Server version 6.0, the following methods are deprecated in the generic process API
  • The following methods are deprecated on the HumanTaskManager bean, and their replacements for use in WebSphere Process Server version 6.0 are given:
    • createMessage( TKIID tkiid, String messageTypeName )
      • Use the specific methods createInputMessage( TKIID tkiid ), createOutputMessage( TKIID tkiid ), createFaultMessage( TKIID tkiid ) instead.
    • createMessage( String tkiid, String messageTypeName )
      • Use the specific methods createInputMessage( String tkiid ), createOutputMessage( String tkiid ), createFaultMessage( String tkiid ) instead.
  • For the Task object, the following methods are no longer supported:
    • getInputMessageTypeName()
    • getOutputMessageTypeName()

Recommended migration action:

Use the replacement methods, if any, that are given.

The following database views are deprecated:
  • DESCRIPTION
  • CUSTOM_PROPERTY

Recommended migration action:

For new applications use the TASK_DESC view for the DESCRIPTION view and the TASK_CPROP view for the CUSTOM_PROPERTY view.

Programming Model of Java Code Snippets
  • In WebSphere Business Integration Server Foundation version 5.1, access to BPEL variables within inline Java code snippets (activities and conditions) is provided through getter and setter methods. These methods are not supported. The WSIFMessage method that is used to represent BPEL variables in Java code snippets is also not supported.
  • Methods <typeOfP> getCorrelationSet<cs> Property<p>() are not supported, as they do not consider correlation sets declared at the scope level; they can only be used to access correlation sets declared at the process level.
  • The WebSphere Business Integration Server Foundation version 5.1 methods to access custom properties within Java snippet activities are not supported.
  • The following getPartnerLink methods are not supported. Because they do not consider partner links declared on the scope level, they can only be used to access partner links declared at the process level.
    • EndpointReference getPartnerLink();
    • EndpointReference getPartnerLink (int role);
    • void setPartnerLink (EndpointReference epr);

Recommended migration action:

Use the migration wizard provided by WebSphere Integration Developer 6.0 to migrate WebSphere Business Integration Server Foundation version 5.1 service projects (including process definitions) to WebSphere Process Server version 6.0. After the migration wizard has finished, you must carry out some manual steps to complete the migration. For more information about migrating service projects, refer to the information center for WebSphere Integration Developer version 6.0.

Application services features
The Extended Messaging Service feature and all of the EMS/CMM APIs and SPIs listed below are deprecated:
  • com/ibm/websphere/ems/CMMCorrelator
  • com/ibm/websphere/ems/CMMException
  • com/ibm/websphere/ems/CMMReplyCorrelator
  • com/ibm/websphere/ems/CMMRequest
  • com/ibm/websphere/ems/CMMResponseCorrelator
  • com/ibm/websphere/ems/ConfigurationException
  • com/ibm/websphere/ems/FormatException
  • com/ibm/websphere/ems/IllegalStateException
  • com/ibm/websphere/ems/InputPort
  • com/ibm/websphere/ems/OutputPort
  • com/ibm/websphere/ems/transport/jms/JMSRequest
  • com/ibm/websphere/ems/TimeoutException
  • com/ibm/websphere/ems/TransportException
  • com/ibm/ws/spi/ems/CMMFactory
  • com/ibm/ws/spi/ems/format/cmm/CMMFormatter
  • com/ibm/ws/spi/ems/format/cmm/CMMParser
  • com/ibm/ws/spi/ems/format/Formatter
  • com/ibm/ws/spi/ems/format/Parser
  • com/ibm/ws/spi/ems/transport/CMMReceiver
  • com/ibm/ws/spi/ems/transport/CMMReplySender
  • com/ibm/ws/spi/ems/transport/CMMSender
  • com/ibm/ws/spi/ems/transport/MessageFactory

Recommended migration action:

Instead of using the Extended Messaging Service and its associated tooling, you will need to use standard JMS APIs, or equivalent messaging technologies.

Deprecated features in WebSphere Business Integration Server Foundation version 5.1.1

WebSphere Business Integration Server Foundation version 5.1.1 has no deprecated features.

Deprecated features in WebSphere Business Integration Server Foundation version 5.1

Installation and migration tools
Business processes modeled with WebSphere Studio Application Developer Integration Edition version 5.0 or earlier are deprecated.

Recommended migration action:

Use the Migrate option provided with WebSphere Studio Application Developer Integration Edition version 5.1 to migrate business process to a BPEL-related process.

Several Business Process Choreographer API interfaces and methods used for business processes created with WebSphere Studio Application Developer Integration Edition version 5.0 or earlier.

Recommended migration action:

Refer to the Javadoc provided with Business Process Choreographer for a detailed list of these API interfaces and methods.

Application programming model and container support features
Business Rule Bean programming interfaces that include the following public classes, methods, and attributes are deprecated:
  • Public classes:
    • com.ibm.websphere.brb.RuleImporter
    • com.ibm.websphere.brb.RuleExporter
  • Public method:
    • getLocalRuleManager() on class com.ibm.websphere.brb.TriggerPoint
  • Protected attribute:
    • ruleMgr on class com.ibm.websphere.brb.TriggerPoint

Recommended migration action:

No action is required.

The com.ibm.websphere.scheduler class programming interface scheduler.Scheduler methods are deprecated:
  • public BeanTaskInfo createBeanTaskInfo();
  • public MessageTaskInfo createMessageTaskInfo();

Recommended migration action:

Use the following methods:

  • public Object createTaskInfo(Class taskInfoInterface) throws TaskInfoInvalid;
  • BeanTaskInfo ti = (BeanTaskInfo) Scheduler.createTaskInfo(BeanTaskInfo.class);
The Web Services gateway customization API is deprecated.

Recommended migration action:

No action is required. However, where possible, use the Java API for XML-based Remote Procedure Call (JAX-RPC) handlers rather than Web Services gateway-specific interfaces, such as filters. The Web Services gateway API will be replaced in a future release. For more information, see the topic 'JAX-RPC handlers - An alternative to gateway filters' in the WebSphere Business Integration Server Foundation information center.

Deprecated features in WebSphere Application Server Enterprise Edition version 5.0.2

Application programming model and container support features
The com.ibm.websphere.scheduler class interface scheduler.MessageTaskInfo is deprecated
  • public int setJMSPriority();

Recommended migration action:

Use the following method instead of the deprecated method:
  • public int getJMSPriority();

Deprecated features in WebSphere Application Server Enterprise Edition version 5.0.1

WebSphere Application Server Enterprise Edition version 5.0.1 has no deprecated features.

Deprecated features in WebSphere Application Server Enterprise Edition version 5.0

WebSphere Application Server Enterprise Edition version 5.0 has no deprecated features.

Last updated: Thu 02 Nov 2006 03:41:28

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)