Creating the Siebel Installation Image on the Network

This chapter describes how to obtain the Siebel installation media files and how to create a network image from which you install Siebel CRM software. It includes the following topics:

About the Siebel Network Image

For each Siebel CRM release representing the products that you have purchased, you run the Siebel Image Creator utility to create a Siebel network image, which is also called a Siebel image. All installations of Siebel CRM modules must be performed from a Siebel image. Unless otherwise stated in documentation for a particular release, each Siebel release includes Siebel Image Creator and you use this utility to create a version-specific Siebel image. The Siebel Image Creator is also called the Network Image Creator.

To install all of the Siebel CRM software for the current release, you require an image of two versions: Siebel CRM 17.0 and Siebel CRM 20.9 Update. You must create any network image as described in this chapter. For Siebel Enterprise Server (including Siebel Application Interface), Siebel Web Client, Siebel Tools, and any other modules you require, you create one network image for Siebel CRM 17.0 and another one for Siebel CRM 20.9 Update.

Also obtain and install the ZIP file for Oracle Database SE2 for Siebel Web Client installations of Siebel CRM 20.8 Update or later, as described in Installing and Using Oracle Database SE2 for the Local Database.

For more information, see Installation-Related Changes for Siebel CRM 20.x Update and relevant topics.

You must allocate disk space on the network for the Siebel images that you will use as the source location for Siebel installations. Retain all of the Siebel images until they no longer apply. Also retain all of the Siebel media files, particularly the JAR files that you use to create the Siebel images.

The remaining topics in this chapter describe how to obtain the Siebel media files from Oracle and how to create a Siebel image.

Obtaining Siebel Installation Media Files

In general, Oracle distributes the media files for Siebel CRM to customers as follows:

The media files for Siebel CRM base releases, including Siebel CRM 17.0, are provided as ZIP files on Oracle Software Delivery Cloud.
https://edelivery.oracle.com
The media files for Siebel CRM 20.9 Update are provided as ZIP files on My Oracle Support.
https://support.oracle.com

Note: Whether particular releases are distributed as described above might change in some cases. If you cannot find your release, then check the Siebel CRM Update Guide and Release Notes on My Oracle Support and other relevant information on My Oracle Support.

Use a standard unpacking tool such as WinZip to extract from each ZIP file a set of JAR files that serve as the Siebel media files. (Validate that the unpacking tool that you are using can handle files of the sizes of the Siebel media files.) These JAR files, which are compressed files using the Java Archive format, are processed when you run the Siebel Image Creator utility. Siebel CRM releases are also available on DVD.

Note: Siebel CRM software must be installed from a Siebel network image that was created using Siebel Image Creator. You cannot install directly from the ZIP files, JAR files, or DVDs.

Download the ZIP files representing the Siebel CRM modules and languages that you require into one or more target locations. After you download the files, review the ZIP file sizes and validate the checksum values of the downloaded files against the published values. Also provided are the Siebel Image Creator executable program and the files it requires. Extract the JAR files from the ZIP files and place them in a single directory on your network. You run Siebel Image Creator from the JAR files directory. All of the JAR file names include the designation SBA (for Siebel Business Applications). For the full requirements for running Siebel Image Creator, see Preparing to Create a Siebel Installation Image.

Tip: If you obtain JAR files for more than one release, then it is generally recommended that you put them into a separate directory for each release, corresponding to the version number.

You use Siebel Image Creator to create a network image (also called a Siebel image) from which you subsequently install Siebel CRM. All installations for Siebel CRM modules must be performed from the Siebel image, for Siebel CRM 17.0 and Siebel CRM 20.9 Update. The installation process is described in Installing Siebel CRM Server Modules and other chapters for installing particular Siebel CRM modules.

For more information about the contents and organization of the Siebel media files, see Siebel Installation Media Contents.

Before you download the ZIP files to your network, see Preparing to Create a Siebel Installation Image.

Siebel Installation Media Files Provided on DVD

Alternatively, you can obtain Siebel media ZIP files on DVD. These files are the same as the ZIP files that you can obtain from Oracle Software Delivery Cloud.

