򔻐򗗠򙳰

ii
Contents
Manually configuring WebSphere Creating the JMS connection factory . . . . . 15
Application Server Network Deployment . 1 Creating the continuous inbound (CQIN) JMS
Performing WebSphere Application Server Network queue . . . . . . . . . . . . . . . 16
Deployment configuration tasks . . . . . . . . 1 Creating the sequential inbound (SQIN) JMS
Creating a Windows service for the node agent . . . 7 queue . . . . . . . . . . . . . . . 17
Manually creating a data source for the persistent Creating the sequential outbound (SQOUT) JMS
store . . . . . . . . . . . . . . . . . 8 queue . . . . . . . . . . . . . . . 18
Manually configuring JMS queues . . . . . . . 10 Creating JMS activation specification for the
Adding a server to the service integration bus . . 11 continuous inbound queue (CQIN) . . . . . 19
Creating the service integration bus destination Error queues . . . . . . . . . . . . . 20
for the continuous inbound (CQINBD) queue . . 12
Creating the service integration bus destination Index . . . . . . . . . . . . . . . 25
for the sequential inbound (SQINBD) queue . . 13
Creating the service integration bus destination
for the sequential outbound (SQOUTBD) queue . 14

iii
iv
Manually configuring WebSphere Application Server Network
Deployment
This section contains instructions for manually configuring an existing WebSphere®
Application Server Network Deployment for use by Maximo Asset Management.

You must manually configure WebSphere Application Server Network Deployment

before you use the Maximo Asset Management installation program if you do not
want the Maximo Asset Management installation program to configure it
automatically.

Performing WebSphere Application Server Network Deployment

configuration tasks
Use this procedure to perform WebSphere Application Server Network
Deployment configuration tasks.

About this task

If you elect to manually configure Maximo Asset Management middleware for use
with Maximo Asset Management, you have to manually configure the WebSphere
Application Server Network Deployment.

Procedure
1. Manually copy the keystore file from the WebSphere Application Server
Network Deployment deployment manager host to a temporary directory on
the Maximo Asset Management administrative system where you are
installing Maximo Asset Management: WAS_HOME/profiles/ctgDmgr01/etc/
trust.p12
2. Open a browser and access the administrative console by typing in the
browser address bar: http://server_name:9060/admin. This URL address
depicts the default port number (9060) and context (admin) for the
administrative console. Enter a user name to log in. The browser is redirected
to a secure port (9043).
3. Create the MXServer application server. This step is only necessary if you did
not install WebSphere Application Server Network Deployment v7 using the
middleware installation program. For WebSphere Application Server Network
Deployment v8, you must create the application server.
a. Expand Servers > Server Types > WebSphere application servers.
b. Click New.
c. Type MXServer and click Next.
d. Accept all default settings and click Next.
e. Accept default settings and click Next.
f. Click Finish.
g. Click Preferences.
h. Select the Synchronize changes with Nodes check box, and then click
Apply.
i. Click Save.
j. Click OK.

1
Figure 1. Manually create the application server

4. Edit JVM Memory Settings and JVM Arguments for the application server.
a. Click MXServer in the main window.
b. From the Server Infrastructure group, expand the Java and Process
Management link.
c. Click Process Definition.
d. Click Java Virtual Machine.
e. For 32-bit platforms, scroll down and type 1536 for Initial Heap Size and
Maximum Heap Size. For 64-bit platforms, set these values to 4096.
f. Enter the following values in the Generic JVM arguments field, using a
space between each argument:
-Dsun.rmi.dgc.ackTimeout=1000
-Xdisableexplicitgc
-Xgcpolicy:gencon
-Xmn320m # 320 for 32-bit JVM, 1024 for 64-bit JVM
-Xlp64k # AIX

2
Figure 2. Manually create the application server

