Application is Deployed successfully but new code is not reflecting

There are couple of reasons for this code is not updating

sometimes code deployed is not updated in applications in JVM level ,we can see that time stamp will not be updated in installed apps level,in such a cases we need to restart the nodeagent then newly installed code will be updated.

If still you are not getting the new code reflected then you need to generate the WebServer plugin and propagate the WebServer Plugin.if there is possibility restart WebServers.

now the new code will be reflected.

Note:Ensure you have deployed new ear ,and updated latest jar files in shared libraries.

server is not coming up and showing HAManager related error with server(ex:server A) is not in syn with the servers(server b ,server c ,server d) in logs

server is not coming up and showing hamanger related error with server(ex:server A) is not in syn with the server(server b,server c ,server d) in SystemOut.log

This will occur when HA coordinator is not in sync with all the servers in cell.

resolution is restart all the server that are not in sync with hamanager and restart the server b,server c ,server d then start server A.

Note: be carefull if you are dealing with Production and DR servers

If Node agent is not starting

some times due to unix level patches ip address of host changes to other IP Address which not available during profile installation.so if profile is created with IP Address based constraints we will get IP related  exceptions in SystemOut.log.

If you find IP Address based exception then request unix Team to get back the old IP address host name should be resolved.after getting the IP Address we can restart the Nodeagent.

for getting IP Address of  Unix box use below command

$ifconfig

During Deployment time if we are getting application already existing and not allowing us to complete the deployment successfully

We will get this error stop means application binaries still exist in profiles,this existing binaries are not allowing to deploy an application

To make Deployment sucessfull

1. Stop Dmgr

clear the application related binaries from cus  and blas and applications directories in below location of dmgr and all profiles.

"/opt/IBM/WebSphere/Appserver/profiles/<profilename>/config/cells/<cellname>/

2. Start Dmgr

now Deploy the Application

Application is not Starting After Deplyment in one of the servers in cluster

It happens with some times with WebSphere7 and WebSphere6.1 it is because of Bug in WebSphere Product.we have noticed this with WebSphere7 with fix pack 11(i.e WebSphere7.0.0.11)

To Start Application we need to copy cus and blas folder from Application working host to applcation not starting host.

location of cus , blas folder is under the location

"/opt/IBM/WebSphere/Appserver/profiles/<profilename>/config/cells/<cellname>/

Ex:-
"/opt/IBM/WebSphere/Appserver/profiles/Appserver01/config/cells/localhostCello1"