Saturday, 24 March 2012

The Transaction Manager based on Oracle BPEL Process Manager - installation

Following are the requirements, assumptions and actions needed to install the Transaction Manager based on Oracle BPEL Process Manager.


  1. Oracle BPEL Process Manager,
  2. JDeveloper - used when the business processes are installed,
  3. The Transaction Commiter - there is known URL at which it is/will be available.
  4. The Concurrency Control Module (optionally) - there is known URL at which it is/will be available
List of software that is used, with their Web pages is presented at Hardware and software requirements.

Installation steps

Installation of Transaction Manager based on Oracle BPEL Process Manager:
  1. First, installation file must be downloaded and unzipped.
  2. Then, project located in the file:Example1 directory must be imported to JDeveloper
Example1 project
Example1 project
  1. This project includes BPEL processes which initiate TC and CCM transactions. These processes should not be modified.
  2. The third BPEL process is an example that illustrates how transactional extensions can be used in the BPEL process. On the basis of this process, you can create your own BPEL process which will use the extensions in the imported project.
  3. At the end, it is necessary to modify the settings in the configuration file in the library: Example1/Example/SCA-INF/lib/mzt1.0.jar. This modification is described below, in the Configuration section.


Uninstallation can be done by removing all components of the project related to the Transaction Manager. This will probably be a significant part of the project, therefore, we propose to delete the entire project and save your own processes, or other important files.


Project can function as the Transaction Manager if it is configured correctly. Configuration consists in entering the appropriate addresses in the configuration file. These addresses are used during communication performed by extensions. Configuration file configuration.conf there is in the archive: Example1/Example/SCA-INF/lib/mzt1.0.jar. In this file, an entries that relate addresses of coordinators (TC and CCM) and initiators (which initiate transactions coordinated by TC and CCM), installed in the BProCORE environment should be updated. The addresses of the coordinators should be known after their installation. After the first deployment of the project is possible to verify the addresses of the initiators. These initiators are the business processes MZTInitiator and TFPInitiator.
The sample configuration is as follows:
Assume that MATaddr is address of the Transaction Commiter and MATport is port on which TC is listening, and that MZWDaddr is address of the Concurrency Control Module and MZWDport is port on which CCM is listening.
Then, after a standard installation of these modules, a sample configuration is as follows:
Individual parameters in the configuration file have the following meaning:
Address of TC activation service.
The standard type of coordination (not modify this value).
Address of the protocol service of Enhanced2PC, used by the participant of transactions. This service is used for nested transactions.
Address of CCM activation service.
Address of the protocol service of Enhanced2PC, used by the initiator of TC transactions after deployment on Oracle BPEL Process Manager (MZTInitiator business process),
Address of the protocol service of TransactionFinallizationProtocol, used by the initiator of CCM transactions after deployment on Oracle BPEL Process Manager (TFPInitiator business process).

1 comment:

  1. Thank You

    The given information is very effective
    i will keep updated with the same

    industrial automation