Endevor web services for HA environment

book

Article ID: 221872

calendar_today

Updated On:

Products

CA Endevor Software Change Manager (SCM)

Issue/Introduction

Endevor is in our Development sysplex which operates with shared dasd and fully shared uss environment.

When web service was installed - the installation was to the uss system root rather than the sysplex root. As we are currently in the process of upgrading Endevor to version 18 we thought it would be better to put web service in our shared environment.

Do we have to have a started task for the apache on every system in the sysplex to create a HA environment ?

 

Environment

Release : 18.1

Component : CA Endevor Software Change Manager

Resolution

To create high availability environment, each Lpar should have it's own Tomcat instance.

Run web services installation twice (use WSTOMCCS or ENWSIns.sh)

In ENWSInstallOptions.properties: 

Set different value for ENDEVOR_TOMCAT_INSTANCE and WSTOM_DATASET

This will create two seperate CATALINA_BASE USS directory structure,  and two seperate WSTOMENV. 

Customize Endevor.cfg for each Lpar (hostname is different), JobName (spawn task name) can be the same. 

Run WSTOMSTC for each Lpar to bring up it's own Tomcat instance.