Deployment of BPEL processes to SOA Suite fails after upgrade to 10.1.3.4
If you apply patch 10.1.3.4 to Oracle SOA Suite and use OID as security provider then you might run into the following problem when deploying your BPEL processes from JDeveloper or custom Ant scripts:
A problem occured while connecting to server [host] using port [port]: java.security.AccessControlException: access denied (com.collaxa.security.DomainPermission [domain] read)
If this is the case then open Enterprise Manager and check that the deploy_service application (which is a child application of orabpel and new in SOA Suite 10.1.3.4) is configured to use OID as security provider instead of file-based JAZN. Restart SOA Suite and deployment should work.
Leave comment
Comments: (1)
Loading ...Blogs
- 26 Jul
- 10 Jun
- 02 Jun
- 26 Mar
- 25 Feb
-
05 Nov
Some tips & tricks on migrating SOA Suite 10g to 11g – Part 2
- 04 Nov
- 02 Nov
- 25 Oct
- 20 Oct
- Best practices 2 - Web Services
- Fault handling in Oracle SOA Suite 11g - Part II
- Fault handling in Oracle SOA Suite 11g
- Experiences with Vista and Oracle software (2)
- Migrating Web Services from JDeveloper 10g to 11g
- Migrating EJB 3 applications from OC4J to WebLogic
- Best practices for BPM, SOA and EDA
- Some tips & tricks on migrating SOA Suite 10g to 11g - Part 2
- Logging messages in Oracle SOA Suite 11g using OWSM
Sometimes is then still does not work. have a look at the orion-application.xml in the application-deployment directory of the deploy-services.
make sure the jaas-mode exists. The line should be: <jazn provider=”LDAP” jaas-mode=”doAsPrivileged”/>.
Regards, Edward