Maximo Development,Support and Training : Installing Maximo Asset Management version 7.6 in a WebSphere Application Server Network Deployment v8.5.5 liberty profile

NOTE: The following information is provided as-is and does not describe an officially-supported configuration.

Maximo Asset Management version 7.6 can be installed in a WebSphere® Application Server Network Deployment v8.5.5 liberty profile. WebSphere Application Server liberty profiles are dynamic in nature and they allow the WebSphere Application Server server to provision only the features needed by the application which contributes to faster load speed and a smaller footprint.

To install Maximo Asset Management version 7.6 in a WebSphere Application Server Network Deployment v8.5.5 liberty profile, you must install the product, manually create a database, modify files, and then rebuild the Maximo Asset Management and deploy Maximo Asset Management EAR files.

Install DB2 v10.5.
1. Log in to the target system as a user with administrative authority. If you are running the IBM Maximo Asset Management version 7.6 installation program from a Linux or UNIX terminal window, you must be logged in as the root user.
2. Start the IBM Maximo Asset Management version 7.6 installation program from the launchpad.
3. From the Install Product panel, select IBM DB2 v10.5 and then click Install IBM Maximo Asset Management components.
4. In the package selection panel, click Next.
5. In the package prerequisite validation panel, review the results of the prerequisite check and then click Next. If any errors are reported on this panel, resolve the issue and then click Recheck Status before continuing.
6. In the license agreement panel, review the license information for each package being installed, select I accept the terms in the license agreements if you agree with the terms, and then click Next.
7. In the Installation Manager installation location panel, specify path information for the shared resources directory and the Installation Manager installation directory, and then click Next. Installation Manager is the installation framework that is used to install Maximo Asset Management version 7.6 components. The shared resources directory is a common workspace directory used by Installation Manager when installing packages.
8. In the package installation location panel, select a package group, specify the path information for its installation directory, and then click Next. Repeat this process for each package group listed.
9. In the package translations panel, specify language support for DB2, and then click Next.
10. In the package features panel, leave all default options checked, and then click Next.
11. In the package configuration panel, specify configuration information for DB2 v10.5, and then click Next.
12. In the package summary panel, review the information for the planned installation, and then click Install.
Install Maximo Asset Management v7.6.
1. Log in to the Maximo Asset Management administrative workstation. If you run the IBM Maximo Asset Management version 7.6 installation program from a Linux or UNIX terminal window, you must be logged in as the root user.
2. Launch the IBM Maximo Asset Management version 7.6 installation program from the launchpad.
3. From the Install Product panel, select IBM Maximo Asset Management v7.6 and then click Install IBM Maximo Asset Management components.
4. In the package selection panel, click Next.
5. In the package prerequisite validation panel, review the results of the prerequisite check, and then click Next. If any errors are reported on this panel, resolve the issue and then click Recheck Status before continuing.
6. In the license agreement panel, review the license information for each package being installed, select I accept the terms in the license agreements if you agree with the terms, and then click Next.
7. In the Installation Manager installation location panel, specify path information for the shared resources directory and the Installation Manager installation directory, and then click Next. Installation Manager is the installation framework that is used to install Maximo Asset Management version 7.6 components. The shared resources directory is a common workspace directory used by Installation Manager when installing packages.
8. In the package installation location panel, select the IBM Tivoli’s process automation suite package group, specify the path information for the Maximo Asset Management version 7.6 installation directory, and then click Next.
9. In the package features panel, leave all default options checked, and then click Next.
10. In the package summary panel, review the information for the planned installation, and then click Install. If you install in a non-English environment, you might notice the environment summary is listed as English. You configure supported languages for Maximo Asset Management later with the Maximo Asset Management configuration program.
11. After the installation is complete, select the option to start the Maximo Asset Management version 7.6 configuration program, and then click Finish. The Maximo Asset Management version 7.6 installation program exits and the Maximo Asset Management version 7.6 configuration program is started automatically. Exit the Maximo Asset Management version 7.6 configuration program
Install Liberty. Refer to the WebSphere Application Server Network Deployment v8.5.5 knowledge center for details.
Manually configure DB2 v10.5.
1. Log in to the DB2 host system as a user that has administrative permissions on the system.
2. Create system users if they do not exist on the system.

Windows	db2admin maximo
Linux or UNIX	db2admin maximo ctgfenc1 ctginst1 The ctginst1 user ID must be assigned to db2iadm1 as its primary group.

Open a console window and set up the DB2 environment.

Windows	db2cmd
Linux or UNIX	Ensure that the /opt/ibm/db2/V10.5/bin, /opt/ibm/db2/v10.5/ instance, and /opt/ibm/db2/V10.5/adm directories are added to your PATH.

Create the DB2 instance:

Windows

db2icrt -s ese -u db2admin,myPassword -r 50005,50005 ctginst1

