Connection Points

Connection points replace the router process that is used in previous releases, connecting the Process Java™ API to an associated isolated region. Connection points are defined in the Content Engine API (the PEConnectionPoint and IsolatedRegion classes) and persisted in the Global Configuration Data (GCD) on the Content Platform Engine server. Multiple connection points can reference the same isolated region. The set of connection points that are defined is reflected in the Content Platform Engine Domain.PEConnectionPoints property. To create and manage connection points, use the Administration Console for Content Platform Engine.

To establish or log on to a workflow system session, a connection point must be specified and the Content Platform Engine host must be accessible.

Setting the Content Platform Engine URI

The Content Platform Engine host URI must be set prior to creating or logging on to a session (by calling the VWSession constructors or logon methods).

You can specify the Content Platform Engine URI in any of the following ways:

• Call VWSession.setBootstrapCEURI to specify the URI as a String.
• Specify the value of the system property filenet.pe.bootstrap.ceuri. For example, you might start your application with the -D JVM parameter as illustrated in the following example:

  
     -Dfilenet.pe.bootstrap.ceuri=t3://hqruby:7001/FileNet/Engine
  

• Call VWSession.setBootstrapConfiguration to specify the URI as an InputStream.
• Specify the value of the "RemoteServerUrl" property in a file that is named WCMApiConfig.properties, which is located in your application's class path. The format for this property is:

  
   RemoteServerUrl=cemp:ContentPlatformEngineURI
  

  Where ContentPlatformEngineURI is the URI of the Content Platform Engine (for example, t3://server:7001/FileNet/Engine).