g. Click OK.
h. Click Save in the messages box.
5. Edit thread pool settings for the application server.
a. Click MXServer from the WebSphere application servers panel.
b. From the Additional Properties group, click Thread pools.
c. Click Default. Set Minimum Size to 20. Set Maximum Size to 50. Set
Thread inactivity timeout to 30000. Click OK.
d. Click TCPChannel.DCS. Set Minimum Size to 5. Set Maximum Size to
20. Set Thread inactivity timeout to 5000. Click OK.
e. Click WebContainer. Set Minimum Size to 20. Set Maximum Size to 50.
Set Thread inactivity timeout to 30000. Click OK.

Manually configuring the WebSphere Application Server Network Deployment 3

Figure 3. Edit thread pool settings for the application server

6. Edit JVM Memory Settings for the deployment manager.

a. From System administration, click Deployment manager.
b. From the Server Infrastructure group, expand the Java and Process
Management link.
c. Click Process Definition.
d. Click Java Virtual Machine.
e. Scroll down and type 512 for Initial Heap Size and 1024 for Maximum
Heap Size and click OK.

Figure 4. Edit JVM Memory Settings for the deployment manager

f. Click Save in the messages box.

7. Start the application server.

4
 a. From Servers > Server Types > WebSphere application servers, click
Application servers.
b. Select the check box beside MXServer.
c. Click Start.
8. Identify the HTTP Transfer Port Numbers.
a. Expand Servers > Server Types > WebSphere application servers, and
click MXServer from the main window.
b. Open the Web Container Settings and click Web container transport
chains.
c. Note the default port number as it appears with WCInboundDefault
(9080).

Figure 5. Identify the HTTP Transfer Port Numbers

9. Create the virtual host.

a. Expand Environment.
b. Click Virtual Hosts.
c. Click New.
d. In the General Properties section, type maximo_host in the Name box.
e. Click Apply.
f. Click Save.
g. Click OK.
h. From the Virtual Hosts window, click maximo_host.
i. Click the Host Aliases link.
j. Click New.
k. Type * (asterisk) for host name and type the HTTP port number (by
default 80).
l. Click OK.
m. Click New.
n. Type * (asterisk) for host name and type 9061 for the port number.
o. Click OK.
p. Click New.
q. Type * (asterisk) for host name and type 9443 for the port number.

Manually configuring the WebSphere Application Server Network Deployment 5

 r. Click OK.
s. Click New.
t. Type * (asterisk) for host name and type 9080 for the port number.
u. Click OK.
v. Click New.
w. Type * (asterisk) for host name and type 9044 for the port number.
x. Click OK and then click Save.

Figure 6. Create the virtual host

10. Enable automatic startup of the application server when the node agent is
started.
a. Expand Servers > Server Types > WebSphere application servers.
b. Click MXServer in the main window.
c. From the Server Infrastructure group, expand Java and Process
Management.
d. Click Monitoring Policy.
e. Set Node restart state to RUNNING and click OK.
f. Click Save in the messages box.

6
Figure 7. Enable automatic startup of the application server when the node agent is started

If you used the middleware installation program to install WebSphere

Application Server Network Deployment v7, this step has already been
performed by the middleware installation program.

Creating a Windows service for the node agent

You can create a Windows service for starting the WebSphere Application Server
Network Deployment node agent.

About this task

Although not required, you can optionally start the node agent as a Windows
service.

If you used the middleware installation program to install WebSphere Application

Server Network Deployment v7, this step has already been performed by the
middleware installation program.

Procedure
1. Open a command prompt.
2. Change directory to <WAS_HOME>\bin.
3. Type the following command with no line breaks (case-sensitive).
WASService
-add NodeAgent
-serverName nodeagent
-profilePath "C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01"
-wasHome "C:\IBM\WebSphere\AppServer"
-logRoot "C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs\nodeagent"
-logFile "C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs\nodeagent\
startServer.log"
-restart true
4. Close the Command Prompt.

Manually configuring the WebSphere Application Server Network Deployment 7

Manually creating a data source for the persistent store
If you chose to manually configure WebSphere Application Server Network
Deployment, you must create a data source in order to store JMS messages in a
DB2® database.

About this task

You have the option of having WebSphere Application Server Network

