Gathering information about your current installation
Before you upgrade, you must collect and note down some information about your current installation.
|#||Information about current installation||Your Notes|
|4||Collect information on third-party libraries used for adapter configurations that
were added to your current release.
You will need to add each of these libraries to the upgraded system.
|5||Locate any configuration file changes for JDBC adapter or Lightweight JDBC
adapter in your current release.
You will need to copy these changes to the upgraded system.
|6||Record your performance tuning configuration.
You will need to restore these settings after the system has been upgraded.
|7||Review and note the adapters, business processes, and other configurations in
your current release.
This information will help you identify the need for updating transport messages, third-party adapters, or configurations to adapters, such as File System or Command Line adapters.
|8||Determine if you have edited any of the property files
(.properties or .properties.in).
The upgrade process overwrites these property files, unless these changes were made using the customer_overrides.properties file. Your previous property file edits might not be applicable this version of the software.
Determine if you edited any of the following cdinterop files:
You must back them up before upgrading. The cdinterop files do not have initialization (*.in) files. After the upgrade, use the backup version of the files in your upgraded installation.
|10||Determine if you have LDAP (Lightweight Directory Access Protocol) configuration information in the security.properties file. This information will automatically be moved to the authentication_policy.properties file.|
|11||Determine whether Sterling B2B Integrator is using an application
server (JBoss™, WebLogic® or WebSphere®).
Sterling B2B Integrator does not require an application server for installation or at runtime.
Sterling B2B Integrator supports integration with JBoss and WebLogic during the installation. You can also integrate with WebSphere, JBoss, or WebLogic by using the Sterling B2B Integrator EJB Adapter. This does not represent a WebLogic server for deploying the Application Console.
|12||If you use a File System as your document storage method, determine and record
the path to the File System.
You will need the File System path structure so that after the upgrade, you can copy/mount the documents to the new installation directory. The directory structure (path to the File System) must be the same in the current and in the upgraded system.
|13||Review the EDI Sequence Check Queue to ensure that no interchanges are in the queue. The EDI Sequence Check Queue is used for X12 and EDIFACT sequence and duplicate checking.|
|14||Determine if you have any JVM Containers configured.
If yes, you will have to reconfigure the JVM containers after you have upgraded the software.