Siebel Life Sciences Guide > Completing Contact and Account Call Activities >

Configuring the Digital Migration Service for Signatures

NOTE:  This solution works on Microsoft Windows only.

High interactivity signatures are not visible in Siebel Life Sciences applications. If you want to view high interactivity signatures in Siebel Life Sciences applications, then you must migrate those signatures accordingly as shown in the following procedure. This ensures that previously captured high interactivity signatures are usable in Siebel Life Sciences deployments.

Before starting to configure the digital migration service for signatures, the following prerequisites are required:

1. Ensure that the SIGNATURE_IMAGE column in the (default) S_ACT_SIGN table is empty.
2. Verify that you can launch the Siebel HI URL in Internet Explorer 8 from the machine where the Siebel Server is hosted. This is required to ensure that the server has access to the signature image files.
3. Verify that the iSign90.cab file is not being used for signature control as follows:
   1. Log in to Siebel Tools, and click Applet in the Object Explorer.
   2. Click any record on the right hand side of the page.
   3. Query for the following applet: LS Pharma Call Signature Form Applet.
   4. Go to Control and query for the following name: Signature Capture.
   5. Expand the Control User Props and check the value of the AxCodeBase property.

      If AXCodeBase has the value iSign90.cab, then perform Change 1 and Change 2 as detailed in the following table.

      NOTE:  The repository changes detailed in the following table are temporarily required during signature migration. You must revert back to the original configuration once the signature migration process is complete.

      Change #	Description
      1	Change 1 details are as follows: Click Applet in the Object Explorer, click any record on the right hand side of the page, and then query for the following applet: LS Pharma Master Signature Form Applet. Go to Control and do the following: Query for the following name: Signature. Expand the Control User Props. Modify the value of the CLASSID property from clsid:93E5204A-4344-4381-8912-8A7091E0FAE5 to {EFB7D763-97A3-11CF-AE19-00608CEADE00}. Delete the CodeBase property. Modify the value of the Enabled property from 1 to TRUE. Change the name of the Signature property to Ink. Compile the LS Pharma Master Signature Form Applet.
      2	Change 2 details are as follows: Click Applet in the Object Explorer, click any record on the right hand side of the page, and then query for the following applet: LS Pharma Audit Signature Linear Form Applet. Go to Control and do the following: Query for the following name: Signature 1. Expand the Control User Props. Modify the value of the CLASSID property from clsid:93E5204A-4344-4381-8912-8A7091E0FAE5 to {EFB7D763-97A3-11CF-AE19-00608CEADE00}. Delete the CodeBase property. Modify the value of the Enabled property from 1 to TRUE. Change the name of the Signature property to Ink. Repeat this step for Control Signature 2, Control Signature 3, Control Signature 4, Control Signature 5, Control Signature 6. Compile the LS Pharma Audit Signature Linear Form Applet.

3. Before running the migration process (see Step 3 in the following procedure), create the SignMigration folder with read/write (and not read-only) permission.
4. If you observe any slowness or hang issue during signature migration, then clear the browser cache, restart the browser, and run migration.
5. If configuring the digital migration service for signatures where the signatures are stored in tables other than the (default) S_ACT_SIGN table, then do the following:
   1. Go to Business Component in Siebel Tools, query for LS Pharma Call Signature Migration, and modify the table property as follows:

      Business Component Name	Table
      LS Pharma Call Signature Migration	Change to the (New Table Name).

   2. Go to Fields in the Object Explorer and configure the columns appropriately for the fields described in the following table:

      Field	Column	Description
      Signature	Change to the (Column Name) where the signature is currently stored.	The name of the column where the signature is currently stored and from where the signature will be migrated. The value in this field is not modified during signature migration. The value in this field is read and converted to image data, and stored in the SignatureImg field.
      SignatureImg	Change to the (Column Name) where the signature will be stored after migration.	The name of the column where the signature will be stored after migration. The value in this field is modified during migration. This column must be of type CLOB (for more information, see the SIGNATURE_IMAGE column in the S_ACT_SIGN table).
      Call Date	Change to (any appropriate Column Name).	This column has no role in signature migration. The value in this field is not modified during migration.

   3. Configure the digital migration service for the signatures as shown in the following procedure.

The following procedure shows you how to configure the digital migration service for signatures. This procedure is required when migrating signatures from high interactivity mode to Siebel Open UI, and the solution works on Microsoft Windows only.

To configure the digital migration service for signatures

1. Configure the signature profile for the server as follows:
   1. In the Siebel business application, navigate to the Administration - Server Configuration screen, then the Enterprises view.
   2. In the Enterprises Server applet, select the enterprise server that you want to configure, and then click the Profile Configuration tab.
   3. Query for a profile configuration where the profile name is SignMigration. The details of the record returned are shown in the following table.

      Field Name	Value
      Profile	SignMigration
      Alias	SignMigration
      Subsystem Type	JVMSubsys

   4. In the Profile Parameters applet, set the following parameters for SignMigration:

      Name	Alias	Data Type	Value
      JVM Classpath	CLASSPATH	String	For example, the path to the classes is: SIEBSRVR_ROOT\CLASSES \InkToolsLib.jar; SIEBSRVR_ROOT\CLASSES \CLASSES\ iSignBmp.jar; SIEBSRVR_ROOT\CLASSES \ Build \CLASSES\SignMigration. jar; SIEBSRVR_ROOT\CLASSES\ Build \CLASSES\Siebel.jar
      JVM DLL Name	DLL	String	For example, the path to the JVM library file is: C:\PROGRA~1\Java\JDK15~1.0_0\jre\bin\c lient\jvm.dll

      If you are running signature migration from a thick client, then make sure that the following settings are set in the application cfg file:

   [SignMigration]

   FullName = SignMigration

   Description = Signature Migration Business Service Subsystem Parameters

   SubsysType = JVMSubSys

   CLASSPATH = C:\MyFiles\DBuilds\15072\siebel\classes\InkToolsLib.jar;C:\MyFiles\DBuilds\15072\siebel\classes\original\iSignBmp.jar;C:\MyFiles\DBuilds\15072\siebel\classes\SignMigration.jar;C:\MyFiles\DBuilds\15072\siebel\classes\Siebel.jar

   DLL = C:\Program Files (x86)\Java\jre1.8.0_51\bin\client\jvm.dll

2. Add the new view (LS Pharma Signature Migration Administration View) to the Admin responsibility.
3. Run the signature migration as follows:
   1. Log in to the machine where the Siebel Server is running.
   2. Start the (Microsoft Windows Internet Explorer 8) browser.
   3. Start and log into the Siebel Pharma application with Admin (administration) credentials.
   4. Go to Site Map.
   5. Navigate to the LS Pharma Signature Migration Administration View.
   6. Go to the LS Pharma Call Signature Conversion applet.
   7. Click the Convert Button.

NOTE:  If you generate a report from the Signature Audit View and converted signatures from high interactivity mode to Siebel Open UI do not appear in the report, then see release note Bug ID 21872840 in Siebel Patchset Installation Guides for Siebel Innovation Pack (Doc ID 1344310.1) on My Oracle Support for information about how to resolve this issue.