Page History
...
- Open Siebel Tools.
- In the Object Explorer, on the Types tab, select Project.
- Create a new project by holding down the pressing Ctrl+n.
- Name the new project, "Precise Interpoint."
- Lock the project by clicking the Locked column to the right.
| Anchor | ||||
|---|---|---|---|---|
|
...
To create the CX_VTSSPID table1. From
- From the File menu, select New Object.
...
- In the New Object Wizard, on the General tab, select Table; then click OK.
...
- In the General dialog box, do the following:
- In the Enter a name for the new Table text box, type CX_VTSSPID.
- From the Choose a Project in which you wish to create the Table list, select Precise Interpoint.
- Under Select the type of the Table, select A stand-alone Table.
...
- Click Next; then click Finish to close the dialog box.
...
- In the Tables workspace, click Apply.
...
- In the Apply Schema dialog box, if needed, type a valid privileged user ID and privileged user password into the relevant text boxes.
...
- Click Apply. The dialog box closes, and the table is created.
...
- In the Tables panel, click Activate to activate the new table.
| Anchor | ||||
|---|---|---|---|---|
|
...
To create the business component1. In
- In Siebel Tools, from the File menu, select New Object. The New Object Wizard opens.
...
- On the General tab, select BusComp.
...
- Click OK.
...
- In the New Business Component dialog box, do the following:
- In the Enter a name for the new Business Component text box, type VTS_SPID.
- From the Select the Project this Business Component will be part of list, select Precise Interpoint.
- From the Select the Table this Business Component will operate on list, select CX_VTSSPID.
...
- Click Next.
...
- In the Single Value Fields dialog box, from the Select a column in the Base table list, select ROW_ID. A default Field name automatically appears in the Enter a name for the Field text box.
...
- Click Add to move the selected row to the table; then click Finish to create the business component.
| Anchor | ||||
|---|---|---|---|---|
|
...
To create the business object1. In
- In Siebel Tools, in the Objects Explorer, on the Types tab, select Business Object.
...
- In the Business Objects panel, from the Edit menu, select New Record. A new record is added to the table in the Business Objects panel.
...
- In the Name column, type: VTS_SPID.
...
- In the Project column, assign the new record to the VERITAS Interpoint project.
...
- On the Types tab in the Object Explorer, select Business Object > Business
...
- Object Component.
...
- From the Edit menu, select New Record. A new record is added to the table in the Business Object Components panel.
...
- In the BusComp column, type: VTS_SPID.
...
- From the Tools menu, select Compile Project.
| Anchor | ||||
|---|---|---|---|---|
|
...
To add the Application_PreNavigate() function1. In
- In Siebel Tools, from the View menu, select Options.
...
- In the Development Tools Options dialog box, on the Scripting tab, note the value of the Scripting Language list and click OK.
...
- In the Object Explorer, on the Types tab, expand Application.
...
- Right-click on the application to be modified and select Lock Object.
...
- Right-click on the application to be modified and select Edit Server Scripts.
...
- In the Server Script Editor, select the Application_PreNavigate function. The function's default script appears in the text panel.
If this function already contains a custom script, contact Precise Customer Support for alternative instructions.
...
- Replace the default script with the following script:
Function Application_PreNavigate (DestViewName As String,
...
DestBusObjName As String) As Integer
Dim cmd As String
Dim oActionBO As BusObject
Dim vtsBC As BusComp
Dim spid As String
Const appName = "Siebel Sales Enterprise"
On Error Resume Next Set oActionBO = theApplication.GetBusObject("VTS_SPID")
...
Set vtsBC = oActionBO.GetBusComp("VTS_SPID")
With vtsBC
ClearToQuery
ActivateField "Row Id"
ExecuteQuery ForwardOnly
FirstRecord
i = .GetFieldValue("Row Id")
End With
Set oActionBO = Nothing
Set vtsBC = Nothing
cmd = "vrts_srf_agent.exe " + i + " """ + appName + """ """ +
...
DestViewName + """ """ + DestBusObjName + """ """ + LoginName
...
+ """"
Shell(cmd)
Application_PreNavigate = ContinueOperation
End Function
If the Scripting Language in use is eScript, use the following script:function Application_PreNavigate (DestViewName, DestBusObjName)
{
try
{
var cmd;
var oActionBO;
var vtsBC;
var appName = "Siebel Sales Enterprise";
oActionBO = TheApplication().GetBusObject("VTS_SPID");
vtsBC = oActionBO.GetBusComp("VTS_SPID");
vtsBC.ClearToQuery();
vtsBC.ActivateField("Row Id");
vtsBC.ExecuteQuery(ForwardOnly);
vtsBC.FirstRecord();
cmd = "start cmd /c vrts_srf_agent.exe " +
vtsBC.GetFieldValue("Row Id") +//SPID
...
" \"" + appName +
"\" \"" + DestViewName +
"\" \"" + DestBusObjName +
"\"\"" + TheApplication().LoginName() +
"\"";
vtsBC = null;
oActionBO = null;
Clib.system(cmd);
}
catch (obj)
{
Clib.system( "start cmd /c vrts_srf_agent.exe \"" + obj +
...
"\"" );
return (ContinueOperation); //Ignore all exceptions
}
}
...
- Modify the appName variable to match the name of the Siebel application.
| Anchor | ||||
|---|---|---|---|---|
|
The following procedure replaces the table with a custom view. To replace the table with a custom view1. Log
- Log on to your Siebel database using Query Analyzer. Make sure to log on with a privileged account.
...
- Run the following script:
DROP TABLE CX_VTSSPID
GO
CREATE VIEW [CX_VTSSPID] as select
'1' as [CONFLICT_ID],
getdate() as [CREATED],
'--' as [CREATED_BY],
getdate() as [LAST_UPD],
'2' as [LAST_UPD_BY],
1 as [MODIFICATION_NUM],
@@spid as [ROW_ID]
GO
GRANT SELECT ON [CX_VTSSPID] TO public
GO
| Anchor | ||||
|---|---|---|---|---|
|
...
To complete the modification1. Save
- Save all changes.
...
- Compile the Siebel project. This will create a new Siebel.srf file.
...
- Test the project on your development machine.
...
- On each of your production Siebel Servers:
...
- Stop the Siebel Server.
...
- Deploy the new Siebel.srf file
...
- Verify that the EnableScripting option in the application CFG file is set to TRUE.
...
- Start the Siebel Server.
| Anchor | ||||
|---|---|---|---|---|
|
The following procedure debugs the script.
To debug the script1. Before
- Before attempting to debug, from the View menu, select Options.
...
- On the Debug file tab, open the file that is specified in the CFG file text box in a text editor.
...
- Make sure that the RepositoryFile and ApplicationName options are set correctly.
...
- Make sure the EnableScripting option is set to TRUE.
| Anchor | ||||
|---|---|---|---|---|
|
For Siebel batch processes to be sampled by the Interpoint for Siebel Collectors, create a tab-delimited text file that contains the mapping of each Siebel server to its host machine, as it appears in Oracle.
To create the text file:1. Log
- Log on to the server where your Siebel AppTier Collector instance is installed.
...
- Create the following tab-delimited text file:
...
- Windows
...
...
<Precise_
...
root>\products\oracle\<SID>\etc\siebel_machines.txt
...
- UNIX
...
...
<Precise_
...
root>/products/oracle/<SID>/etc/siebel_machines.txt
To obtain the list of Siebel servers:1. Log
- Log on to the SrvrMgr utility.
...
- Execute the following command:
list servers
The following list is an example of the results:
Table 1-1 List 1 List of Siebel servers
SBLSRVR_ |
|---|
...
NAME | HOST_NAME |
|---|
...
AsDev1 | POOL-SIEBEL1 |
...
AsDev2 | POOL-SIEBEL2 |
Each returned row represents a Siebel server. The row information can be split into two columns:• The
- The first column,
SBLSRVR_NAMErepresents the name of the Siebel server, for exampleAsDev1.
...
- The second column
HOST_NAMErepresents the corresponding physical machine name, but not necessary as it appears in Oracle.
To find the physical machine name as it appears in Oracle, connect to the Siebel database and execute the following command:
SELECT DISTINCT MACHINE FROM V$SESSION;
The following list is an example of the results:
Table 1-2 Machine 2 Machine name list
MACHINE |
|---|
PRECISE\POOL-SIEBEL1 |
PRECISE\POOL-SIEBEL2 |
If there is no entry in V$SESSION with the physical machine name, use the results from the HOST_NAME column. After inserting the previous results into the siebel_machines.txt file, the contents is as follows:
AsDev1 PRECISE\POOL-SIEBEL1AsDev2 PRECISE\POOL-SIEBEL2
| Anchor | ||||
|---|---|---|---|---|
|
...