Deployment use a DB2 database to store JMS messages. For more information
about WebSphere Application Server Network Deployment message storage,
including the usage of products other than DB2, see http://
publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/
com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/tjm0045_.html.

To create a data source for the persistent store, complete the following steps:

Procedure
1. Create a system user and password on the server hosting the database server.
For example, a user named mxsibusr with a password of mxsibusr.
2. Create and configure the database.
a. Open DB2 Control Center.
b. Browse to the Databases folder listed under your system.
c. Right-click the Databases folder and select Create Database > Standard.
d. Create a database named maxsibdb using default settings.
e. After the database has been created, expand the maxsibdb database and
select User and Group objects.
f. Right-click DB Users and select Add.
g. Select mxsibusr from the User menu.
h. Grant all authorities to the mxsibusr except Security administrator authority.
i. Click Apply.
j. Verify that you can connect to the database using the mxsibusr user by
right-clicking maxsibdb and selecting Connect.
3. Configure J2C authentication data and JDBC provider in WebSphere
Application Server Network Deployment.
a. Open and login to the WebSphere Application Server Network Deployment
administrative console.
b. Browse to Security > Global Security.
c. Under the Authentication header, click Java Authentication and
Authorization Service > J2C authentication data.
d. Click New.
e. Complete the following fields in the User identity form.
Alias maxJaasAlias
User ID
mxsibusr
Password
Password you created for mxsibusr.
Description
SIB database user alias.

8
 f. Click Apply, and then click Save.
g. From the WebSphere Application Server administrative console, browse to
Resources > JDBC > JDBC Providers.
h. Under Scope, click Show scope selection drop-down list with the all
scopes option, select Cell=ctgCell01, and then, under Preferences, click
Apply.
i. Click New.
j. Specify the following values, and then click Apply:
Database type
DB2
Provider type
DB2 Universal JDBC Driver Provider
Implementation type
XA data source
Name maxJdbcProvider
k. Click Next.
l. Complete the WebSphere Application Server variable
${DB2UNIVERSAL_JDBC_DRIVER_PATH} field with a value of
<WAS_HOME>ctgMX\lib. For example, C:\Program Files\IBM\WebSphere\
AppServer\ctgMX\lib.
m. Click Next.

Figure 8. Create a new JDBC provider

n. Click Finish.
o. Click Save.
4. Open a command prompt and copy <DB2_HOME>/java/db2jcc.jar and
<DB2_HOME>/java/db2jcc_license_cu.jar to the <WAS_HOME>\ctgMX\lib
directory. Go back to Resources > JDBC > JDBC Providers >
maxJdbcProvider, and correct the class path if required for both db2jcc.jar
and db2jcc_license_cu.jar. Ensure that each jar file has the full path from
${DB2UNIVERSAL_JDBC_DRIVER_PATH}
5. Configure WebSphere Application Server:

Manually configuring the WebSphere Application Server Network Deployment 9

 a. From the WebSphere Application Server Network Deployment
administrative console, browse to Resources > JDBC > Data sources.
b. Under Scope, click Show scope selection drop-down list with the all
scopes option, select Cell=ctgCell01, and then, under Preferences, click
Apply.
c. Click New.
d. Specify the following values:
Data source name
intjmsds
JNDI name
jdbc/intjmsds
e. From the Component-managed authentication alias and XA recovery
authentication alias menu, select maxJaasAlias
f. Click Next.
g. Choose Select an existing JDBC provider, and then select maxJdbcProvider
from the menu.
h. Click Next.
i. Specify the following values:
Database name
maxsibdb
Driver type
4
Server name
Specify the DB2 server host name.
Port number
Specify the DB2 port number. For example, 50005.
j. Ensure the Use this data source in container managed persistence (CMP)
option is selected, and then click Next.
k. Click Finish.
l. Click Save.
6. Verify the data source by selecting intjmsds, and then clicking Test
Connection.

Manually configuring JMS queues

This procedure provides details on steps to configure JMS queues, which must be
completed before using the product installation program.

About this task

During the installation process, the Maximo Asset Management installation

