Show TOC

Procedure documentationConfiguring the SLD Client Locate this document in the navigation structure

 

The SLD service provides every J2EE application with the option of generating a CIM client for accessing an SLD server. The CIM client is common for all applications that are using it and therefore plays the role of a standard SLD. Changing the data for the CIM client may have an effect on many applications. We recommend that you consider it carefully.

The generation process is subject to a security check that is not based on the user that started the application (user-based security), but on the Java software archive that was used for deploying the application on the J2EE Engine (code-based security). This procedure explains how to configure this process.

Prerequisites

  • You are logged on to the Visual Administrator of the J2EE Engine as an administrator.

  • In the Visual Administrator, on the   Cluster   Server   Services   Security Provider   Properties   tab page, you have set the SynchPermissionsWithDatabase property to true.

Procedure

  1. In the Visual Administrator, choose   Cluster   Server   Services   SLD Data Supplier   Runtime   CIM Client Generation Settings  .

    A list of archives of all J2EE applications is displayed.

  2. Enter the following data for generating the CIM client:

    1. In the Host field, enter the name of the host where the SLD runs.

    2. In the Port (http/https) field, specify the port of the SLD.

    3. In the User field, specify a J2EE user. This user must be assigned to the LcrInstanceWriterLD role. The J2EE user must be specific for this J2EE Engine and must not be used on another J2EE Engine.

    4. In the Password field, enter the user password.

      Note Note

      The generated CIM client can use both HTTP and HTTPS as a communication protocol.

      If you want to use HTTPS, select the Use HTTPS? indicator. In the Port field, you must also specify the HTTPS port of your destination.

      The Trust Store field is enabled. A trust store contains the root certificates of the trusted roots and checks the authentication of a received server certificate. The default setting for the trust store is TrustedCAs. If necessary, you can change this setting. For a list of available trust stores, choose   Cluster   Server   Services   Key Storage   Runtime   Views  .

      End of the note.

      Note Note

      Both the sending and the receiving J2EE Engines must be configured for Secure Socket Layer (SSL) connections before you can use HTTPS. For more information, see Configuring the Use of SSL on the J2EE Engine.

      End of the note.

  3. Save your entries.