Siebel Loyalty Administration Guide > Setting Up Siebel Loyalty Promotions > About Simulating Loyalty Transactions >

Configuring Summary XML File Destinations for Simulations

This topic explains how to modify the destination location for XML summary files generated for simulations.

The default destination is on the server, and it is recommended that you do this configuration because some users do not have access to the server.

NOTE:  Write access must be granted to the folders that are used to store output files.

The number of files generated depends on the output batch size. For example, if there are 300 transactions and the output size is 10, then 30 files will be created.

The naming of the file for bulk transaction simulations uses the following form:

SimulationResults_<Bulk Ref ID>_<Output Batch Size Num>.XML

Single transaction simulation is not saved automatically, but the user can choose to save it in a file. You can modify the location where the user is prompted to save the file.

You can refer to the Bulk Action History list applet to find the Bulk Reference ID. For information about accessing this list, refer to Viewing Bulk Transaction Simulation History.

Modifying the XML Output File Destination for Bulk Transaction Simulations

Perform the steps in the following procedure to modify the XML output file destination for bulk transaction simulations.

To modify the XML output file destination for bulk transaction simulations

1. Select the LOY Bulk Simulation Process workflow in Siebel Tools.
2. Query for the PathName process property.
3. Update the value of the PathName process property to the desired destination path.
4. Activate and deploy the workflow.

Modifying the XML Output File Destination for Single Transaction Simulations

Perform the steps in the following procedure to modify the XML output file destination for single transaction simulations.

To modify the XML output file destination for single transaction simulations

1. Select the LOY Simulate Single Txn business component in Siebel Tools.
2. Query for the File user property.
3. Update the value of the File user property to the desired destination path.
4. Compile the business component in the SRF file.
5. Restart the services.