Friday, January 30, 2015

Maximo Rebuild and Redploy EAR


1 Ensure that no database configuration changes are pending.
2 Shut down the Maximo application server.
3 Back up the database.
4 Back up the C:\IBM\SMP\maximo.
5 Take Comodo Snapshot backup
6 Extract the files to a folder
7 Copy all files to C:\IBM\SMP\maximo
8 When asked choose to overwrite all files new copied files
9 Open a DOS prompt:
i) cd \<maximo_root>\tools\maximo
ii) updatedb
10 Apply any manual updates listed in this readme.txt file. Manual changes if any are listed for each APAR in the section “Manual Changes”
11 Delete the application server cache
C:\Program Files\IBM\Websphere\AppServer\profiles\CtgApp01\temp\ctgNode01\MAXIMOSERVER
12 Rebuild and redeploy the EAR files, and then restart the application server
i) Backup existing ear file.
cd C:\ibm\SMP\maximo\deployment\
run buildmaximoear.cmd
ii)     cd C:\ibm\smp\maximo\tools\maximo
run encryptproperties.bat
iii) shutdown application server
iv) cd C:\ibm\SMP\jacl\solutions
v) DeployApplication.bat wasadmin WASADMIN_PASSWORD “MAXIMO” ctgNode01 MXServer “C:\ibm\SMP\maximo\deployment\default\maximo.ear” maximo_host webserver1
vi) Now try to start MXServer from WAS  admin console https://localhost:9043/ibm/console/
It should automatically start Maximo Enterprise Application as well.
vii) if MXServer starts but Maximo Enterprise application does not, then try running Maximo Enterprise Application again while MXServer is running.
If it fails saying Not synchronized
Then follow the following:
a. stop nodeagent service from services.msc
b. run this command
C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\bin>syncNode.bat TSRM_WAS_SERVER_NAME 8879 -username wasadmin -password WASADMIN_PASSWORD
(Note: If you face issues like unable to authenticate, check if TDS is running or not.)
output will be like below:
————————————–
ADMU0116I: Tool information is being logged in file C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs\syncNode.log
ADMU0128I: Starting tool with the ctgAppSrv01 profile
ADMU0401I: Begin syncNode operation for node ctgNode01 with Deployment Manager
<hostname>: 8879
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0402I: The configuration for node ctgNode01 has been synchronized with Deployment Manager <hostname>: 8879
————————————–
c. after successful syncnode start nodeagent from services.msc
d. start maximo enterprise application in WAS
Database configuration is in progress message starting Maximo. Start fails
Technote (troubleshooting)
Problem(Abstract)
java.lang.Exception : Database Configuration is in process . ConfigDB and RestoreFromBackup must complete before MXServer can be booted .
at pdsi.server.MXServer.boot
Login receives Error 500: system#notboundexception
Resolving the problem
It is possible for configdb to leave a flag set, which can stop Maximo from starting.
Run the following SQL
select * from MAXVARS where varname=’CONFIGURING’;
Check the VARVALUE returned. It will be a ’1′ to signify that configdb is running . If it is not, then do not continue and call into support to report the error.
update MAXVARS set varvalue=’0′ where varname=’CONFIGURING’;
This will reset the flag that signifies configdb to be running.
Maximo should now start.

No comments:

Post a Comment