Page Comparison

This section lists the prerequisites and steps for applying this patch.

Info
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

Ensure that you have:

...

Pre-Patch Deployment

If any of your Database (Backend, Log, Quarts, and Log Archival) is using jTDS driver to connect with MS SQL Server, then you must change the jTDS driver to sqljdbc driver.

Ensure that you do this change before applying this patch. Click here for the instructions given to change the driver to sqljdbc.

Steps to apply the patch

Expand

title	For Windows

Download the latest patch from the provided URL.
Extract the downloaded zip file in a folder.
Open the Command Prompt.
Go to the folder 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 AdeptiaServer 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.
Note: While applying the patch you may come across following warning messages that you should ignore.
Warning: Not deploying connect2.0 accelerator because no change list is present.
Warning: Not deploying EDI accelerator because no change list is present.

7. Start Kernel and WebRunner.

Expand

title	For Linux

Open the Terminal.
Download the latest patch from the provided URL.
Extract the downloaded zip file in a directory.
Go to the directory where you have extracted the zip file.
Run the following command to apply the patch:
```
./Apply-Patch.sh <Path where Adeptia Suite is installed till AdeptiaServer folder> 
```
For example:
```
./Apply-Patch.sh /mnt/AdeptiaSuite-x.x/AdeptiaServer
```
Note: While applying the patch you may come across following warning messages that you should ignore.
Warning: Not deploying connect2.0 accelerator because no change list is present.
Warning: Not deploying EDI accelerator because no change list is present.
Once the patch is applied, a confirmation message will be displayed.
Start Kernel and WebRunner.

Post Patch Application Changes

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.

Patch application may take some time, in case there are a large number of records in the backend and log database.

The patch will automatically rollback, in case of any error during the deployment.

Next Step

Verifying Patch

See also

Recovering PatchTo change the driver for Backend & Log Database:

Go to etc folder in Adeptia installation directory: …AdeptiaServer/ServerKernel/etc
Take back-up of server-configure.properties file.
Open server-configure.properties:
To change driver for Backend Database, go to Database Configuration group.
Change JDBC Database driver in the abpm.jdo.driver, paste the following value: com.microsoft.sqlserver.jdbc.SQLServerDriver.
Change the JDO Database Connection URL by setting the JDBC connection URL in the abpm.jdo.url in the following format:

jdbc:sqlserver://<databaseServerName>:<port>; DatabaseName=<name of the database>

For the Named Instance, abpm.jdo.url will be in the following this format:

jdbc:sqlserver://<databaseServerName>:<port>; databaseName=<name of the database>;instanceName=<name of the instance>
where,
<databaseServerName> is the host name where database server is running.
<port> port number on which database server is running.
<name of the database> is the name of the database.
<instanceName> is the name of named database instance.
For example,
jdbc:sqlserver://127.0.0.1:1433;databaseName=backend;instanceName=production
To change driver for Log Database, go to Database Appender group.
Change JDBC Database driver in the log4j.appender.jdbc.dbclass. Paste the following value: com.microsoft.sqlserver.jdbc.SQLServerDriver.
Change the JDBC connection URL and set the JDBC connection URL in the log4j.appender.jdbc.url in the following format:

jdbc:sqlserver://<databaseServerName>:<port>; DatabaseName=<name of the database>

For the Named Instance, log4j.appender.jdbc.url will be in the following format:
jdbc:sqlserver://<databaseServerName>:<port>; databaseName=<name of the database>;instanceName=<name of the instance>
where,
<databaseServerName> is the host name where database server is running.
<port> port number on which database server is running.
<name of the database> is the name of the database.
<instanceName> is the name of named database instance.
For example,
jdbc:sqlserver://127.0.0.1:1433;databaseName=log;instanceName=production
Save and exit the file.

To change the driver for Quartz Database:

Go to etc folder in Adeptia installation directory: …AdeptiaServer/ServerKernel/etc
Take back-up of quartz.properties file.
Open quartz.properties file.
Go to Configure Datasources group, set the value of org.quartz.dataSource.aBPM.driver as com.microsoft.sqlserver.jdbc.SQLServerDriver.
Set the JDBC connection URL in the org.quartz.dataSource.aBPM.URL in this format:

jdbc:sqlserver://<<Database Server>>:<<port>>; databaseName=<<name of the database>>;

For Named Instance, set the JDBC connection URL in the org.quartz.dataSource.aBPM.URL in the following format:

jdbc:sqlserver://<databaseServerName>:<port>; databaseName=<name of the database>;instanceName=<name of the instance>

Versions Compared

Old Version 1

New Version 2

Key

Post Patch Application Changes

Log File Changes