Configuring WorkSpace Across Multiple Domains

You can deploy WorkSpace, or any PAPI application, in a separate domain than the domain where the Oracle BPM engine is running. This is often necessary in an environment where you want to physically isolate the WorkSpace application from the Process Execution Engine.

After you have configured your domain environment, you must perform the following additional configuration tasks:

  1. Create a JDBC Datasource. This datasource is used to connect to the directory database for the process execution engine. This datasource should be created on the domain where WorkSpace is deployed.
  2. Enable Domain Trust. To allow the WorkSpace application to communicate with the domain of the process execution engine, you must allow trust between the two domains.
  3. Create Foreign JNDI Provider. You must create and configure a foreign JNDI provider on the domain where the WorkSpace application is deployed.
    1. Launch the Oracle WebLogic Server Administration Console.
    2. Select Lock and Edit.
    3. Expand Services.
    4. Select Foreign JNDI Providers.
    5. Click New.
    6. Provide a name for the foreign JNDI provider, then clickOK.
    The new foreign JNDI provider appears in the list of available providers. You must configure the foreign JNDI provider and create links between domain resources as outline in the following task.
  4. Configure the Foreign JNDI Provider.
    1. Expand Services.
    2. Select Foreign JNDI Providers.
    3. Select the foreign JNDI provider created in the previous step.
    4. Click the Configuration tab, then click General
    5. Enter a value for the Initial Context Factory. This should be something like: weblogic.jndi.WLInitialContextFactory. The exact value depends on the JNDI provider and vendor you are using.
    6. Enter a value for the Provider URL. For example, t3://hostname: port
    7. Click Save.
    8. Click Links.
    9. Create the JNDI links. You must create the following four JNDI links:
      Local JNDI Name Remote JNDI Name
      /engines/ engine_name /engines/ engine_name
      /processes/engine-engine_name/EJBProcessControl /processes/engine-engine_name/EJBProcessControl
      XATopicConnectionFactory XATopicConnectionFactory
      topic/EngineNews topic/EngineNews
      Note: The value for engine_name corresponds to the process execution engine you are configuring. XATopicConnectionFactory and topic/EngineNews correspond to the value of the JMS topics defined in Process Administrator.