Symptom/Problem/Error:
When the below command is executed from Application Service Unix
Box, the error is returned:
Command:
ant -f
$JAVA_TOP/oracle/apps/fnd/isg/ant/isgDesigner.xml
-Dactions="undeploy" -DserviceType=REST
-DirepNames="FND_WEB_SEC"
Result/Error:
[java] Invoking undeploy method on class Id : 2365...
[java] oracle.apps.fnd.isg.mgmt.common.error.ISGManagementException:
Wrong AdminUserName or/and AdminUserPassword or/and Server not reachable or/and
Unknown jmxUrl
Cause:
Incomplete or incorrect ISG Setup.
Solution:
To implement the solution test the following steps in a development
instance and then migrate accordingly:
Step 1. Reset the ASADMIN password:
1. Check that the permission of isgagent.zip are set to 777
2. Follow Oracle Metalink Note 1311068.1, "Section 3: Enabling ASADMIN User
with the Integration Administrator Role"
3. On the Web Logic Server, Log into the WebLogic Server Administration
Console. This will require special login link to the console. The user details are different from database. Contact Admin for access details.
a. Expand Service -> Data Source -> Select the link of the
correct Data Source.
b. Configuration -> Connection Pool
c. Check inside the Properties box:
- The 'User's property
would normally be set to 'ASADMIN' e.g. user=ASADMIN
- There should be dbcFile defined
e.g. dbcFile=/<directory path>/<dbc file name>.dbc .
Make sure the <path> and <file name> are absolute, present in the middle tier and has access permissions.
- If the password of the
user provided here has been changed on the EBS Side, then update the password
parameter with the new(same) password and confirm password.
d. Restart the Data Source if any of the above was updated.
4. Also in Web Logic Server (WLS) complete the following steps:
a. Navigate to bifoundation_domain - Services - Security Realms.
b. Select myrealm.
c. Select User Lockout tab.
d. Disable Lockout Enabled option.
e. Save
5. Use the below SQL statement to check whether ASADMIN user exists
in fnd_vault or not. If the user exists in fnd_vault then this statement will
return its password, otherwise it will return nothing.
select FND_VAULT.get('ISG', 'ASADMIN') from
dual;
If the user does not exist, add it using the following statement:
SQL> @$FND_TOP/sql/afvltput.sql FND ASADMIN <ASADMIN_PASSWORD>
Step 2. Undeploy the web service, then retest the configuration steps
from section 6.2 and confirm the complete without error.
Keywords:
Oracle EBS, SOAP, REST, isgDesigner.xml, ant, ISGManagementException, AdminUserName, AdminUserPassword,
ASADMIN, Web Service, R12, R12.2.8, ISG, Integrated SOA Gateway
