Errors encountered if the connection factory is not XA enabled

Errors encountered if the connection factory is not XA enabled Problem(Abstract)Only WebLogic environments are affected. Resolving the problemProblem Description: After setting up the MEA, if the connection factory is not XA enabled, you will see the following error:

Message-Driven EJB: JMSContQueueProcessor-1 is unable to connect to the JMS destination: jms/mro/int/queues/cqin. The Error was: [EJB:010112]The Message Driven Bean 'JMSContQueueProcessor-1' is transacted, but the provider defined in the EJB is not transacted. Provider should be transacted if onMessage method in MDB is transacted.>

Solution: To correct the problem, log in to the WebLogic console, and navigate in the left pane to the following: services/jms/connection factories Select the MEA connection factory you created during the installation process. Click on the Transaction tab. Make sure that the checkbox beside the option "XA Connection Factory Enabled" is checked. Save and apply your changes, then restart WebLogic. .

http://www-01.ibm.com/support/docview.wss?uid=swg21261986

Weblogic 9: Security Realms and Deleting Cache

NOTE: We are unable to send the ETX data to NAG standalone system.

If you delete the cache of a standalone instance of maximo, you will have to go recreate any users that were set up... like the maximouser

Ok.. I had to add it to a group called maximousers as well.

Weblogic - STATE is ADMIN mode...UGGGGH!

Here is a running list to help when your server is in the STATE: ADMIN
Check the Error log... it will most of the time tell you whats wrong...

ERROR:
ORA-28000: the account is locked
FIX:
A password may have changed or you lock the schema owner on the database...
Check your maximo.properties file mxe.db.password= and weblogic in your Service>JDBC>Data Sources>NAMEOFSOURCE>Connection Pool>Password:

Node Manager SSL comunication

REF: Thread: Problem whit Node Manager SSL comunication

Also if you dont want your NodeManager to listen over SSL, you can set

SecureListener=false

And also under machines, change the Listen Type to Plain.

Then the communication between Admin Server and NodeManger will not be over SSL.

Good Maximo Links

BEA WebLogic Server® 9.2

BEA WebLogic Server® 9.2 - Administration Console Online Help

Configuring, Starting, and Stopping Node Manager (8.1)