it

Deployment Guide

SOP Title:

Deployment_Guide

Application Name: SSO

Business Owner: Infibeam

Document Change Control

Version

Effective

Author:

No:

Date:

03-03-2016 Aishwarya
Bharuka

Reviewer

Approver

Nature of changes
1)Login Radius
2)Defect fixes

Table 0: Document change control

Issue Date: 7/24/2015

Page 1

Table of Contents

1. PURPOSE:...............................................................................................................3
2. SCOPE:....................................................................................................................3
3. DOWNTIME DETAIL............................................................................................. 3
4. APP CONTACT DETAILS:..................................................................................... 3
5. VERSION HISTORY:............................................................................................. 3
6. PRE-REQUISITES................................................................................................. 4
7. INSTALLATION PROCEDURE............................................................................. 4
A. PRE-DEPLOYMENT STEPS...................................................................... 6
B. DEPLOYMENT STEPS................................................................................ 7
C. POST-DEPLOYMENT STEPS............................................................................... 8
D. VALIDATIONS.......................................................................................................8
E. TEST STEPS........................................................................................................... 8
8. ROLLBACK-PLAN................................................................................................ 8

Issue Date: 7/24/2015

Page 2

1. Purpose:
This document is a comprehensive lay out of the steps to be executed for deployment process.

2. Scope:
Its defect fix release

3. Downtime detail
SN#
1

Application Name
SSO

Duration time
00 Min

Preferred time
00 Min

4. App contact details:

Contact detail for application support during deployment.
SN#
1

Name
Aishwarya Bharuka

Prashant Padmanabhan

Satish Puli

Email
aishwarya.bharuka@infib
eam.ooo
prashant.padmanabhan@
infibeam.ooo
satish.puli@infibeam.ooo

Mobile
+91 9421302075
+91 9930019328
+91 9322502414

5. Version history:
GIT path: ( access using GIT client)

https://infibeam.unfuddle.com/git/infibeam_sso/ (For SSO Build)

Latest Code Detail

SN#
1.

File Name & Path

Version #
git clone
V0.2.6(Branch:
https://infibeam.unfuddle.com/git v0.2.6)
/infibeam_sso/

Issue Date: 7/24/2015

Page 3

Date & time

03-Mar-2016

6. Pre-Requisites
Following are pre-requisite in sequential manner.
1. Internet connectivity required to install supporting software's for installation. Also, it will be required while making the
builds.
2. GIT Client, Apache Maven, Java Runtime 1.8

Issue Date: 7/24/2015

Page 4

7.

Installation Procedure

Loadbalancing with mod_jk and Apache is configured in SSO stagging environment. Hence, we need to pull out
nodes/application server one by one from the load balancer to deploy the application.

Load-balancer configuration details of Apache on 172.20.218.17

Location of Setting file : /etc/httpd/conf/worker.properties.

Node1: points to 172.20.218.17's Application server.

Node2: points to 172.20.218.18's Application server.
Here is the steps to switch between nodes while deployment and post deployment.

1) Deployment of SSO on 172.20.218.17

Locate the /etc/httpd/conf/worker.properties and find the entry of worker.loadbalancer.balance_workers=node1,node2

Replace with worker.loadbalancer.balance_workers=node2 and save and exit.

It requires to restart the Apache to changes reflect.

Being on the root login shell, execute the /sbin/service/httpd restart
After this SSO application running on node2 server only. Now we can start deployment SSO on 172.20.218.17.
2) Deployment of SSO on 172.20.218.18

Issue Date: 7/24/2015

Page 5

Locate the /etc/httpd/conf/worker.properties and find the entry of worker.loadbalancer.balance_workers=node2

Replace with worker.loadbalancer.balance_workers=node1 and save and exit.

It requires to restart the Apache to changes reflect.

Being on the root login shell, execute the /sbin/service/httpd restart
After this SSO application running on node1 server only. Now we can start deployment SSO on 172.20.218.18.
3) After successful deployment of SSO on both servers. We have to put all nodes on load-balancer.
Locate the /etc/httpd/conf/worker.properties and find the entry of worker.loadbalancer.balance_workers=node1

Replace with worker.loadbalancer.balance_workers=node1,node2 and save and exit.

Being on the root login shell, execute the /sbin/service/httpd restart.

A. Pre-deployment steps
The following activity needs to done/performed in Sequential manner.
Switch your network to STC DC, open terminal
Go to : cd /opt/infibeam/sso_deployment/backup
Remove previous backup if present: rm -rf sso.war,rm -rf PortalCMS.war
Get the build backup:
cp -rf /opt/infibeam/jboss-eap-6.4/standalone/deployments/sso.war .
cp -rf /opt/infibeam/jboss-eap-6.4/standalone/deployments/PortalCMS.war .

Issue Date: 7/24/2015

Page 6

B. Deployment steps
The following Steps need to be followed/perform in Sequential manner.
Open the command line. Go to D:\sapphire_sso\sso
git clone https://infibeam.unfuddle.com/git/infibeam_sso/
select the branch code:
git checkout remotes/origin/v0.2.6
Locate the directory
1) D:/sapphire_sso/sso/infibeam_sso/SapphireSSO/
Run Command: mvn clean install
Go to target: cd target/
After his, switch your network to STC DC and copy sso.war from target folder to
opt/infibeam/sso_deployment/build/ using the winscp/SCP tool.

2) D:/sapphire_sso/sso/infibeam_sso/PortalCMS/
Run Command: mvn clean install
Go to target : cd target/
After his, switch your network to STC DC and copy PortalCMS.war from target folder to
opt/infibeam/sso_deployment/build/ using the winscp/SCP tool.

SSO deploment:
copy war to JBOSS: cp /opt/infibeam/sso_deployment/build /sso.war
/opt/infibeam/jboss-eap-6.4/standalone/deployments
copy war to JBOSS: cp /opt/infibeam/sso_deployment/build /PortalCMS.war
/opt/infibeam/jboss-eap-6.4/standalone/deployments
Issue Date: 7/24/2015

Page 7

C.Post-Deployment steps
D.Validations
E.Test steps
1. Below is the Jboss application server runtime log file path to check for deployment status SSO application.
/opt/infibeam/jboss-eap-6.4/bin/nohup.out file is available in 172.20.218.17 and 172.20.218.18 server.

2. Load the sso https://ssostg.hathaqararak.com/ssoLogin.html url to check if build deployed.

3.Load the sso https://ssostg.hathaqararak.com/sso-cms url to check if build deployed

8. Rollback-plan
1. It is the same process as mentioned in Deployment Process. Only, it changes in terms of considering previous
version builds.

Issue Date: 7/24/2015

Page 8