Bookshelf Home | Contents | Index | Search | PDF |
Siebel Life Sciences Guide > Importing Data > Administrator Procedures >
Extracting Data for Mobile Users
Once the data is in the database, it needs to be made visible to the users. The data is visible by position and can be viewed on many chart and analysis views in Siebel Life Sciences. This is fine for connected users, but the typical user of such data will be the sales rep or sales manager of a particular territory, who are likely to be remote users, synchronizing with the database using Siebel Remote. Therefore, the data needs to be extracted from the database.
The application administrator extracts syndicated data according to data-routing (visibility) rules that the administrator defines. When you do this, a full export-process audit trail is generated through log files. You can run multiple instances of the extraction process on each Siebel Server to maximize hardware capacity. The resulting output files are written in a compressed form and then zipped again to minimize file transfer time.
NOTE: You will need to work with Siebel Technical Services when you perform this procedure the first time.
The general steps for data extraction are:
- Create a data extraction rule.
- Associate the necessary nodes of mobile users with the rule.
- Define the portion of the data you want to extract and specify whether any truncation or deletions should be performed on the extracted data.
- Set the environment by running the siebenv.bat file at the command prompt under the Siebel Server bin directory.
- Run the Syndexp.exe executable file to perform the extraction.
These general steps are detailed in the following procedures.
To create a data extraction rule
- From the application-level menu, choose View > Site Map > Syndicated Data Administration > Export Rules.
- Click to select the Rules list and add a record.
- Complete the fields described in the following table.
You can create multiple rules for different types of extractions. For example, you could create one rule for Rx data and another rule for Outlet Level data. You can also extract data by multiple criteria (for example, sales force or position).
The WHERE part of a SQL SELECT statement specifies the rows of the S_SYND_DATA table that should be exported. In most cases, this WHERE clause is
WHERE T.POSITION_ID = [Position Id]
When you specify the users to extract, it will match their position ID to the position ID on the syndicated data table and extract only the data that is visible to them.
To associate nodes with an extract rule
- In the Syndicated Data Export Rules view, select the correct extract rule.
If a different view is currently displayed, navigate to Data Administration > Export Rules and select the appropriate rule.
- Click in the Nodes list and add a record.
- Complete the fields. Some fields are described in the following table.
To specify the data that is routed to mobile users
- In the Syndicated Data Export Rules view, select the correct extract rule.
If a different view is currently displayed, navigate to Data Administration > Export Rules and select the appropriate rule.
- Click in the Tables list and add a record.
- Complete the fields. The fields are described in the following table.
- In the Syndicated Data Administration screen, from the Show drop-down list, select SQL Statements.
- Click in the Pre SQL Statements list and add a record.
- Complete the fields described in the following table.
You can refresh the entire syndicated data table, or you can refresh only certain specified data periods.
NOTE: Do not use the TRUNCATE TABLE function. Use the DELETE function instead.
To set the environment
- In a DOS window, navigate to the
siebel_server
\BIN
directory.- Run the siebenv.bat file.
CAUTION: If you do not run siebenv.bat, you may encounter the following error message: "Unable to start common api. Error in DATAExpStartApis function."
- Set the environment variables.
NOTE: Syndexp.exe will not detect nodes in a clustered environment successfully unless you manually set CLUSTER_NETWORK_NAME in either siebenv.bat or syndexp.bat.
Refer to the command line arguments listed in Table 21 for multiple variables that are specific to the user environment. For more information on administering data extracts, see Siebel Remote and Replication Manager Administration Guide.
To perform the data extraction
- In the
siebel_server
\BIN
directory, run the Syndexp.exe executable file.Use the command line arguments listed in Table 21 to define multiple variables that are specific to the user environment. For example:
syndexp /U sadmin /P sadmin /D phdemo /E "Rule One" /C siebsrvr_siebel
NOTE: Interruption of the extraction process at any point causes the system to fail and necessitates restarting the data extraction from the beginning.
- If an interruption occurs, you must go into the Pharma Node Attachment Administration view (View > Site Map > Syndicated Data Files) and delete the previously generated data files. You also must go into each node and delete the latest file that was created in the previous run.
After the program executes the Syndicated Data Loading (SDL) process, it displays the name of the user whose data is being extracted. This process continues until it has completed the extraction process for each user defined in the Syndicated Data Export Rules.
- After you successfully complete the extraction process, you may want to create a batch file for use with subsequent extractions.
The extracted files are output in a compressed form to minimize file transfer time. Files are transferred using Siebel Remote, which is described in Siebel Remote and Replication Manager Administration Guide. After mobile users receive their extracted files, they must import the data into their local databases.
Full and Partial Data Extracts
Because syndicated data loading does not use EIM to maintain synchronization between the server and the remote databases, you must force a resynchronization step at the end of each direct load. Force resynchronization either by re-extracting an entirely new remote database for each mobile user or by performing a partial extract that includes only the refreshed syndicated data. A new, full database extract creates a database snapshot file for a given mobile user. A partial extract contains only S_SYND_DATA table data.
Some users receive syndicated data updates once a week, while some may receive syndicated data updates monthly or quarterly. Therefore, partial extract is preferred.
Possible Data Loss
Sometimes remote users connect to Siebel Server using unstable dial-up connections that prevent the data file from being transferred correctly, so that the data file does not reach the remote server. Siebel Server does not verify that the data file reached its destination successfully. At the end of the transfer step, Siebel Server removes the data file from the server.
In the case in which a data file is lost and removed from the server, you must extract a new data file for users.
CAUTION: The loss of data or files may occur without warning. You might not be able to automatically determine the success or failure of a particular transfer. As a result, sales representatives may be using incorrect data for up to several months without realizing it.
Bookshelf Home | Contents | Index | Search | PDF |
Siebel Life Sciences Guide Published: 18 April 2003 |