Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Business Process Framework: Workflow Guide > Example Workflow Processes That Call a Business Service > Externalizing Properties When Using a Business Service > Overview of Externalizing PropertiesIf you migrate a repository between the development environment, test environment, and the production environment, then you must modify any workflow process that uses a business service that interacts with an external system.The EAI HTTP Transport business service is an example of a business service that interacts with an external system. The HTTPRequestURLTemplate input argument requires the URL of the external system. A workflow process that uses the EAI HTTP Transport business service references the following items:
This example does the following work:
This configuration uses values stored in files in the following ways:
This example does not hard code values for the input arguments of the business service that the workflow process references. Instead, the script on the Service_PreInvokeMethod Event method reads the file at run time. The file that this configuration uses must use a particular file name and must be available to each Siebel Server. If not, then the business service fails and Siebel Workflow creates an error at the business service step, which is the required behavior. If you add a script to the Service_PreInvokeMethod event of a business service, then you must define an input argument named ExternalSystem, and the value for this argument must match the XML tag name of the child of the root element in the file. This script uses the child elements as input arguments. These child elements are children of the parent element that resides at the second level of the file. Benefits of Externalizing PropertiesYou can realize the following benefits if you externalize properties:
|
![]() ![]() |
Siebel Business Process Framework: Workflow Guide | Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |