Product Documentation
Abstract
Installing IBM Maximo Asset Management 7.5 on
IBM PureApplication System
Content
IBM PureApplication System
IBM PureApplication System is a cloud management appliance that uses a patterns-based approach to creating, deploying, and managing application environments in the cloud. You use IBM PureApplication System to quickly build and deploy Maximo Asset Management 7.5 as a virtual system pattern that
represents your configured application environment.
By deploying Maximo Asset Management 7.5 as a pattern in a IBM PureApplication System environment, you get consistent results from one deployment to another deployment. You can focus on creating a Maximo Asset Management platform for development, test, and production, and you spend less time configuring the supporting environment.
Prerequisites
The Maximo Asset Management 7.5 pattern is available for download from Passport Advantage.
The installation of Maximo Asset Management on IBM PureApplication System supports the following components. Ensure that your environment meets the minimum standards and requirements before you perform the installation. Java 1.6 or above must be present on all systems used in the deployment.
Administrative workstation
The following operating systems are supported for Maximo Asset Management on IBM PureApplication System for pattern installation and customization.
Table 1. Operating supported versions
| Operating system | Requirements |
| AIX |
Maximo Asset Management can only be installed on AIX in the IBM PureApplication System environment. After deploying Maximo Asset Management on AIX in the IBM PureApplication System environment, you can choose to use the default pattern you just deployed, or, you can modify it and repackage it into a customized pattern that can be deployed within the IBM PureApplication System environment repeatedly. |
| Red Hat Enterprise Linux |
Maximo Asset Management can only be installed on Linux in the IBM PureApplication System environment. After deploying Maximo Asset Management on Linux in the IBM PureApplication System environment, you can choose to use the default pattern you just deployed, or, you can modify it and repackage it into a customized pattern that can be deployed within the IBM PureApplication System environment repeatedly |
Maximo Asset Management
Table 2. Maximo Asset Management supported versions
| Software | Requirements |
| Maximo Asset Management | 7.5.0.3 |
Maximo Asset Management Industry Solutions and Add-ons
Contact customer support for the latest information on Maximo Asset Management Industry Solutions and Add-ons that are supported for Maximo Asset Management on IBM PureApplication System.
IBM PureApplication System
Table 3. IBM PureApplication System supported versions
| Software | Requirements |
| IBM PureApplication System |
|
| IBM Workload Deployer |
|
Application server
Table 4. Application server supported versions
| Software | Requirements |
| WebSphere Application Server |
When using WebSphere Application Server v8.0, you have the option to deploy sample Maximo Asset Management data in the database. If you want to deploy sample data, set the use_demo_data parameter of the IBM Maximo Asset Management 7.5.0 DB2 Database Setup database script package to true. The use_demo_data parameter is set to false by default. Maximo Asset Management on IBM PureApplication System supports a single application server deployment. You cannot deploy Maximo Asset Management on IBM PureApplication System using multiple application servers. |
| IBM® HTTP Server |
|
Database server
Table 5. Database server supported versions
| Software | Requirements |
| DB2 |
Both the database and index table spaces must be named MAXDATA. The schema name must be defined as maximo. |
Installing the Maximo Asset Management 7.5 pattern on IBM PureApplication System
You add Maximo Asset Management 7.5 virtual system images to the IBM PureApplication System catalog by using a script to upload pattern image files.
Before you begin, ensure that you have sufficient permission to create patterns and script packages within IBM PureApplication System. Also, ensure that no other instances of the Maximo Asset Management pattern and script packages already exist on IBM PureApplication System.
You must have IBM Java 1.6 or later installed on the system used to install the image.
The Maximo Asset Management 7.5 pattern consists of a collection of scripts and content that are used to configure virtual images that have been created to work together. Deploy the Maximo Asset Management 7.5 pattern by first installing the IBM PureApplication System command-line tool and then using it to install the Maximo Asset Management 7.5 pattern.
1. In a web browser, log into IBM PureApplication System.
2. Install the IBM Workload Deployer command-line tool on your system.
a. Click Download Tooling > Download command line tool, and save the zip file to your
system. The file is named pure.cli-version.zip.
b. Extract the files from the IBM Workload Deployer zip file. The pure.cli directory is created.
3. Download the Pattern.zip file and extract it in the pure.cli directory. The Pattern.zip file contains packages and deployment scripts for Maximo Asset Management 7.5.
4. Open a command prompt, change directory to where you extracted the Pattern.zip file, and then run the Maximo Asset Management 7.5 images deployment script:
installMaximoPattern -h IBM PureApplication System host -l IBM PureApplication path
-u IBM PureApplication System user name -p password
For example:
installMaximoPattern.bat -h MyIBMPureApplicationSystemHost.mydomain.com
-l C:\IWD\pure.cli -u MyIBMPureApplicationSystemUserName
-p MyIBMPureApplicationSystemUserNamePassword
5. When prompted, enter 1 to accept the license agreement.
If you use WebSphere Application Server v7 for deployment, during installation, the following warnings occur:
Unable to find matching property for original pattern part "IBM HTTP servers" (id 1),
pclass "ConfigWAS", key "was_im_repo_location".
Unable to find matching property for original pattern part "IBM HTTP servers" (id 1),
pclass "ConfigWAS", key "was_im_repo_user".
Unable to find matching property for original pattern part "IBM HTTP servers" (id 1),
pclass "ConfigWAS", key "was_im_repo_pass".
These warnings can be safely ignored. The warnings are based upon the differences in installation technology used for WebSphere Application Server v7 and WebSphere Application Server v8.
Deploying a Maximo Asset Management virtual system instance
After the Maximo Asset Management 7.5 pattern is uploaded to IBM PureApplication System, you deploy a virtual system that is based upon that pattern.
1. In a web browser, log into IBM PureApplication System.
2. Click Patterns > Virtual Systems.
3. Select the pattern that you uploaded, for example, IBM Maximo Asset Management 7.5.0.3, and then click Deploy. The virtual system configuration dialog is displayed.
4. In the Virtual system configuration window, specify the required configuration information
a. Enter a name for the system in the Virtual system name field.
b. Click Choose environment and select the environment profile according to your
preferences.
c. Click Schedule deployment and configure the deployment period for the
system.
d. Click Configure virtual parts and configure the five individual objects that
comprise the virtual system. Click the label for each object to access the
configuration dialog for it. Required fields are marked with a red asterisk.
In general, except for providing user names and passwords, default values
included with the pattern are sufficient. Do not modify any configuration
field values set to a variable, for example, ${DB2_ESE.service_port}.
IBM HTTP Servers
Supply values for the system administrator or root password and
the WebSphere Application Server administrative user name.
Deployment manager
Supply values for the system administrator or root password and
the WebSphere Application Server administrative user name.
Custom nodes
Supply values for the system administrator or root password, the
WebSphere Application Server administrative user name, the
application server name, database name, database user, schema
name, or node name.
Core OS
Supply values for the root password, the application server name,
and the application server node. The value that you supply for the
Password (virtuser) field must match the password value for the
Password (virtuser) field that is configured for the DB2 Enterprise
object.
e. When you complete the configuration, click OK.
You can monitor the progress of the deployment by referring to the Current Status field. The deployment can take several hours to complete.
Maintaining a Maximo Asset Management virtual system instance
If fix packs and test fixes become available for Maximo Asset Management components after you deployed a virtual system, you can install them remotely.
Before you are able to deploy industry solutions and add-ons, apply fix packs, or perform other upgrade actions, you must configure security policies on virtual system components to allow the exchange of ICMP packets. The ping command, used to test connectivity between systems, is one of the most common commands that generates an ICMP packet. By default, Maximo Asset Management virtual system components include firewall rules that are configured to deny the exchange of ICMP packets. You must remotely log into and configure the virtual system components to send and receive ICMP traffic through the use of TCP/IP filtering. For AIX systems, you can enable ipsec, and for Linux systems, you can use iptables rules.
To apply a fix pack to a previously deployed virtual system component, download the fix pack to your system. Log in to IBM PureApplication System to identify the IP address or host name for the component and then remotely apply the fix.
If you are installing or updating an industry solution or add-on for Maximo Asset Management, you cannot use the product launchpad to start the industry solution installation program. You must start the solution installation program, solutionInstallerGui, directly from the command-line. By default, the industry solution program is located in the /opt/IBM/SMP/bin directory.
1. Download the fix pack from IBM Fix Central (http://www.ibm.com/support/fixcentral/).
2. Locate the IP address or host name for the target virtual machine.
a. In a web browser, log into IBM PureApplication System.
b. Click Instances > Virtual Systems.
c. Select the virtual system that you deployed, and then click Virtual machines.
d. Click the name of the virtual machine that is hosting the software that
requires the fix pack and make a note of the host name and IP address. The
Network interface 0 field contains both the host name and IP address for
the virtual machine.
3. Copy the fix pack file to the virtual machine and apply it using remote system access software such as Virtual Network Computing (VNC) or Secure Shell (SSH). When prompted, you must choose to deploy the application EAR file manually. Refer to the Maximo Asset Management installation documentation for more information about deploying application EAR files manually.
If you redeploy the Maximo Asset Management pattern, remember that the fix pack is not included. You must either update the virtual image and then redeploy the pattern, or reapply the fix after the pattern is deployed.
Removing the Maximo Asset Management pattern
Remove the Maximo Asset Management pattern and virtual system instances from the IBM PureApplication System.
To remove Maximo Asset Management from IBM PureApplication System, you first remove all virtual system instances and then remove the pattern.
1. In a web browser, log into IBM PureApplication System.
2. Click Instances > Virtual Systems.
3. Select one of the virtual system instances you previously created from the Maximo Asset Management pattern.
4. Click Delete. Repeat this process for all virtual system instances that are created from the Maximo Asset Management pattern.
5. Click Patterns > Virtual Systems.
6. Select the pattern that you uploaded, for example, IBM Maximo Asset Management 7.5.0.3, and then click Delete.
7. Click Catalog > Script Packages.
8. Select the following patterns and then click Delete.
- IBM Maximo Asset Management 7.5.0 Administrative Workstation Configuration
- IBM Maximo Asset Management 7.5.0 DB2 Database Setup
- IBM Maximo Asset Management 7.5.0 WebSphere Setup and EAR Deploy
- mx_shutdown_firewall
Customizing the Maximo Asset Management pattern
The Maximo Asset Management pattern, and the virtual system instances that are created from that pattern, can be modified before deployment on Pure Systems.
Java 1.6 or higher and Apache Ant scripting engine 1.8 or higher must be present on all systems used in the customization process.
When customizing an image, you must ensure that the use_demo_data property is set to false before deploying the pattern. The default value of the use_demo_data property is false.
If you plan to customize portions of Maximo Asset Management, for example, updating icons used in the user interface, editing product help files, or modifying workflows, you can update the Maximo Asset Management pattern before deploying to Pure Systems. This allows you to create a custom deployment image that can be deployed in a repeatable and reliable fashion.
1. Download the Pattern.zip file and extract it in the pure.cli directory that is created when you extracted files for the IBM Workload Deployer command-line tool. The Pattern.zip file contains packages and deployment scripts for Maximo Asset Management 7.5.
2. Deploy Maximo Asset Management in a separate development environment. The virtual environment can be established on IBM PureApplication System using the standard Maximo Asset Management pattern.
3. Customize the Maximo Asset Management development environment.
4. Shut down the maximo application on the application server. The maximo application must be shut down before you capture data from the deployment.
5. Update the Maximo Asset Management administrative workstation script package.
a. Update the Maximo Asset Management administrative workstation script package.
b. Create a temporary directory.
mkdir /tmp/adminWsPackageWorkspace
c. Copy the
MaximoAssetManagement_7.5.0.3_Pattern_v1.0.0.0/script_packages/Maximo7503AdminWs.tar.gz
file from the pure.cli directory of the system hosting the IBM Workload Deployer
command-line tool to the /tmp/adminWsPackageWorkspace directory.
d. Unzip and untar the /tmp/adminWsPackageWorkspace/Maximo7503AdminWs.tar.gz file.
gzip -d Maximo7503AdminWs.tar.gz
tar xvf Maximo7503AdminWs.tar
e. Copy the MaximoAssetManagement_7.5.0.3_Pattern_v1.0.0.0/Utilities/
createImagesFromInstall[.sh|bat] and
MaximoAssetManagement_7.5.0.3_Pattern_v1.0.0.0/Utilities/
createImagesFromInstall.xml files from the pure.cli directory of the
system hosting the IBM Workload Deployer command-line tool to the /tmp
directory.
f. Run the image creation script to capture the customizations you made to the
administrative workstation.
createImageFromInstall.sh -a Ant_Install_Home -i
Maximo_Asset_Management_Install_Home -o
Output_Directory -t capture_admin
So, for example:
createImageFromInstall.sh -a /opt/ibm/smp/ant -i /opt/ibm/smp
-o /tmp -t capture_admin
g. Open the dbschema.sql file for editing, remove the database connect to
statement appearing at the beginning of the file, and then save the file.
h. Copy the contents of the output directory to the directory where you
extracted the Maximo7503AdminWs package.
cp -pr /tmp/adminWsPackage/* /tmp/adminWsPackageWorkspace
i. Delete the original /tmp/adminWsPackageWorkspace/Maximo7503AdminWs.tar
file to make way for the creation of a new file.
rm /tmp/adminWsPackageWorkspace/Maximo7503AdminWs.tar
j. Create a new package archive.
tar cvf Maximo7503AdminWs.tar *
gzip -S .gz Maximo7503AdminWs.tar
k. Copy the /tmp/adminWsPackageWorkspace/Maximo7503AdminWs.tar.gz file to
the pure.cli/MaximoAssetManagement_7.5.0.3_Pattern_v1.0.0.0/
script_packages/directory of the system hosting the IBM Workload
Deployer command-line tool. Overwrite the file when prompted.
6. Update the WebSphere Application Server script package.
a. Log into the system hosting WebSphere Application Server in your custom
Maximo Asset Management development environment.
b. Create a temporary directory.
mkdir /tmp/WASScriptPackageWorkspace
c. Copy the MaximoAssetManagement_7.5.0.3_Pattern_v1.0.0.0/
script_packages/Maximo7503ConfigureWAS.tar.gz file from the pure.cli
directory of the system hosting the IBM Workload Deployer command-line
tool to the /tmp/WASScriptPackageWorkspace directory.
d. Unzip and untar the /tmp/WASScriptPackageWorkspace/
Maximo7503ConfigureWAS.tar.gz file.
gzip -d Maximo7503ConfigureWAS.tar.gz
tar xvf Maximo7503ConfigureWAS.tar
e. Copy the MaximoAssetManagement_7.5.0.3_Pattern_v1.0.0.0/Utilities/
createImagesFromInstall[.sh|bat] and
MaximoAssetManagement_7.5.0.3_Pattern_v1.0.0.0/Utilities/
createImagesFromInstall.xml files from the pure.cli directory of the
system hosting the IBM Workload Deployer command-line tool to the /tmp
directory.
f. Run the image creation script to capture the customizations you made to
WebSphere Application Server.
createImageFromInstall.sh -a Ant_Install_Home -i
Maximo_Asset_Management_Install_Home -o
Output_Directory -t capture_was
So, for example:
createImageFromInstall.sh -a /opt/ibm/smp/ant -i /opt/ibm/smp
-o /tmp -t capture_WAS
g. Copy the contents of the output directory to the directory where you
extracted the Maximo7503ConfigureWAS package.
cp -pr /tmp/WASScriptPackage/* /tmp/WASScriptPackageWorkspace
h. Delete the original /tmp/WASScriptPackageWorkspace/Maximo7503ConfigureWAS.tar
file to make way for the creation of a new file.
i. Create a new package archive.
tar cvf Maximo7503ConfigureWAS.tar *
gzip -S .gz Maximo7503ConfigureWAS.tar
j. Copy the /tmp/WASScriptPackageWorkspace/Maximo7503ConfigureWAS.tar.gz
file to the pure.cli/MaximoAssetManagement_7.5.0.3_Pattern_v1.0.0.0/
script_packages/ directory of the system hosting the IBM Workload
Deployer command-line tool. Overwrite the file when prompted.
7. Update the DB2 script package.
a. Log into the system hosting DB2 in your custom Maximo Asset
Management development environment. The user ID used must be a
member of the db2iadm1 group on IBM PureApplication System. The user
ID must also have DBADM authority for the database. You can update
/etc/groups to ensure that the user ID is a member of the db2iadm1 group.
You can use a grant statement to give DBADM authority for the
database. For example GRANT DBADM ON DATABASE TO USER user_ID.
b. Create a temporary directory.
mkdir /tmp/DB2ScriptPackageWorkspace
c. Copy the MaximoAssetManagement_7.5.0.3_Pattern_v1.0.0.0/
script_packages/Maximo7503ConfigureDB2.tar.gz file from the pure.cli
directory of the system hosting the IBM Workload Deployer command-line
tool to the /tmp/DB2ScriptPackageWorkspace directory.
d. Unzip and untar the /tmp/DB2ScriptPackageWorkspace/
Maximo7503ConfigureDB2.tar.gz file.
gzip -d Maximo7503ConfigureDB2.tar.gz
tar xvf Maximo7503ConfigureDB2.tar
e. Copy the MaximoAssetManagement_7.5.0.3_Pattern_v1.0.0.0/Utilities/
createImagesFromInstall[.sh|bat] and
MaximoAssetManagement_7.5.0.3_Pattern_v1.0.0.0/Utilities/
createImagesFromInstall.xml files from the pure.cli directory of the
system hosting the IBM Workload Deployer command-line tool to the /tmp
directory.
f. Run the image creation script to capture the customizations you made to
DB2.
createImageFromInstall.sh -a Ant_Install_Home -i
Maximo_Asset_Management_Install_Home -o
Output_Directory -t capture_db -h
Instance_User_Name_Home -d Database_Name
-u Database_User_ID -p Database_User_Password
So, for example:
createImageFromInstall.sh -a /opt/ibm/smp/ant -i /opt/ibm/smp
-o /tmp -t capture_db -h /home/ctginst1 -d maxdb75 -u maximo -p maximo
g. Copy the contents of the output directory to the directory where you
extracted the Maximo7503ConfigureDB2 package.
cp -pr /tmp/DB2ScriptPackage/* /tmp/DB2ScriptPackageWorkspace
h. Delete the original /tmp/DB2ScriptPackageWorkspace/
Maximo7503ConfigureDB2.tar file to make way for the creation of a new file.
rm /tmp/DB2ScriptPackageWorkspace/Maximo7503ConfigureDB2.tar
i. Create a new package archive.
tar cvf Maximo7503ConfigureDB2.tar *
gzip -S .gz Maximo7503ConfigureDB2.tar
j. Copy the /tmp/DB2ScriptPackageWorkspace/Maximo7503ConfigureDB2.tar.gz
file to the pure.cli/MaximoAssetManagement_7.5.0.3_Pattern_v1.0.0.0/
script_packages/ directory of the system hosting the IBM Workload
Deployer command-line tool. Overwrite the file when prompted.
8. Run the Maximo Asset Management 7.5 images deployment script to deploy
the updated Maximo Asset Management on IBM PureApplication System
pattern using the IBM Workload Deployer command-line tool.
[{"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"}],"Version":"7.5","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27037736