Configuring the AS Java for IIOP Security 

Use

So that you can use security for your RMI-IIOP applications, you need to provide an additional parameter for the Java Virtual Machine that can be used to initialize the AS Java’s ORB.

Prerequisites

You must have configured your AS Java to use SSL if you want to use SSL to encrypt IIOP messages.

Procedure

We assume you have stopped the AS Java to configure it for IIOP security, proceed as follows:

...

       1.      Start the offline configuration editor tool provided with your AS Java installation. Use the offlinecfgeditor script file located in the <SAP_install_dir>\<system_name>\<instance_name>\j2ee\configtool directory.

       2.      In the Configurations tree that appears on the screen, browse to the cluster_data  → Propertysheet instance.properties.ID<number>.

       3.      To switch the editor from view to edit mode, choose . Since you have stopped your AS Java, you can choose Yes when the Switch to Edit mode warning appears.

       4.      Select the Propertysheet instance.properties.ID<number> and choose  to open it for editing.

A Change Configuration screen appears.

       5.      In the name column, find the key ID<number>.JavaParameters that defines the parameters of the JVM in which the server instance runs.

You can locate the ID number of the server process by locating the property with name ID<number>.Name and value of server.

Select the ID<number>.JavaParameters field and a new Change property entry screen appears.

       6.      Enter the following parameter in the Custom: field:

-Dorg.omg.PortableInterceptor.ORBInitializerClass.
com.sap.engine.services.iiop.csiv2.interceptors.SecurityInitializer

       7.      Choose Apply custom to save your custom parameters. Then choose OK from the Change Configuration screen.

       8.      Exit the Config Tool.

       9.      Start your AS Java.

Result

The AS Java must now be appropriately initialized to support security for RMI-IIOP applications.