7.3 Preparing the WebLogic Environment

7.3.1 Configuring the Data Source

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

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

Note that the JNDI name for the datasource must be 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 Specifying RBPM Configuration File Locations

The WebLogic user application needs to know how to locate the sys-configuration-xmldata.xml file, the idmuserapp_logging.xml file, and the wl_idmuserapp_logging.xml file. Therefore, you need to add the location of the files to the setDomainEnv.cmd file.

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

Open setDomainEnv.cmd or setDomainEnv.sh file.

Locate the line that looks like this:

set JAVA_PROPERTIES

export JAVA_PROPERTIES

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.
- -Dlog.init.file==<file-name>: Specify the wl_idmuserapp_logging.xml file, which is used for log4j configuration. This file handles the appender and logger configurations required for the User Application in situations where multiple applications are installed on the same application server.
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
set JAVA_OPTIONS=%JAVA_OPTIONS%
-Dlog.init.file=wl_idmuserapp_logging.xml
```

Set the environment variable EXT_PRE_CLASSPATH to point to the following JAR files:

antlr-2.7.6.jar
IDMselector.jar
log4j.jar
commons-logging.jar

NOTE:You need to download this JAR file from the Apache site.
xalan.jar
xercesImpl.jar
xsltc.jar
serializer.jar

NOTE:An alternative approach to adding these JAR files to the EXT_PRE_CLASSPATH variable would be to copy these files into WEB-INF/lib directory within the IDMProv.war file.

Locate this line:
```
ADD EXTENSIONS TO CLASSPATH
```

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\domains\base_domain\lib\IDMselector.jar;C:\bea\user_projects\domain\base_domain\lib\log4j.jar;C:\bea\user_projects\domains\base_domain\lib\commons-logging.jar;C:\bea\user_projects\domains\base_domain\lib\xalan.jar;C:\bea\user_projects\domains\base_domain\lib\xercesImpl.jar;C:\bea\user_projects\domains\base_domain\lib\xsltc.jar;C:\bea\user_projects\domains\base_domain\lib\serializer.jar

For example, on Linux:

export EXT_PRE_CLASSPATH=/opt/bea/user_projects/domains/base_domain/lib/antlr-2.7.6.jar:/opt/bea/user_projects/domains/base_domain/lib/IDMselector.jar:/opt/bea/user_projects/domain/base_domain/lib/log4j.jar:/opt/bea/user_projects/domains/base_domain/lib/commons-logging.jar:/opt/bea/user_projects/domains/base_domain/lib/xalan.jar:/opt/bea/user_projects/domains/base_domain/lib/xercesImpl.jar:/opt/bea/user_projects/domains/base_domain/lib/xsltc.jar:/opt/bea/user_projects/domains/base_domain/lib/serializer.jar

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:

Open configupdate.bat or configupdate.sh.
Locate the following line:
```
-Duser.language=en -Duser.region="
```
Update the existing line to include the path to the sys-configuration.xml file:

For example, on Windows:
```
-Dextend.local.config.dir=c:\novell\idm
```
For example, on Linux:
```
-Dextend.local.config.dir=/opt/novell/idm
```
Save and close the file.
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:
```
c:\jrockit\jre\lib\security\cacerts
```

7.3.3 Removing OpenSAML JAR Files

The OpenSAML JAR files that WebLogic uses conflict with the ones needed for the User Application. Therefore, you need to remove the ones in the WebLogic /WL103/modules directory to ensure that the User Application is installed properly on WebLogic. This requirement applies to any User Application that does not have SSO enabled.

Be sure to remove the following JAR files in the WebLogic /WL103/modules directory:

com.bea.core.bea.opensaml_1.0.0.0_5-0-2-0.jar
com.bea.core.bea.opensaml2_1.0.0.0_5-0-2-0.jar

7.3.4 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:

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

Add the following line in the <security-configuration> section right before the closing of this section:

<enforce-valid-basic-auth-credentials>false</enforce-valid-basic-auth-credentials>
</security-configuration>

Save the file and restart the server.

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