Redirect Port 50000 to Http Again for Sap Nwa
Purpose:
The purpose of this page is to enable you lot to resolve errors which occur when logging in to the Process Integration (PI) Enterprise Services Repository (ESR) or Integration Builder tools.
Overview:
I volition certificate 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 organization bug preventing logon.
Groundwork:
To be able to launch the Integration Builder tools on a client pc, Java Web Start must first exist installed. The Java Spider web Starting time software allows you to download and run Java applications from the web. Java Web Kickoff provides the runtime environment required for the Integration Builder to run. Coffee Web Outset is automatically started when you lot click on the Integration Builder links.
Basic checks:
- Ensure the XIREPUSER/PIREPUSER/PIREP<SID> and XIDIRUSER/PIDIRUSER/PIDIR<SID> users are non locked and that they have the required authorizations. You tin do this in transaction SU01 or in the Java UME.
- Bank check for whatever Repository/Directory related locks. Go to http://<server>:<port>/dir/get-go/index.jsp
-> Administration
-> Repository/Directory (tab)
-> Lock Overview - Ensure that the Repository and Directory services are started in the Visual Ambassador or the NetWeaver Administrator (see table below for details on where to check this). The services are:
- com.sap.xi.repository
- com.sap.eleven.directory
- com.sap.xi.ib.resources
| XI iii.0/PI vii.0x | PI 7.1x | PI 7.3x |
| Go to Visual Administrator | Go to http://<server>:<port>/nwa | Get to http://<server>:<port>/nwa |
Supported Java Web Start Versions:
SAP have recently released Note 2073368 Compatibility matrix: recommended Java version for Integration Builder tools of SAP Process Integration. The Coffee one.7_u65 is at present tested and supported with the PI releases and SP'southward below:
Java 7 update 65 both 32 scrap and 64 fleck is uniform with:
-
SAP PI 7.01 >= SP15
- SAP PI 7.02 >= SP15
- SAP PI 7.x >= SP18
- SAP PI 7.11 >= SP13
- SAP PI 7.3 >= SP12
- SAP PI seven.31 >= SP13
- SAP PI 7.iv >= SP08
If you are on an older PI release or SP, and then the information below still holds true.
The supported Java version depends on the version of PI yous are using. It is important that you are using the correct Java version to launch the Integration Builder on your customer pc, otherwise you may encounter bug logging on and/or problems when working with the Integration Builder objects.
| Eleven 3.0/PI 7.0x | PI 7.1x | PI 7.3x |
| Xi Server: | XI Server: | 11 Server: |
Working with dissimilar PI versions on aforementioned client pc:
If you have a requirement, for instance, to work with a PI 7.0 release and a PI seven.ane release you will demand to have the Java Web Start 1.4 version and the 1.5 (or higher) version installed on your client pc. You will need to disable the unsupported java version to launch the required Integration Builder. If y'all take two Coffee versions installed, you will accept two Java Command Panels. It is important to remember that you may need to enable/disable on both Coffee Control Panels. Run into Note 1614742 Using Java Web Beginning with different PI releases.
From the 1.4 Control Panel:
- Open the Java Web Starting time tool
- Become to Start -> All Programs -> Coffee Web Get-go
- Become to File -> Preferences -> Java
- Disable the unsupported java versions as required
From the 1.5 and higher Control Panel:
- Call the Java Command Panel from the Command Prompt (On Windows: Showtime -> Run -> cmd)
- Become to Java -> View and disable the version equally required
See the official Oracle site for more details on this:
Java Control Panel
-> Java Runtime Surroundings Settings
-> Example:
Caches:
When you lot encounter logon issues, it is advisable to articulate out the Java Web Start cache (client side) and the server side cache.
Client Side Cache:
- To clear the java web start cache in the ane.4 version, open the Java Spider web Start application and go to:
-> File
-> Preferences
-> Advanced
-> Articulate Binder - To clear the coffee cache in the versions higher than 1.4, open the DOS Command Prompt (On Windows go to Start -> Run -> cmd) and enter the command:
Javaws -viewer
This volition open up the Java Control Panel where yous can then delete the cache entries.
See Also:
-
How exercise I clear the Coffee cache?
-
The SAP KBA 2356069 Integration Builder: "Unable to launch the application", documents another method for clearing the client side enshroud
- 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
Server Side Enshroud:
To articulate the server side cache go to the PI start folio:
http://<server>:<port>/dir
-> Administration
-> Repository/Directory (tab)
-> Java Spider web Commencement Assistants
-> Restore Archives
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 organisation, are downloaded from the SAP Service Marketplace.
Whenever a signature outcome occurs, it is advisable to download the XI *.SCA's from the Service Market place and deploy these into the system to avoid the error.
Notwithstanding, in certain situations, signing errors practice occur and the pick provided in the 'Java Web Start Administration' page (documented beneath) is a workaround for those bug. Even though SAP advises to use workaround merely in the Examination systems, in some very critical situations, the workaround can be used in Product systems too.
After deleting the SAP signatures from the jars (using the processes beneath), the certificates will accept a dummy signature, which will enable the Integration Builder to launch successfully. To restore the original SAP signatures, you lot must deploy the Xi SCA'due south (freshly downloaded from the SAP Service Market place) once more.
To restore the Java Web Start archives at the client and to assign a new dummy primal to all archives:
| 11 3.0/PI 7.0x | PI 7.x | |
| http://:/dir/get-go/alphabetize.jsp (http://%3cserver%3e:%3cport%3e/dir/first/alphabetize.jsp) | http://:/dir/start/index.jsp (http://%3cserver%3e:%3cport%3e/dir/start/index.jsp) |
Notes relating to certificate changes (virtually contempo first):
NEW (22.07.2021): SAP Note 3082175 XI/PI:Jar Files are signed past dissimilar certificates in 2021 - this is the latest change to certificates.
SAP Note 2881268 Xi/PI:Jar Files are signed by different certificates in 2020
SAP Note 2507008 XI/PI:Jar Files are signed by unlike certificates in 2017
SAP Note 2104787 XI/PI:Jar Files are signed by dissimilar certificates in 2014 II
SAP Annotation 1981572 XI/PI:Jar Files are signed by different certificates in 2014 - changed in March 2014
SAP Note 1598282 11/PI:Jar Files are signed by unlike certificates in 2011
SAP Note 1640559 XI/PI:Jar files in JNLP aren't signed by aforementioned certificate
How to trace connectedness issues:
See the notes below for details on how you can activate client side tracing:
- 1891480 How to enable logging in Java WebStart console
- 912414 Activate client logging of Integration Builder tools
- Depending on the event the following traces may as well be useful:
- dev_icm
- dev_ms
- defaultTrace
Browser Issues:
Having a pop-up blocker switched on has been known to prevent the launch of the Integration Builder tools. Pop-ups must exist enabled in the browser to let the download of the jnlp file.
Some Known Issues:
- The Partner Connectivity Kit (PCK) is installed on the PI host machine. This is unsupported and is known to crusade issues with Integration Architect logons. To check if the PCK is installed become to the Component Info (run into SAP note 1381878 How/where to check the patch levels of your Eleven/PI organization). If necessary, you will need to uninstall the PCK software:
- For Xi iii.0/PI 7.0x: see the Eleven Troubleshooting Guide (SAP note 806546 XI Troubleshooting Guide).
- For PI seven.1x/PI 7.3x: see the SAP notation 1295094 Initialization of PI vii.1x to 7.30x XITOOLS fails
- If the client is located in a different network domain from the server (i.due east. the XI host) or the server uses multiple IP addresses logon issues tin can occur. Come across solutions in the notes:
- 609603 Bug with Multiple NICs and SAP J2EE Engine
- 1158626 P4 connection to ICM on machine with multiple IPs fails
- From fourth dimension to time SAP will change the certificates. This volition requrie an update of the relevant *.SCA's. See the notes beneath:
-
2104787 Xi/PI:Jar Files are signed past different certificates in 2014 Two
- 1981572 Xi/PI:Jar Files are signed by dissimilar certificates in 2014
- 1683776 Missing signatures in client jars in NW and CE seven.10 SP13
- 1598282 XI/PI:Jar Files are signed by dissimilar certificates in 2011
- 1595580 Missing signatures in client jars in NW 7.01 SP09
- 928887 NW04s:Jar Files signed past different certified keys
-
- If you get the following error when launching the IB tools: "Unable to launch application - com.sun.deploy.net.JARSigningException: Could not verify signing in resource: http://host:port/dir/directory/aii_ibdir_sbeans.jar" run into the SAP annotation 1764895 Java Spider web First cannot verify signed jar. This is applicative for vii.0x and lower releases.
- If you get a LAZY_CLASSLOADING_FAILED mistake when logging on see note 1883576 LAZY_CLASSLOADING_FAILED error opening PI Integration Builder tools.
- A new security related warning message when launching the Integration Architect tools when using Coffee one.vii.0_45. With Java release one.7.0_51, this alarm becomes an fault and prevents access to the Integration Builder. To resolve this, utilize the fixes in SAP Note 1959264 Coffee Applet Security Warnings for PI Dev Tools
-
Error: "Unable to launch the application" - Exception: InvalidArgumentException[ Invalid arguments supplied: { }
The InvalidArgumentException is a known issues from Oracle java - encounter https://bugs.openjdk.coffee.net/scan/JDK-8027818 The fix will be available publicly in JRE 7u60. The other releases which also contain the prepare (7u51 b32 and 7u55 b31) are bachelor, for customers with an Oracle support contract. Please refer to this note 1920326 Oracle JDK support agreement terminated, for more details. The workaround in note 1911069 Workaround for bug launching the PI tools with Java 7, may work for you (it does not work in all cases). - "Single Sign-On failed" error or "Authorization error; unknown user name or incorrect password" error when logging in. The solution is documented in SAP Note 2049621 Unable to login to PI ESR and Directory
- New bug (Q2 2016) with latest Java versions - run across SAP KBA 2316581 Unable to start PI ESR with Java one.eight.0_91 and 1.8.0_92
HTTPS related issues:
- SAP Note 1752259 ESR / Directory doesn't work via P4S protocol
- SAP KBA 2225603 Security alert when launching PI Integration Builder tools
- SAP KBA 2253896 InvalidKeyException: No installed provider supports this key when logging in to PI Integration Builder
- SAP KBA 2511283 The SSO of Integration Directory and Enterprise Services Repository do not work
Oracle have recently appear plans to remove the Java Web First option and their standalone JRE starting with the Java 11 release. Run into their data from Oracle Java SE Support Roadmap.
- SAP recommends to use JRE eight on the client systems if you wish to continue using swing based PI tools (ESR and IB) for all SAP NetWeaver releases >=vii.one
- For single stack usage, i.e., SAP Process Orchestration and Avant-garde Adapter Engine Extended, the SAP NetWeaver Developer Studio (NWDS) based tools can be used as an alternative to the Java Web Kickoff based PI tools.
See SAP Note 2677849 Update on usage of Java Web Showtime for swing based SAP Procedure Integration tools, for more details on this
Run into Too:
PI Troubleshooting Tips: Cannot connect to server using message server error when logging on to Integration Builder
Coffee 7 Webstart with SAP PI Integration Builder tools
New error when launching the PI Integration Builder tools
Alter in certificates used to launch Integration Builder
blountsieneat1998.blogspot.com
Source: https://wiki.scn.sap.com/wiki/display/XI/Troubleshooting+PI+ESR+and+Integration+Builder+Logon+Issues
0 Response to "Redirect Port 50000 to Http Again for Sap Nwa"
Post a Comment