We can export an EAR file and its configuration file of deployed application in Admin with AppManage command

AppManage -export -out c:\temp\SRIK.xml -genEar -ear c:\temp\Srik.ear -app root/folder1/ExampleApp -user <username> -pw <password> -domain <domain name>

The deployment configuration file and EAR file are created in the c:\temp folder. The application is embedded in root/folder1/, which is relative to the Application Management root in the TIBCO Administrator GUI.

We can export all applications EARs in an administration domain using the appManage -batchExport option.

Example, 
AppManage -batchExport -user <user name> -pw <password> -domain <domain name> -dir c:\temp\test


For training on TIBCO Administrator Information mail us at [email protected]

You can configure mediation flow components to route messages to endpoints that are determined dynamically at run time. When you create the mediation module, you configure the endpoint look up to use version-aware routing.

If you use the IBM_VRM style (<version>.<release>.<modification) for the snapshot, you can export the process application EAR file to WebSphere Service Registry and Repository (WSRR). When you create the mediation module, you then configure the endpoint lookup to use version-aware routing. For example, you select Return endpoint matching latest compatible version of SCA module-based services from the Match Policy field, and you select SCA for Binding Type.

Future versions of the process application are deployed to the server and published to WSRR, and the mediation module endpoint lookup dynamically invokes the latest compatible version of the service endpoint.

Note that, as an alternative, you can set the target in the SMO Header, and the value can be carried by the request message.



For training on IBM Lombardi mail us at [email protected]

Understand what products and capabilities IBM offers for business process management, and choose the right one for your enterprise.

IBM Business Process Manager is a single BPM platform that combines human-centric and integration-centric capabilities into a unified product. Different configurations of the product are available for different users, and satisfy different needs in the enterprise. Product configurations can be combined for collaborative authoring and network-deployed runtime environments.

IBM Business Process Manager configuration capabilities:

Business processes evolve over time. They need to reflect changing environments and business needs. These changes might be business-driven changes, such as changes in regulations, or optimizations of processes. Business-process applications can include long-running BPEL instances. These instances can run for weeks, months, or even years. This characteristic imposes specific requirements on the introduction of new versions of BPEL processes.

To create a new version of your BPEL process, you create a new version of a module in Integration Designer. Make the changes that you need to the new version of the process, give the new version a valid-from date if the process is not part of a process application or toolkit, and then deploy it to your runtime environment. If you want to enable the migration of existing process instances to the new version, you must also define a process migration specification in Integration Designer, and deploy it together with the new version of the process.

After the new version of the process is deployed, new process instances can be created from the new version of the BPEL process. Existing instances continue to complete using the version that they were created and started with, or depending on the nature of the changes to the process, they can be migrated to the new version. In some situations, for example, when you want to correct an error in the process, you might also want to migrate the running instances of a process to the newer version so that they complete using this version.

In process applications or toolkitsA BPEL process that is part of a process application or a toolkit is versioned through Process Center. In Process Center, BPEL processes are versioned as part of snapshots of the corresponding process application or toolkit. The following properties uniquely identify a process version on a deployment target.

• A process version that is part of the process application, or part of a toolkit that is referenced by a process application can be identified in one of the following ways:
  • Process application acronym, process application snapshot name, and process name
  • Process application snapshot ID and process name
• A process version that is part of a top-level toolkit (a top-level toolkit is not referenced by a process application), or part of a toolkit that is transitively referenced by the top-level toolkit can be identified in one of the following ways:
  • Top-level toolkit acronym, top-level toolkit snapshot name, and process name
  • Top-level toolkit snapshot ID, and process name

In enterprise applications that were generated in Integration DesignerA BPEL process that is deployed by exporting an enterprise application (EAR) file from Integration Designer, and installing it on a process server is versioned using time-based versioning. A process version is identified on a deployment target using the process name and the valid-from date, which is based on the valid-from property that was specified in Integration Designer.

• Invoking different versions of a BPEL process
  You can invoke a specific version of a process (early binding), or dynamically invoke the version of a process that is currently valid (late binding).
• Migrating running process instances to a new version of the BPEL process
  When you introduce a new version of a BPEL process, you might want this version to apply to both new process instances and to instances that have already started. This can be important in environments where changes to processes are needed frequently, but where an individual process instance can be relatively long-lived. In such cases you need to migrate the process instances that are running to the newer version.

For training on IBM Lombardi mail us at [email protected]