[riftsaw-commits] riftsaw SVN: r608 - in trunk: samples/esb/webservice_esb_bpel and 1 other directories.

Author: jeff.yuchang Date: 2010-03-30 00:47:17 -0400 (Tue, 30 Mar 2010) New Revision: 608 Modified: trunk/docs/docbook/gettingstartedguide/src/main/module/installation.xml trunk/samples/esb/webservice_esb_bpel/readme.txt trunk/samples/quickstart/loan_approval/readme.txt Log: * update the readme file and add upgrade ws stack in the installation. Modified: trunk/docs/docbook/gettingstartedguide/src/main/module/installation.xml =================================================================== --- trunk/docs/docbook/gettingstartedguide/src/main/module/installation.xml 2010-03-29 02:33:47 UTC (rev 607) +++ trunk/docs/docbook/gettingstartedguide/src/main/module/installation.xml 2010-03-30 04:47:17 UTC (rev 608) @@ -21,7 +21,7 @@ <section> <title>Prerequisites</title> <orderedlist> - <listitem>JBossAS (version 5.1.0.GA or higher) <strong>jdk6</strong> version, available from <ulink url="http://www.jboss.org/jbossas">http://www.jboss.org/jbos... + <listitem>JBossAS (version 5.1.0.GA or higher) <strong>jdk6</strong> version, available from <ulink url="http://www.jboss.org/jbossas">http://www.jboss.org/jbos...;, please upgrade the web service stack into 3.2.2.GA version, detail please refer to the following 'Upgrade web service for JBoss AS' section.</listitem> <listitem>JBossESB (version 4.7.GA or higher), should download the <emphasis role="bold">jbossesb-4.7.GA.zip</emphasis>, available from <ulink url="http://www.jboss.org/jbossesb">http://www.jboss.org/jbo...;. This is only required to run the ESB/BPEL example.</listitem> <listitem>RiftSaw (version 2.0 or higher), available from <ulink url="http://www.jboss.org/riftsaw">http://www.jboss.org/rift... Modified: trunk/samples/esb/webservice_esb_bpel/readme.txt =================================================================== --- trunk/samples/esb/webservice_esb_bpel/readme.txt 2010-03-29 02:33:47 UTC (rev 607) +++ trunk/samples/esb/webservice_esb_bpel/readme.txt 2010-03-30 04:47:17 UTC (rev 608) @@ -1,55 +1,53 @@ -Overview: -========= - This Quickstart demonsrates how the BPEL Engine can be used to - orchestrate business process flow through JBoss ESB. - - It also demonstrates a number of other features of the ESB: - 1. Exposing a Webservice interface for a Service that doesn't have a - Webservice interface (using the SOAPProcessor action). In this example, - the Service being exposed is a legacy EJB based Order Management Service. - 2. How to use a jaxb-intros.xml config to "Introduce" JAXB Annotations on a - Java interface/typeset that isn't annotated for use with JAXB and how to - add this config on a JBossWS Webservice endpoint deployment. - 3. Easily transforming a CSV based notification message into a Java object - that's then used to populate a SOAP request. See next. - 3. Making an invocation on an external Webserivce from within an Action - Processing Pipeline using the SOAPCleint action. - - See docs folder. - -Running this quickstart: -======================== - Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts - and a more detailed descripton of the different ways to run the quickstarts. - - NOTE: This Quickstart DOES NOT run Standalone, or on the ESB Server. It only runs on the - JBoss Application Server. - - - 1. Ensure that the value of the 'directory' attribute on the - 'notificationChannel' (jboss-esb.xml) matches the value of the - 'order.approval.drop.location' property in +Overview: +========= + This Quickstart demonsrates how the BPEL Engine can be used to + orchestrate business process flow through JBoss ESB. + + It also demonstrates a number of other features of the ESB: + 1. Exposing a Webservice interface for a Service that doesn't have a + Webservice interface (using the SOAPProcessor action). In this example, + the Service being exposed is a legacy EJB based Order Management Service. + 2. How to use a jaxb-intros.xml config to "Introduce" JAXB Annotations on a + Java interface/typeset that isn't annotated for use with JAXB and how to + add this config on a JBossWS Webservice endpoint deployment. + 3. Easily transforming a CSV based notification message into a Java object + that's then used to populate a SOAP request. See next. + 3. Making an invocation on an external Webserivce from within an Action + Processing Pipeline using the SOAPCleint action. + + See docs folder. + +Running this quickstart: +======================== + Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts + and a more detailed descripton of the different ways to run the quickstarts. + + NOTE: This Quickstart DOES NOT run Standalone, or on the ESB Server. It only runs on the + JBoss Application Server. + 1. Ensure that the value of the 'directory' attribute on the + 'notificationChannel' (jboss-esb.xml) matches the value of the + 'order.approval.drop.location' property in 'webservice_esb_bpel/services/order-manager/order-manager.properties', - and that the directory exists. - 2. Restart your JBoss Application Server. - 3. Goto the BPEL Console (http://localhost:8080/bpel-console) and confirm - it displays. - -To Run: -======= - 1. In a command terminal window in this folder, type 'ant deploy'. - 2. Goto 'Processes' on the BPEL Console - (http://localhost:8080/bpel-console) and confirm that the 'Customer' and - 'OrderProcess' BPEL processes are deployed. - 3. Start your favorite SOAP client (e.g. SOAPUI) and load the - 'Retailer' WSDL located in the sample's 'bpel/wsdl' folder. - 4. Load the SOAP client (RetailerBinding/SubmitOrder) with the sample order in - 'bpel/sampleData/customerOrder.xml'. - 5. Submit the new order using the SOAP UI client. - 6. View the state of the new process in 'Instances' on the BPEL - Console. Will appear as 'ACTIVE'. This is because the process is waiting on an - acknowledgement/notification from the OrderManager service. - 9. Goto http://localhost:8080/order-manager/ - From here, you can approve the order. - 10. When finished, undeploy the application by typing 'ant undeploy'. - + and that the directory exists. + 2. Restart your JBoss Application Server. + 3. Goto the BPEL Console (http://localhost:8080/bpel-console) and confirm + it displays. + +To Run: +======= + 1. In a command terminal window in this folder, type 'ant deploy'. + 2. Goto 'Processes' on the BPEL Console + (http://localhost:8080/bpel-console) and confirm that the 'Customer' and + 'OrderProcess' BPEL processes are deployed. + 3. Start your favorite SOAP client (e.g. SOAPUI) and load the + 'Retailer' WSDL located in the sample's 'bpel/wsdl' folder. + 4. Load the SOAP client (RetailerBinding/SubmitOrder) with the sample order in + 'bpel/sampleData/customerOrder.xml'. + 5. Submit the new order using the SOAP UI client. + 6. View the state of the new process in 'Instances' on the BPEL + Console. Will appear as 'RUNNING'. This is because the process is waiting on an + acknowledgement/notification from the OrderManager service. + 9. Goto http://localhost:8080/order-manager/ + From here, you can approve the order. + 10. When finished, undeploy the application by typing 'ant undeploy'. + Modified: trunk/samples/quickstart/loan_approval/readme.txt =================================================================== --- trunk/samples/quickstart/loan_approval/readme.txt 2010-03-29 02:33:47 UTC (rev 607) +++ trunk/samples/quickstart/loan_approval/readme.txt 2010-03-30 04:47:17 UTC (rev 608) @@ -1,46 +1,46 @@ -Quickstart Examples - Loan Approval -=================================== - -This is a loan approval example that uses the amount field inside the -loan request to determine which action should be performed. - -If the loan amount is less than 10000, then it will invoke the loan -assessor to determine the risk. If the risk is low, then it will approve -the loan. If the risk is not low, then it will invoke the loan -approver service. In the current implementation, all amounts less than -10000 are considered low risk. - -If the loan amount is greater or equal to 10000, then it will invoke +Quickstart Examples - Loan Approval +=================================== + +This is a loan approval example that uses the amount field inside the +loan request to determine which action should be performed. + +If the loan amount is less than 10000, then it will invoke the loan +assessor to determine the risk. If the risk is low, then it will approve +the loan. If the risk is not low, then it will invoke the loan +approver service. In the current implementation, all amounts less than +10000 are considered low risk. + +If the loan amount is greater or equal to 10000, then it will invoke the loan approver service. If the amount is greater than 20000, then the -approver will return a fault, indicating that the amount is too much. - -To deploy the example, open a command line window in the example's folder, -and simply type 'ant deploy'. To undeploy, use the command 'ant undeploy'. - -To test the example, for example using the SOAPUI client, example messages -can be found in the messages sub-folder, with the relevant WSDL (loanServicePT.wsdl) being -located in the bpel sub-folder. - -Alternatively, use the 'ant sendloanreq1' command (from a command line window) -to send an example loan request message with amount less than 10000 -directly to the deployed process. Or use the command 'ant sendloanreq2' to +approver will return a fault, indicating that the amount is too much. + +To deploy the example, open a command line window in the example's folder, +and simply type 'ant deploy'. To undeploy, use the command 'ant undeploy'. + +To test the example, for example using the SOAPUI client, example messages +can be found in the messages sub-folder, with the relevant WSDL (loanServicePT.wsdl) being +located in the bpel sub-folder. + +Alternatively, use the 'ant sendloanreq1' command (from a command line window) +to send an example loan request message with amount less than 10000 +directly to the deployed process. Or use the command 'ant sendloanreq2' to send a loan request with amount greater or equal to 10000. Or use command 'ant sendloanreq3' to send an amount greater than 20000, which will result in a fault from the approver service. To generate a fault from the BPEL process directly, use 'ant sendloanreq4', to send a request with an amount -of zero. - -NOTE: The "ant deploy" command will by default deploy version 1 of the -example to the server. If you wish to change the example, and redeploy, -then you will need to update the version number in the build.xml, or -override the version property, e.g. "ant -Dversion=2 deploy" (and similarly -when undeploying "ant -Dversion=2 undeploy"). - -Feel free to change the logic in the JAX-WS implemented services and re-deploy -the example to see the effects. - -Some handy URLs: -http://localhost:8080/bpel-console is the BPEL console -http://localhost:8080/Quickstart_bpel_loan_approvalWS?wsdl is the URL to the BPEL process' WSDL -http://localhost:8080/Quickstart_bpel_loan_approval/LoanApproval?wsdl is the URL to the Loan Approval service -http://localhost:8080/Quickstart_bpel_loan_approval/RiskAssessment?wsdl is the URL to the Risk Assessment service +of zero. + +NOTE: The "ant deploy" command will by default deploy version 1 of the +example to the server. If you wish to change the example, and redeploy, +then you will need to update the version number in the build.xml, or +override the version property, e.g. "ant -Dversion=2 deploy" (and similarly +when undeploying "ant -Dversion=2 undeploy"). + +Feel free to change the logic in the JAX-WS implemented services and re-deploy +the example to see the effects. + +Some handy URLs: +http://localhost:8080/bpel-console is the BPEL console +http://localhost:8080/Quickstart_bpel_loan_approvalWS?wsdl is the URL to the BPEL process' WSDL +http://localhost:8080/Quickstart_bpel_loan_approval/LoanApproval?wsdl is the URL to the Loan Approval service +http://localhost:8080/Quickstart_bpel_loan_approval/RiskAssessment?wsdl is the URL to the Risk Assessment service