Maximo 7.6 Asset Management Post Installation Check List

Maximo 7.6 Asset Management Post Installation Check List

Step 1: Verifying the Installation Programatically

The installation is programatically verified through the use of post installation validation utilities.        

Note: The JAVA_HOME environment variable must be set on the system before you can use the verification utilities.

Procedure

1.  Log in to the server using the user ID that was used to run the installation program. If you intend to use the installValidation utility, log in to the administrative workstation.

2. Ensure the JAVA_HOME environment variable is set properly to the location of a JRE 1.7 installation.

3. To verify product installation, from the administrative workstation, change directory to ibm\smp\configtool\scripts and run the installValidation.[sh|bat] command.  

                             

For example: installValidation.bat -action validate Results

The installValidation.bat validation utility results are logged in ctginstallvalidationtrace00.log. This log is found in the \smp\configtools\logs directory on the administrative workstation.

Step 2: Verifying the Installation Manually

To verify that the Maximo Asset Management installation was completed successfully, perform the following verification procedures:

Procedure

1.  Examine the CTGConfigurationXX.log files for success messages.

The following success messages are found in the CTGConfigurationTraceXX.log file and can be used to verify which phases of the installation were successful:

CTGIN2114I: The database was created successfully

CTGIN2135I: Tablespace maxdata created successfully

CTGIN2135I: Tablespace maxtemp created successfully

CTGIN2079I: process automation engine database configuration completed successfully (This message indicates that maxinst finished successfully.)

CTGIN2222I: WebSphere Application Server creation successful

CTGIN2188I: Creation and configuration of service integration bus successfully completed

CTGIN2184I: Creation and configuration of JMS resources successfully completed

CTGIN2310I: Application server security was successfully enabled for process automation engine

CTGIN2253I: buildmaximoear.cmd completed successfully

CTGIN2224I: Deployment of application MAXIMO was successful

CTGIN2253I: buildhelpear.cmd completed successfully

CTGIN2224I: Deployment of application MAXIMOIEHS was successful

CTGIN2208I: runConfigurationStep completed successfully

CTGIN2370I: The installation finished successfully

Search the CTGConfigurationTraceXX.log file for the following message, which indicates that the maxinst task completed successfully:

CTGIN2079I, maxinst.*completed

2. Compare the packages chosen for installation with the packages that were installed. The Package Summary panel of the Maximo Asset Management installation program provides a summary of all the packages to be installed. You can compare the contents of that panel with a listing of what was installed on the system by using the configuration tool and selecting the update database task. The resulting list matches the packages listed in the Package Summary panel.

3. Log in to the product and verify that applications are present. Being able to log in to the product manually is a good indicator that the installation was successful. Once you have logged in, navigate through the GoTo menu to verify that it has been populated with the applications you expect. If you experience access problems with the product, clear the cache of your browser and try again.

Step 3 :Validate whether the WAS Console URL is accessible.               https://[HOSTNAME]:9043/ibm/console

Step 4: Login with wasadmin user credentials.

Step 5: Once logged in Navigate to Server Types->WebSphere Applicaton Servers and check whether MXServer is started.

Step 6: Validate whether the Maximo URL is accessable. http://host name:port/maximo

Step 7: Login with MAXADMIN Credentials for initial validation.

Step 8: Check whether the Maximo Home page is displayed after logged in.

Step 9: From the top hand right side, Click Help icon and validate whether all the installed components are displayed in the System Information(Installed versions of Maximo,WebSphere,Database).

Step 10: Open any Applications ( Asset,Person etc..) in Maximo and validate whether the OOB functionality is working as expected.

Step 11: For checking DB Connectivity, Open SQL Server Studio from the Server and perform querying with Maximo.

Post Installation Configurations

Below Configurations need to be setup before using Maximo Asset Management.

1. SMTP Configuration

2. Currency Codes

3. Item Set

4. Company Set

5. Organization and Sites

6. GL accounts Setup 

7. Foundational Data Setup( Data Loading of Locations/Assets/Users etc)

8. DocLinks Configuration