IBM Support

Installing Maximo 7.6 to Oracle WebLogic 12c: Part 2 - Configuring WebLogic

Technical Blog Post


Abstract

Installing Maximo 7.6 to Oracle WebLogic 12c: Part 2 - Configuring WebLogic

Body

For those who tuned in yesterday, hello again! For those just joining us, take a look at that post to catch up.

Note: Because this entry was too short, I updated this entry to including configuring WebLogic configuration for Maximo.

 

A. Creating a WebLogic Domain

 

1. Start Configuration Wizard C:\Oracle\Middleware\Oracle_Home\wlserver_12.1\common\bin\config.exe

 

2. Create Domain
image
Change domain name to maximoserver. Click Next.

 

3. Templates
image
Keep only Basic WebLogic Server Domain - 12.1.3.0 (wlserver) selected. Click Next.

 

4. Administrator Account
image
Enter a username and password. (I kept the default weblogic name and used Manager1 for password).

 

5. Domain Mode and JDK
image
Select Production. WebLogic will choose the JDK that was used to install it. As I said yesterday, make sure that the JDK is Oracle HotSpot. It must be JDK 1.7 because that is what Maximo 7.6 uses.

 

6. Advanced Configuration
image
I checked off Administration Server here. It is not necessary to do so.

 

7. Configuration Summary
image
Look it over, make any changes that are needed, and click Create.

 

8. Configuration Progress
image

 

9. Configuration Successful
image

Do not check Start Admin Server. Click Finish.

 

B. Configuring WebLogic and starting the Admin Server

 

1. (Oracle database only ) Copy the oraclethin.jar file.

 

Windows: Copy the oraclethin.jar file from the administrative workstation (default C:\IBM\SMP\maximo\applications\maximo\lib\) to the Oracle server directory (using install location above, C:\Oracle\Middleware\Oracle_Home\wlserver_12.1\server\lib).

Unix: Copy the oraclethin.jar file from the administrative workstation (default /opt/IBM/SMP/maximo/applications/maximo/lib/) to the Oracle server directory (using install location above, /home/oracle/Oracle/Middleware/Oracle_Home/wlserver/server/lib).

 

2. Update setDomainEnv.cmd|sh.


a. Navigate to Windows: C:\Oracle\Middleware\Oracle_Home\user_projects\domains\maximoserver\bin Unix: /home/oracle/Oracle/Middleware/Oracle_Home/user_projects/domains/maximoserver/bin


b. Right-click and edit (do not double-click) Windows: setDomainEnv.cmd or Unix: setDomainEnv.sh.


c. Using your text editor, search for and replace the following entries:

 

Windows:

(Oracle database only) Search for

if NOT "%EXT_PRE_CLASSPATH%"=="" (
    if NOT "%PRE_CLASSPATH%"=="" (
        set PRE_CLASSPATH=%EXT_PRE_CLASSPATH%;%PRE_CLASSPATH%
    ) else (
        set PRE_CLASSPATH=%EXT_PRE_CLASSPATH%

Update the last set PRE_CLASSPATH to include the parameters below

set PRE_CLASSPATH=%WL_HOME%\server\lib\oraclethin.jar

Unix:

 

(Oracle database only) Search for

if [ "${EXT_PRE_CLASSPATH}" != "" ] ; then
    if [ "${PRE_CLASSPATH}" != "" ] ; then
        PRE_CLASSPATH="${EXT_PRE_CLASSPATH}${CLASSPATHSEP}${PRE_CLASSPATH}"
        export PRE_CLASSPATH
    else
        PRE_CLASSPATH="${EXT_PRE_CLASSPATH}${CLASSPATHSEP}$%WL_HOME%/server/lib/oraclethin.jar"
        export PRE_CLASSPATH
    fi
fi

Update the last PRE_CLASSPATH to include the parameters below

PRE_CLASSPATH="${EXT_PRE_CLASSPATH}${CLASSPATHSEP}$%WL_HOME%/server/lib/oraclethin.jar"

 

Increase the Java Heap parameters by searching for MEM_ARGS and setting the parameter as follows:

Search for and change the second instance

Windows:

WLS_MEM_ARGS_64BIT=-Xms256m -Xmx512m
to
WLS_MEM_ARGS_64BIT=-Xms4096m -Xmx4096m

Unix

WLS_MEM_ARGS_64BIT=-Xms256m -Xmx512m
to
WLS_MEM_ARGS_64BIT=-Xms4096m -Xmx4096m

 

Search for and change the first instance

Windows:

set MEM_PERM_SIZE_64BIT=-XX:PermSize=128m
to
set MEM_PERM_SIZE_64BIT=-XX:PermSize=512m

Unix:

MEM_PERM_SIZE_64BIT="-XX:PermSize=128m"
to
MEM_PERM_SIZE_64BIT="-XX:PermSize=512m"

 

Search for and change the first instance

Windows:

set MEM_MAX_PERM_SIZE_64BIT=-XX:MaxPermSize=256m
to
set MEM_MAX_PERM_SIZE_64BIT=-XX:MaxPermSize=512m

Unix:

MEM_MAX_PERM_SIZE_64BIT="-XX:MaxPermSize=256m"
to
MEM_MAX_PERM_SIZE_64BIT="-XX:MaxPermSize=512m"

 

Windows only:

Search for set JAVA_OPTIONS=%JAVA_OPTIONS% %JAVA_PROPERTIES%. Insert an option directly after this string, as follows:

-Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0

The entry looks like this example when complete:

set JAVA_OPTIONS=%JAVA_OPTIONS% %JAVA_PROPERTIES% -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 -Dwlw.iterativeDev=%iterativeDevFlag% -Dwlw.testConsole=%testConsoleFlag% -Dwlw.logErrorsToConsole=%logErrorsToConsoleFlag%

 

d. Save and close the setDomainEnv.cmd|.sh file.

 

3. Verify settings by starting Oracle WebLogic Server. To ensure that the edits that you made to the previous Oracle WebLogic Server files were accurate, start the Oracle WebLogic Server.

 

a. Start a command prompt at C:\Oracle\Middleware\Oracle_Home\user_projects\domains\maximoserver\bin

startWebLogic.cmd

It has completed startup when you see <Notice> <WebLogic Server> <BEA-000360) <The server started in RUNNING mode.>

 

b.Log into the WebLogic Administration Console at http://localhost:7001/console with the username and password you set during configuration.

 

4. Create a boot.properties file
a. In <weblogic_home>\user_projects\domains\maximoserver\servers\AdminServer, create a directory called \security
b. Create a text file called boot.properties. In that file, put two lines, for example:

username=weblogic

password=weblogic1

c. When the Admin Server is started, the username and password will be encrypted.

 

Next part: Creating the JMS Queues.

[{"Business Unit":{"code":"BU005","label":"IoT"}, "Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":""}]

UID

ibm11113837