ACS 6 has added a few database fields to support new business models. These changes should be added to the database schema automatically after you update the WAR files from ACS versions 4.1 and above.
Since Version 5.0, Java 1.7 is required. Previous versions of ACS were compatible with Java 1.5 and 1.6, but version 5 and 6 require that you upgrade to Java 1.7. We recommend that you upgrade Java first, confirm that the rest of your system still functions as expected, then upgrade ACS.
There shouldn't be any changes required in your store to continue using ACS after upgrading to newer versions of ACS, including ACS 6. There are new business models supported in ACS 6. However, none of these new models require changes from how you interface with ACS services.
To update (upgrade) Adobe Content Server from 4.0 to 4.1 or newer versions, please follow the instructions in the User Guide to migrate the database properly first. There's one additional step discussed at the end of this solution. Also, always make sure that the database is set to be transactional.
In 4.1, there is a subtle change in how the status check is performed. Status executes by (amongst other things) calling certain URLs on its own service, essentially to make sure that calls over the web service interface will operate properly. In 4.1, those certain URLs are constructed to go to “localhost”. If you are binding your Tomcat to a specific address (for example, the fulfillment server address), you need to configure to allow localhost calls to see status check complete, by adding something like this:
<connector address="127.0.0.1" port="8080" protocol="HTTP/1.1" connectiontimeout="20000" redirectport="8443"></connector>
to your Tomcat server config file.
After you are done with the database migration, before you copy over the war files from the 4.1 version, make sure that you follow these steps:
- Stop the Tomcat services.
- Remove the folders: admin, fulfillment and packaging from Tomcat's Webapps folder. If you've made any changes to the properties file in those folders, back them up first.
- Remove the older versions of 3 war files.
- Copy over the new war files.
- Restart Tomcat services.
If you're updating from version 4.0 to newer versions, you can follow the same database migration for upgrading to 4.1. If the migration ran successfully, there is no need to use the intermediate versions first; you can go directly to the latest version once the database migration is complete. All newer versions, 4.2, 5.0 and 6.0, will make the database changes when the service starts again.
It is critical that you delete the old ACS servlet folders before starting Tomcat with the new war files.