Describes some settings and procedures to check if you encounter
problems running the adapter.
If you are unable to connect to the PeopleSoft EIS
using the enterprise metadata discovery component or the adapter, make sure
of the following:
- The psjoa and component interface jar files have been added to classpath.
- Valid values have been entered for Username, Password, serverName, and
PortNumber.
- The PeopleSoft application server is running.
If you encounter problems when using the enterprise metadata discovery
component, make sure of the following:
- You have selected the Use Discovered Connection Properties option
within the enterprise service discovery wizard.
- You have specified a valid language value for the configured PeopleSoft
instance.
- You have specified the authentication alias that will be used during deployment.
If you encounter problems when creating the EAR file, try the
following:
- Make sure there are no validation errors in WebSphere® Integration Developer
- Check the deployment descriptors for EJB projects on the module for entries
of JNDI names for Managed Connection Factory or ActivationSpec. If there are
errors, try rebuilding the workspace by selecting Project > Clean
option, or try closing and opening WebSphere Integration Developer.
If you encounter problems at run time, make sure you have not
created multiple service descriptions within the same Business Integration
module that contain the same business object names and targetNameSpace definitions.
If you need to use more than one service description, use a common set of
business objects for both; do not save each description to a different location
using the BO Location field in the enterprise metadata discovery component.
If the services are saved to different business objects, there is no mechanism
at run time to define which business object definitions are for which service
descriptions.