Simplified
Workshop Series
Design
Time Governance
in
Fuse Service Works
Welcome
to the Simplified demo series. I refer to this as a workshop in a
box, meaning everything is included to get you started such as the
source, instructions, videos, presentations, etc. This demo will walk
you through a quick demo of Design Time Governance in Fuse Service
Works. It is split into 3 main sections. First is the quick demo
which walks you through the quick steps to run a quick, easy demo
(The What). The second section gives an overview of the technology
and how the demo was created (The Why and How). The third section
gives you additional collateral. So let’s get started and as they
say so easy a non techie can do it...
Section
1 : Run a quick demo
NOTE:
Screen shots and more step by step for creating/running the demo from
scratch are in section 2.
Step
1: Clone the repository from
https://github.com/kpeeples/simplified-dtgov.git
Step 2:
Download Fuse Service Works from
http://www.jboss.org/products/fsw.html
Step 3:
Place the software in the distros folder
Step 4:
Modify the support/InstallationScript.xml file to contain the full
path to the installed/fsw directory. Make sure to leave the
installed/fsw directory. The script performs the automated install of
Fuse Service Works. You will notice in the installation script the
components that are being installed. NOTE: This is installing the Switchyard, DTGov, S-RAMP and RTGov
components which wouldn’t be the recommended setup as Design Time
would be a separate server from the Switchyard/Run Time Server.
<installpath>/home/kpeeples/demos/fsw-simple-demo/installed/fsw</installpath>
Step 5:
Modify the post-run.sh file to have the appropriate directory of the
fsw-simple-demo for the link for the production server. This allows
for the demo to be installed on the server after moving to the prod
task in the DTGov workflow.
ln
-sv /tmp/prod/jbossas7/standalone/deployments
/home/kpeeples/demos/fsw-simple-demo/installed/fsw/jboss-eap-6.1/standalone/deployments
Step 6:
Run the install-run.sh script to install FSW and start the server
Step 7:
Open another terminal and run the post-run.sh script. This may take a
little bit of time to compile and deploy the default DTGov workflow,
compile and deploy the switchyard demo to dtgov/s-ramp and create the
link for the production server. The build should be created
successfully.
Step 8:
The demo is now setup. First browse to http://localhost:8080/dtgov-ui
and sign on with fswAdmin and redhat1!
Step 9:
View Deployments. Click on deployments under deployment life cycle.
You should see the
switchyard-quickstart-demo-orders-1.1.1-p5-redhat-1.war
deployment.
Click on the deployment to see the deployment history, deployment
contents and browse in S-RAMP options.
Step 10:
Move the deployment through the workflow. Click on the DTGov
dashboard on the breadcrumbs. Click on task inbox. Select the second
TestDev and check the artifact which should be the switchyard war
deployment. The first is the source jar. Notice it indicates deployed
to target /tmp/dev. The dtgov properties file indicates the
deployment targets which default to the file copy. We setup a link in
tmp to the deployment folder for the server for testing so that once
the task hits prod then the war will be deployed to the server. Click
Claim, Start, Pass, Complete. Then click on Task inbox. You will now
see Test QA. Click on the task and follow the same process to move
the depoyment to stage. Do the same for the Test Stage task. Once in
Test Prod the war has been deployed to the server.
Step 11:
Test the Orders Demo once deployed to Production. Now that the
deployment is in Prod we can test the application. Browse to the
Order Service at http://localhost:8080/demo-orders/OrderService?wsdl.
Browse to the application screen
http://localhost:8080/switchyard-quickstart-demo-orders-1.1.1-p5-redhat-1/home.jsf
enter
PS-19838-XY for the order ID and BUTTER for the Item Id. Click Create
to have the order accepted.
This
is a quick demo of an artifact going through the DTGov workflow. More
detail of configuration and step by step are below.
Section
2 : Technology Overview and creating the demo step by step
Technology
Overview
Step by
Step
Section
3 : Additional Collateral and demo structure
The
root folder of the demo contains:
- install-run.sh to install and run FSW
- pre-run.sh to do any pre-installation setup or compiling
- post-run.sh to do any post-install setup or compiling
- README.MD to briefly descibe the demo
- readme.html to meet the objectives 1) quick and easy demo 2) step by step instructions with collateral
- reset.sh to reset the demo
The
collateral folder contains:
- Video for videos or link to video
- Presentation for presentations or link to presentation
- Blog for a blog document or link to blog
- Simulation for a simulation of the demo or link to simulation
The
distros folder contain the downloads for the demo
The
installed folder contains subfolders for the software to be installed
when the script is run
The
source folder contains any source projects to be compiled and
deployed
The
support folder contains any supporting files/directories
Closing
