Configuring JMS Buses and queues for Multiple Independent Instances of Maximo using a filestore | MAXIMO Integration Framework (MIF) | MAXIMO Forum

I'm trying to setup a few instances of Maximo on one webshpere server. Maximo is running fine I just need to separate the MEA messages.

I followed this document http://www-01.ibm.com/support/…..3221tivoli and get stuck on step 9. I don't have anything about the activationspecification on any of my deployment steps.

If I continue and install the app things freeze.

In the log it's looking for intjmsbus when it should be looking for intjmsbusdev.

Any ideas?

Hmm… I did that.

From my maximo.ear

<!– MEA MDB–>
  <ejbBindings xmi:type="ejbbnd:MessageDrivenBeanBinding" xmi:id="MessageDrivenBeanBinding_1" activationSpecJndiName="intjmsactdev">
    <enterpriseBean xmi:type="ejb:MessageDriven" href="META-INF/ejb-jar.xml#MessageDriven_JMSContQueueProcessor_1"/>
  </ejbBindings>

<!– MEA MDB for error queue–>
  <ejbBindings xmi:type="ejbbnd:MessageDrivenBeanBinding" xmi:id="MessageDrivenBeanBinding_1" activationSpecJndiName="intjmsacterrdev">
    <enterpriseBean xmi:type="ejb:MessageDriven" href="META-INF/ejb-jar.xml#MessageDriven_JMSContQueueProcessor_2"/>
  </ejbBindings>

Sorry my first post was incorrect. Dealing with this side of websphere is new to me.

I have two Activation specifications: intjmsact, and intjmsactdev

I have two buses: intjmsbus, and intjmsbusdev

The first ear had activationSpecJndiName="intjmsact" and the MEA works like it should.

The second ear, I will call it dev, had activationSpecJndiName="intjmsactdev".

Both Activation specifications have the correct bus selected.

Also I don't know if this was the right way to make this work but I appended dev to all the JNDI names for the bus and queues for my second set.

Was it this link?

http://maximotimes.com/maximo/…..-maximo-7/

I don't know if this is part of my issue or not. From the guide:

Since there will be a new message engine created automatically when this instance is added to the new bus and each message engine must use it's own schema, the schema name on the message engine's data store will need to be changed. The below instructions assume you are using the cloudscape database which is the default for WebSphere.

a. Navigate on the left side in the WebSphere console to Service Integration/buses

b. Bring up your new bus intjmsbus2

c. On the right side, select Message Engines

d. Select the new message engine, and on the right side, select "data store"

e. In the Schema field, change the name of the schema you see in the schema name field. This can be as simple as adding a value to the end of the schema name such as adding the number "2".

I'm using a file store. Can I skip this step?

Nice new photo.

What are you using as store?

When I get to step 'd' is where things diverge. I have an option called "Message Store" but not "Data Store".