Key Points:
• Using XML Gateway Business Service to serve the VBC
• Using Business Integration Manager (Server Request) as Transport Protocol
• Create your own workflow to deal with the logic
Architecture:
• VBC trigger XML Gateway: Init(), Query(), etc
XML Gateway generates xml files corresponding to the command. Eg. It generates xml file
Contact
Matching Init() command
• XML Gateway triggers Business Integration Manager to invoke SendReceive() method
• Business Integration Manager sends the xml files generated by XML Gateway to Workflow
• Workflow gets the xml file and passes it to external application like MQ Series, MSMQ, HTTP Web Application or processes it inside the Siebel
• Workflow gets the result xml file from external application or Siebel Application and passes it back to Business Integration Manager (BIM)
• BIM receives the result xml file and passes back to XML Gateway to populate the VBC
Points of configuration:
• Create a BC of Class CSSBCVExtern
• Configure the above BC with following user properties
Service Name: XML Gateway
Service Parameters: Transport=EAI Business Integration Manager (Server
Request);ProcessName=;
• Create a process property as type of binary/string. Set the default to. It will hold the xml file generated by XML Gateway
• Create a process property as type of binary and named. It will pass back to BIM and XML Gateway to populate the VBC
• Analyse the xml file generated by XML Gateway to determine what action to be taken. (Query, Insert…)
• Use XSLT to transform the result xml file to the format XML Gateway needs to populate the VBC
Sample Workflow Design
Workflow Process Properties
Step Type Method Business Service
SaveIncomingXML Business Service Send EAI File Transport
Input Argument Type Value Property name
Process Property IncomingXML
FileName Literal C:\XMLGateway.txt
AppendToFile Literal True
Step Type Method Business Service
Analyse Incoming XML Business Service Echo Workflow Utilities
Output Argument Type Value Property name
CheckPoint Expression InStr([&IncomingXML],"fields-req")
Step Type Method Business Service
Is Init Request? Decision Point
Branch Condition Expression
Is Init Condition (CheckPoint Greater Than('0'))
Not Init Default
Step Type Method Business Service
Get Init XML Response Business Service Receive EAI File Transport
Input Argument Type Value Property name
FileName Literal C:\TEMP\TestVBCInit.xml
Output Argument Type Value Argument name
Output Argument
Step Type Method Business Service
Analyse Incoming Query XML Business Service Echo Workflow Utilities
Output Argument Type Value Property name
CheckPoint Expression InStr([&IncomingXML], "query-req")
Step Type Method Business Service
Is Query Request? Decision Point
Branch Condition Expression
Is Query Condition (CheckPoint Greater Than('0'))
Not Query Default
Step Type Method Business Service
Get Query XML Response Business Service Receive EAI File Transport
Input Argument Type Value Property name
FileName Literal C:\TEMP\TestVBCQuery.xml
Output Argument Type Value Argument name
Output Argument
TestVBCQuery.xml
Mr.
Sara
Chan
|
TestVBCInit.xml
• Using XML Gateway Business Service to serve the VBC
• Using Business Integration Manager (Server Request) as Transport Protocol
• Create your own workflow to deal with the logic
Architecture:
• VBC trigger XML Gateway: Init(), Query(), etc
XML Gateway generates xml files corresponding to the command. Eg. It generates xml file
Matching Init() command
• XML Gateway triggers Business Integration Manager to invoke SendReceive() method
• Business Integration Manager sends the xml files generated by XML Gateway to Workflow
• Workflow gets the xml file and passes it to external application like MQ Series, MSMQ, HTTP Web Application or processes it inside the Siebel
• Workflow gets the result xml file from external application or Siebel Application and passes it back to Business Integration Manager (BIM)
• BIM receives the result xml file and passes back to XML Gateway to populate the VBC
Points of configuration:
• Create a BC of Class CSSBCVExtern
• Configure the above BC with following user properties
Service Name: XML Gateway
Service Parameters: Transport=EAI Business Integration Manager (Server
Request);ProcessName=
• Create a process property as type of binary/string. Set the default to
• Create a process property as type of binary and named
• Analyse the xml file generated by XML Gateway to determine what action to be taken. (Query, Insert…)
• Use XSLT to transform the result xml file to the format XML Gateway needs to populate the VBC
Sample Workflow Design
Workflow Process Properties
Step Type Method Business Service
SaveIncomingXML Business Service Send EAI File Transport
Input Argument Type Value Property name
FileName Literal C:\XMLGateway.txt
AppendToFile Literal True
Step Type Method Business Service
Analyse Incoming XML Business Service Echo Workflow Utilities
Output Argument Type Value Property name
CheckPoint Expression InStr([&IncomingXML],"fields-req")
Step Type Method Business Service
Is Init Request? Decision Point
Branch Condition Expression
Is Init Condition (CheckPoint Greater Than('0'))
Not Init Default
Step Type Method Business Service
Get Init XML Response Business Service Receive EAI File Transport
Input Argument Type Value Property name
FileName Literal C:\TEMP\TestVBCInit.xml
Output Argument Type Value Argument name
Step Type Method Business Service
Analyse Incoming Query XML Business Service Echo Workflow Utilities
Output Argument Type Value Property name
CheckPoint Expression InStr([&IncomingXML], "query-req")
Step Type Method Business Service
Is Query Request? Decision Point
Branch Condition Expression
Is Query Condition (CheckPoint Greater Than('0'))
Not Query Default
Step Type Method Business Service
Get Query XML Response Business Service Receive EAI File Transport
Input Argument Type Value Property name
FileName Literal C:\TEMP\TestVBCQuery.xml
Output Argument Type Value Argument name
TestVBCQuery.xml
TestVBCInit.xml
No comments:
Post a Comment