program provides you with the option of automatically configuring Maximo Asset
Management middleware. If you elect to have the Maximo Asset Management
installation program automatically configure Maximo Asset Management
middleware, it creates and configures JMS message queues for you. If you elect to
manually configure Maximo Asset Management middleware for use with Maximo
Asset Management, you must manually configure these message queues.

To configure the JMS queues, complete the following steps:

10
 Procedure
1. Start the WebSphere Application Server Network Deployment application
server.
2. Start Internet Explorer and open the WebSphere Application Server Network
Deployment administrative console by typing the following URL:
http://<server_name>:<port_number>/ibm/console
For example, enter a URL like the following sample URL:
http://localhost:9060/ibm/console
3. At the login screen, enter your user ID, then click Log in. This action opens
the Welcome screen for the WebSphere Application Server Network
Deployment administrative console.
4. Click Service Integration > Buses to open the Buses dialog. 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 Create a new Service Integration Bus panel where
you can add a new service integration bus.
6. Enter intjmsbus as the name of the new bus in the Name field.
7. Clear the Bus security check box. If you leave this box checked, intjmsbus
inherits the Global Security setting of the cell.

Figure 9. Create a new Service Integration Bus

8. Click Next.
9. Click Finish.
10. Click Save. This step propagates the JMS bus setup to the cluster
configuration.

Adding a server to the service integration bus

A server must be defined for the service integration bus.

About this task

Complete the following steps to add a server to the service integration bus:

Procedure
1. From the WebSphere Application Server Network Deployment administrative
console, click Service Integration > Buses to open the Buses dialog box.
2. Click intjmsbus to open the Buses > intjmsbus dialog box.
3. Under Topology, click Bus members.
4. In the Buses > intjmsbus > Bus members dialog box, click Add to open the
Add a new bus member dialog box.

Manually configuring the WebSphere Application Server Network Deployment 11

 5. Select the Server option, and select the server name ctgNode01:MXServer to
add to the bus, and then click Next.
6. Check that the Data store radio button is selected, and then click Next.
Alternatively, you can use a file store to store messages by selecting File store.
7. From the Specify data store properties panel, select Use existing data source.
8. For Data source JNDI name , enter jdbc/intjmsds. For Authentication alias,
select ctgCellManager01/maxJaasAlias, and then click Next.
9. From the Tune application server for messaging performance panel, click
Next.
10. Click Finish.
11. Click Save.

Figure 10. Add a server to the service integration bus

Creating the service integration bus destination for the

continuous inbound (CQINBD) queue
You must create a service integration bus destination for the continuous inbound
(CQINBD) queue.

About this task

To add a logical address for the continuous inbound bus destination queue
(CQINBD) within the JMS bus, complete the following steps:

Procedure
1. From the WebSphere Application Server Network Deployment Administrative
Console, click Service Integration > Buses to open the Buses dialog box.
2. Click intjmsbus to open the Buses > intjmsbus dialog box.
3. Click Destinations under Destination resources to open the Buses >
intjmsbus > Destinations dialog box.
A bus destination, for example CQINBD, is a virtual place within a service
integration bus where applications can attach and exchange messages.
4. Click New to open the Create new destination dialog box.
5. Leave Queue checked as the destination type, and click Next to open the
Create new queue dialog box.

12
 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.
7. Select the Bus Member pull-down and choose
Node=ctgNode01:Server=MXServer as the bus member that will store and
process messages for the CQINBD bus destination queue.
8. Click Next to open the Confirm queue creation dialog box.
9. Review your selections, then click Finish to complete the creation of the
CQINBD bus destination queue.
10. Navigate the path Buses > intjmsbus > Destinations, then click CQINBD to
open the configuration dialog box.
11. Click None as the Exception destination value.
12. Click Apply.
13. Click Save.

Figure 11. Add a logical address for the continuous inbound bus destination queue

Creating the service integration bus destination for the

sequential inbound (SQINBD) queue
You must create the service integration bus destination for the sequential inbound
(SQINBD) queue.

About this task

To add a logical address for the sequential inbound bus destination queue
(SQINBD) within the service integration bus, complete the following steps:

Procedure
1. From the WebSphere Application Server Network Deployment Administrative
Console, click Service Integration > Buses to open the Buses dialog box.
2. Click intjmsbus to open the Buses > intjmsbus dialog box.
3. Click Destinations under Destination resources to open the Buses >
intjmsbus > Destinations dialog box. A bus destination is a virtual place
within a service integration bus where applications can attach and exchange
messages.
4. Click New to open the Create new destination dialog box.

Manually configuring the WebSphere Application Server Network Deployment 13

 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. Note that you must use this value and it
must contain only uppercase letters.
7. Select the Bus Member pull-down and choose
Node=ctgNode01:Server=MXServer
8. Click Next to open the Confirm queue creation dialog box.
9. Review your selections, then click Finish to complete the creation of the
SQINBD bus destination queue.
10. Navigate the path Buses > intjmsbus > Destinations, then click SQINBD to
open the configuration dialog box.
11. Click None as the Exception destination value.
12. Click Apply.
13. Click Save.

Figure 12. Add a logical address for the sequential inbound bus destination queue

Creating the service integration bus destination for the

sequential outbound (SQOUTBD) queue
You must create the service integration bus destination for the sequential outbound
(SQOUTBD) queue.

About this task

To add a logical address for the sequential outbound bus destination queue
(SQOUTBD) within the service integration bus, complete the following steps:

Procedure
1. From the WebSphere Application Server Network Deployment administrative
console, click Service Integration > Buses to open the Buses dialog box.
2. Click intjmsbus to open the Buses > intjmsbus dialog box.
3. Click Destinations under Destination resources to open the Buses >
intjmsbus > Destinations dialog box. A bus destination, for example
SQOUTBD, is a virtual place within a service integration bus where
applications can attach and exchange messages.

14
 4. Click New to open the Create new destination dialog box.
5. Leave Queue checked as the destination type, and click Next to open the
Create new queue dialog box.
6. Enter SQOUTBD in the Identifier field and Sequential Queue Outbound in the
Description field, then click Next to open the Create a new queue for
point-to-point messaging dialog box. You must use this value and it must
contain only uppercase letters.
7. Select the Bus Member menu and choose Node=ctgNode01:Server=MXServer
as the bus member that stores and processes messages for the SQOUTBD bus
destination queue.
8. Click Next to open the Confirm queue creation dialog box.
9. Review your selections, then click Finish to complete the creation of the
queue.
10. Navigate the path Buses > intjmsbus > Destinations, then click SQOUTBD
to open the configuration dialog box where you must make the following
changes:
11. Click None as the Exception destination value.
12. Click Apply.
13. Click Save.

Creating the JMS connection factory

Add a connection factory for creating connections to the associated JMS provider
of point-to-point messaging queues.

About this task

To create the JMS connection factory, complete the following steps:

Procedure
1. From the WebSphere Application Server Network Deployment administrative
console, click Resources > JMS > Connection factories.
2. From the Scope drop-down list, select Cell=ctgCell01.
3. Click New.
4. Verify that the Default Messaging Provider is selected and click OK.
5. Enter the following information:
Name Enter intjmsconfact.
JNDI name
Enter jms/maximo/int/cf/intcf.
Bus name
Select intjmsbus.

Manually configuring the WebSphere Application Server Network Deployment 15

Figure 13. Create the JMS connection factory

6. Click Apply.
7. Click Save.

Creating the continuous inbound (CQIN) JMS queue

You must create a JMS queue (CQIN) as the destination for continuous inbound
point-to-point messages.

About this task

To create the CQIN JMS queue, complete the following steps:

Procedure
1. From the WebSphere Application Server Network Deployment administrative
console, click Resources > JMS > Queues.
2. From the Scope drop-down list, select Cell=ctgCell01.
3. Click New.
4. Verify that the Default Messaging Provider is selected and click OK.
5. Enter the following information, and click OK.
Name Enter CQIN.
This value must contain only uppercase letters.
JNDI name
Enter jms/maximo/int/queues/cqin
Bus name
Select intjmsbus.

