5 Troubleshooting

This chapter contains the following sections:

• Troubleshooting

• Guidelines on Using the Connector

5.1 Troubleshooting

Table 5-1 lists solutions to some commonly encountered issues associated with the connector.

Table 5-1 Troubleshooting

Problem Description	Solution
Oracle Identity Manager cannot establish a connection to the IBM OS/400 Server.	Ensure that the IBM OS/400 server is up and running. Check that the necessary ports are working. View the LDAP Gateway logs to determine if messages are being sent or received. Examine the Oracle Identity Manager configuration to verify that the IP address, admin ID, and admin password are correct. Check with IBM OS/400 platform manager to verify that OS/400 user account and password have not been changed.
OS/400 does not appear to respond.	Ensure that the Oracle Identity Manager mappings are correct. Check the configuration mappings for the Advanced Adapter Gateway.
A particular use case does not appear to be functioning.	Check for the use case event in question on the LDAP Gateway Server Log. Then check for the event in the specific log assigned to that Advanced Connector. If the event does not register in either of these two logs, investigate the connection between Oracle Identity Manager and the Advanced Connector Gateway. If the event is in the log but the command has not had the intended change on an OS/400 user profile, check for configuration and connections between the LDAP Gateway and IBM OS/400.

5.2 Guidelines on Using the Connector

Apply the following guidelines while using the IBM OS/400 Advanced connector:

• The connector can accept and transmit any non-ASCII data to the mainframe, but the mainframe does not accept non-ASCII characters. As a result, any task that requires non-ASCII data transfer fails. In addition, there is no provision in the connector to indicate that the task has failed or that an error has occurred on the mainframe. You must exercise caution when providing non-ASCII data to the connector.

• Passwords used on the mainframe must conform to stringent rules related to passwords on mainframes. These passwords are also subject to restrictions imposed by corporate policies and rules about mainframe passwords.

• If you configure the connector for trusted source reconciliation and set the idfTrusted property in the initialAs400Adv.properties file to true in one of the target system installations on the mainframe, then it must be set to true in all installations that connect to the same LDAP Gateway. Otherwise, the connector will fail. This applies only to a configuration in which a single LDAP Gateway connects to multiple installations of the target system.

• When using any version of IBM OS/400 earlier than 5.4, the Reset Password function for real-time reconciliation is not used. Instead, you can use the User Change Password function.

• The reconciled data may look different than the provisioning data for the following fields:

  • Initial Program (INLPGM)

  • Initial Menu (INLMNU)

  • Job Description (JOBD)

  The reconciliation data displays the expanded value including the entire path, such as /QSYS.LIB/%LIBL%.LIB/MAIN.MNU, and the provisioning data displayed is LIBL/MAIN.