The installation checklist contains the tasks you need to complete prior to installing Sterling B2B Integrator.
For a clustered environment, record the information for each node in the cluster.
- AS2 Edition
|1||Review your IBM contract to determine what software you have licensed. You need to know this License Information so that you can select the correct components/features to install.|
|2||Ensure that you have read and write privileges on the parent installation directory.|
|3||Determine which installation method you are going to use:
|4||Determine if you are going to run the pre-upgrade checks during the upgrade.|
|5||Decide which type of security certificates you will use:
For more information, see Security certificates.
|6||Determine the ports that are to be used. Sterling B2B Integrator requires a range of 200 consecutive open ports between 1025 and 65535. The port range starts with the initial port number and ends with the number that equals the initial port number plus 200.
Note: Because of RMI, on occasion, a port number outside the range may be assigned.
For more information, see Port Numbers.
|7||If you are using an Oracle, Microsoft SQL Server, or DB2 database and if you are going to manually apply DDL statements, decide if you are going to manually or automatically apply Database Definition Language (DDL) Statements (schema) to the database.|
|8||If you are using an Oracle database, you must set it up for native compilation by allocating space and by setting the
Important: If you are using Oracle SSL authentication, you cannot install or upgrade Sterling B2B Integrator. You must roll back the SSL configuration to a Standard Oracle database connection before you install or upgrade Sterling B2B Integrator. This includes applying a Fix Pack for Sterling B2B Integrator.
|10||If you are using the Unix/Linux operating systems, verify the following items:
For more information, see UNIX accounts.
|11||If you are using the Unix/Linux operating systems, verify that you have installed the following software:
For more information, see Installing an X Windows system for Unix/Linux.
|12||If you are using the Unix/Linux operating systems, set the ulimit and language as follows:
|13||If the SAP Jco 3.x adapter is used, make a backup of the files dynamic_os.sh and dynamic_os.sh.in in the <B2BInstallDir>/bin directory and restore (replace the files) after the upgrade. This ensures that the environment variables required for the SAP JCo 3.x adapter are retained which references the SAP Jco libraries and makes sure that adapter remains enabled and functional after the upgrade.|
|14||If you are using a messaging queue, add the required properties to the customer_overrides.properties file. For more information, see Properties for messaging queues.|
|15||For systems with multiple IP addresses, verify that the IP address on which Sterling B2B Integrator resides is accessible by any client computer that is running a browser interface.
If you do not verify the IP addresses, your system may not operate properly after installing Sterling B2B Integrator.
|16||Determine if you are going to use FIPS (Federal Information Processing Standards) mode.|
|17||Back up your Sterling B2B Integrator installation directory and the database.
If there are problems with your upgraded system, the only way to ensure that you can roll-back to your previous version is to back up Sterling B2B Integrator and the database.
|18||Archive your data.
Archived data can only be restored from the same version of Sterling B2B Integrator from which it was archived. If you need to restore archived data that was archived prior to performing the upgrade, then you must have a running instance of Sterling B2B Integrator that matches the version from which the archive was taken.
|19||Purge any data that is not required.|
|20||Export any business objects that can not be upgraded. Including business processes, service configurations, trading partners, and maps.
The exported business object can be imported into the upgraded system if you need them.
|21||Create a process output log. For more information, see Creating process output log.|
|22||Disable the virus protection software on the server.
If the virus protection software is enabled, the upgrade will fail.
|23||Complete the installation worksheet.|