Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Release 6.2.1
Installation Guide
Microsoft Windows | IBM WebSphere
Note
Before using this information and the product it supports, read the information in “Notices” on page Notices-1.
Third-Party Technology: Certain Maximo products contain technology provided under license from third
parties, as noted in the following table:
Open Source: Maximo contains computer software obtained from the public domain, known as "Open Source"
ownership of which is attributed as follows: Portions © 2002, Steve Souza (admin@jamonapi.com). Portions ©
2000-2004, Jason Hunter & Brett McLaughlin. Portions © 2004-2005, The Apache Software Foundation
(http://www.apache.org/).
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule
Contract with IBM Corp.
Contents
Chapter 6: Creating the Maximo Application Server and Deploying the EAR Files . . . . . . . . . . . 6-1
Creating a Windows Service for the Node Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Creating the Maximo Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Editing JVM Memory Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Adding a Redirect to IBM WebSphere 6.0.2.17 for Actuate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Identify the HTTP Transfer Port Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
Creating Virtual Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
Deploying the EAR Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notices-1
This section explains how this guide can help you to use IBM® Maximo®. It
also provides information about other IBM Corporation resources available to
you, such as additional documentation and support.
Audience
This guide is intended for implementation analysts, support personnel, and
system administrators who are installing Maximo for the first time.
Related Documentation
For more information about Maximo, refer to the following documentation:
Document Description
Document Description
Support
IBM Maximo users with a valid Annual Customer Support Plan (ACSP) can
obtain product support online at Support Online: support.mro.com.
T Application Server
®
T Actuate Report Server
T Database Server
NOTE Installing Maximo and its components requires a valid and active connection
to the Internet.
Application Server
Maximo is built using Java™ 2 Enterprise Edition (J2EE™) technology, which
requires a commercial application server, such as IBM WebSphere. IBM
Corporation uses the term application server to refer to a J2EE container that
provides the infrastructure to run business applications such as Maximo. It
uses the term Application Server (initial capital letters) to refer to an
application server running Maximo.
The Maximo application installs the Active Portal, which enables you to use
the Web to access reports in your Encyclopedia volume and the Management
Console. This web-based capability further enables you to deploy and test
reports on an Encyclopedia volume. You access reports by using a Web
browser (Internet Explorer) to access the Encyclopedia volume through Active
Portal.
T Web Application Archive (WAR) files that contain for example, JSP or
HTML pages
T Java Enterprise Application (JAR) files that contain class files and other
programming code modules
T Enterprise Java Bean (EJB) files that contain class files
Introduction 1-3
Understanding the Maximo Components
Context is the name through which you access a specific web application, such
as Maximo deployed on an Application Server. Maximo has the following
contexts:
You access Maximo from the browser using the /maximo context.
T Maximo creates three EAR files from the contents placed on your local
drive as part of the Maximo installation process:
T To run Maximo, you use your Application Server software (such as IBM
WebSphere), to deploy the Maximo application EAR files in the
Application Server.
T After you deploy Maximo application EAR files in the Application Server,
the server maintains its own copy of the EAR files in the Application
Server software folder structure. The Application Server uses this copy
when running and does not access the EAR files from the Maximo root
folder.
T To make configuration changes to Maximo, you must edit the EAR files,
and then rebuild and redeploy them.
Actuate iServer
WAR files acweb.ear
JAR files
JSP Technology Maximo applications use JSP™ technology. The Application Server, such as
the IBM WebSphere server, accepts HTTP requests from client programs (web
browsers) and responds in HTML content.
When a client requests a JSP page, the application server processes the JSP
page, and the web server sends the result of the JSP page in HTML content
back to the client. Refer to the
http://java.sun.com/products/jsp/ index.html link for more information about
JSP Technology.
XML Technology Maximo applications uses XML files to render the layout and creation of the
user interface.
EJB Technology EJB technology enables rapid and simplified development of distributed,
transactional, secure and portable applications based on Java technology.
Additional Information If you have an active Annual Customer Service Plan (ACSP) agreement with
IBM Corporation, you can access the Support Online Web site:
support.mro.com
To create a Support Online user account, you will need your IBM Corporation
product serial number.
Introduction 1-5
Understanding the Maximo Components
Maximo supports other reporting tools as well. (If you choose not to use
Actuate, skip the Actuate references when you install Maximo in Chapter 4.)
Database Server
A Maximo installation using IBM WebSphere application server software is
compatible with the following database software: IBM DB2® Universal
DataBase (UDB), Microsoft® SQL Server, and Oracle®. See “Hardware and
Software Considerations”, on page 7 for a complete listing of supported
hardware and software releases, and exceptions.
The following table lists supported hardware and software for Maximo release
6.2.1.
Database Server: T Refer to vendor specifications T IBM DB2 Universal Database 8.2.7
(configured for TCP/IP support)
T Oracle 9.2.0.6 or 10.2.0.2 server software
T Microsoft SQL Server 2000 SP4
T Microsoft SQL Server 2005
Introduction 1-7
Hardware and Software Considerations
For additional tuning and configuration information, refer to the IBM Maximo
System Administrator’s Guide.
The Oracle and SQL Server items mentioned in the above list refer to either
the Standard or Enterprise editions of the software.
Installation Roadmap
CAUTION Existing Maximo 6.x customers can overwrite files and data when following
the standard installation procedures. If you are an existing Maximo 6.x
customer, refer to the IBM Maximo 6.2.1 Release Notes on the Support Online
Web site for your specific installation instructions.
Introduction 1-9
Installation Roadmap
The Maximo installation process requires that you complete the procedures in
the order they appear in the following roadmap:
The following diagram illustrates the software components and the order in
which you must install them for a successful Maximo system installation:
T Install the Refresh Pack for the application server, HTTP server, and the
Plugins.
T Install the fix Pack for the application server, HTTP Server, the Plugins,
and the Java JDK.
You must log on as a member of the administrator group to install the product
successfully. Some steps of the installation on a Microsoft Windows platform
require the administrator group user to have the following advanced user
rights:
Leave this window open — you will refer back to it to install the IBM
HTTP Server later in this chapter.
5 Select the I accept the terms in the license agreement option. Click
Next.
Important Spaces (such as the one in \Program Files) are not supported in the name
of the installation directory.
c:\WebSphere\Appserver
c:\IBMHttpServer
c:\WebSphere\Appserver
c:\IBMHttpServer
10 Select the Launch the Profile creation wizard check box. Click Next.
<Node_name>
<Host_name>
5 Accept the default values or specify the Node name, Host name, and
Cell name. Click Next.
6 Review the assigned port numbers. Click Next. Note the Administrative
port number. You will use this context when invoking the Console via a
browser (unless you specify another port number later in this chapter and
Chapter 8).
7 Select the Run the Application Server as a Windows service and log
on as a local system account. Click Next.
9 Select the Launch the First steps console option. Click Finish.
12 Use the launchpad command and click the Profile creation wizard to
open the First Steps window (if not open already) .
4 Specify a unique Profile name and select the Make this profile the
default check box. Click Next.
6 Specify a unique node name and the computer name (or IP address) of the
machine where you are performing this installation. Click Next.
9 Select the Launch the First steps console check box. Click Finish.
Leave the Launchpad window open. You will need it in the next section.
Install the IBM HTTP Server, on the same machine as the application server.
It provides a more robust Web server environment. Also, this type of
installation supports rigorous testing environment or production
environments that do not require a firewall.
To install the IBM HTTP Server on the same machine where you have
installed the Network Deployment product, complete the following steps:
1 From the Launchpad ND window open on your desktop, click Launch the
installation wizard for IBM HTTP Server.
<user_id>
username
7 Click Next.
9 Click Next.
The Plug-in installation wizard for version 6 opens. Continue with the
following section.
1 Clear both check boxes in the Welcome dialog box. Click Next.
8 The Wizard does not default to the location of the httpd.conf file. You
must click the Browse button to select the following location:
<drive_letter>:\IBM HTTP Server\conf\httpd.conf
Accept the default Web server port number: 80. Click Next.
C:\IBMHTTPSERVER\conf\httpd.conf
9 Accept the default name or specify a unique sever definition name. Click
Next.
11 Click Next.
12 Click Next.
13 Click Next.
in step 15.
14 Click Finish.
4 Allow for the process to complete and close the command prompt window.
5 Close the command prompt, the Launchpad window, the IE session, and
all other IBM-related windows that are open at this time.
IBM WebSphere Application From the Services panel, select the IBM Deployment Manager
Server V6 - Deployment Manager service name, right click, and stop it.
To update to IBM WebSphere 6.0.2, you perform preparation steps, copy and
extract a platform-specific file from the Refresh Pack CD-ROM to the required
directory, run an executable file, and use the Install Wizard. You repeat this
process for each of the three Refresh-Pack files (listed below) needed for your
platform. Once completed, this process updates the core WebSphere
Application Server, the HTTP Server, and the HTTP Server Plugins to release
6.0.2.
The Files that You Extract from the IBM The Directory where You unzip The Executable file that
WebSphere Refresh Pack CD-ROM the Refresh Pack Files You Run
NOTE Do not start any of the IBM WebShpere services until you have completed
all the steps in this chapter.
9 Change directory to
<drive_letter>:\IBM\WebSphere\AppServer\updateinstaller.
11 Click Next in the IBM Update Installer for WebSphere Software Welcome
dialog box.
14 Accept the default path of the maintenance package and click Next.
15 Click Next to copy the JDK. Allow for the JDK-copying process to
complete.
18 Accept the default path of the maintenance package to install and click
Next.
21 Read the Wizard panel text to verify successful installation of 6.0.2.0 and
then click Finish. The Refresh Pack (6.0.2) Core Application Server Patch
installation process is complete.
Now proceed to the next section to install the Refresh Pack for IBM
WebSphere HTTP Server Patch (6.0.2).
3 Change directory to
<drive_letter>:\IBMHTTPServer \updateinstaller.
5 Click Next in the IBM Update Installer for WebSphere Software Welcome
dialog box.
8 Accept the default path to the maintenance package file and click Next.
9 Read the Wizard panel text to verify you are installing the 6.0.2 Refresh
Pack for the IBM HTTP Server and click Next to begin the installation.
10 Allow for the JDK-copying process to complete. (The panel displays the
message: Backing up component prereq.ihs.)
11 Read the Wizard panel text to verify successful installation of 6.0.2.0 and
then click Finish. The Refresh Pack (6.0.2) HTTP Server Patch
installation process is complete.
Now proceed to the next section to install the Refresh Pack for IBM
WebSphere Application Server Plugin Patch (6.0.2).
3 Change directory to
<drive_letter>:\IBM\WebSphere\Plugins\updateinstaller.
5 Click Next in the IBM Update Installer for WebSphere Software Welcome
dialog box.
8 Accept the default path to the maintenance package file and click Next.
9 Click Next to copy the JDK. Allow for the JDK-copying process to
complete.
12 Accept the default path to the maintenance package file and click Next.
13 Read the Wizard panel text to verify you are installing the 6.0.2.0 Refresh
Pack for the IBM HTTP Server Plugins patch and click Next to begin the
installation. The file-copying process starts.
14 Allow for the JDK to finish copying. Read the Wizard panel text to verify
successful installation of 6.0.2.0 and then click Finish. The Refresh Pack
(6.0.2) HTTP Server Plugin Patch installation process is complete.
NOTE Before you proceed to the fix pack installation procedure in the next
section, delete all the updateinstaller folders created in this process.
When updating IBM WebSphere from 6.0.0.x, you cannot update directly to
6.0.2.17. You must first install the Refresh Pack to update to 6.0.2, as
described in the previous section.
For the 6.0.2.17 update, you perform preparation steps, copy and extract a
platform-specific file from the Fix-Pack CD to the required directory, run an
executable file, and interface with the Install Wizard, as described in this
section. You repeat this process for each of the four Fix-Pack files (listed
below) needed for your platform. Once completed, this process updates the
core WebSphere Application Server, HTTP Server, HTTP Server Plugins, and
the JavaSDK to release 6.0.2.17.
The Files that You Extract from the IBM WebSphere The Directory where You unzip The Executable file
Fix Pack CD-ROM the Fix Pack Files that You Run
NOTE Do not start any of the IBM WebShpere services until you have completed
all the steps in this chapter.
8 Change directory to
<drive_letter>:\IBM\WebSphere\AppServer\updateinstaller.
10 Click Next in the IBM Update Installer for WebSphere Software Welcome
dialog box.
13 Accept the default path to the maintenance package file and click Next.
14 Read the Wizard panel text to verify that Fix Pack 6.0.2.17 (FP60217) is
being installed and then click Next to begin the installation.
15 Allow the JDK-copying process to complete. Read the Wizard panel text to
verify successful installation of 6.0.2.17 and then click Finish. The Fix
Pack (6.0.2.17) core Application Server Patch installation process is
complete.
Now proceed to the next section to install the IBM WebSphere Fix Pack
(6.0.2.17) HTTP Server Patch.
NOTE The IBM WebSphere Fix Pack 6.0.2.15 (for the HTTP Server patch) is forward
compatible with all the other Fix Pack 6.0.2.17 installs.
3 Change directory to
<drive_letter>:\IBMHTTPServer\updateinstaller.
5 Click Next in the IBM Update Installer for WebSphere Software Welcome
dialog box.
8 Accept the default path to the maintenance package file and click Next.
9 Read the Wizard panel text to verify that Fix Pack 6.0.2.15 (FP60215) is
being installed, and then click Next to begin the installation.The file
copying process starts. (Wizard text reads: Backing up component:
prereq.ihs.)
10 Allow the JDK-copying process to complete. Read the Wizard panel text to
verify successful installation of 6.0.2.15 and then click Finish. The Fix
Pack (6.0.2.15) HTTP Server Patch installation process is complete.
Now proceed to the next section to install the Fix Pack for IBM WebServer Fix
Pack (6.0.2.17) Application Server Plugin Patch.
3 Change directory to
<drive_letter>:\IBM\WebSphere\Plugins\updateinstaller.
5 Click Next in the IBM Update Installer for WebSphere Software Welcome
dialog box.
8 Accept the default path to the maintenance package file and click Next.
9 Read the Wizard panel text to verify that Fix Pack 6.0.2.17 (FP60217) for
the Plugin is about to be installed and then click Next to begin the
installation.
10 Allow the file-copying process to complete. Read the Wizard panel text to
verify successful installation of Plugin 6.0.2.17 and then click Finish. The
Fix Pack (6.0.2.17) HTTP Server Patch installation process is complete.
Now proceed to the next section to install the IBM WebSphere Fix Pack
(6.0.2.17) JavaSDK Patch.
3 Change directory to
<drive_letter>:\IBM\WebSphere\AppServer\updateinstaller.
5 Click Next in the IBM Update Installer for WebSphere Software Welcome
dialog box.
8 Accept the default path to the maintenance package file and click Next.
9 Read the Wizard panel text to verify that Fix Pack 6.0.2.17 (FP60217) for
the JavaSDK is being installed and then click Next to begin the
installation.
10 Allow the file-copying process to complete. Read the Wizard panel text to
verify that the JDK successfully copied and click ReLaunch.
The fix pack (6.0.2.17) javasdk patch installation process is now complete,
which completes the IBM WebSphere 6.0.2.17 installation process.
You can now startup the IBM WebSphere and HTTP Servers to verify
successful installation. After which, proceed to the next chapter to install the
Actuate iServer application.
Pre-Installation Procedures
The following sections describe the pre-installation procedures.
DB2 Connectivity
Complete the following steps to ensure connectivity from DB2 to Actuate.
1 If you are installing Actuate on a server that is separate from the DB2
server, install the following DB2 client software on your Actuate Server
before you install Actuate:
Oracle Connectivity
Complete the following steps to ensure connectivity from Oracle to Actuate:
1 f you are installing Actuate on a server that is separate from the DB2
server, install the following DB2 client software on your Actuate Server
before you install Actuate:
3 Create a TNS name for your Maximo connect string as you will need this
information in Step 10 on page 4-2.
NOTE If you are using Oracle 10 server software, you must install the Oracle 9 client
on the Actuate iServer.
You must also create a DSN name for your Maximo connect string as you will
need this information in Step 10 on page 4-2.
2 Insert the Actuate 8 iServer for Windows CD-ROM into the CD drive.
From the \iserver folder on your CD double-click the setup.exe.
5 Select Custom and read the following warning before clicking Next.
8 Click the browse button and navigate to the location of the xml file, in this
example: Actuate_key_18802.xml. This file resides under the root CD
folder on your Actuate Release 8 iServer for Windows CD-ROM. Click
Next.
d:\Actuate_key_18802.xml
9 Accept the default values that appear in your Locale Information dialog
box and click Next.
10 Enter a user that is in the Administrator Group and ensure that both
check-boxes in the Services Profile frame are checked. Click Next.
<actuate_user>
a The host name or the IP address of the machine where you are
installing Actuate iServer.
d The host name or the IP address of the machine where you are
installing Actuate iServer (same as above).
f Click Next.
13 Select Use the default volume and type the computer name or IP
address. Click Next.
Actuate
15 Enter the computer name where requested and accept the default port
numbers. Click Next.
16 Accept the default HTTP port number (8900), or specify another port
number and click Next.
You open the Actuate Administrative console via a browser, using this
port number. For example: http://<actuate_computer>:8900/acadmin
<host name>
Record the port number and the context path that you created.
The above two steps enable system administrators to access, generate, and
manage reports using Actuate’s web-based console.
18 Accept the default values for the program folder and click Next.
Complete the following worksheet by recording certain names and values that
will help you during installation. The page and step numbers in the right
column of the worksheet indicate where you need the requested information.
Maximo-related
Listen Port number Default is 9080 You can either use the
default port number or
specify another. Make a note
or specify another: ___________________ of it, you will need this
number in Chapter 8.
Database-related
Actuate-related
4 Select the desired language from the drop-down list. Selecting a language
only changes the installation screens into that language but does not affect
the underlying files that get installed.
T If your language is not available from the list, select English, and click
OK.
T If it is Japanese or Chinese you must have those fonts installed on your
system.
T For any selected language other than English, that you are installing
on a SQL Server database, you must perform certain post-installation
tasks as described in “Post Installation Tasks” on page 7-5. This
procedure does not apply if you are using an Oracle database.
7 Enter the serial number included in your Maximo license agreement and
click Next.
8 Enter the name of the folder where the installation program will install
Maximo. The default value is C:\Maximo. Click Next.
Database server Enter the DB2 server host Enter the Oracle server Enter the SQL Server host
name
name host name name
Port number 50000 1521 (Default) 1433 (default)
Database name Enter the DB2 database Enter the Oracle system Enter the SQL Server
name identifier database name
Database/Schema Maximo (default) Maximo (default) Maximo (default)
owner
11 Enter the host name of the machine running the SMTP server. Click
Next.
You must enter this in order to run reports. Contact your Network
Administrator if you don’t know the host name of the machine running the
SMTP server.
a If you are using Workflow, enter the e-mail address of the Workflow
Administrator, otherwise, leave it blank.
c Click Next.
13 Enter the host name or IP address and the port number of the machine
where your WebSphere application server is installed. Click Next.
You may either use the default port 9080, and later in Chapter 8, specify
this port number in WebSphere as the default Maximo Port number; or
specify another port number and use that in Chapter 8.
14 If you have purchased the MEA Product Enabler, then check the Enable
Enterprise Adapter check-box, otherwise accept default (unchecked) and
click Next.
15 Accept the default Maximo Server name (MXServer) and click Next.
d Click Next
17 Enter the host name of the Actuate iServer in the Default Volume Name
field. Click Next.
18 Accept the default value that appears in the Actuate Encyclopedia root
name text box (rpt) and click Next.
20 Once the installation is complete, click Next in the Install Complete dialog
box.
CAUTION Ensure that you have installed the required JVM as stated in Chapter 1.
21 Click inside the install dialog box. Select the Check for Updates... box and
click Next.
22 Click Next in the Welcome to PowerUpdate! dialog box. You will see a
Checking for Update dialog box while PowerUpdate searches for updates
to Release 6.2.1.
If no updates are required, you will see the Your Software is Already Up to
Date dialog box. Click Exit to close PowerUpdate.
If updates are available, click Next in the Update Available dialog box to
retrieve the executable with updated files. The program displays a status
message and the Updater Retrieved dialog box when finished.
23 To run the executable, click Next to open the Choose Install Folder dialog
box.
25 Click Done.
NOTE If you are a new customer, the install program closes and you are taken to
support.mro.com. You must create a Maximo support account. Complete
the New Account Creation form, and click Submit.
<Maximo_root>\applications\activeportal\WEB-
INF\classes\com\actuate\ExternalText
27 If you are running DB2, uncomment the following text string by removing
the pound (#) sign:
actuate.externText.JDBCDriverName=com.ibm.db2.jcc.DB2Driver
actuate.externText.JDBCConnectionURL=jdbc:db2://
<database_server_name>:<port_number>/<database_name>
actuate.externText.JDBCDriverName=oracle.jdbc.driver.OracleDriv
er\
actuate.externText.JDBCConnectionURL=jdbc:oracle:thin:@<databas
e_server_name>:<port_number>:<tns_name>
If you are running SQL Server, uncomment the following text string by
removing the pound (#) sign:
actuate.externText.JDBCDriverName=com.inet.tds.TdsDriver
actuate.externText.JDBCConnectionURL=jdbc:inetdae7a:<database_s
erver_name>:<port_number>?database=<database_name>&language=us_
english&nowarnings=true
actuate.externText.username=
Enter the Database Schema owner name you used in Step 10. For
example, enter Maximo.
actuate.externText.password=
Enter the Database Schema password you used in Step 10. For example,
enter Maximo.
actuate.externText.password=
Enter the Schema Owner name you used in Step 10 after “from” and
“.reportlabel.” For example, enter Maximo.
At the end of this string, enter the Schema Owner name you used in Step
10. For example, enter Maximo.
Update charsets.jar
If you install Maximo in a DB2 environment using a Korean locale, you must
complete the following steps before you build the Maximo schema.
T Copy charsets.jar from the DB2 install directory to the Maximo JRE
and application libraries
NOTE To access the charsets.jar file, you must have already installed Maximo and
the Language Utilities (See page 4-11).
Rename charsets.jar to Complete the following steps to rename the charsets.jar file:
charset_Sun.jar
1 Locate charsets.jar in your Maximo JRE library. For example:
c:\<maximo_root>\tools\java\jre\lib\charsets.jar
Copy charsets.jar from DB2 Complete the following steps to copy charsets.jar from the DB2 install
install directory to the directory to the Maximo JRE and application libraries:
Maximo JRE and Maximo
application libraries 1 Locate charsets.jar in your DB2 JRE library. For example:
c:\<DB2_install>\java\jdk\jre\lib\charsets.jar
c:\<maximo_root>\tools\java\jre\lib
c:\<maximo_root>\applications\maximo\lib
By completing the above steps, you have replaced the Sun charsets.jar with
the IBM DB2 charasets.jar. You have also included a copy of this file in the
Maximo application library.
Update the classpaths for Complete the following steps to update the classpaths for buildmaximoear.xml
buildmaximoear.xml and and commonenv.bat.
commonenv.bat files with
charsets.jar 1 Open buildmaximoear.xml in c:\<maximo_root>\deployment in a text
editor.
value=”${maximo.propertiesjarfile}
value=”${maximo.propertiesjarfile}lib/charsets.jar
value=”${maximo.propertiesjarfile} ${maximo.propertiesjarfile}
value=”${maximo.propertiesjarfile} ${maximo.propertiesjarfile}
<exclude name=”lib/charsets.jar”/>
@rem MAXIMO_DB_LIBS
set MAXIMO_DB_LIBS=%MAXIMO_LIB_PATH%\oraclethin.jar;
13 Insert the following text string after the equal (=) sign in Step 12:
%MAXIMO_LIB_PATH%\charsets.jar;
@rem MAXIMO_DB_LIBS
set MAXIMO_DB_LIBS=%MAXIMO_LIB_PATH%\oraclethin.jar;
17 Insert the following text string after the equal (=) sign in Step 16:
%MAXIMO_LIB_PATH%\charsets.jar;
Run maxinst from a DB2 After you finish editing the buildmaximoear.xml and commonenv.bat files,
Command Line Processor and install the product enablers (See page 4-12), you can run maxinst to build
(CLP) window the Maximo schema. See page 5-8 for detailed information on building the
Maximo schema using a DB2 database.
Complete the following steps to open a DB2 Command Line Processor (CLP)
window. You must run maxinst from this window.
1 From your desktop, click Start > Run and type db2cmd to open a DB2 CLP
window.
How to Modify Language-specific JDBC Settings in Maximo for SQL Server Database
NOTE Perform the tasks outlined in this section only if you are installing a non-
English language, and you are using SQL Server database; otherwise, ignore
this section and the post-installation tasks outlined in “Post Installation
Tasks” on page 7-5.
You must modify the JDBC settings in order for Maximo and Actuate
Reporting to work properly with translated databases that contain special
characters. For example: French, Swedish, or double-byte languages such as
Chinese, Japanese and Korean.
There are a total of four files that you must edit. In this section you edit the
maximo.properties file. If are using Actuate as your Reporting tool, then you
must edit the remaining three Actuate-related files as described at the end of
“Post Installation Tasks” on page 7-5.
NOTE If you have multiple instances of Maximo, you must modify all Maximo (or
Actuate) properties files.
Remove the a
Add &charset=<the code> after true
<charset code> is the character set code and depends on the language
that you are using.
Use the following character set codes in the JDBC setting for the primary
languages supported in Maximo:
For example if you have a Japanese database, type Shift_JIS for the
character set.
In this case, you do not need to rebuild and redeploy the maximo.ear file. The
Product Enablers program builds all the necessary EAR files for you and so
the changes that you made to the maximo.properties page in this section is
incorporated in the resulting EAR files. Later in this guide, you are instructed
on how to deploy the EAR files.
However, you must manually rebuild and re-deploy the acweb.ear file because
you modify this file after having built and Deployed it. Therefore, any changes
that you make to the actuate-related properties file in “Post Installation
Tasks” on page 7-5 requires you to manually rebuild and re-deploy the
acweb.ear file.
This program installs language-specific Help files and database scripts. You
install the Language Utilities after Maximo is installed.
1 Insert the IBM Maximo Language Utilities CD-ROM into the CD drive.
3 Select the desired language from the drop-down list. Selecting a language
only changes the installation screens into that language but does not affect
the underlying files that get installed.
T If your language is not available from the list, select English, and click
OK.
T If it is Japanese or Chinese you must have those fonts installed on your
system.
T For any selected language other than English, that you are installing
on a SQL Server database, you must perform certain post-installation
tasks as described in “Post Installation Tasks” on page 7-5. This
procedure does not apply if you are using Oracle database.
5 Verify that the default value (c:\Maximo) is the Maximo Home Directory
and click Next.
7 If you are performing the steps in this Chapter because you are adding
additional languages to an existing Maximo installation, check the Build
maximohelp.ear file check-box and click Next, otherwise accept default
(unchecked) and click Next.
8 Click Done.
The EAR files are built at this time. Complete the following steps:
1 Insert the IBM Maximo Product Enablers CD-ROM into the CD drive.
3 Select the desired language from the drop-down list. Selecting a language
only changes the installation screens into that language but does not affect
the underlying files that get installed.
T If your language is not available from the list, select English, and click
OK.
T If it is Japanese or Chinese you must have those fonts installed on your
system.
T For any selected language other than English, that you are installing
on a SQL Server database, you must perform certain post-installation
tasks as described in “Post Installation Tasks” on page 7-5. This
procedure does not apply if you are using Oracle database.
5 Verify that the default value (c:\Maximo) is the Maximo Home Directory
and click Next.
7 If you are installing additional packages, you must at this time select Yes
and the program will exit allowing you to add the other Product Enablers.
See Appendix C, "Adding Additional Product Enablers."
Three message boxes appear indicating that the EAR files are being built.
Click Done.
After you install the database instance, you configure it (with commands) and
tune it (with parameters) for optimal use with Maximo. The command
examples provided herein are guidelines for changing the standard database
configuration. For more details on Oracle, DB2, or SQL Server configuration
commands, refer to your Oracle, DB2, or SQL Server documentation. The
tuning-parameter examples provided herein are generally recommended by
IBM Corporation, however, the actual parameters required for your
environment might differ depending on server disk space and site
requirements.
The following section explains how to create the Maximo schema using an
Oracle database. If you are using a DB2 database, begin at the section entitled
“DB2”, on page 5-8. If you are using a Microsoft SQL Server database, begin at
the section entitled “Microsoft SQL Server”, on page 5-12.
Oracle
To create the Maximo schema using an Oracle database, perform the following
tasks as described in this section.
If you plan to use a mix of languages that cannot use a single character set,
such as English, Chinese, and Polish, create the database with the Unicode
character set AL32UTF8, which is the only Unicode character set that can be
used with Maximo.
If you create the database with AL32UTF8, or any multi-byte character set,
you must also set the initialization parameter nls_length_semantics=CHAR.
NOTE You do not need to specify a National Character Set. Maximo only supports
Database Character Sets.
If Oracle Text is installed, this command will return the name CTXSYS.
NOTE The instance for Maximo will need at least 100MB of temporary tablespace
and 100MB of undo tablespace.
In addition to using the tuning features above, you can determine optimal
sizing for SGA, PGA, and optimal performance adjustments, by using the
Oracle Enterprise Manager (or a third-party database monitoring and
administration tool) to analyze the database under load.
CAUTION If you have created the database with AL32UTF8 or any multi-byte character
set, you must also set the initialization parameter
nls_length_semantics=CHAR.
T Use related names for Maximo schemas and tablespaces. For example, to
set up a MAXDEMO database, a production database, and a test copy of
the production database, you might choose MAXDEMO, MAXPROD, and
MAXTEST as schema owners and MAXDEMO_DATA, MAXPROD_DATA,
MAXPROD_INDEX, MAXTEST_DATA, and MAXTEST_INDEX as
tablespace names (MAXDEMO has only one tablespace name as splitting
a small demo database has no real advantage).
Determining Maximo T The expected size of your database determines the size of a Maximo
Tablespace Size tablespace, as shown in the following table.
Initial Maximum
T If you plan to create an empty Maximo schema, use the estimated size of
the database, as listed in the previous table.
T To permit growth, you can add another datafile later or use the
AUTOEXTEND option of the CREATE TABLESPACE command.
Command to Create a To create a Maximo tablespace in an Oracle instance, use the following
Maximo Tablespace command:
where:
T <file_name> is the name of the data file. Use the full path of the
server on which the data file exists, including the local drive, and
enclose the full path in single quotes (‘). For example:
‘C:\oracle\oradata\MXES\MAXIMO01.DBF’
T <file_size> is the initial size of the data file (see previous table),
expressed as a number of megabytes (nM). For example, 1000M.
You can customize the storage parameters for the particular database.
T schema — the schema (userid) to own the tables (same value that you
specified in Step 10 on page 4-2)
T data_ts — the name of the table space to hold the Maximo tables (and
indexes if the optional index table space is not used)
T index_ts — the name of the table space to hold the Maximo tables
schema name
password
data_ts tablespace
--To allow Maximo to give Database Access to Maximo Users in Sig. Security, run these:
--grant create user to MAXIMO;
--grant drop user to MAXIMO;
--grant create session to MAXIMO with ADMIN OPTION;
--grant alter user to MAXIMO;
NOTE Ensure that the alter user schema temporary tablespace temp line
reflects your temporary tablespace name.
@”<drive_letter>:\<Maximo_installation_location>\tools\Maximo\e
n\createMaximoES.sql”;
4 Press Enter.
If you would like to create an empty database, use the -imaximo flag. For
example, at the command prompt, instead of just maxinst, type:
maxinst -imaximo
The following table lists the flags that you can use with maxinst.
Flag Description
-d log file directory If using the -l parameter, it will output logfile to the specified directory;
otherwise, it outputs to the MXServer log directory, which typically is
tools\maximo\log.
-f file name Filename for properties file. If not specified, uses maximo.properties.
-i file name Filename of input file (without path or extension). The default filename
is Unlcvt if the -i param is not provided.
-o file name If using the -l parameter, the filename for the logfile.
If not specified, logfile is "Maxinst" + timestamp + ".log".
-u user name Username for database connection. If not specified, uses mxe.db.user
property, or MAXIMO (must be all capital letters).
-x doclink file This parameter fixes the doclink (Attached Documents) file separators.
separators If a UNIX environment is deployed without using this parameter, the
doclinks will not work properly.
CAUTION -S and -T PARAMETERS: Maxinst does not provide a default value for
tablespace.
The -S and the -T PARAMETERS are required. You must always specify the
data and index tablespace names. There is no default value.
CAUTION If MAXINST fails for any reason, you must drop and recreate the Maximo
schema before re-running MAXINST.
DB2
To create the Maximo schema using a DB2 database, perform the following
tasks as described in this section.
Determine and record the following information you need to connect DB2 to
Maximo:
T database name
T DB2 schema and tablespace name (see your DB2 Database Administrator
for the required names)
T User ID and password that enables full read access to the database. (The
user you use to connect Maximo to DB2 must have full access to the DB2
schema and the tablespaces used to store data.)
NOTE If you use Actuate as your reporting tool, enter the Maximo user ID and
password in upper case.
Chinese GBK
Dutch IBM-1252
French IBM-1252
German IBM-1252
Italian IBM-1252
Japanese IBM-943
Korean 1363
Portuguese IBM-1252
Spanish IBM-1252
Swedish IBM-1252
NOTE Run the above bind commands from a DOS command prompt by navigating to
the BND location. For example, C:\IBM\SQLLIB\BDN
Tuning DB2 Configuration Note: IBM Maximo does not provide detailed configuration parameter settings
Parameters for Maximo because there are infinite combinations of data sizes, user counts,
module usages, add-on module usages, system configurations, and
customizations possible in a Maximo system. Your DB2 System Administrator
can help ensure proper tuning of the database configuration parameters:
APP_CTL_HEAP_SZ, LOCKLIST and MAXLOCKS.
database. If you would like to create an empty database, use the -imaximo
flag.
For example, at the command prompt, instead of just maxinst, type: maxinst
-imaximo
The following depicts the various flags that you can use with maxinst.
Flag Description
-d log file directory If using the -l parameter, it will output logfile to the specified directory; otherwise, it
outputs to the MXServer log directory, which typically is tools\maximo\log.
-f file name Filename for properties file. If not specified, uses maximo.properties.
-i file name Filename of input file (without path or extension). The default filename is Unlcvt if
the -i param is not provided.
-o file name If using the -l parameter, the filename for the logfile.
If not specified, logfile is "Maxinst" + timestamp + ".log".
-p password Password for database connection. If not specified, uses mxe.db.password property, or
MAXIMO (must be all capital letters).
-u user name Username for database connection. If not specified, uses mxe.db.user property, or
MAXIMO (must be all capital letters).
-x doclink file This parameter fixes the doclink (Attached Documents) file separators. If a UNIX
separators environment is deployed without using this parameter, the doclinks will not work
properly.
CAUTION -S and -T PARAMETERS: Maxinst does not provide a default value for
tablespace.
The -S and the -T PARAMETERS are required. You must always specify the
data and index tablespace names. There is no default value.
CAUTION If MAXINST fails for any reason, you must drop and recreate the Maximo
schema before re-running MAXINST.
Note: The file, which contains output for each operation performed by the
maxinst.bat file, might be very large (up to 80 MB if the error occurred late in
the maxinst process). Therefore, IBM recommends you use a text editor other
than Notepad to open the file.
3. “Task 3: Create the Maximo User for SQL Server”, on page 5-16.
In the event that you did not install Full-text Search (the resulting value is
zero), you must do so at this time. The following steps provide a general
guideline describing how you can change this and other settings after having
installed SQL Server.
1 Insert the Microsoft SQL Server 2000 CD-ROM onto the server where you
had it installed originally.
2 Navigate through the installation dialog boxes and from the Setup Type
dialog box, select Custom.
1 Open SQL Server Enterprise Manager (from Program Files >> Microsoft
SQL Server).
2 Right Click the Databases folder from the tree view, and select New
Database.
3 In the Database Properties dialog box, in the General tab, specify a unique
database name (for example max602db).
4 From the Data Files tab, change the Space allocated size to 500 (MB) and
check the Automatically grow file check box.
5 If you prefer, from the Transaction Log tab modify the settings to
accommodate your production environment.
6 Click OK.
2 Select the correct database name from the drop-down menu. This is the
value you entered in Step 3 on page 5-14.
Maximo01
sp_addlogin MAXIMO,MAXIMO
go
sp_changedbowner MAXIMO
go
c If you intend to use the Users app to add native database logins and
users, then run the following script:
To finish creating the Maximo schema using a SQL Server database, see
“Task 4: Create the Maximo Database Objects”, on page 5-9.
Before creating the Maximo Application Server, you must create a Windows
Service for the Node Agent.
1 Ensure that the WebSphere related services and processes are running.
See “System Server Administration”, on page A-1.
1 Invoke a browser window (preferably from the machine where you have
installed Maximo) and open the Administrative Console by typing in the
browser address bar: http://<machine_name>:9060/admin
This URL address depicts the default port number (9060) and context
(admin) for the Administrative Console.
You can use any name to log in. Security is not enabled.
You can set security levels for various user privileges. See the IBM
Maximo System Administrator’s Guide for more details.
9060
4 Click New.
Creating the Maximo Application Server and Deploying the EAR Files 6-3
Creating the Maximo Application Server
8 Click Finish.
Creating the Maximo Application Server and Deploying the EAR Files 6-5
Creating the Maximo Application Server
10 Check the Synchronize changes with Nodes check-box and click Save.
This setting specifies the initial memory size (in MB) required to start the
server.
This setting specifies the maximum memory size (in MB) for the server.
Do not set the java heap size so that it exceeds the physical memory (RAM) of
your server. Complete the following steps:
1 From the Servers link in the tree view click Application servers.
3 From the Server Infrastructure group, expand the Java and Process
Management link.
Creating the Maximo Application Server and Deploying the EAR Files 6-7
Creating the Maximo Application Server
6 Scroll down and type 512 for Initial Heap Size and 1024 for Maximum
Heap Size and click OK.
Specify the
memory size
Creating the Maximo Application Server and Deploying the EAR Files 6-9
Creating the Maximo Application Server
8 Check the Synchronize changes with Nodes check-box and click Save.
2 Click New.
Creating the Maximo Application Server and Deploying the EAR Files 6-11
Creating the Maximo Application Server
a Name: com.ibm.websphere.sendredirect.compliance
b Value: 1
d Click Apply.
2 Open the Web Container Settings and click the Web container
transport chains.
Creating the Maximo Application Server and Deploying the EAR Files 6-13
Identify the HTTP Transfer Port Numbers
If you choose to use port number 9080, then continue with the next
section: Creating Virtual Host. Otherwise, continue with the next step to
create another port number. The same port number that you specified on
page 4-1, other than 9080.
c Type the new port number (not the default 9080) that you specified on
page 4-1.
d Click Next.
7 Click Finish.
Creating the Maximo Application Server and Deploying the EAR Files 6-15
Identify the HTTP Transfer Port Numbers
8 Click Save.
9 Check the Synchronize changes with Nodes check-box and click Save.
3 Click New.
Creating the Maximo Application Server and Deploying the EAR Files 6-17
Identify the HTTP Transfer Port Numbers
5 Click Apply.
6 Click Save.
Creating the Maximo Application Server and Deploying the EAR Files 6-19
Identify the HTTP Transfer Port Numbers
10 Click New.
11 Type * (star) for Host Name and type the HTTP port number (by default
80).
12 Click OK.
Type * (star) for Host Name and type the port number that you specified in
Step 6 on page 6-15 for the HTTP port number.
14 Click Apply and then click OK. You must apply this setting before saving
the settings in the next step.
Creating the Maximo Application Server and Deploying the EAR Files 6-21
Identify the HTTP Transfer Port Numbers
Creating the Maximo Application Server and Deploying the EAR Files 6-23
Deploying the EAR Files
b Select both servers that appear in the Clusters and Servers box.
c Click Apply.
d Click Next.
Creating the Maximo Application Server and Deploying the EAR Files 6-25
Deploying the EAR Files
If you are a MEA customer, you will see the following window. Accept the
default settings and click Next to continue. If you are not a MEA customer
you will not see the following screen. Continue with the following step.
Selected by default
Creating the Maximo Application Server and Deploying the EAR Files 6-27
Deploying the EAR Files
c Click Next.
Creating the Maximo Application Server and Deploying the EAR Files 6-29
Deploying the EAR Files
15 Repeat all the steps in this section (Deploying the EAR Files) to deploy
maximohelp.ear and acweb.ear.
16 Expand the Servers link from the tree view and click Application
servers.
17 Select MAXIMOSERVER and click Start. Allow for the Status to change
to a green arrow.
19 Ensure that all three Applications (only Maximo shown here) are running.
20 You may log out of the console at this time and close the browser session.
Creating the Maximo Application Server and Deploying the EAR Files 6-31
Deploying the EAR Files
You must install the Actuate Encyclopedia for Maximo on the same machine
where you installed the Actuate iServer. Before you install the Actuate
Encyclopedia for Maximo, ensure:
T After installing the Actuate Encyclopedia for Maximo, if you selected any
language other than English, and you are connecting to a SQL Server
database, you must modify language-specific JDBC settings, similar to the
procedure at the end of Chapter 4. You must also rebuild and re-deploy the
acweb.ear file before Importing the Encyclopedia.
3 Click Start.
1 From a command prompt change directory to the C:\ drive (or your root
Actuate installation folder).
3 Select the desired language from the drop-down list. Selecting a language
only changes the installation screens into that language but does not affect
the underlying files that get installed.
T If your language is not available from the list, select English, and click
OK.
T If it is Japanese or Chinese you must have those fonts installed on your
system.
T For any selected language other than English, that you are installing
on a SQL Server database, you must perform certain post-installation
tasks as described in this chapter. This procedure does not apply if you
are using Oracle database.
Database server name Enter the DB2 host name Enter the SQL Server host Enter the Oracle host name
name
Port number 50000 (default) 1433 (default) 1521 (default)
Database name Enter the Service name Enter the SQL Server Enter the Oracle system
of the DB2 instance database name identifier
Database owner MAXIMO (default) MAXIMO (default) MAXIMO (default)
Database owner’s MAXIMO (default) MAXIMO (default) MAXIMO (default)
password
10 Click Install.
12 Check the check box in the Update dialog box and click Done.
The PowerUpdate wizard opens. The computer where you are performing
this installation from must be connected to the Internet.
You must modify the JDBC settings in order for Maximo and Actuate
Reporting to work properly with translated databases that contain special
characters. For example: French, Swedish, or double-byte languages such as
Chinese, Japanese and Korean.
<charset code> is the character set code and depends on the language
that you are using.
Use the following character set codes in the JDBC setting for the primary
languages supported in Maximo:
T Portuguese : 8859_1
T Spanish : 8859_1
T Swedish : 8859_1
For example if you have a Japanese database, type Shift_JIS for the
character set.
<Actuate_root_directory>\iServer\bin\com\actuate\ExternalText
NOTE If you have multiple instances of Maximo, complete the steps outlined in this
section for each of the actuatei18ntext_rsseAlias.properties file that you have.
You must now modify the rsse_maximo.properties page, which resides in the
Actuate directory. Complete the following steps:
Remove the a
Add &charset=<the code> after true
<charset code> is the character set code and depends on the language
that you are using.
Use the following character set codes in the JDBC setting for the primary
languages supported in Maximo:
For example if you have a Japanese database, type Shift_JIS for the
character set.
NOTE If you have multiple instances of Maximo, complete the steps outlined in
this section for each of the rsse_maximo.properties files that you have.
6 You must now rebuild and re-deploy the acweb.ear file. Refer to the IBM
Maximo System Administrator’s guide for more details.
If you are installing on systems that use Chinese, Japanese, or Korean system
locale, the acserverconfig.xml file (located in the Actuate iServer directory) is
saved improperly by the Actuate Encyclopedia installation program. The file
name is appended with corrupted characters and a question mark at the
beginning of the file. The result is that the Actuate iServer is unable to read
the file or to startup properly. Complete the following steps to remedy this
issue:
3 Note the corrupted character and a question mark at the beginning of the
file. Remove them and save the file.
3 Login as Administrator.
6 Click OK in the ensuing message box. Wait 1 to 2 minutes for the Stop to
take effect.
9 Open a command prompt and change path to Actuate’s bin directory. For
example: C:\actuate8\iServer\bin
1 To open Maximo login page, launch Internet Explorer and in the URL
address bar type: http://<host_name>:<port_number>/maximo
where
9080
MEA Users
If you have obtained the MEA Product Enabler, you must complete additional
integration steps that are detailed in Chapter 6 of the IBM Maximo Enterprise
Adapter System Administrator’s Guide.
Administration
This Appendix describes how to start and stop various services from the
Services window and also from a command prompt.
You must start the IBM HTTP Server prior to starting IBM WebSphere’s
Network Deployment or the Node Agent servers.
2 From the tree view in the left pane, open the Servers link.
5 Click Start.
1. Click Servers
3. Check box
4. Click Start 2
To stop the server from running, click Stop and the status icon changes to
an x ( ).
http://<machine_name>:<port_number>/ibm/console
http://localhost:9060/ibm/console
3 At the Welcome, please enter your information login screen, enter your
User ID, then click Log in.
This action opens the Welcome screen for the WebSphere Administrative
Console.
4 Click Service Integration > Buses to open the Buses dialog box as
shown below:
NOTE A bus is a group of interconnected servers and clusters that have been
added as members of the bus.
5 Click New to open the Buses > New dialog box where you can add a new
service integration bus.
T Text description of the new bus in the Name field, for example,
meajmsbus.
T Deselect the Secure check box. If you leave this box checked,
meajmsbus inherits the Global Security setting of the cell.
NOTE If you decide to change the High message threshold setting after the
initial configuration, you must open the Additional Properties menu in the
Administrative Console and change the threshold value for each child
configuration.
7 Click Apply to create the new service integration bus. This step
propagates the JMS bus setup to the cluster configuration. Confirm that
build completed screen displays the following:
4 In the Buses > meajmsbus > Bus members dialog box, click Add to open
the Add a new bus member dialog box as shown in the following figure:
5 Click the Server drop-down arrow, and select a server name, for example
QAERP7Node01.server1 to add to the bus.
6 Click Next.
7 Click Finish.
8 Click Save.
The Configuration > General Properties dialog box for the new bus
member, server QAERP7, appears similar to the following:
NOTE A bus destination, for example cqinbd, is a virtual place within a service
integration bus where applications can attach and exchange messages.
5 Leave Queue checked as the destination type, and click Next to open the
Create new queue dialog box.
6 Type cqinbd in the Identifier field and Continuous Queue Inbound in the
Description field, then click Next to open the Create a new queue for
point-to-point messaging dialog box.
The Buses - Add the cqinbd Bus Destination Queue to a Bus Member
7 Select the Bus Member pull-down and choose a server, such as QAERP7...
as the bus member that will store and process messages for the cqinbd bus
destination queue.
The Buses - Confirm the Creation of the cqinbd Bus Destination Queue
9 Review your selections, then click Finish to complete the creation of the
cqinbd bus destination queue.
10 Navigate the path Buses > meajmsbus > Destinations, then click cqinbd
to open the configuration dialog box where you must make the following
changes:
This is the maximum number of times you want the system to process
a failed messaging attempt before forwarding the message to the
exception destination.
11 Click Apply.
12 Click Save.
NOTE A bus destination, for example sqinbd, is a virtual place within a service
integration bus where applications can attach and exchange messages.
5 Leave Queue checked as the destination type, and click Next to open the
Create new queue dialog box.
6 Enter sqinbd in the Identifier field and Sequential Queue Inbound in the
Description field, then click Next to open the Create a new queue for
point-to-point messaging dialog box.
7 Select the Bus Member pull-down and choose a server, such as QAERP7...
as the bus member that will store and process messages for the sqinbd bus
destination queue.
9 Review your selections, then click Finish to complete the creation of the
sqinbd bus destination queue.
10 Navigate the path Buses > meajmsbus > Destinations, then click sqinbd
to open the configuration dialog box where you must make the following
changes:
This is the maximum number of times you want the system to process
a failed messaging attempt before forwarding the message to the
exception destination.
11 Click Apply.
12 Click Save.
NOTE A bus destination, for example sqoutbd, is a virtual place within a service
integration bus where applications can attach and exchange messages.
5 Leave Queue checked as the destination type, and click Next to open the
Create new queue dialog box.
7 Select the Bus Member pull-down and choose a server, such as QAERP7...
as the bus member that will store and process messages for the sqoutbd
bus destination queue.
9 Review your selections, then click Finish to complete the creation of the
sqinbd queue.
10 Navigate the path Buses > meajmsbus > Destinations, then click sqoutbd
to open the configuration dialog box where you must make the following
changes:
This is the maximum number of times you want the system to process
a failed messaging attempt before forwarding the message to the
exception destination.
11 Click Apply.
12 Click Save.
3 Select the Node, (not the cell Manager) and click OK.
5 Click New to complete the General Properties section for the new
connection factory. For example, you minimally need to enter the
information below as shown in the following figure:
T Name – meaconfact
T JNDI name – jms/mro/int/qcf/intqcf
T Bus name – meajmsbus
7 Click Save.
2 Under Destinations, click JMS queue to open the JMS queue dialog box
where you can create a new queue for continuous inbound messages.
3 Click New to complete the General Properties section for the new
continuous inbound messaging queue. For example, you minimally need to
enter the information below as shown in the following figure:
T Name – cqin
T JNDI name – jms/mro/int/queues/cqin
T Bus name – meajmsbus
T Queue name – cqinbd
JMS Providers - Add General Properties for Continuous inbound Queue (cqin)
4 Click OK.
5 Click Save.
2 Under Destinations, click JMS queue to open the JMS queue dialog box
where you can create a new queue for sequential inbound messages.
3 Click New to complete the General Properties section for the new
sequential inbound messaging queue. For example, you minimally need to
enter the following information:
T Name – sqin
T JNDI name – jms/mro/int/queues/sqin
T Bus name – meajmsbus
T Queue name – sqinbd
4 Click OK.
5 Click Save.
2 Under Destinations, click JMS queue to open the JMS queue dialog box
where you can create a new queue for sequential outbound messages.
3 Click New to complete the General Properties section for the new
sequential outbound messaging queue. For example, you minimally need
to enter the following information:
T Name – sqout
T JNDI name – jms/mro/int/queues/sqout
T Bus name – meajmsbus
T Queue name – sqoutbd
4 Click OK.
5 Click Save.
3 Click New to complete the General Properties section for the new JMS
activation specification. For example, you minimally need to enter the
following information:
T Name – meajmsact
T JNDI name – meajmsact
T Destination type – Queue (default)
T Destination JNDI name – jms/mro/int/queues/cqin
T Bus name – meajmsbus
T Maximum batch size – 10
T Maximum concurrent endpoints – 5
The following figure shows the General Properties dialog box (note that
you have to scroll down in the dialog box to view Maximum batch size and
Maximum concurrent endpoints):
JMS Providers - Add General Properties for JMS Activation of the cqin Queue
4 Click OK.
5 Click Save.
7 Ensure to stop all IBM-related processes and daemons. See Appendix A for
more details.
8 You must now restart these processes for the update to take effect.
4 Select the desired language from the drop-down list. Selecting a language
only changes the installation screens into that language but does not affect
the underlying files that get installed.
T If your language is not available from the list, select English, and click
OK.
T If it is Japanese or Chinese you must have those fonts installed on your
system.
T For any selected language other than English, that you are installing
on a SQL Server database, you must perform certain post-installation
tasks as described in “Post Installation Tasks” on page 7-5. This
procedure does not apply if you are using Oracle database.
6 Verify that the default value (c:\Maximo) is the Maximo Home Directory
and click Next.
8 If you are installing additional Product Enablers, select Yes and the
program exits. You must now insert other Product Enabler CD-ROM(s)
that you may have obtained, otherwise select No and click Done.
Three message boxes appear indicating that the EAR files are being built.
4 Wait until the message The request page XML has been generated
displays.
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this
document in other countries. Consult your local IBM representative for
information on the products and services currently available in your area. Any
reference to an IBM product, program, or service is not intended to state or
imply that only that IBM product, program, or service may be used. Any
functionally equivalent product, program, or service that does not infringe any
IBM intellectual property right may be used instead. However, it is the user's
responsibility to evaluate and verify the operation of any non-IBM product,
program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant
you any license to these patents. You can send license inquiries, in writing, to:
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the
purpose of enabling: (i) the exchange of information between independently
created programs and other programs (including this one) and (ii) the mutual
use of the information which has been exchanged, should contact:
IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758 U.S.A.
The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer
Agreement, IBM International Program License Agreement or any equivalent
agreement between us.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include
the names of individuals, companies, brands, and products. All of these names
are fictitious and any similarity to the names and addresses used by an actual
business enterprise is entirely coincidental.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.
Trademarks
AIX, IBM, IBM Corporation, the IBM logo, Tivoli, and WebSphere are
registered trademarks of the International Business Machines Corporation
in the United States, other countries, or both.
Intel, the Intel logo, and Pentium are registered trademarks of the Intel
Corporation in the United States, other countries, or both.
Sun, Sun Microsystems, the Sun logo, and Solaris are trademarks of Sun
Microsystems, Inc.
Notices-3
Notices-4 IBM Maximo: Installation Guide