16
 Queue name
Select CQINBD.

Figure 14. Create the CQIN JMS queue

6. Click OK.
7. Click Save.

Creating the sequential inbound (SQIN) JMS queue

You must create a JMS queue (SQIN) as the destination for sequential inbound
point-to-point messages.

About this task

To create the SQIN JMS queue, complete the following steps:

Procedure
1. From the WebSphere Application Server Network Deployment administrative
console, click Resources > JMS > Queues.
2. From the Scope drop-down list, select Cell=ctgCell01.
3. Click New.
4. Verify that the Default Messaging Provider is selected and click OK.
5. Enter the following information, and click OK.
Name Enter SQIN.
This value must contain only uppercase letters.
JNDI name
Enter jms/maximo/int/queues/sqin
Bus name
Select intjmsbus.

Manually configuring the WebSphere Application Server Network Deployment 17

 Queue name
Select SQINBD.

Figure 15. Create the SQIN JMS queue

6. Click OK.
7. Click Save.

Creating the sequential outbound (SQOUT) JMS queue

You must create a JMS queue (SQOUT) as the destination for sequential outbound
point-to-point messages.

About this task

To create the SQOUT JMS queue, complete the following steps:

Procedure
1. From the WebSphere Application Server Network Deployment administrative
console, click Resources > JMS > Queues.
2. From the Scope drop-down list, select Cell=ctgCell01.
3. Click New.
4. Verify that the Default Messaging Provider is selected and click OK.
5. Enter the following information, and click OK.
Name Enter SQOUT.
This value must contain only uppercase letters.
JNDI name
Enter jms/maximo/int/queues/sqout
Bus name
Select intjmsbus.

18
 Queue name
Select SQOUTBD.

Figure 16. Create the SQOUT JMS queue

6. Click OK.
7. Click Save.

Creating JMS activation specification for the continuous

inbound queue (CQIN)
You must activate the continuous inbound queue (CQIN) before it can receive
messages.

About this task

Complete the following steps to activate the CQIN queue:

Procedure
1. From the WebSphere Application Server Network Deployment administrative
console, click Resources > JMS > Activation Specifications.
2. From the Scope drop-down list, select Cell=ctgCell01.
3. Click New.
4. Select Default messaging provider and then click OK.
5. Enter the following information, and then click OK.
Name intjmsact
This value is case-sensitive. This value must be lowercase.
JNDI name
intjmsact

Manually configuring the WebSphere Application Server Network Deployment 19

 Destination type
Queue
Destination JNDI name
jms/maximo/int/queues/cqin
Bus name
intjmsbus
Maximum concurrent MDB invocations per endpoint
10

Figure 17. Activate the CQIN queue

6. Click OK, and then click Save.

Error queues
You must create an error queue that receives redirected messages from the
continuous queue (CQIN).

When the messages go in error, the error queue receives redirected messages from
the continuous queue (CQIN).

Creating the service integration bus destination for the inbound

error queue (CQINERRBD) queue
You must add a logical address for the inbound error queue (CQINERRBD) queue
within the JMS bus.

About this task

Perform the following steps:

20
 Procedure
1. From the WebSphere Application Server Network Deployment administrative
console, click Service Integration > Buses to open the Buses dialog box.
2. Click intjmsbus to open the Buses > intjmsbus dialog box.
3. Click Destinations under Destination resources to open the Buses >
intjmsbus > Destinations dialog box. A bus destination is a virtual place
within a service integration bus where applications can attach and exchange
messages.
4. Click New to open the Create new destination dialog box.
5. Leave Queue checked as the destination type, and click Next to open the
Create new queue dialog box.
6. Enter CQINERRBD in the Identifier field and Error Queue Inbound in the
Description field, then click Next to open the Create a new queue for
point-to-point messaging dialog box. You must use this value and it must
contain only uppercase letters.
7. From the Bus Member menu, select Node=ctgNode01:Server=MXServer
8. Click Next to open the Confirm queue creation dialog box.
9. Review your selections, then click Finish to create the CQINERRBD bus
destination queue.
10. Select Buses > intjmsbus > Destinations, then click CQINERRBD to open the
configuration dialog box where you must make the following changes:
a. Select the Specify option and enter CQINERRBD as the exception destination
value.
b. Change the Maximum failed deliveries value to 5.
This option is the maximum number of times you want the system to
process a failed messaging attempt before forwarding the message to the
exception destination.

