@FaijasNK

so how i did this was to have a two servers a webserver and appserver 

webserver was pointed to app server - below steps should help i guess :)

This procedure describes how you can put a Pega instance (and the PRD instance in particular) into Maintenance Mode and back into regular production mode. This involves making the JBoss unavailable for regular users and bringing up a "Maintainance page".

Step 1) Make Plan

Define the details of the outage (start, duration , reason) because you need to know what to put on the Sorry Page

Define the list of systems/instances involved. 

This Procedure assumes you are using the current PRD JBoss instance and the Apache instance on the same server.

Step 2) Define Maintainence Message

create a html file with sorry message index.html file in /apache/htdocs 

 Step 3) Stop JBoss

Bring the Jboss down as usual.

From /etc

Run ./stop.sh

You should get a "success" status.

Do a process check "ps -ef | grep jboss" to make sure that no jboss is running before continue with the next step.

Step 4) Reconfigure Apache

Stop the Apache server

From  /etc

run command ./apache_stop.sh  

Open the httpd.conf file in /apache/conf 

Command : vi httpd.conf then enter ‘i’ and comment your existing port XXX.XX.XX.XX:8090and add a new port Listen XXX.XX.XX.XX:8080

add a statement

Listen XXX.XX.XX.XX:8080

where XXX.XX.XX.XX:8080 is the current IP/port of you application 

in our case listen to 8080.

command to save : enter escape :wq

Step 5) Restart the Apache

From /etc

Run ./apache_start.sh

Restart the Apache and check the sorry page is shown under the production link

Step 6) Reconfigure JBoss

a) command : vi standalone-full.xml enter ‘i’ and make your changes 

Open the standalone-full.xml file in /jboss/standalone/configuration

and look for the socket binding configuration for HTTP connector on port 8080

        <socket-binding name="http" port="8080"/>         <socket-binding name="https" port="8443"/>         

b) Change the Connector port to 8090 (or any other available port number)

command to save : enter escape :wq

Step 7) Start the JBoss 

From /etc

Run ./start.sh ..And make sure it listens on the new port number

Step 8) Perform you maintenance work: On the new port 8090

Step 9) Stop the JBoss

From /etc

Run ./stop.sh

You should get a "success" status.

Do a process check "ps -ef | grep jboss" to make sure that no jboss is running before continue with the next step.

Step 10) Reconfigure JBoss

Revert the change from Step 4. Do not start the JBoss yet (as the Apache is still using your port)

Step 11) Reconfigure Apache

Remove the additional Listen line or comment it out. make it listen to previous port . all others must be commented.

Step 12) Restart the Apache

This releases the port number and you configuration files should be back to where they were in the beginning

Step 13) Start the Jboss

From /etc

Run ./start.sh ..and make sure it listens on the new port number

Continue only to the next step after the JBoss is up and the PRPC has completed deploying

Regards,

Vineeth Kichilu