Accessing the Siebel media files that are provided on DVD requires a compatible DVD drive (+R compatible). You must use an appropriate mount command to mount each DVD before you can access its contents.

Note: The Siebel DVD media require the Rock Ridge extensions. On some UNIX operating systems, such as HP-UX, the mount command might require the -o rr switch to properly mount Rock Ridge-compliant media. For details, see the mount CDFS command manpages for your operating system.

For each DVD, copy the ZIP media files representing the Siebel CRM modules or languages that you require into one or more target locations. Review the ZIP file sizes before you copy them. Each DVD uses up to 5 GB of storage.

For more information about the contents and organization of the Siebel media files, see Siebel Installation Media Contents.

Before you copy the ZIP files to your network, see Preparing to Create a Siebel Installation Image.

Related Books

For more information about finding and downloading releases for Siebel CRM, see 975535.1 (Article ID) on My Oracle Support.

For more information about the Siebel CRM installers and media files, see 1461640.1 (Article ID) on My Oracle Support.

Siebel Installation Media Contents

For each Siebel CRM release, the software is provided through the base media for individual installable Siebel CRM modules and media for associated Siebel language packs, for all of the applicable languages. Most Siebel CRM modules require one or more language packs for successful installation. Siebel CRM deployments include installations from both base media and language media.

The media for ancillary third-party modules are also provided with the base media. Siebel installable modules that are based on third-party modules do not use Siebel language media.

As the Siebel image is created when you use Siebel Image Creator, each JAR file is extracted and the directories and files for the corresponding module are copied to the Siebel image location.

Note: This guide generally refers to Siebel CRM modules to mean the same thing as the items selectable as products in Siebel Image Creator, and might sometimes be called components.

Siebel Installation Base Media

The base media for Siebel CRM software are organized by operating system, product category, version number, and product (module) name. For most of the Siebel CRM modules, language support is delivered separately through the language media. The operating systems are as follows:

Microsoft Windows
IBM AIX
HP-UX
Linux
Oracle Solaris (for SPARC)

For detailed support information about the listed operating systems, see the Certifications tab on My Oracle Support.

The base media for the listed operating systems are provided as described in Obtaining Siebel Installation Media Files. Note the following points regarding the organization of the base media files:

For Siebel Enterprise Server, Siebel Application Interface, Siebel Web Client, and Siebel Tools, the network image for Siebel CRM 17.0 is the base media.
For client modules, the base, language, and third-party media files are available for Windows only, and might apply for customers on all of the server operating systems. Example client modules include Siebel Web Client (Siebel Mobile Web Client) and Siebel Tools.

Note: When you run Siebel Image Creator, you must select the Windows operating system to be able to select any Windows-based modules. For more information about cross-platform issues when creating Siebel images, see Cross-Platform Issues When Creating Siebel Image Directories.
For server modules, the base, language, and third-party media files are included with the base media for your operating system, where applicable. The media files for such modules are provided with the UNIX base media where these modules run natively on Windows and are not available on UNIX.

Note: When you run Siebel Image Creator, you must select the Windows operating system to be able to select any Windows-based modules.

Third-party media files provide separately installable third-party software modules that work with Siebel CRM. In this context, third-party products might also include non-Siebel products from Oracle. These third-party modules are not installed through Siebel installers, and do not use language media. Documentation is provided in this guide (the Siebel Installation Guide for the operating system you are using) or in other books on the Siebel Bookshelf. See also the Certifications tab on My Oracle Support.

Language Media

The language media, also known as language extension packs or language packs, provide language support for Siebel CRM.

When you run Siebel Image Creator to create a Siebel image or to add modules to an existing Siebel image, you specify the languages for all of the modules that you include in the Siebel image. Alternatively, you can also add languages to all of the modules in an existing Siebel image.

When you install Siebel CRM modules, you can include languages when you install. You can also install additional languages later. It is strongly recommended that you install and deploy, or at least install, all of the languages that you expect to require, on each physical server.