set db2instance=ctginst1

db2start

db2 update dbm config using SVCENAME 50005 DEFERRED

db2stop

db2set DB2COMM=tcpip

db2start

Linux or UNIX

db2icrt -s ese -u ctgfenc1 -p 50005 ctginst1

. /home/ctginst1/sqllib/db2profile

db2start

db2 update dbm config using SVCENAME 50005 DEFERRED

db2stop

db2set DB2COMM=tcpip

db2start

Create the database.

db2 create db ’maxdb76’ ALIAS ’maxdb76’ using codeset UTF-8 territory US pagesize 32 K

db2 connect to ’maxdb76’

db2 GRANT DBADM ON DATABASE TO USER db2admin (windows only)

db2 GRANT SECADM ON DATABASE TO USER db2admin (windows only)

db2 connect reset

Configure the database.

db2 update db cfg for maxdb76 using SELF_TUNING_MEM ON

db2 update db cfg for maxdb76 using APPGROUP_MEM_SZ 16384 DEFERRED

db2 update db cfg for maxdb76 using APPLHEAPSZ 2048 AUTOMATIC DEFERRED

db2 update db cfg for maxdb76 using AUTO_MAINT ON DEFERRED

db2 update db cfg for maxdb76 using AUTO_TBL_MAINT ON DEFERRED

db2 update db cfg for maxdb76 using AUTO_RUNSTATS ON DEFERRED

db2 update db cfg for maxdb76 using AUTO_REORG ON DEFERRED

db2 update db cfg for maxdb76 using AUTO_DB_BACKUP ON DEFERRED

db2 update db cfg for maxdb76 using CATALOGCACHE_SZ 800 DEFERRED

db2 update db cfg for maxdb76 using CHNGPGS_THRESH 40 DEFERRED

db2 update db cfg for maxdb76 using DBHEAP AUTOMATIC

db2 update db cfg for maxdb76 using LOCKLIST AUTOMATIC DEFERRED

db2 update db cfg for maxdb76 using LOGBUFSZ 1024 DEFERRED

db2 update db cfg for maxdb76 using LOCKTIMEOUT 300 DEFERRED

db2 update db cfg for maxdb76 using LOGPRIMARY 20 DEFERRED

db2 update db cfg for maxdb76 using LOGSECOND 100 DEFERRED

db2 update db cfg for maxdb76 using LOGFILSIZ 8192 DEFERRED

db2 update db cfg for maxdb76 using SOFTMAX 1000 DEFERRED

db2 update db cfg for maxdb76 using MAXFILOP 32768 DEFERRED #32-bit Windows

db2 update db cfg for maxdb76 using MAXFILOP 65335 DEFERRED #64-bit Windows

db2 update db cfg for maxdb76 using MAXFILOP 30720 DEFERRED #32-bit UNIX

db2 update db cfg for maxdb76 using MAXFILOP 61440 DEFERRED #64-bit UNIX

db2 update db cfg for maxdb76 using PCKCACHESZ AUTOMATIC DEFERRED

db2 update db cfg for maxdb76 using STAT_HEAP_SZ AUTOMATIC DEFERRED

db2 update db cfg for maxdb76 using STMTHEAP AUTOMATIC DEFERRED

db2 update db cfg for maxdb76 using UTIL_HEAP_SZ 10000 DEFERRED

db2 update db cfg for maxdb76 using DATABASE_MEMORY AUTOMATIC DEFERRED

db2 update db cfg for maxdb76 using AUTO_STMT_STATS OFF DEFERRED

db2 update db cfg for maxdb76 using STMT_CONC LITERALS DEFERRED

db2 update alert cfg for database on maxdb76 using db.db_backup_req SET THRESHOLDSCHECKED YES

db2 update alert cfg for database on maxdb76 using db.tb_reorg_req SET THRESHOLDSCHECKED YES

db2 update alert cfg for database on maxdb76 using db.tb_runstats_req SET THRESHOLDSCHECKED YES

db2 update dbm cfg using PRIV_MEM_THRESH 32767 DEFERRED

db2 update dbm cfg using KEEPFENCED NO DEFERRED

db2 update dbm cfg using NUMDB 2 DEFERRED

db2 update dbm cfg using RQRIOBLK 65535 DEFERRED

db2 update dbm cfg using HEALTH_MON OFF DEFERRED

##

Windows: AGENT_STACK_SZ 1000

# Unix : AGENT_STACK_SZ 1000

#

db2 update dbm cfg using AGENT_STACK_SZ 1000 DEFERRED

db2 update dbm cfg using MON_HEAP_SZ AUTOMATIC DEFERRED

db2set DB2_SKIPINSERTED=ON

db2set DB2_INLIST_TO_NLJN=YES

db2set DB2_MINIMIZE_LISTPREFETCH=Y

