Post-Installation Procedures 

There are a number of post-installation procedures to perform if want to use certain features on the J2EE Engine as listed below:

·        Deploying the SAP Java Cryptographic Toolkit

The SAP Java Cryptographic Toolkit is necessary if you want to use encryption functions with the J2EE Engine. Therefore, perform this procedure if you want to use any of the following security features on the J2EE Engine:

¡        Secure Sockets Layer (SSL) protocol for securing HTTP connections

¡        Secure storage in the file system to encrypt the data used to connect to the database or to encrypt the password for the user Administrator.

¡        Secure storage in the database to encrypt application-specific data.

·        Activating Secure Storage in the File System

Use this procedure to activate secure storage in the file system.

·        Creating a second administrator user

To prevent locking the administrator in case you do change its password and forget to update the entry secure storage, we also recommend you create a second administrator user after installing the J2EE Engine.

·        Add-In installation only: Specifying the J2EE Engine Client to Use for Logon Tickets

Single Sign-On using logon tickets requires a client from the ticket-issuing system. For this purpose, the J2EE Engine uses the client 000 per default. However, the system ID and client combination must be unique when tickets are to be accepted by an SAP Web AS ABAP system. Therefore, in an Add-In installation, you have to change the default client (000) to a client that does not exist on the SAP Web AS ABAP system.

See also:

Using SSL and SNC for Transport Layer Security

Secure Storage for Application-Specific Data