Hide Forgot
Affects: Documentation (Ref Guide, User Guide, etc.) project_key: SOA Len, please undertake a QE review of the first build of the BPEL Console Guide: http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_SOA_Platform/5/html/JBoss_SOA_BPEL_Guide/index.html
Hi David a few notes to get thinks started 1.2.2. Logging in. True for riftsaw installation on pure JBoss AS. Not true for SOA-P though . default login:password is admin:admin which is defined in soa-user.properties, soa-roles.properties. Login policy is definied in login-config.xml and can be changed in deploy/bpel-console/gwt-console-server.war/WEB-INF/jboss-web.xml in the <security-domain/> element. 1.2.5. What about process archives which do not have a version definition? e.g. process archive name Quickstart_bpel_simple_invoke.jar. These are handeled as version 0. So Quickstart_bpel_simple_invoke-1.jar may be deployed as the next process version. 2.2. Example 2.1. Sample Configuration: IMHO this should include a sample build file from SOA-P not Riftsaw. 2.3. consider to include: BPEL processes can be tested directly using JBDS. No ANT scripts are necessary. right click the process WSDL -> Web Services -> Test with Web Service Explorer -> ... 6.2. Mentioning the farm directory is good but we don't want to make the impression that it's suited for enterprise use. The process archives should be copied separately to each server.
Parent: Added: SOA-3147
I have made most of these changes thanks, Marek. :-) The only thing I haven't altered is the sample build file - can an SME please provide a relevant SOA one? Cheers.
Could you please add to guide steps to configure riftsaw clustering? In default It's disabled and old steps are for deploy riftsaw with clustering. It would be nice to have some template files in docs/examples as jboss-beans.xml and riftsaw-cache-manager-jboss-beans.xml (these files are ready in qa/clusterinstall2/resources/riftsaw/META-INF where is 1 configurable part @database@ in jboss-beans.xml). Step 1 would be set @database@ in jboss-beans.xml example file to some of these mysql, postgre, db2, sqlserver, oracle or sybase Step 2 would be copy jboss-beans.xml to [server-config]/deploy/riftsaw.sar/META-INF/ Step 3 would be replace [server-config]/deploy/cluster/jboss-cache-manager.sar/META-INF/jboss-cache-manager-jboss-beans.xml with riftsaw-cache-manager-jboss-beans.xml
Hi David, can you have a look at the following please? 1.2 Quickstart Examples - Hello World - wrong path - should be SOA_ROOT/samples/quickstarts/bpel_hello_world - the user can send a message to the process as: ant runtest 1.3 ESB Examples. - wrong path - should be SOA_ROOT/samples/quickstarts/bpel_esb_helloworld 2.3 BPEL properties bpel.uddi.* property is located in the table header. I suppose this is a typo. 3.4 Changing End-Point Configuration Properties Everything in this section refering to Apache ODE should be removed since it's not configurable in Riftsaw. Riftsaw only supports process specific config. Also for completion the only property supported at this time is mex.timeout (as stated in the guide). 5.2 The note about the ClerkManager includes also Table 5.1. Is this a mistake or intention? 7.1 Installation Steps provided above by ibek should be in this section. Attempting to install another Riftsaw deployment can break the integration.
Comments added. Assigning back to David.
Changes made and document restaged.
Closing - QE doc reviews are complete.