In some cases, the initial JetPatch application server (A.S) does not answer the specifications (location, storage etc.) and there is a need for a new JetPatch app. server, for all the endpoint servers in your current environment.
This article specifies what actions should be taken to move smoothly from one JetPatch server to another. Please contact JetPatch support team if you have any questions before moving your server.
Before we start
Collect all the data that you need in order to move your server smoothly:
- Binaries (tool image)
- Management service configurations
- Smart groups
- Discovery sources credentials
- User accounts
- Maintenance Schedules
- List of all servers in your env. (to validate all of them were moved successfully)
Before you start the moving process:
- Backup your DB
- Backup the following directories:
STEP 1: Setup a new JetPatch Application Server
- Launch a new JetPatch application server (alternatively, you could take an image of your existing application server)
- Add the tools you previously had in your JetPatch application server (your backup of /usr/share/tomcat/default/conf/)
- Create the exact same management services for each and every tool you have added
- Add the tags you would like to have in the new JetPatch A.S
- Add users and permissions (RBAC)
- Add server accounts and Policy-Based Endpoint Account Assignment
Creating smart groups, policies and tagging servers in bulk can only be done after we move all servers to the new JetPatch A.S
STEP 2: Re-Configure JetPatch connector
To communicate with the new JetPatch A.S you will need to re-configure all servers to communicate with the new A.S. In order to do so please follow the next steps:
- Create a new Connector management service in the current JetPatch A.S and Save.
- Add a secondary URL and enter the address of the new JetPatch A.S
- Apply the management service to ALL servers (if different configurations are needed, create multiple management services but make sure the secondary URL is pointing to the new JetPatch server.
- Make sure all servers are re-configured to use the new JetPatch connector.
- Shut down the current JetPatch application server
All servers, which were re-configured to use the new connector, should now appear in the new JetPatch server as 'physical' machines.
- If you no longer have access to current JetPatch, then please follow this article.
- If you are also shifting your DB server, make sure to use the correct properties in intigua.properties file
- If you are using a single server for your JetPatch console and DB, please contact the JetPatch support team before performing this procedure.
STEP 3: Merge Servers
Now that all servers are shown in the new Application Server you can add the discovery sources and merge the servers.
- Go to settings > Discovery sources > Add the same discovery sources you currently have
- Select the endpoints and click the 'Refresh status' button.
- Physical servers and discovered servers should be merged according to their discovery source
STEP 4: Additional Configuration
After you've performed all previous steps, you are able to see all servers from previous console. The next step is to create the following instances, same as they were configured in the previous console:
- Smart Groups
- Policy Rules
- Endpoint Groups
- Bulk assign tags
- Scripts (your backup of /usr/share/intigua/scripts)
- Maintenance Schedules
You're all set!