sso deployment sop

8/20/2019 SSO Deployment SOP

1/8

Issue Date: 7/24/2015 Page 1

it

Deployment Guide

SOP Title: Deployment_Guide

Application Name: SSO

Bu ine Owner: nfibeam

Document Change Control

Ver ion

No:

Effective

Date:

Author: Reviewer Approver Nature of change

1 03-03-2016 Aishwarya

Bharuka

1)Login Radius

2)Defect fixes

Table

0

: Document change control


2/8


Table of Content

1. PURPOSE:............................................................................................................... 3

2. SCOPE:.................................................................................................................... 3

3. DOWNT ME DETA L............................................................................................. 3

4. APP CONTACT DETA LS:..................................................................................... 3

5. VERS ON H STORY:............................................................................................. 3

6. PRE-REQU S TES

.................................................................................................

4

7. NSTALLAT ON PROCEDURE............................................................................. 4

A. PRE-DEPLOYMENT STEPS...................................................................... 6

B. DEPLOYMENT STEPS................................................................................ 7

C. POST-DEPLOYMENT STEPS............................................................................... 8

D. VAL DAT ONS

.......................................................................................................

8

E. TEST STEPS........................................................................................................... 8

8. ROLLBACK-PLAN................................................................................................ 8


3/8


1. Purpo e:

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

2. Scope:

It’s defect fix release

3. Downtime detail

SN# Application Name Duration time Preferred time

1 SSO 00 Min 00 Min

4. App contact detail :

Contact detail for application support during deployment.

SN# Name Email Mobile

1 Aishwarya Bharuka aishwarya.bharuka@infib

eam.ooo

+91 9421302075

2 Prashant Padmanabhan prashant.padmanabhan@

infibeam.ooo

+91 9930019328

3 Satish Puli [email protected] +91 9322502414

5. Ver ion hi tory:

G T path: ( acce u ing G T client)

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

Late t Code Detail

SN# File Name & Path Ver ion # Date & time

1. git clonehttps://infibeam.unfuddle.com/git

/infibeam_sso/

V0.2.6(Branch:v0.2.6)

03-Mar-2016


4/8


6. Pre-Requi ite

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


5/8


7. n tallation 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_worker =node1,node2

Replace with worker.loadbalancer.balance_worker =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


6/8


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

Replace with worker.loadbalancer.balance_worker =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_worker =node1

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

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

A. Pre-deployment tep

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 .


7/8


B. Deployment tep

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

https://infibeam.unfuddle.com/git/infibeam_oms/http://d/sapphire_oms/oms/infibeam_oms/oms-service/oms-dto/http://d/sapphire_oms/oms/infibeam_oms/oms-service/oms-dto/http://d/sapphire_oms/oms/infibeam_oms/oms-service/oms-dto/http://d/sapphire_oms/oms/infibeam_oms/oms-service/oms-dto/https://infibeam.unfuddle.com/git/infibeam_oms/


8/8


C.Po t-Deployment tep

D.Validation

E.Te t tep

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.
https://ssostg.hathaqararak.com/ssoLogin.htmlhttps://ssostg.hathaqararak.com/sso-cmshttps://ssostg.hathaqararak.com/sso-cmshttps://ssostg.hathaqararak.com/ssoLogin.html

sso deployment sop

Documents