db2set DB2_EVALUNCOMMITTED=YES

db2set DB2_FMP_COMM_HEAPSZ=65536

db2set DB2_SKIPDELETED=ON

db2set DB2_USE_ALTERNATE_PAGE_CLEANING=ON

For Linux or UNIX, log into the system as the ctginst1 user, and then restart the DB2 command-line environment.

su - ctginst1

db2

Restart DB2.

db2stop force

db2start

Reconnect to the database.

db2 connect to ’maxdb76’

Create a buffer pool.

db2 CREATE BUFFERPOOL MAXBUFPOOL IMMEDIATE SIZE 4096 AUTOMATIC PAGESIZE 32 K

Create table spaces.

db2 CREATE REGULAR TABLESPACE MAXDATA PAGESIZE 32 K MANAGED BY AUTOMATIC STORAGE INITIALSIZE 5000 M BUFFERPOOL MAXBUFPOOL

db2 CREATE TEMPORARY TABLESPACE MAXTEMP PAGESIZE 32 K MANAGED BY AUTOMATIC STORAGE BUFFERPOOL MAXBUFPOOL

db2 CREATE REGULAR TABLESPACE MAXINDEX PAGESIZE 32 K MANAGED BY AUTOMATIC STORAGE INITIALSIZE 5000 M BUFFERPOOL MAXBUFPOOL

db2 GRANT USE OF TABLESPACE MAXDATA TO USER MAXIMO

Create Schema.

db2 create schema maximo authorization maximo

Grant authority to maximo.

db2 GRANT DBADM,CREATETAB,BINDADD,CONNECT,CREATE_NOT_FENCED_ROUTINE,IMPLICIT_SCHEMA,

LOAD,CREATE_EXTERNAL_ROUTINE,QUIESCE_CONNECT,SECADM ON DATABASE TO USER MAXIMO

db2 GRANT USE OF TABLESPACE MAXDATA TO USER MAXIMO

db2 GRANT CREATEIN,DROPIN,ALTERIN ON SCHEMA MAXIMO TO USER MAXIMO

Break the database connection.

db2 connect reset

Exit the DB2 command-line environment.

Update values for database properties located in the maximo.properties file.

Log in to the Maximo Asset Management administrative workstation.
Change to the Product_root\applications\maximo\properties directory.
Edit the maximo.properties. Update database properties with the values you used to install and configure DB2.

mxe.db.user
mxe.db.name
mxe.db.driver
mxe.db.url

Save and close the file.

Run the maxinst command to populate the database.

Log in to the Maximo Asset Management administrative workstation.
Change to the Product_root\maximo\tools\maximo directory.
Run the maxinst command.

maxinst -sINDEXTABLESPACE -tDATATABLESPACE -iDATABASENAME -y

For example,

maxinst -sMAXINDEX -tMAXDATA -imaxdb76 -y

Edit EJB module files.

Log in to the Maximo Asset Management administrative workstation.
Change to the Product_root\maximo\applications\maximo\mboejb\ejbmodule\META-INF directory.
Edit the ejb-jar.xml file by uncommenting the following blocks of text. After the edits are complete, save and close the file.

<!-- MEA MDB

  <container-transaction>

    <method>

      <ejb-name>JMSContQueueProcessor-1</ejb-name>

      <method-name>*</method-name>

    </method>

    <trans-attribute>Required</trans-attribute>

  </container-transaction>

-->

<!-- MEA MDB for error queue

  <container-transaction>

    <method>

      <ejb-name>JMSContQueueProcessor-2</ejb-name>

    <method-name>*</method-name>

    </method>

    <trans-attribute>Required</trans-attribute>

  </container-transaction>

-->

Edit the ibm-ejb-jar-bnd.xmi file by uncommenting the following blocks of text. After the edits are complete, save and close the file.

<!-- MEA MDB

  <ejbBindings xmi:type="ejbbnd:MessageDrivenBeanBinding"

xmi:id="MessageDrivenBeanBinding_1"

activationSpecJndiName="intjmsact">

  <enterpriseBean xmi:type="ejb:MessageDriven"

href="META-INF/ejb-jar.xml#MessageDriven_JMSContQueueProcessor_1"/>

  </ejbBindings>

-->

<!-- MEA MDB for error queue

  <ejbBindings xmi:type="ejbbnd:MessageDrivenBeanBinding"

xmi:id="MessageDrivenBeanBinding_1"

activationSpecJndiName="intjmsacterr">

  <enterpriseBean xmi:type="ejb:MessageDriven"

href="META-INF/ejb-jar.xml#MessageDriven_JMSContQueueProcessor_2"/>

  </ejbBindings>

-->

Rebuild the Maximo Asset Management application EAR file.

Log in to the Maximo Asset Management administrative workstation.
Change to the Product_root\maximo\deployment directory.
Run the buildmaximoearwas8 command. The maximo.ear file is built and stored in the Product_root\maximo\deployment\default directory.