Figure 18. Creating the service integration bus destination for the inbound error queue

11. Click Apply.

12. Click Save.
13. From the WebSphere Application Server Network Deployment administrative
console, click Service Integration > Buses to open the Buses dialog box.
14. Click intjmsbus to open the Buses > intjmsbus dialog box.

Manually configuring the WebSphere Application Server Network Deployment 21

 15. Click Destinations under Destination resources to open the Buses >
intjmsbus > Destinations dialog box.
16. Select CQINBD.
17. Specify CQINERRBD as the exception destination. Set the Maximum failed
deliveries value to 5.

Figure 19. Set the exception destination

18. Click OK.

19. Click Save.

Creating the error (CQINERR) JMS queue

After creating the Error Queue Bus Destination, you create the Error queue.

About this task

To create the Error queue, complete the following steps.

Procedure
1. From the WebSphere Application Server Network Deployment administrative
console, click Resources > JMS > Queues.
2. From the Scope drop-down list, select Cell=ctgCell01.
3. Click New.
4. Verify that the Default Messaging Provider is selected and click OK.
5. Enter the following information, and click OK.
Name Enter CQINERR.
This value must contain only uppercase letters.

22
 JNDI name
Enter jms/maximo/int/queues/cqinerr
Bus name
Select intjmsbus.
Queue name
Select CQINERRBD.

Figure 20. Create the Error queue

6. Click OK.
7. Click Save.

Creating JMS activation specification for the inbound error

queue (CQINERR)
You must activate the continuous inbound queue (CQINERR) before it can receive
messages.

About this task

Complete the following steps to activate the CQINERR queue:

Procedure
1. From the WebSphere Application Server Network Deployment administrative
console, click Resources > JMS > Activation Specifications.
2. From the Scope menu, select Cell=ctgCell01, and then click Apply.
3. Click New to complete the General Properties section for the new JMS
activation specification.
4. Click OK.
5. Enter the following information, and click OK.
Name Enter intjmsacterr.

Manually configuring the WebSphere Application Server Network Deployment 23

 This value must only contain lowercase letters.
JNDI name
Enter intjmsacterr.
This value must be the same as the one used for the Name field.
Destination type
Enter Queue.
Destination JNDI name
jms/maximo/int/queues/cqinerr
Bus name
intjmsbus
Maximum concurrent MDB invocations per endpoint
10

Figure 21. Activate the continuous inbound queue

6. Click OK.
7. Click Save.
8. Ensure that you stop all IBM-related processes and daemons.
9. You must now restart these processes for the update to take effect.
10. Start the bus member for the ctgNode MXServer intjmsbus if it is not started.
If you cannot start ctgNode MXServer intjmsbus, restart MXServer under
Servers > Application servers.

24
Index
C J sequential outbound (SQOUT) JMS queue
creating 18
continuous inbound (CQIN) JMS queue JMS activation specification service integration bus
creating 16 creating for the continuous inbound adding a server 11
CQINERR JMS queue queue (CQIN) 19 service integration bus destination
creating 22 creating for the inbound error queue creating for the continuous inbound
(CQINERR) 23 (CQINBD) queue 12
JMS connection factory creating for the inbound error queue
D creating 15
JMS queues
(CQINERRBD) queue 20
data source creating for the sequential inbound
manually configure 10 (SQINBD) queue 13
manually creating for the persistent
store 8 creating for the sequential outbound
(SQOUTBD) queue 14
N
E node agent
error queue 20
creating as a Windows service 7 W
WebSphere Application Server Network
Deployment
S configuration tasks 1
sequential inbound (SQIN) JMS queue manually configuring 1
creating 17

25