Overview of the Java Service Connector

The Java Service Connector enables a client application to access the BPM runtime services that are hosted in a TIBCO ActiveMatrix container.

Note: The documentation sometimes refers to the Java Service Connector as Service Connector and these two terms are used interchangeably.

A client application can communicate with the Java Service Connector using local Java calls.

The Java Service Connector takes the information from the Java call and:

  1. converts it to a SOAP request.
  2. adds security information to the SOAP header to identify the calling user.
  3. sends the SOAP request to the endpoint used by the appropriate service in the BPM runtime.

When the BPM runtime returns the SOAP response, the Service Connector unwraps the SOAP response envelop and converts it to a data object.

Data Handling

The Service Connector contains stubs and data bindings (XML Beans) that are generated from the public WSDLs that are provided with this guide.

The data bindings adhere to the public WSDL and XSD files provided. See TIBCO ActiveMatrix BPM Services for more information on the WSDL and XSD files.