Reconfiguring Public-key certificates

This article shows the procedure to re-configure public key certificates post refresh/migrations

Procedure:

Run Netweaver administrator and go to configuration management --> Security tab and select Certificates and Keys

Select the TicketKeystore entry and delete the SAPLogonTicketKeypair and SAPLogonTicketKeypair-cert entries in "Key Storage view details" section at rock bottom of the page


Create a brand new Key pair and Public Key certificate

Click Create


Enter the following information

Entry Name: SAPLogonTicketKeypair

Algorithm: DSA

Key Length: 1024

Store Certificate: Ensure checked


Click next and enter

countryName: DE

organizationalUnitName: J2EE

comonName: 


Click Next


Click Finish

Export the certificate:

Select the SAPLogonTicketKeypair-cert entry and click export entry


Click on the download link


Click save (and save it to a local file)

Import certificate:

Login to SAP system and run transaction STRUST.

Import the certificate just exported (Menu path Certificate --> Import). Make sure that the file format is that the same as that wont to export the certificate


Click on Add to Certificate list.


Your public key is ready now

Restore the JAVA system connections and destinations as PI refresh post action

This procedure is one among the post refresh action of SAP PI/PO system.
It explains on the way to restore the Java system connections (JCO) and destinations post refresh.

Run the NWA and access “Jco RFC Destinations” (Menu path à Configuration Management--> Connectivity--> Jco RFC provider).

For every connection, set the configuration details from details taken before;

Delete all the Jco connections for the <SOURCE_PI> System (*_<SOURCE_SID>), replacing them with connections for <TARGET_PI>.

Access “SLD Data Supplier Destinations” (Netweaver admin: Configuration Management--&gt;Connectivity--&gt;Destinations). 

Update all connections with the data saved prior to the refresh.  Use the ping option to test each connection

Check the connections in the ABAP engine using transaction SMGW (Goto --&gt; Logged on Clients)

All connections should be for <TARGET_SID>

Java (Channel/Thread) Lock Administration in PI/PO

SAP PI/PO contains numerous communication channels thorough which they process the messages between SAP to SAP and SAP to Non-SAP systems also.
Sometimes these channels are going to be locked thanks to several reasons which require to be fixed to permit the PI system work perfectly.
Follow below procedure to fix the issue.

Login to nwa portal with below link .

http://:500/nwa

Login using your valid and authorized credentials

Select Locks option (left side bottom option).
It shows the screen with "java Locks".

Open another browser tab navigating to nwa home as shown below
(http://:500/nwa)

Here you'll search with a lock argument if channel name isn't provided or if you've got channel name you'll look for lock argument using search term as “lock”

Match the lock argument within the Java locks screens.
Get confirmation from user and proceed as shown below for releasing locks
You can see Remove lock option if you decide on just one lock entry.

If you decide on quite one lock entry you'll be ready to see Remove all selected Locks tab to release all the chosen lock entries at a time.

Removing single lock entry.
Removing multiple lock entries

It asks for confirmation and then click yes if you want to release the lock.