Professional Documents
Culture Documents
Community WIKI SAP Community Welcome, Guest Login Register Search the Community
Process Integration / Process Orchestration - Process Integration - Exchange Infrastructure / Troubleshooting Main Page
Purpose:
The purpose of this page is to enable you to resolve errors which occur when logging in to the Process Integration (PI) Enterprise Services Repository (ESR) or Integration Builder tools.
Overview:
I will document the solutions to some of the known errors which occur when logging on to the PI Integration Builder tools and some checks you should make to ensure there are no system issues
preventing logon.
Background:
To be able to launch the Integration Builder tools on a client pc, Java Web Start must first be installed. The Java Web Start software allows you to download and run Java applications from the web. Java
Web Start provides the runtime environment required for the Integration Builder to run. Java Web Start is automatically started when you click on the Integration Builder links.
Basic checks:
1. Ensure the XIREPUSER/PIREPUSER/PIREP<SID> and XIDIRUSER/PIDIRUSER/PIDIR<SID> users are not locked and that they have the required authorizations. You can do this in transaction
SU01 or in the Java UME.
2. Check for any Repository/Directory related locks. Go to http://<server>:<port>/dir/start/index.jsp
-> Administration
-> Repository/Directory (tab)
-> Lock Overview
3. Ensure that the Repository and Directory services are started in the Visual Administrator or the NetWeaver Administrator (see table below for details on where to check this). The services are:
a. com.sap.xi.repository
b. com.sap.xi.directory
c. com.sap.xi.ib.resources
If you are on an older PI release or SP, then the information below still holds true.
The supported Java version depends on the version of PI you are using. It is important that you are using the correct Java version to launch the Integration Builder on your client pc, otherwise you may
encounter problems logging on and/or problems when working with the Integration Builder objects.
1. Call the Java Control Panel from the Command Prompt (On Windows: Start -> Run -> cmd)
2. Go to Java -> View and disable the version as required
Caches:
When you encounter logon issues, it is advisable to clear out the Java Web Start cache (client side) and the server side cache.
Javaws -viewer
This will open the Java Control Panel where you can then delete the cache entries.
See Also:
How do I clear the Java cache?
The SAP KBA 2356069 Integration Builder: "Unable to launch the application", documents another method for clearing the client side cache
The SAP KBA 2390426 Unable to open PI ESR or Integration Builder, documents a method for clearing server side files used during the launch of the tool
Certificates:
SAP signs the client software (jars) required for the XI Integration Builder logon. This client software includes parts of the J2EE client software. Ideally jar signature issues should not occur if the XI
*.SCA's, deployed into the system, are downloaded from the SAP Service Marketplace.
Whenever a signature issue occurs, it is advisable to download the XI *.SCA’s from the Service Marketplace and deploy these into the system to avoid the error.
However, in certain situations, signing errors do occur and the option provided in the 'Java Web Start Administration' page (documented below) is a workaround for those issues. Even though SAP advises
to use workaround only in the Test systems, in some very critical situations, the workaround can be used in Production systems as well.
After deleting the SAP signatures from the jars (using the processes below), the certificates will have a dummy signature, which will enable the Integration Builder to launch successfully. To restore the
original SAP signatures, you must deploy the XI SCA’s (freshly downloaded from the SAP Service Marketplace) again.
To restore the Java Web Start archives at the client and to assign a new dummy key to all archives:
Browser Issues:
Having a pop-up blocker switched on has been known to prevent the launch of the Integration Builder tools. Pop-ups must be enabled in the browser to allow the download of the jnlp file.
1. SAP Note 1752259 ESR / Directory doesn't work via P4S protocol
2. SAP KBA 2225603 Security warning when launching PI Integration Builder tools
3. SAP KBA 2253896 InvalidKeyException: No installed provider supports this key when logging in to PI Integration Builder
4. SAP KBA 2511283 The SSO of Integration Directory and Enterprise Services Repository do not work
SAP recommends to use JRE 8 on the client systems if you wish to continue using swing based PI tools (ESR and IB) for all SAP NetWeaver releases >=7.1
For single stack usage, i.e., SAP Process Orchestration and Advanced Adapter Engine Extended, the SAP NetWeaver Developer Studio (NWDS) based tools can be used as an alternative to the Java
Web Start based PI tools.
See SAP Note 2677849 Update on usage of Java Web Start for swing based SAP Process Integration tools, for more details on this
See Also:
PI Troubleshooting Tips: Cannot connect to server using message server error when logging on to Integration Builder