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:

[MAXIMO] Importing Reports

Import the reports
Note: Edit the file \reports\birt\tools\reporttools.properties according to your environment configuration.

1. Run the IMPORTREPORTS tool for the LIBRARIES in the command prompt:
\reports\birt\tools\importreports.cmd libraries

2.Run the IMPORTREPORTS tool for the REPORTS in the command prompt:
\reports\birt\tools\importreports.cmd

3.Login to Maximo application

4.Go To Administration -> Reporting -> Report Administration

5.On List tab, click on the “Generate Request pages” button

Note: this process may take a few minutes to complete

Note: If you have more than one instance of maximo on the box, you want to make sure you use the host name or IP of the instance that will access the reports instead of the computername.
reportools.properties

# HostName or IP address of the machine that has MAXIMO application running in an App Server
maximo.report.birt.hostname=IP-ADDRESS
# HTTP port of the application server (the port used to access maximo from browser)
maximo.report.birt.port=80
# Indicates whether the SSL communication is enabled or not
maximo.report.birt.ssl=false
# User that has access to perform the operation
maximo.report.birt.username=maxadmin
# Password of the user that has access to perform the operation
maximo.report.birt.password=##########
# Output folder used for the export operation
maximo.report.birt.outputfolder=./../../birt

View SQL ran in Maximo Logs

GOTO > System Configuration > Platform Configuration > Logging

Search for SQL

Change log4j.logger.maximo.sql Log Level to DEBUG

Log Level:DEBUG
key:log4j.logger.maximo.sql
Inherited Appenders: Console,Rolling

Hit SAVE
then Apply Changes

Import a Report Design File into Maximo

1) GOTO > Administration > Reporting > Reporting Administration

2) Search for and select wms_woprint.rptdesign
3) Select Action Import Report
4) Upload to Report Design File
5) OK on override message
6) OK on the Resource file message

7) Verify all the settings and update them as below

Limit Rec? - checked
Max Rec Limit - 200
Priority - 2
Toolbar Seq - 4
Browser view - checked
Browser loc - ALL
Direct Print - checked
Drct Prnt loc - All
Drct Prnt atch - checked
Drct Prnt atch loc - All

8) Press the Generate Request pages button
9) SAVE

Display Maximo System info in IE title bar

in the Installserver.cmd file edit the following

Use the JVM parameter -Dmxe.name= to name each server, where
is the name that you use to identify the server.

set CMDLINE="%JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath \"%CLASSPATH%\" -Dmxe.name=UI2MAN1-372 -Dweblogic.Name=%SERVER_NAME% -Dweblogic.management.username=%WLS_USER% -Dweblogic.management.server=\"%ADMIN_URL%\" -Dweblogic.ProductionModeEnabled=%PRODUCTION_MODE% -Djava.security.policy=\"%WL_HOME%\server\lib\weblogic.policy\" -Dcom.sun.xml.namespace.QName,useCompatibleSerialVersionUID=1.0 -DJMSQSEQCONSUMER.SEQQOUT1=1 weblogic.Server"

REF:http://www-01.ibm.com/support/docview.wss?uid=swg21366402&aid=4

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)