Configuring the AS Java for IIOP Security

Use

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

Prerequisites

You have configured your AS Java to use SSL to encrypt IIOP messages.
Make sure your AS Java is stopped.

Procedure

Start the Config Tool by double-clicking the configtool script file in <SAP_install_dir>/<system_name>/<instance_name>/j2ee/configtool directory.
Choose cluster-data → <template_name> → <Instance_number>.
To switch to the configuration editor, choose .
To switch the editor from view to edit mode, choose .
A warning message appears. Choose Yes.
Choose Configurations → cluster_config → system → instances → Propertysheet_instance_<number>.
Select Propertysheet instance.properties.ID<number> and choose to open it for editing.
A Change Configuration screen appears.
In the name column, find ID<number>.JavaParameters. It defines the JVM parameters via which the Java instance runs.

Note

You can locate the ID number of the server process by locating the property with name ID<number>.Name and value of server.
Double-click the ID<number>.JavaParameters field.
A Change Property Entry screen appears.
In the Custom-value field, enter the following string:
-Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.iiop.csiv2.interceptors.SecurityInitializer
Choose Apply custom to save your custom parameters.
Choose OK in the Change Configuration screen.
Exit the Config Tool.
Start your AS Java.

Result

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