Siebel CRM Anywhere Administration Guide Siebel 2018 E24720_01 |
|
![]() Previous |
![]() Next |
View PDF |
Preparing to create an upgrade kit involves gathering the software, files, or Siebel database schema updates required for the upgrade kit. It can also involve preparing simple batch scripts. The specific process to follow depends on the type of components you are planning to upgrade.
This task is a step in "Process of Planning and Preparing to Create Upgrade Kits".
Note: Do not use the component type Customer Revision for upgrade kits containing a Siebel runtime repository or CFG file. Instead, use the Siebel Repository ExportImport and Siebel CFG File component types, respectively, for these upgrades. Using the proper types will allow proper version checking. |
The following topics describe specific steps to take for certain upgrade kit types:
"Preparing Contents for a Siebel Upgrade Wizard Upgrade Kit"
"Preparing Contents for a Siebel Client Executables Upgrade Kit"
"About Reducing the Size of Siebel Client Executables Upgrade Kits"
"Preparing Contents for Runtime Repository or Third Party Software Upgrade Kits"
You must create a Siebel Upgrade Wizard upgrade kit whenever there are changes to the Upgrade Wizard in a Siebel CRM release. For more information about whether a specific release contains such changes, see the release-specific documentation for the release.
This topic is part of "Preparing Upgrade Kit Contents".
A Siebel Upgrade Wizard upgrade kit must contain a set of DLL files, along with the Upgrade Wizard executable file, siebupg.exe. The following procedure describes how to prepare the contents for such an upgrade kit.
To prepare the contents for a Siebel Upgrade Wizard upgrade kit
Create a new directory to hold the Upgrade Wizard executable program and related DLL files.
Make a note of the directory name, because you must specify it while defining the upgrade kit.
If you have not already done so, then install the client software for the new Siebel CRM release on a test computer or a Siebel administrator's computer. Make a note of where you installed it.
Locate the client BIN
directory within the installation directory of the new Siebel CRM release.
The installation location might resemble the following:
C:\Siebel\Client\BIN
Copy the following files from the release client BIN
directory into the new directory that you created in Step 1.
siebupg.exe
MSVCR71D.dll
MFC71UD.dll
MSVCP71D.dll
libarm.dll
pw32a.dll
srlcver.dll
sslcacln.dll
sslccore.dll
sslcdb.dll
sslcevt.dll
sslclm.dll
sslcnapi.dll
sslcns.dll
sslcos.dll
sslcosa.dll
sslcosd.dll
sslcosslimpl.dll
sslcrsa.dll
sslcrsaimpl.dll
sslcrsa56.dll
sslcsc.dll
sslcscr.dll
sslcsecm.dll
sslcshar.dll
sslcsnns.dll
sslcsnsc.dll
sslcsrd.dll
sslcsrvr.dll
sslcsym.dll
sslcupg.dll
sslcver.dll
You can use the Siebel Client Executables components to deliver Siebel Innovation Pack releases and Siebel language packs to Siebel Mobile or Developer Web Clients.
This topic is part of "Preparing Upgrade Kit Contents".
Siebel Innovation Pack releases consist of a set of language-independent files (called base files) and one or more sets of language-specific files. The following components are available:
Upgrade kits using the Siebel Client Executables component are used to distribute base files. Language-specific files can also be included in this upgrade kit, along with the base files. You can use this component for standard installation or delta installation upgrade kits.
Upgrade kits using the Siebel Client Executables__language-code components are optionally used to distribute language-specific files. You can use these components only for delta installation upgrade kits.
For more information about delta installation upgrade kits, see "About Reducing the Size of Siebel Client Executables Upgrade Kits" and "Roadmap for Creating a Delta Installation Siebel Client Executables Upgrade Kit".
The following procedures describe how to prepare files for inclusion in base client executables upgrade kits.
To prepare files for inclusion in Siebel Client Executables upgrade kits (for standard installation upgrade kits)
Create a new, network-accessible UNC directory to use for storing the base client executable files in the Siebel Innovation Pack release.
An example name for this directory might be \\
computer_name
\siebel\base
.
Navigate to the parent directory, within the network image file hierarchy, of the Siebel client directory for the Siebel Innovation Pack release. Navigate to a directory like the following:
Windows\Client
Copy the Siebel_Web_Client
directory to the clipboard.
Paste the directory that you copied in Step 3 to the directory that you created in Step 1.
Related Topics
"About Reducing the Size of Siebel Client Executables Upgrade Kits"
"Roadmap for Distributing a Siebel Innovation Pack or Patchset Release"
"Roadmap for Creating a Delta Installation Siebel Client Executables Upgrade Kit"
"Defining a Siebel Client Executables Upgrade Kit"
This topic describes a feature called the delta installation upgrade kit type for a Siebel Client Executables upgrade kit.
This topic is part of "Preparing Upgrade Kit Contents".
It is possible to reduce the size of some Siebel Client Executables upgrade kits, which also reduces the time it takes users to retrieve and install these upgrade kits. This reduction in upgrade kit size is accomplished by creating the delta installation type of Siebel Client Executables upgrade kit (as opposed to a standard installation upgrade kit). Delta installation upgrade kits contain condensed information about specific changes to client executable files, instead of an actual set of the new executable files.
When you create a Siebel Client Executables upgrade kit, you choose whether to create it as a delta installation upgrade kit or a standard installation upgrade kit.
Note: Delta installation upgrade kits are suitable for delivering Siebel Innovation Pack releases that contain relatively few changes to client executable files. For example, you could use a delta installation upgrade kit to upgrade Siebel CRM client executables from Siebel CRM version 17.0 to version 17.1. Delta installation upgrade kits are not suitable for major upgrades, such as to upgrade Siebel CRM from version 8.1.1 or version 8.2.2 to Siebel Innovation Pack 2017 (Siebel CRM version 17.0). In addition, delta installation upgrade kits are not suitable for adding languages. |
You can create delta installation upgrade kits for the Siebel Client Executables base (language-independent) component or for each language-specific Siebel Client Executables__language-code component that is for a language that your users already have installed.
Caution: If you want to add an additional language for your users, then do not use a delta installation upgrade kit to add that language. Instead, use a standard installation upgrade kit. That is, create an upgrade kit for the Siebel Client Executables__language-code component and select Standard Install as the installation type for the upgrade kit. Delta installation upgrade kits are not supported for the addition of a new language. If a delta installation upgrade kit is incorrectly used to install a new language, then it can damage some client executable files. |
Before defining a delta installation upgrade kit, a Siebel administrator must use the Siebel Patch Utility (siebpatch.exe) to create a delta patch file. This is a file that contains information about the changes that were made to client executable programs between two specific Siebel releases. For details, see "Creating a Delta Patch File".
Users retrieve and install delta installation upgrade kits just as if the upgrade kits contained complete sets of client executable files. When a delta installation upgrade kit is installed, the Upgrade Wizard applies the changes that are described in the upgrade kit to the user's existing client executable files, rather than replacing the user's files.
Depending on the release you are installing, users might need to upgrade the Upgrade Wizard before installing a delta installation upgrade kit. In this case, a Siebel administrator must define an Upgrade Wizard upgrade kit, and make any delta installation upgrade kits dependent on that Upgrade Wizard kit. For more information about whether this requirement applies to you, see the release-specific documentation for the release you want to install.
For more information about the process of creating delta installation upgrade kits, see "Roadmap for Creating a Delta Installation Siebel Client Executables Upgrade Kit".
You can use the Siebel Quick Fix component to deliver Siebel Patchset releases to Siebel Mobile or Developer Web Clients.
This topic is part of "Preparing Upgrade Kit Contents".
Note: For Siebel Innovation Pack releases, see "Preparing Contents for a Siebel Client Executables Upgrade Kit". |
The following procedure describes how to prepare files for inclusion in Siebel Patchset upgrade kits.
To prepare files for inclusion in Siebel Patchset upgrade kits
Create a new, network-accessible UNC directory to use for storing the files in the Siebel Patchset release.
An example name for this directory might be \\
computer_name
\siebel\patchset
.
Navigate to the parent directory, within the network image file hierarchy, of the Siebel client directory for the Siebel Patchset release. Navigate to a directory like the following:
Windows\Client
Copy the Siebel_Web_Client
directory to the clipboard.
Paste the directory that you copied in Step 3 to the directory that you created in Step 1.
To prepare for creating an upgrade kit for a Siebel runtime repository update, third-party application, or other non-Siebel file, copy the files to a directory on the Siebel Server from which you will run the Upgrade Kit Builder server component, or to a directory that is accessible from that server.
This topic is part of "Preparing Upgrade Kit Contents".
Siebel Anywhere can install third-party applications or other files using one of the following methods:
Executing a batch script or installation program.
Copying files to a specified location.
Note: Before deploying an upgrade kit, make sure that any files, scripts, or other programs required to install third-party applications contain the necessary data and are fully tested. |