Chem XML Message eStandards and CIDX Scenario Part III

http://scn.sap.com/people/suraj.pabbathi/blog/2011/08/15/chem-xml-message-estandards-and-cidx-scenario-part-iii

In my earlier blogs efforts are made to explain about CIDX standards, how to design and configure the object to support CIDX communication. [Blog1 | Chem XML Message eStandards and CIDX Scenario – Part I] [Blog2 | Chem XML Message eStandards and CIDX Scenario development – Part II] I would like to make your experience pleasant and fruitful with CIDX communication through this blog. This blog covers those intricate details in regard to security, certificates through simple steps, focusing on PI 7.1 You have already selected CIDX adapter with Transport Protocol as “HTTPS” and Message Protocol as “RNIF 1.1” for communication. Selecting the message protocol to RNIF 1.1 means you are configuring the scenario to handle Preamble, Service Header, Service Content, Digital Signatures etc… We will focus on achieving HTTPS communication which is a combination of HTTP with SSL/TLS protocol to provide encrypted communication and secure identification of a network web server.  *Step 1:* Since the CIDX adapter is available through adapter engine, you need to set your server through Java stack to receive and send secured messages.*Step 2:* Restart the server to notice automatic creation of Keystore views in SAP NetWeaver Administration (NWA).*Step 3:* Load the public key of your partner with entire certificate chain (Public Key, Intermediate and Root) into keystore Views “ICM_SSL_XXXX”, Trusted CAs.  In the following screenshot, you can view Verisign as Certificate Authority and chain of certificates. They can be recognized as Verisign as root, Verisign Class 3 Secure Server CA – G3 as intermediate and business.partner.com as public key.