For Siebel Tools, a base JAR file and a U.S. English (ENU) language JAR file are provided. Support for other languages is provided through separate JAR files. When using Siebel Image Creator to add Siebel Tools to your Siebel image, you must select ENU and any other desired languages to proceed with extracting the base JAR file for Siebel Tools. When you later install Siebel Tools, you must select U.S. English (ENU) and optionally select any other languages that are part of the Siebel image.

For more information about the supported languages and about deploying languages, see:

Installing and Deploying Siebel CRM with Multiple Languages
For Siebel CRM language support, Unicode support, and legacy code page support for supported databases, see 1513102.1 (Article ID) on My Oracle Support.
Certifications tab on My Oracle Support
Siebel Global Deployment Guide

Preparing to Create a Siebel Installation Image

Before you create a Siebel installation image on your network, review the issues described in the following information:

Determining the Locations for the Siebel Media Files and the Siebel Image

This topic is part of Preparing to Create a Siebel Installation Image.

It is recommended that you download or copy all of the Siebel media files to a central location on your network where you have sufficient disk space. Typically, this location would not be the same location where you will create your Siebel image. For example, for Siebel CRM 17.0, you might create the directory Siebel_media_17.0, and then create subdirectories ZIP_17.0 and JAR_17.0, in which you would store the ZIP files and JAR files that you use to create the Siebel image for files of Siebel CRM 17.0. Also place the Siebel Image Creator files in the JAR files directory and run the utility from there.

The default top-level names used by Siebel Image Creator for the Siebel image directory are C:\Siebel_Install_Image on Windows or /Siebel_Install_Image on UNIX. For example, if you are creating a Siebel image for Siebel CRM 17.0 on a UNIX computer, then you might create a directory /Siebel_Install_Image, in which you store your Siebel images. In this example, when you run Siebel Image Creator, specify /Siebel_Install_Image as the top-level directory.

Siebel Image Creator automatically creates a subdirectory (such as 17.0.0.0) under the specified top-level directory. This version-specific directory contains the installable Siebel CRM modules, organized by operating system, that you choose to include in the Siebel image.

Your directories for the Siebel image, the ZIP files, and the JAR files might be as shown in the following table. For other Siebel CRM releases, substitute the appropriate version numbers. You can create similar directories later for ZIP files and JAR files for subsequent Siebel CRM 20.x Update releases.

Table Siebel Media Files and Image Directories

Directory Function	Example Directory Locations	Comments
ZIP files directory	/Siebel_media_17.0/ZIP_17.0 /Siebel_media_17.0/ZIP_20.9	Before you run Siebel Image Creator, it is recommended to create a version-specific subdirectory like this example, to contain the ZIP files that you obtain from Oracle.
JAR files directory	/Siebel_media_17.0/JAR_17.0 /Siebel_media_17.0/JAR_20.9	Before you run Siebel Image Creator, it is recommended to create a version-specific subdirectory like this example, to contain the JAR files and the Siebel Image Creator files. (You must extract the JAR files from the ZIP files.) Note: You will run Siebel Image Creator from the JAR files directory. For the full requirements for running Siebel Image Creator, see Preparing to Create a Siebel Installation Image.
Siebel image directory	/Siebel_Install_Image/17.0.0.0 /Siebel_Install_Image/20.9.0.0	When you run Siebel Image Creator, the utility creates a version-specific subdirectory like this, which contains the Siebel image: the installer files for each applicable module.

Note: Optionally, after you create the Siebel image in a central location, you might choose to copy a module-specific subdirectory of the Siebel image to a computer where you will install this module. Doing so can significantly improve performance during the installation, particularly for installations of Siebel Enterprise Server or Siebel Application Interface. For additional recommendations or requirements for installers, see Oracle Universal Installer documentation on Oracle Technology Network. See also Requirements for Installing and Configuring Siebel CRM.

Requirements for the Siebel Image Directories

This topic is part of Preparing to Create a Siebel Installation Image.

The directory in which you create a Siebel image, or the directory that you specify as the location for Siebel media files (JAR files), must meet the following requirements:

The user creating the Siebel image must have write permission in the Siebel image directory.
Users who have to access the Siebel image directory in order to perform installations must have read and execute permissions. Users who have to modify files to support unattended installation mode must also have write permission.
See also the relevant topics in Planning Your Siebel Deployment.
Any directory that you specify for creating a Siebel image must contain sufficient disk space for all of the Siebel CRM modules and languages that you include in the Siebel image.
When you specify an existing network image directory into which you will add modules or languages, you must specify a top-level directory that contains a valid network image for the JAR files that you are using. For example, if you are adding languages to a Siebel image for Siebel CRM 17.0, then the top-level directory that you specify, such as /Siebel_Install_Image, must contain a subdirectory 17.0.0.0, which must contain an existing Siebel image for the corresponding release. Siebel Image Creator cannot add modules or languages to the network image unless you specify a valid top-level directory.
Any directory that you specify for creating a Siebel image must follow the conventions described in File and Directory Naming Conventions. For example, on Windows, a directory name must not contain spaces or number signs (pound or hash signs).
Do not move or rename any Siebel image subdirectories. Create each Siebel image and all of its directories by running Siebel Image Creator. It is acceptable to move or rename the top-level directory in which the Siebel image was created.

Cross-Platform Issues When Creating Siebel Image Directories

This topic is part of Preparing to Create a Siebel Installation Image.

Each Siebel image that you create contains directories representing the specified operating system platforms that you will use, such as Windows, AIX, and so on. The Siebel image itself can reside on any supported operating system. Siebel Image Creator can run natively on Microsoft Windows, IBM AIX, HP-UX, Linux, and Oracle Solaris.

Many customers support multiple operating systems. For example, a customer who installs server modules on UNIX still might have to install client or server modules that run only on a supported Microsoft Windows operating system, such as Siebel Web Client (Siebel Mobile Web Client) and Siebel Tools. For more information, see Siebel Installation Media Contents.

If you support multiple operating systems (such as Windows and one of the supported UNIX operating systems), then use one or more of the following strategies in creating your Siebel images:

Create a single multi-platform Siebel image on one of your operating systems. Use a cross-platform networking tool, such as Samba, to make the Siebel image accessible from operating systems other than the one where the Siebel image was created.
For example, when you run Siebel Image Creator on Windows, include Windows and all of the applicable UNIX operating systems and include all of the modules for applicable operating systems. Before you run Siebel Image Creator, make sure that you have located the JAR files as described in Determining the Locations for the Siebel Media Files and the Siebel Image. In order to install modules on UNIX computers (in this example), users who perform installations must be able to access the Windows-based Siebel image files.
This approach is generally recommended, because it consolidates all of the modules and applicable operating systems in a single Siebel image.
On each applicable operating system, create a separate Siebel image that includes the modules that will be installed on that operating system.
For example, you might run Siebel Image Creator on Windows and include only the Windows operating system and the modules that will be installed on Windows. Then you might run Siebel Image Creator on Oracle Solaris and include only Oracle Solaris and the modules that will be installed on that operating system. Before you run Siebel Image Creator, make sure that you have obtained the JAR files for the applicable operating system, as described in Determining the Locations for the Siebel Media Files and the Siebel Image.
In order to install the Siebel CRM modules (in this example), no cross-platform tool would be necessary to access the Siebel image files, because the files for each module already reside on the operating system on which the installations will be performed.

Requirements for Running Siebel Image Creator

This topic is part of Preparing to Create a Siebel Installation Image.

Before you run Siebel Image Creator for one of the supported operating systems, consider the following requirements:

Make sure that you have extracted all of the JAR files from the ZIP files.
You must place the Siebel CRM module JAR files and the Siebel Image Creator files in the appropriate directory or directories, as described in Determining the Locations for the Siebel Media Files and the Siebel Image.
You must place at least one JAR file representing a Siebel CRM module in the directory where you run Siebel Image Creator, referred to here as the JAR files directory. Doing so enables the utility to determine the version of the Siebel image that is to be created. For example, run Siebel Image Creator in the JAR files directory for Siebel CRM 17.0 to create a Siebel image for that version. If the directory from which you run Siebel Image Creator contains JAR files with multiple versions, then the utility prompts for the version when you start it.
It is strongly recommended that all of the Siebel CRM module JAR files for the same version be located in the same directory (the JAR files directory). Optionally, some JAR files might be located in one or more other directories that you specify while running Siebel Image Creator.
Siebel Image Creator includes the following files, which must be present in the JAR files directory where you run the utility. Do not modify these files.
- The Siebel Image Creator executable program for the operating system on which you run the utility: snic.bat (for Windows) or snic.sh (for UNIX)
- snic.jar
- siebel.ini
Siebel Image Creator also includes the following template response files, which you can edit and use to run the utility in unattended mode:
- sample_snic_windows.rsp
- sample_snic_unix.rsp
You can run Siebel Image Creator in GUI mode or in unattended mode. The following requirements apply only to running the utility in unattended mode:
- To run Siebel Image Creator in unattended mode, you must use the U.S. English (ENU) locale.
- When using unattended mode, you can only create a new Siebel image. You cannot add languages or products to an existing Siebel image.
- To run Siebel Image Creator in unattended mode, you must use a template response file provided by Oracle that you have edited for your purposes. These files are named sample_snic_windows.rsp and sample_snic_unix.rsp. Example values are shown in the template response files. For example, you might specify values like the following, from the file sample_snic_windows.rsp:
```
imageVersion="17.0.0.0"
imageDirectory="Siebel_Install_Image"
platformList={Windows}
productList={Siebel_Tools}
languageList={ENU}
```
Java Runtime Environment (JRE) must be installed on any computer where you will run Siebel Image Creator. Also, the JAVA_HOME environment variable must be set to point to the JRE installation location at the time that you run Image Creator (for example, C:\Program Files\Java\jre8 on Windows or /usr/java8_64 on AIX). For supported version information, see the Certifications tab on My Oracle Support.
A Siebel Image Creator session might take a long time to complete. While the files are being extracted or copied, you cannot click Cancel to cancel a Siebel Image Creator session. Be sure of your selections before you begin creating the Siebel image.
For any issues that you encounter while running Siebel Image Creator as described in Creating a Siebel Installation Image, see Troubleshooting Siebel Image Creation.

Creating a Siebel Installation Image

You use Siebel Image Creator to create the Siebel installation image (the Siebel image) on the network for all of the Siebel CRM modules that were delivered through the Siebel media files.

The procedure in this topic describes running Siebel Image Creator to create a new Siebel image or running the utility to add modules or languages to an existing Siebel image. When you add modules or languages to an existing Siebel image, some of the steps do not apply.

Note: You can run Siebel Image Creator in GUI mode or unattended mode. If you will run Siebel Image Creator in unattended mode, then you must first prepare a response file. For more information about running Siebel Image Creator in unattended mode, see Requirements for Running Siebel Image Creator.

To create a Siebel installation image

Review the information that is presented in Obtaining Siebel Installation Media Files and Siebel Installation Media Contents.
Review the issues that are described in Preparing to Create a Siebel Installation Image. In particular, determine where the Siebel JAR files will reside and where you will create the Siebel image.
Obtain the Siebel media ZIP files, as described in Obtaining Siebel Installation Media Files. If you download the files, then validate the checksum values of the downloaded files against the published values. Then extract the JAR files from the ZIP files.
Place the JAR files into one or more version-specific directories that you created for the purpose.
For example, for Siebel CRM 17.0, you might place the Siebel CRM 17.0 JAR files into a directory like JAR_17.0. Also place the files for Siebel Image Creator in this directory. For more information, see Determining the Locations for the Siebel Media Files and the Siebel Image.
Log on to the server computer on which you will run Siebel Image Creator.
Open a shell window and navigate to the directory where you placed the Siebel media JAR files and the Siebel Image Creator files. For example, for Siebel CRM 17.0, navigate to a directory like /export/home/Siebel_Install_Image/JAR_17.0.
If it is not already set, then set the JAVA_HOME environment variable to point to the Java Runtime Environment installation location.
To run Siebel Image Creator in unattended mode from the JAR files directory, first prepare a response file, and then run a command like the following:
```
./snic.sh -silent -responseFile response_file
```
The Siebel image is created, according to the settings you made in the response file, as described in Requirements for Running Siebel Image Creator. Go to the last step.
To run Siebel Image Creator in GUI mode from the JAR files directory, run the following command:
```
snic.sh
```
Siebel Image Creator displays a welcome message.
Click Next to proceed.
Specify whether you are creating a new Siebel image (or adding modules to an existing Siebel image) or adding languages to an existing Siebel image. Click Next.
If you are creating a new Siebel image, then specify the directory in which the version-specific image directory is to be created. For example, navigate to a directory like /export/home/Siebel_Install_Image. You can enter a directory (which must be an absolute path) or click Browse to specify the directory. Click Next.
When you specify the network image directory for adding modules or languages, you must specify the top-level directory containing the valid network image for the JAR files that you are using. For more information, see Requirements for the Siebel Image Directories.
For guidelines for creating the directories for Siebel images, see Preparing to Create a Siebel Installation Image.
If applicable, then specify the version for the Siebel image.
The Siebel image version automatically derives from the presence of one or more Siebel media JAR files for Siebel CRM modules in the directory from which you are running Siebel Image Creator. If JAR files exist for multiple versions, such as Siebel CRM 17.0 and Siebel CRM 20.9 Update, then specify one of the versions shown.
The version determines the version-specific subdirectory in which the Siebel image is created, such as 17.0.0.0. Or, the version specifies an existing Siebel image to be added to.
If you are adding modules to an existing Siebel image, then go to the next step.

If you are adding languages to an existing Siebel image, then go to Step 16.
Specify one or more operating systems to include in your version-specific Siebel image. You can specify Windows, AIX, HP-UX, Linux, and Oracle Solaris. Click Next.
You can specify one or more operating systems to include in your Siebel image. In general, include all of the operating systems for which you will install one or more Siebel CRM modules. You can add operating systems and modules to the Siebel image later. For more information, see Cross-Platform Issues When Creating Siebel Image Directories.
For more information about the contents of the Siebel media, see Siebel Installation Media Contents.
Specify the Siebel CRM modules to include in your version-specific Siebel image. Click Next.
The Siebel image will include the selected modules for each applicable operating system that you specified in Creating a Siebel Installation Image. Some modules do not apply to certain operating systems. For example, Siebel Tools applies to Windows only.
For more information about the contents of the Siebel media, see Siebel Installation Media Contents.
Each module can be selected by clicking its check box. The listed modules represent the superset of the client and server modules, including third-party modules, that are supported by this version of Siebel Image Creator for all of the applicable operating systems.
Specify all of the languages that you want to include in the Siebel image. When you are ready to begin creating the Siebel image based on your selections, click Next.
The selected languages are included for each selected or existing module, where they apply. The languages do not apply to some modules, such as third-party modules. For information about Siebel Tools and the U.S. English language pack, see Siebel Installation Media Contents.

Note: If you are adding modules to an existing Siebel image, then you must specify all of the languages that were previously included in the Siebel image, in order to be able to install these modules correctly.
Siebel Image Creator now processes all of the Siebel media JAR files in the current directory, and includes all of the selected modules and languages in the version-specific Siebel image subdirectory of the directory that you specified in Step 12. Siebel Image Creator displays the current processing status, as follows:
- If all of the Siebel media JAR files matching your selections were found in the current directory, then Siebel Image Creator completes creating or adding modules or languages to the Siebel image. Go to Step 18.
- If one or more of the JAR files matching your selections were not found in the current directory, then the utility prompts for the location of the next file. Go to Step 17.
If Siebel Image Creator cannot locate a JAR file matching your selections, then specify the location of the indicated Siebel media JAR file. You can enter a directory (which must be an absolute path) or click Browse to specify the directory. Click Next.
For example, for a Siebel CRM 17.0 Siebel image, assume that you selected Windows and Siebel Tools, but Siebel Image Creator could not locate the file SBA_17.0.0.0_Base_Windows_Siebel_Tools.jar. Specify the location of this file, and click Next. If the file is found, then it is processed and the module that it represents is included in your Siebel image.
If you do not have the current media JAR file, then you might have to obtain the required Siebel media from Oracle before proceeding. Place the JAR file in the appropriate directory before clicking Next. If all of the remaining Siebel media files matching your selections were found in the current directory, then Siebel Image Creator completes creating or adding the modules or languages to the Siebel image.
If you decide that you do not require the Siebel CRM module or language component represented by the current media file to be included in the Siebel image at this time, then click Next again. You are prompted to either skip the file (click Skip) or look for the file in another directory (click Select). You might have to rerun Siebel Image Creator later to add items that you previously skipped because of missing JAR files. See also Troubleshooting Siebel Image Creation.
After all of the modules or languages have been added to the Siebel image, or skipped, Siebel Image Creator indicates that the Siebel image has been successfully created. Click Finish.
After the Siebel image has been created, review the products.txt file to validate the modules that were included in the Siebel image. This file is located in the main directory for the Siebel image, such as /Siebel_Install_Image/17.0.0.0.

Troubleshooting Siebel Image Creation

When you run Siebel Image Creator, the utility validates the integrity of each JAR file that it processes as it creates the Siebel image. Consequently, it is unnecessary to validate the JAR files beforehand.

If a JAR file is invalid for some reason, then Siebel Image Creator displays a message to this effect. Obtain a new copy of the JAR file and rerun Siebel Image Creator in order to include the content in the Siebel image. Rerunning Siebel Image Creator might also be necessary in some other cases identified in this topic.

When you run Siebel Image Creator and create a Siebel image successfully, the files in the Siebel image have the same timestamp as the corresponding files that were included in the JAR files.

When you rerun Siebel Image Creator, it will not replace any files that have the same or a newer timestamp.

Rerunning Siebel Image Creator might be necessary in the following cases:

If you have deleted a Siebel image or any part of the Siebel image by mistake. In this case, remove all of the files generated by Siebel Image Creator for any affected Siebel CRM modules, then run Siebel Image Creator again to recreate the Siebel image for those modules.
If a JAR file is invalid and you have since obtained a new version of the JAR file.
If you skipped a missing JAR file during a Siebel Image Creator session and have since obtained the missing JAR file.
If any Siebel CRM module was incompletely processed by Siebel Image Creator. In this case, remove all of the files generated by Siebel Image Creator for the affected module, then run Siebel Image Creator again to recreate the Siebel image for this module.

Note: Keep track of the operating systems, Siebel CRM modules, and languages in your Siebel image for the applicable version. If you have to rerun Siebel Image Creator, then reselect the options that you require to complete the Siebel image.

You might also have to run Siebel Image Creator multiple times if you intentionally processed only some of the Siebel CRM modules that you require and have to process the JAR files in multiple batches.

Siebel Image Creator Logging

Siebel Image Creator logs details about its processing in the file log.txt, which is created in the top-level directory that you specified for the Siebel image (for example, /export/home/Siebel_Install_Image).

Review the log file to identify where problems occurred when you created the Siebel image, such as in the following cases:

Siebel Image Creator logs a message like the following after each JAR file has been successfully extracted. (If a JAR file is only partially extracted, then this message is not written.)

Extracted SBA_17.0.0.0_Base_Windows_Siebel_Enterprise_Server.jar

Siebel Image Creator logs a message like the following when a JAR file has been skipped.

Skipped JAR_file_name - Please run Siebel Image Creator again and add module_name to the network image, once all image files are available.

Installer Errors and the Siebel Image

You must validate that the Siebel image was created correctly for all of the applicable modules. However, installation errors sometimes indicate problems in the Siebel image.

If, when you run a Siebel installer, errors are returned about missing or corrupt files, then remove all of the files generated by Siebel Image Creator for any module that was incompletely processed, make sure that you have all of the JAR files that you require (including those representing third-party files), and then run Siebel Image Creator again to recreate the Siebel image for that module.

For installation instructions, see Installing Siebel CRM Server Modules and other chapters for installing particular Siebel CRM modules.

For installation requirements, see Requirements for Installing and Configuring Siebel CRM.

For installation troubleshooting information, see Verifying and Troubleshooting Your Installation.

12Creating the Siebel Installation Image on the Network