This section lists the prerequisites and steps for applying this patch.
Though every release of Adeptia comes with seamless upgrades and bug-free patches. For customer's complex use cases, we recommend applying the patch in a non-production environment first followed by testing. After the use cases run successfully without any errors or warnings, you can apply the patch in the production environment.
Prerequisites
Make sure that:
- You have Read and Write permission on all subfolders and files of .../AdeptiaSuite-<Version>.
- You have stopped Kernel and WebRunner.
Steps to apply the patch:
- Download the latest patch from the provided URL.
- Extract the downloaded zip file in a folder.
- Open the Command Prompt.
- Go to the directory where you have extracted the zip file.
Run the following command to apply the patch:
Apply-Patch.bat “<Path where Adeptia Suite is installed till Adeptia Server folder>”
For example:
Apply-Patch.bat "C:/Program Files/AdeptiaSuite/AdeptiaSuite-x.x/AdeptiaServer"
Once the patch is applied, a confirmation message will be displayed.
- (This step is applicable only for v2.1) Now, go to …/<AdeptiaInstallFolder/ServerKernel/etc folder and do the following:
- Open spring-context.xml file in the Text Editor and do the following:
In the Entity Manger Factory group, remove the below property:
<prop key="hibernate.hbm2ddl.auto">update</prop>
In the Entity Manger Factory for Log Database group, remove the below property:
<prop key="hibernate.hbm2ddl.auto">update</prop>
- In the Transaction Manager group, remove the below bean:
<bean autowire="byType" class="com.adeptia.connect2.app.LookupRegistry" id="lookupRegistry"/>
<bean autowire="byType" class="com.adeptia.connect2.app.CompanyRegistry" id="companyRegistry"/>
<bean autowire="byType" class="com.adeptia.connect2.app.NetworkRegistry" id="networkRegistry"/>
<bean autowire="byType" class="com.adeptia.connect2.app.RoleRegistry" id="roleRegistry"/>
<bean autowire="byType" class="com.adeptia.connect2.app.UserRegistry" id="userRegistry"/>
- Save the file.
- Open adapters.properties file in the Text Editor and do the following:
- Go to the application group you are using and set the value of the <application_name>.enableProduction property to true.
For example, if you are using Dropbox application then go to the Dropbox group and set the value of the property dropbox.enableProduction = true. - Save the file.
- Go to the application group you are using and set the value of the <application_name>.enableProduction property to true.
- Open spring-context.xml file in the Text Editor and do the following:
- Restart Kernel and WebRunner.
- The patch will automatically rollback, in case of any error during the deployment.
- Patch application may take some time, in case there are a large number of records in the backend and log database.
- A PatchApplicationLog_<Date>.log file is also 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.