7.3 Preparing the WebLogic Environment

7.3.1 Configure the Connection Pool

  • Copy your database driver JAR files to the domain where you will deploy the User Application.

  • Copy antlr-2.7.6.jar and log4j.jar from the User Application install directory to the domain lib folder (for example, c:\bea\user_projects\domains\idm\lib\). Also copy commons-logging.jar from the c:\bea\tools\eclipse folder to the domain lib folder.

  • Create your datasource.

    Follow the instructions for creating a datasource in the WebLogic documentation.

    Note that the JNDI name for the datasource must jdbc/IDMUADataSource, regardless of what name you specified for the datasource or for the database when you created the User Application WAR.

7.3.2 Specify RBPM Configuration File Locations

The WebLogic user application needs to know how to locate the sys-configuration-xmldata.xml file and the idmuserapp_logging.xml file. You can do so by adding the location of the files to the setDomainEnv.cmd file.

To make them available to the application server, specify its location in the setDomainEnv.cmd or setDomainEnv.sh file:

  1. Open setDomainEnv.cmd or setDomainEnv.sh file.

  2. Locate the line that looks like this:

  3. Below the JAVA_PROPERTIES entry, add entries for:

    • -Dextend.local.config.dir==<directory-path>: Specify the folder (not the file itself) that contains the sys-configuration.xml file.

    • -Didmuserapp.logging.config.dir==<directory-path>: Specify the folder (not the file itself) that contains the idmuserapp_logging.xml file.

    For example on Windows:

    set JAVA_OPTIONS=-Dextend.local.config.dir=c:\novell\idm
    set JAVA_OPTIONS=%JAVA_OPTIONS% -Didmuserapp.logging.config.dir=c:\novell\idm
  4. Set the environment variable EXT_PRE_CLASSPATH to point to the antlr.jar, as well as the log4j.jar and the commons-logging.jar.

    1. Locate this line:

    2. Add the EXT_PRE_CLASSPATH below it. For example, on Windows:

      set EXT_PRE_CLASSPATH=C:\bea\user_projects\domains\base_domain\lib\antlr-2.7.6.jar;C:\bea\user_projects\domain\base_domain\lib\log4j.jar;C:\bea\user_projects\domains\base_domain\lib\commons-logging.jar

      For example, on Linux:

      export EXT_PRE_CLASSPATH=/opt/bea/user_projects/domains/base_domain/lib/antlr-2.7.6.jar;C:\bea\user_projects\domain\base_domain\lib\log4j.jar;C:\bea\user_projects\domains\base_domain\lib\commons-logging.jar
  5. Save and exit the file.

The XML files are also used by the configured utility; therefore, you need to edit the configupdate.bat or configupdate.sh files as follows:

  1. Open configupdate.bat or configupdate.sh.

  2. Locate the following line:

    -Duser.language=en -Duser.region="
  3. Update the existing line to include:

  4. Save and close the file.

  5. Run the configupdate utility to install the certificate into the keystore of the JDK under BEA_HOME.

    When you run configupdate, you are prompted for the cacerts file under the JDK you are using. If you are not using that same JDK that was specified during the installation you must run configupdate on the WAR. Pay attention to the JDK specified because this entry must point to the JDK used by WebLogic. This is done to import a certificate file for the connection to the Identity Vault. The purpose for this is to import a certificate for the connection to eDirectory.

    The Identity Vault Certificates value in the configupdate utility must point to the following location:


7.3.3 Workflow Plug-In and WebLogic Setup

The Workflow Administration plug-in to iManager is unable to connect to the User Application Driver running on WebLogic if the enforce-valid-basic-auth-credentials flag is set to true. For this connection to succeed, you must disable this flag.

To disable the enforce-valid-basic-auth-credentials flag, follow these instructions:

  1. Open the config.xml file in the <WLHome>\user_projects\domains\idm\config\ folder.

  2. Add the following line in the <security-configuration> section:

  3. Save the file and restart the server.

After making this change, you should be able to login to the Workflow Administration plug-in.