Upgrading From Sentinel LDK v.6.x or Later
If Sentinel LDK-EMS or Sentinel LDK Vendor Suite from Sentinel LDK v.6.x or later has been installed on your machine, use the procedures below to upgrade to Sentinel LDK v.10.0.
In this section:
>Modifying the Sentinel LDK-EMS Database for Advanced Channel Partner Functionality
>Resolving Sentinel LDK-EMS Upgrade Issues
Upgrading Vendor Suite
No special action is required to upgrade from any earlier version of the Vendor Suite. The Sentinel LDK installation wizard automatically uninstalls and reinstalls Vendor Suite.
Upgrading Sentinel LDK-EMS
To upgrade from Sentinel LDK-EMS v.6.x or later:
1.Back up the Sentinel LDK-EMS database.
2.Install Sentinel LDK-EMS as described in this section. The installation wizard automatically detects the existence of an earlier version of Sentinel LDK-EMS and offers you the option to upgrade to the latest version.
NOTE Thales recommends that you clear your web browser cache before you start working with the current version of Sentinel LDK-EMS.
3.Re-introduce your Master key or Developer key as described in Using the Master Wizard to Introduce a Sentinel Vendor Key.
4.(Optional) Sentinel LDK-EMS works with OpenJDK. If you want to use JRE, continue to Configuring Sentinel LDK-EMS to Work With JRE to set the JRE_HOME system variable to point to the path of the installed JRE.
Modifying the Sentinel LDK-EMS Database for Advanced Channel Partner Functionality
This topic is relevant if you have recently added or plan to add the Channel Partner module tor your Sentinel LDK Master license.
NOTE If you have not created any channel partners in Sentinel LDK-EMS, no special actions are required before you add the Channel Partner module. You can ignore this topic.
Until you add the Channel Partner module to your Sentinel LDK Master license, Sentinel LDK-EMS allows you to associate the entitlements for a given customer with different channel partners. Once the Channel Partner module is added, each customer can only be associated with a single channel partner.
Before you can work effectively with the advanced Channel Partner functionality provided by the module, a script must be run that modifies the Sentinel LDK-EMS database to create direct links between existing channel partners and their customers. The script ensures that no customers are associated with multiple channel partners. If a customer is associated with multiple channel partners, the script links the customer to only one of the channel partners. A log file lists the customers for whom multiple channel partners were found.
You must work with your channel partners to resolve these conflicts and ensure that each customer is connected to a single channel partner. If necessary, resolve conflicts by creating new customers in Sentinel LDK-EMS.
The script to modify the Sentinel LDK-EMS database is executed using the following methods:
>During the Sentinel LDK-EMS upgrade procedure, the Installer automatically executes the script. Any conflicts that are found are recorded in the Installer log at %SystemDrive%\EMS_Log\emsInstaller.log.
>Click the Sync Data for Channel Partner Module button in the Sentinel LDK-EMS Administration Portal to run the script. Any conflicts that are found are recorded in the configuration log at %ProgramFiles(x86)\Thales\Sentinel EMS\EMSServer\webapps\ems\log\emsConfig.log.
The script can be executed multiple times.
You can add the Channel Partner module to your Sentinel LDK Master license before or after the script is executed. However, you should plan to add the module to your LDK Master license as close as possible to the time when the script is executed (using either method).
Resolving Sentinel LDK-EMS Upgrade Issues
NOTE This topic is applicable when you upgrade from Sentinel LDK-EMS v.6.3 or later to v.10.0.
The Sentinel LDK-EMS installation procedure automatically merges components that you have customized in Sentinel LDK-EMS. In addition, all configuration changes that you performed in the existing Sentinel LDK-EMS are backed up under %EMS_HOME%\Backup. If you find any differences after you upgrade to Sentinel LDK-EMS v.10.0, you can manually merge the conflicting files.
To resolve any differences that you may find after upgrade, you can map the backup and current locations to manually merge the files. The following table provides the details of the components that are placed in the backup location.
| Customizable Component |
Backup Location %EMS_HOME%\Backup\... |
Original Location %EMS_HOME%\EMSServer\ |
|---|---|---|
| Template Files (TPLs) | ||
| .TPL files | WEB-INF\classes | ems\WEB-INF\classes |
| Themes and Languages | ||
| Themes | themes | ems\themes |
| Images | themes\blackGolden\images | ems\themes\ blackGolden\images |
| Language (messages_[language_code].properties) | WEB-INF\classes | ems\WEB-INF\classes |
| Samples | ||
| emsWSDemo | emsWSDemo | emsWSDemo |
| Others | ||
| ems.properties | WEB-INF\classes | ems\WEB-INF\classes |
| message.properties | WEB-INF\classes | ems\WEB-INF\classes |