buildmaximoearwas8.cmd

Create a liberty profile server. Refer to the WebSphere Application Server Network Deployment v8.5.5 knowledge center for details.
Modify liberty profile server settings for Maximo Asset Management.
1. Edit the LibertyProfile_root\usr\servers\MXServer\server.xml file and specify information for Java Server Pages, JMS function, Application Security, Jax Web Services, and the startup statement. A completed server.xml file should look similar to the following.

<server description="new server">


    <!-- Enable features -->

    <featureManager>

        <!-- Java Server Pages --> 

        <feature>jsp-2.2</feature>


        <!-- JMS Function -->

        <feature>wasJmsServer-1.0</feature>

        <feature>jndi-1.0</feature>

        <feature>wasJmsClient-1.1</feature>

        <feature>jmsMdb-3.1</feature>


        <feature>appSecurity-2.0</feature>

        <feature>webProfile-6.0</feature>

        <feature>servlet-3.0</feature>

        <feature>managedBeans-1.0</feature>


        <feature>jaxrs-1.1</feature>

        <feature>wab-1.0</feature>

        <feature>jaxws-2.2</feature>

    </featureManager>

    <webContainer deferServletLoad="false"/>

    <httpEndpoint id="defaultHttpEndpoint"

                  host="localhost"

                  httpPort="9080"

                  httpsPort="9443" />

    <messagingEngine>

        <queue id="sqin"/>

        <queue id="sqout"/>

        <queue id="cqin"/>

        <queue id="cqinerr"/>

    </messagingEngine>

    <jmsQueue id="sqin" jndiName="jms/maximo/int/queues/sqin">

       <properties.wasJms queueName="sqin"/>

    </jmsQueue>  

    <jmsQueue id="sqout" jndiName="jms/maximo/int/queues/sqout">

       <properties.wasJms queueName="sqout"/>

    </jmsQueue>  

    <jmsQueue id="cqin" jndiName="jms/maximo/int/queues/cqin">

      <properties.wasJms queueName="cqin"/>

    </jmsQueue>  

    <jmsQueue id="cqinerr" jndiName="jms/maximo/int/queues/cqinerr">

      <properties.wasJms queueName="cqinerr"/>

    </jmsQueue>  

    <connectionManager id="ConnectionMgr1"/>

    <jmsQueueConnectionFactory id="intjmsconfact" connectionManagerRef="ConnectionMgr1"

               jndiName="intjmsconfact">

      <properties.wasJms/>

    </jmsQueueConnectionFactory>  

   <connectionManager id="ConnectionMgr1"/>

   <jmsActivationSpec id="maximo/mboejb/JMSContQueueProcessor-1">

      <properties.wasJms

          destinationRef="cqin"

      />   

   </jmsActivationSpec>       

   <jmsActivationSpec id="maximo/mboejb/JMSContQueueProcessor-2">

      <properties.wasJms

          destinationRef="cqinerr"

      />   

   </jmsActivationSpec>

   <application id="maximo" type="ear" location="maximo.ear" name="maximo">

        <security-role name="maximouser">

            <special-subject type="ALL_AUTHENTICATED_USERS"/>

        </security-role>

       <classloader> 

            <privateLibrary>

               <fileset 

                   dir="${server.config.dir}/apps/lib" 

                   includes="*.jar" scanInterval="5s"

               />

            </privateLibrary>

       </classloader>

    </application>    

</server>‹

Edit the LibertyProfile_root\usr\servers\MXServer\jvm.options file and specify heap size information. A completed jvm.options file should look similar to the following.

-Xms2048m

-Xmx2048m

-Xgcpolicy:gencon

-Xmn320m

Copy files from the Maximo Asset Management administrative workstation to the liberty profile server.

Log in to the Maximo Asset Management administrative workstation.
Change to the Product_root\maximo\applications\maximo\lib directory.
Copy the following files from the Maximo Asset Management administrative workstation to the LibertyProfile_root\usr\servers\MXServer\apps\lib directory of the WebSphere Application Server Network Deployment server.

mail.jar
activation.jar

Change to the Product_root\maximo\deployment\default directory.
Copy the maximo.ear file from the Maximo Asset Management administrative workstation to the LibertyProfile_root\usr\servers\MXServer\apps directory of the WebSphere Application Server Network Deployment server.

Start the liberty profile server, MXServer. Refer to the WebSphere Application Server Network Deployment v8.5.5 knowledge center for details.

Maximo Development,Support and Training

Thursday, 6 February 2020

Installing Maximo Asset Management version 7.6 in a WebSphere Application Server Network Deployment v8.5.5 liberty profile

No comments:

Post a Comment

IBM Readme for IBM Maximo Asset Management 7.6.1.3 Fix Pack

Contact Form