|Oracle® Fusion Middleware BPEL Component Guide for Content Server
11g Release 1 (11.1.1)
Part Number E16759-01
There are currently two ways to set up a content server to be able to integrate with SOA:
Scenario One involves installing UCM in a domain that has been extended by SOA. This involves installing all the bits and pieces into one domain in a particular order. The SOA libraries are available to all and the class path is augmented to contain the SOA libraries.
Scenario Two involves manually copying the required libraries used by SOA and augmenting the class path used to launch UCM inside of WLS.
The difference between the two scenarios is that the installation of SOA augments the class path for you, while in Scenario Two this is a manual step. In the future, UCM will ship with the appropriate SOA libraries.
Follow these steps:
Create a new domain for SOA.
Extend the SOA domain by BAM and EM.
Extend the SOA by UCM.
You may want to check that setDomainEnv has been populated with SOA-specific libraries. In particular, check that soa-infra-mgmt.jar is mentioned in the class path.
To update a UCM domain that has not been extended by SOA, follow these steps:
Copy the soa directory from the oracle home for SOA to the oracle home for UCM.
Locate the 11g SOA home directory for the SOA server you are connecting to via UCM. There should be a directory called 'soa.' Copy this directory to the UCM home directory and leave it in the top directory, that is, copy SOA_ORACLE_HOME/soa to UCM_ORACLE_HOME/soa.
Augment the class path for the UCM domain by editing the setDomanEnv.cmd or setDomainEnv.sh file, depending on your OS.
The final step for both scenarios is enabling the BpelIngetration component and starting the servers.
If your SOA instance is running in a separate server than UCM, you may see the following security error:
vax.xml.ws.WebServiceException: java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators] at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:209) at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:216)
If you encounter this error, you need to enable cross-domain security for both servers. Follow these instructions:
User will need to setup Trusted Domain on both WLS domain. Goto WLS Console->Respected Domainssoainfra or bam ->Security 1. Make sure "Cross Domain Security Enabled" 2. Click on Save 3. Expand Advanced part of setting 4. Make sure you supplement the Credential and Confirm Credential fields. 5. Click on Save Repeat for the same for the other WLS domain. Finally, Restart both WLS Servers.