Multi-Environment Deployment Test Case
As always, I've had a number of distractions but I am finally back and ready to continue my multi-environment test. I would like to configure an actual deployment so that my "Partner Links" point to the correct URL when they are deployed to my various environments.
I have two different BPEL Processes that I would like to use together.
- First I will take my "HelloWorld" process. This is a very simple, easy to work with program.
- I will then take a BPEL process called "GetProfile" and add it to my "HelloWorld" process. The "GetProfile" process is a simple flow that requires a profile name as an input and with the use of a database call it collects the value for the requested profile.
- So when I enter my input name for the "HelloWorld" process, I want to get the output greeting of "Hello Ben! You are logged into DEV" with DEV being the result from the "GetProfile" partner link call.
- When I deploy and run the process, I should get the correct profile value for the environment. Development -> DEV - System Test -> SYS - and Production -> PRD.
I will be able to tell right away if my partner link is still pointing at development or if the URL points to the new environment. In my next post I will post the steps involved in preparing this type of deployment and any challenges that I experienced.
No comments:
Post a Comment