...
- In case, any other database is used as the backend database, you need to follow the backup instructions given by that Database Server. To know, which database is used as the back end database, refer to Appendix A: Identify Backend Database.
Take backup of export.xml file from …<AdeptiaInstallFolder>\AdeptiaServer\ServerKernel\MigrationUtility location. This backup file will help you replicate the manual changes in case you have done earlier in this file before applying this patch.
Take backup of securityContext.xml file from <AdeptiaInstallFolder>\AdeptiaServer\ServerKernel\etc\
samlsaml location. This backup file will help you replicate the manual changes that you may have done in this file in the past before applying this patch
.Take backup of java.security file from .\AdeptiaConnect\ConnectServer\jre\lib\security location. This backup will help you restore the file, if required.
Ensure that you have followed the Prerequisites' instructions given on the Installing Adeptia Suite page.
...
Changes in securityContext.xml
Go to <AdeptiaInstallFolder>\AdeptiaServer\ServerKernel\etc\saml saml location.
Open securityContext.xml file.
Update the xsi:schemaLocation attribute as shown in the following code snippet.
Code Block language css theme Midnight xsi:schemaLocation="http://www.springframework.org/schema/beans classpath:org/springframework/beans/factory/xml/spring-beans.xsd http://www.springframework.org/schema/security classpath:org/springframework/security/config/spring-security-5.6.xsd http://www.springframework.org/schema/context classpath:org/springframework/context/config/spring-context.xsd">
- Save the file.
Changes in java.security
Download the attached java.security file from here.
- Paste the downloaded java.security file at .\AdeptiaConnect\ConnectServer\jre\lib\security location.
- Restart the Server.
Once the post patch deployment steps are done, start the services, i.e. Kernel and WebRunner.