...
Expand | ||
---|---|---|
| ||
Before you apply this patch on Linux, ensure that you take back up of your existing startup.sh and stop.sh files.
|
Post Patch Deployment Steps:
Log File Changes
After you have applied the patch, PatchApplicationLog_<Date>.log file is created inside the logs folder. The logs folder is available in the same folder from where you have applied the patch. PatchApplicationLog_<Date>.log file contains the logs generated during patch application and can be used to troubleshoot any issue related to the patch application.
...
The patch will automatically rollback, in case of any error during the deployment.
Changes in launcher.properties File
In case, you have done custom changes in the launcher.properties file then follow the below step:
- Go to …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc.
- Open launcher.properties file.
- Ensure that the manual changes which you have done in previous launcher.properties file is available in this file or not.
- If not then do the same manual changes in file that you have done in your previous launcher.properties file (that you had saved as backup).
Changes in jetty.xml File
- Go to …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc\jetty location.
- Take backup of jetty.xml file from the above-mentioned location.
- Go to the downloaded Adeptia Connect zip folder and copy jetty.xml file.
- Replace the existing file with the copied file at the following location: …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc\jetty.
- In case, you have configured SSL certificate then update the jetty.xml file to configure the SSL certificate.
Changes in web.xml File
- Go to …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\web\WEB-INF location.
- Open web.xml file.
- Do the same manual changes in the file that you have done in your previous web.xml file (that you had saved as backup).
- Save the file.
Changes in securityContext.xml File
- Go to …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc\saml location.
- Open securityContext.xml file.
- Do the same manual changes that you have done in your previous securityContext.xml file (that you had saved as backup).
- Save the file.
...