ConnectionException, ORABPEL-30504 and ORABPEL-10509: Errors Registering Soa Composite

(Doc ID 1447217.1)

Last updated on JULY 24, 2016

Applies to:

Identity Manager - Version 11.1.1.5.0 and later
Information in this document applies to any platform.
OIM 11.1.1.5.0
SOA 11.1.1.5.0

**Checked for Relevance on 13-Sep-2013**

Symptoms

SOA composite registration with OIM via fails with either one or both of the following errors depending upon how you installed OIM and SOA:

Issue 1: If installing SOA (ex: port 8001) and OIM  (ex: port 14000) 11.1.1.5.0 on one physical server (ex: server1.corp.com) and the Weblogic Admin server on another physical server (ex: port 7001 on server2.corp.com) then the registration of the SOA composites with OIM via ant will fail.

Exception in thread "main" oracle.iam.platform.workflowservice.exception.IAMWorkflowException: Tasklist mapping failed for workflowdefintion: default/ResourceApproval!1.0 due to javax.naming.CommunicationException (Root exception is java.net.ConnectionException: t3://server2.corp.com:8001/soa-infra: Destination unreachable; nested excpetion is:
java.net.ConnectionException: Connection refused; NO available router to destination]
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)


Issue 2: If using a user other than the default weblogic uesrname of "weblogic" then one may see a secondary failure.

===

Internal error in Verification Service for user Administrator. lookupUser.
Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

ORABPEL-30504

Internal error in Verification Service.
Internal error in Verification Service for user Administrator. lokupUser
Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Cuased by: ORABPEL-10509

User not found.
User "Administrator" is not found in configuration "jazn.com"
Check if the user exists in the repository specified by the configuration. Check the error stack and fix the cause of the error. Contact Oracle Support Services if error is not fixable.


===

Changes

In order to run into these issues one would have installed SOA/OIM on a different physical server than the WLS Admin server and not use the default weblogic username of "weblogic"

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms