Skip Headers
Siebel CRM Composer Developer Preview Guide
Siebel Innovation Pack 2015 Rev. A
E60725-01
  Go to Documentation Home
Home
Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
 
Next
Next
    View PDF

About the Web Template Migration Process

A Web template migration process is automatically completed when:

In this process, a script is run to convert file-based content for Siebel Web templates into the table-based content for Siebel Web templates. This table-based content appears in fields in Siebel CRM Composer. For more information about the newly added fields in Siebel CRM Composer, see "Added Fields in Siebel CRM Composer".

The semantics of the logical Web template are retained in this conversion process. Table 3-1 shows how the information in Siebel Web template files is mapped to the fields in Siebel CRM Composer.

Table 3-1 Information in Siebel Web Template Files Mapped to Fields in Siebel CRM Composer

Information in Siebel Web Template Files Fields in Siebel CRM Composer

HTML (Hypertext Markup Language) tag and SWE (Siebel Web Engine) tag

For more information, see "HTML Tags Migrated to Siebel CRM Composer" and "SWE Tags Migrated to Siebel CRM Composer".

Name

Name of nested content when tags are nested under another tag

Group Name

Order in which a tag appears in the Siebel Web template

Sequence

Class names for an HTML tag or an SWE tag

HTML Attributes


New Web templates are created for the Siebel Web template files that are included in another Siebel Web template file.

All Siebel Web template files in the appropriate directories are included in the migration process. For more information about the appropriate directories, see "Prerequisite for Web Template Migration Process".

The migration script is supported in all environments and database platforms. For more information about installing a new Siebel database, see Siebel Installation Guide for the operating system you are using. For more information about upgrading the Siebel database and about using Incremental Repository Merge, see Siebel Database Upgrade Guide.

Prerequisite for Web Template Migration Process

In the Web template migration process, files associated with Siebel Web templates are migrated to table-based content from the appropriate directories. This process looks for a Siebel Web template, and then looks for its associated file in the siebsrvr_root\webtempl\ouiwebtempl\custom directory. If this file exists in this directory, then the process parses the file, and looks for the next Siebel Web template. If this file does not exist in this directory, then the process looks for the file in the siebsrvr_root\webtempl\custom directory. If this file exists in this directory, then the process parses the file, and looks for the next Siebel Web template. If this file does not exist in this directory, then the process includes the file in the List of Missing Files section of the swt_mig.log file. For more information, see "Verifying the Results of Web Template Migration Process".

Files associated with Siebel Web templates are not migrated from the siebsrvr_root\webtempl\ouiwebtempl directory and the siebsrvr_root\webtempl directory. Consequently, you must copy files associated with Siebel Web templates from these directories into the corresponding custom directories if the files do not already exist in the custom directories.

HTML Tags Migrated to Siebel CRM Composer

Table 3-2 shows the HTML (Hypertext Markup Language) tags that are migrated to fields in Siebel CRM Composer in the Web template migration process.

Table 3-2 HTML Tags Migrated to Siebel CRM Composer

Tag Name General Tag Purpose

div

Generates a container record for a Web template item and for its properties.

li

Generates a container record for a Web template item and for its properties.

span

Generates a container record for a Web template item and for its properties.

ul

Generates a container record for a Web template item and for its properties.


SWE Tags Migrated to Siebel CRM Composer

Table 3-3 shows the SWE (Siebel Web Engine) tags that are migrated to fields in Siebel CRM Composer in the Web template migration process.

Table 3-3 SWE Tags Migrated to Siebel CRM Composer

Tag Name General Tag Purpose Migration Restrictions

swe:applet

Generates a content item record for a Web template item, and updates the corresponding holder name of the template item in the mapped record of the view Web template item.

None.

swe:applet-assoc-mvg

Generates a content item record for a Web template item.

None.

swe:applet-tree-list

Generates a content item record for a Web template item, and updates the corresponding holder name of the template item in the mapped record of the view Web template item.

None.

swe:case

Generates a container record for a Web template item.

None.

swe:control

Generates a container record for a Web template item, and updates the corresponding holder name of the template item in the mapped record of the applet Web template item.

None.

swe:current-view

Generates a content item record for a Web template item, and updates the corresponding holder name of the template item in the mapped record of the Web page item.

None.

swe:default

Generates a container record for a Web template item.

None.

swe:form-applet-layout

Generates a container record for a Web template item.

None.

swe:frame

Generates a container record for a Web template item.

Only the following types are included in the migration:

  • AltView

  • AppMenu

  • ThreadBar

swe:if

Generates a container record for a Web template item.

None.

swe:if-var

Generates a container record for a Web template item.

Only the following names are included in the migration:

  • AppletFilter-No

  • AppletFilter-Yes

  • Child

  • ChildWithPointer

  • Grandchild

  • Parent

  • ParentWithPointer

swe:include

Populates the included template for a Web template item.

None.

swe:list

Generates a content item record for a Web template item, and generates a new control (ListControl) record for the applet Web template item in a mapped applet.

None.

swe:menu

Generates a content item record for a Web template item, and generates a new control (TreeControl) record for the applet Web template item in a mapped applet.

Only the following types are included in the migration:

  • Button

  • Default

swe:nav-control

Generates a content item record for a Web template item and for its properties.

Only the following types are included in the migration:

  • Category View

  • Detail Category

  • Detail Category View

  • Detail Category With View

  • Screen

  • Screen With Category

Only the following styling tabs are included in the migration:

  • HB

  • Tab

swe:node

Generates a content item record for a Web template item.

None.

swe:pageitem

Generates a content item record for a Web template item, and updates the corresponding holder name of the template item in the mapped record of the Web page item.

None.

swe:pdqbar

Generates a content item record for a Web template item.

None.

swe:screenbar

Generates a content item record for a Web template item.

None.

swe:screenlink

Generates a content item record for a Web template item.

None.

swe:this

When this tag appears under an swe:applet tag, swe:control tag, or swe:pageitem tag, generates a property for a Web template item under its parent tag. This property has a type of Control Property.

When the property for this tag is RowCounter or Title, generates a record for a Web template item, and generates a new control (RowCounter or Title) record for the applet Web template item in a mapped applet.

Only the following properties are included in the migration:

  • DisplayName

  • FormattedHtml

  • RequiredIndicator

  • RowCounter

  • Title

swe:togglebar

Generates a content item record for a Web template item, and generates a new control (StaticToggle) record for the applet Web template item in a mapped applet.

None.

swe:toolbar

Generates a content item record for a Web template item and for its properties.

None.

swe:view

Generates a content item record for a Web template item.

None.

swe:viewlink

Generates a content item record for a Web template item.

None.


Manually Running the Migration Script

You can manually run the migration script for the Web template migration process by entering the following command in a command-line interface:

java -jar $DbsrvrRoot\common\SWTMigration.jar /s $SiebelRoot /c "$ODBCDataSource" /t $TableOwner /u $TableOwner /p $TablePassword /o $SiebelLogDir /d $DatabasePlatform /r "Siebel Repository" /l $SiebelLogDir/swt_mig.log

where:

  • $DbsrvrRoot is the path of the database server installation.

  • $SiebelRoot is the path of the Siebel Server installation.

  • $SiebelLogDir is the path to the log directory.

  • $DatabasePlatform is the database platform, such as Oracle, DB2UDB, MSSQL, and DB2390.

You can manually run the migration script as many times as needed.


Caution:

Each time that you run the script, all of the existing table-based content for Siebel Web templates is deleted, and then the new table-based content is created.

Verifying the Results of Web Template Migration Process

After the migration script runs, you can access the swt_mig.log file to review the results of the Web template migration process. This file is available when you manually run the migration script and when the migration script automatically runs. Near the end of this file, the following sections appear:

  • List of Missing Files. This section includes the files that are referenced in the repository but that do not exist in the Siebel Web template file directories.

  • List of Files which cannot be parsed. This section includes the files that are not converted to fields in Siebel CRM Composer because of an incorrect structure in the DOM (Document Object Model).

Publishing Changes to Siebel Web Templates

The Web template migration process generates the table-based content for Siebel Web templates. If the migration installation case applies to you, then you must publish the content in these tables so that the content is implemented in the Siebel application. If the new installation case applies to you, then publication of this content is automatically completed for you.

To publish the table-based content for Siebel Web templates, enter the following command in a command window on the computer where you installed Siebel Tools:

siebdev /c tools.cfg /u $SIEBUSER /p $SIEBPWD /d "$ODBCDataSource" /l enu /fullpublish