Managing Deployment Parameters In Bpel Process Manger-tushar
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Managing Deployment Parameters In Bpel Process Manger-tushar as PDF for free.
More details
- Words: 1,329
- Pages: 15
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Managing Deployment Parameters in BPEL Process Manager While migrating from one environment to another various parameters changes in any application. Any BPEL Process should also be treated as application in this regard. So how to tackle this challenge. In BPEL Process Manager 10.1.3.4 concept of Deployment Plan is introduced which essentially define a XML file (DeploymentPlan file) which can be named as per the convenience. So, how to generate DeploymentPlan file! Step 1: Developer X creates a process BPEL Process named ReadFromAndWriteToFile and deploys it to development server. This in turn creates bpel_ ReadFromAndWriteToFile _vYYYY_MM_DD__XXXX.jar in \Foo\output folder of the workspace. File bpel_ ReadFromAndWriteToFile _vYYYY_MM_DD__XXXX.jar in \Foo\output folder of the workspace also get created if developer executes Make command.
Step 2: Now go to build.xml file in Resource folder & open it. In this file add following lines Just before end of project tag (). Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
(Please ignore TusharPlanForDevelopers.xml next to build.xml)
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
These commands do following tasks: Element
Description
generateplan
This option creates a deployment plan file for editing that includes all partner links, configuration properties, and WSDL imports in the BPEL process. The planfile attribute indicates the name to use for the deployment plan file. You can create a plan from either of two sources. o bpel.xml deployment descriptor file Specify a value with the descfile attribute. For example, descfile="${process.dir}/bpel/bpel.xml". This source is for developers who want to generate a plan without compiling the project. After development is complete, you copy the deployment plan file to the build folder and create the JAR file. o BPEL suitcase JAR file Specify a value with the suitecase attribute. For example, suitecase="${process.dir}/output/bpel_ ReadFromAndWriteToFile _vYYYY_MM_DD__XXXX.jar ".
This source is for administrators who do not want to review code. Instead, you take the JAR file, generate a deployment plan file, attach the file to the JAR file, and deploy it. Note: The content of the deployment plan is the same with either source. attachplan
This option packages a deployment plan file with the suitcase JAR file. The deployment plan file is automatically renamed to bpeldeployplan.xml in the suitcase JAR file. If this file already exists in the suitcase JAR file, it is overwritten with the new plan.
validatePlan
This option validates the deployment plan and identifies all search and replacement changes to be made on the server side during BPEL process deployment. Use this option for debugging only. The reportfile attribute indicates the file name in which the results of this test are written. For example, reportfile="${process.dir}/output/debug.txt"
extractplan
This option extracts the existing deployment plan packaged with the suitcase JAR file for editing. If no plan file exists, this is the same as creating a new file with generateplan.
Step 3: Provide values appropriate to your environment (the values provided above for target name, planfile, descfile, reportfile, and suitecase are only examples). Save the changes. Step 4: Right-click build.xml and select Run Ant
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Step 5: Move deploy (Default) from the Selected Targets section to the Available Targets section and move the target name you entered in Step 2 (for this exercise generateplan1) from the Available Targets section to the Selected Targets section. Click OK.
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
This operation can also be performed with the following ant syntax from the folder in which build.xml is located: command prompt> ant generateplan1
where generateplan1 is the value defined for the target name. This runs generateplan1 and creates a single deployment plan file in which you can modify parameters. This file is created by default in the JDeveloper_Home\JDev\bin directory, unless you explicitly specified a path with the planfile property, such as c:\temp\ AribaPlanForDevelopers.xml
Step 6: Copy AribaPlanForDevelopers.xml from JDeveloper_Home\JDev\bin to \ReadFromAndWriteToFile (same directory as of build.xml). Now refresh JDeveloper. AribaPlanForDevelopers.xml will be visible next to build.xml under Resources.
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Step 7: Now open TusharPlanForDevelopers.xml in editor
Change and replace the content of file as needed. Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com To have a generic Deployment Plan file, comment the contents of TusharPlanForDevelopers.xml and copy following contents into it.
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Step 8: Make the appropriate changes in modified TusharPlanForDevelopers.xml. Right-click on the build.xml file and select Run Ant. Move attachplan from the Selected Targets section to the Available Targets section. Move all other to Available Targets. Click OK.
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
This operation can also be performed with the following ant syntax from the folder in which build.xml is located: command prompt> ant attachplan
This packages the new deployment plan file with the BPEL suitcase JAR file. The file is renamed to bpeldeployplan.xml. The suitcase JAR file is created in the output directory of the BPEL process. Note: The attachplan command does not replace the old bpel.xml, WSDL, and XSD files with files containing the new values. Replacement occurs only when the BPEL process is deployed in Step 10. Step 9: Right-click on the build.xml file and select Run Ant. Move validateplan from the Selected Targets section to the Available Targets section. Move all other to Available Targets. Click OK.
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
This operation can also be performed with the following ant syntax from the folder in which build.xml is located: command prompt> ant validateplan
The Log window in JDeveloper shows if validation succeeded and depicts all search and replacement commands to perform during BPEL process deployment. This information is also written to the file specified with the reportfile attribute in the build.xml file in Step 2 (debug.txt). Review this information to ensure that every thing is correct. Step 10: Right-click on the build.xml file and select Run Ant. Move deploy (Default) from the Selected Targets section to the Available Targets section. Click OK. The files in the BPEL suitcase JAR file are replaced with files that include the URLs and properties appropriate to the next environment. Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com Note: 1. In addition to specifying these commands separately, you can also move attachplan, validateplan, and deploy (Default) to the Available Targets section together and click OK. This runs all three commands as a batch process. 2. Also manage Connection details for various environments while executing this command.
The Process: ReadFromAndWriteToFileïƒ
ReadFromAndWriteT oFile.zip
The same process will be followed in case of generateplan2 (for administrators) -------------------End----------------
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Managing Deployment Parameters in BPEL Process Manager While migrating from one environment to another various parameters changes in any application. Any BPEL Process should also be treated as application in this regard. So how to tackle this challenge. In BPEL Process Manager 10.1.3.4 concept of Deployment Plan is introduced which essentially define a XML file (DeploymentPlan file) which can be named as per the convenience. So, how to generate DeploymentPlan file! Step 1: Developer X creates a process BPEL Process named ReadFromAndWriteToFile and deploys it to development server. This in turn creates bpel_ ReadFromAndWriteToFile _vYYYY_MM_DD__XXXX.jar in \Foo\output folder of the workspace. File bpel_ ReadFromAndWriteToFile _vYYYY_MM_DD__XXXX.jar in \Foo\output folder of the workspace also get created if developer executes Make command.
Step 2: Now go to build.xml file in Resource folder & open it. In this file add following lines Just before end of project tag (). Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
(Please ignore TusharPlanForDevelopers.xml next to build.xml)
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
These commands do following tasks: Element
Description
generateplan
This option creates a deployment plan file for editing that includes all partner links, configuration properties, and WSDL imports in the BPEL process. The planfile attribute indicates the name to use for the deployment plan file. You can create a plan from either of two sources. o bpel.xml deployment descriptor file Specify a value with the descfile attribute. For example, descfile="${process.dir}/bpel/bpel.xml". This source is for developers who want to generate a plan without compiling the project. After development is complete, you copy the deployment plan file to the build folder and create the JAR file. o BPEL suitcase JAR file Specify a value with the suitecase attribute. For example, suitecase="${process.dir}/output/bpel_ ReadFromAndWriteToFile _vYYYY_MM_DD__XXXX.jar ".
This source is for administrators who do not want to review code. Instead, you take the JAR file, generate a deployment plan file, attach the file to the JAR file, and deploy it. Note: The content of the deployment plan is the same with either source. attachplan
This option packages a deployment plan file with the suitcase JAR file. The deployment plan file is automatically renamed to bpeldeployplan.xml in the suitcase JAR file. If this file already exists in the suitcase JAR file, it is overwritten with the new plan.
validatePlan
This option validates the deployment plan and identifies all search and replacement changes to be made on the server side during BPEL process deployment. Use this option for debugging only. The reportfile attribute indicates the file name in which the results of this test are written. For example, reportfile="${process.dir}/output/debug.txt"
extractplan
This option extracts the existing deployment plan packaged with the suitcase JAR file for editing. If no plan file exists, this is the same as creating a new file with generateplan.
Step 3: Provide values appropriate to your environment (the values provided above for target name, planfile, descfile, reportfile, and suitecase are only examples). Save the changes. Step 4: Right-click build.xml and select Run Ant
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Step 5: Move deploy (Default) from the Selected Targets section to the Available Targets section and move the target name you entered in Step 2 (for this exercise generateplan1) from the Available Targets section to the Selected Targets section. Click OK.
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
This operation can also be performed with the following ant syntax from the folder in which build.xml is located: command prompt> ant generateplan1
where generateplan1 is the value defined for the target name. This runs generateplan1 and creates a single deployment plan file in which you can modify parameters. This file is created by default in the JDeveloper_Home\JDev\bin directory, unless you explicitly specified a path with the planfile property, such as c:\temp\ AribaPlanForDevelopers.xml
Step 6: Copy AribaPlanForDevelopers.xml from JDeveloper_Home\JDev\bin to \ReadFromAndWriteToFile (same directory as of build.xml). Now refresh JDeveloper. AribaPlanForDevelopers.xml will be visible next to build.xml under Resources.
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Step 7: Now open TusharPlanForDevelopers.xml in editor
Change and replace the content of file as needed. Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com To have a generic Deployment Plan file, comment the contents of TusharPlanForDevelopers.xml and copy following contents into it.
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Step 8: Make the appropriate changes in modified TusharPlanForDevelopers.xml. Right-click on the build.xml file and select Run Ant. Move attachplan from the Selected Targets section to the Available Targets section. Move all other to Available Targets. Click OK.
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
This operation can also be performed with the following ant syntax from the folder in which build.xml is located: command prompt> ant attachplan
This packages the new deployment plan file with the BPEL suitcase JAR file. The file is renamed to bpeldeployplan.xml. The suitcase JAR file is created in the output directory of the BPEL process. Note: The attachplan command does not replace the old bpel.xml, WSDL, and XSD files with files containing the new values. Replacement occurs only when the BPEL process is deployed in Step 10. Step 9: Right-click on the build.xml file and select Run Ant. Move validateplan from the Selected Targets section to the Available Targets section. Move all other to Available Targets. Click OK.
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
This operation can also be performed with the following ant syntax from the folder in which build.xml is located: command prompt> ant validateplan
The Log window in JDeveloper shows if validation succeeded and depicts all search and replacement commands to perform during BPEL process deployment. This information is also written to the file specified with the reportfile attribute in the build.xml file in Step 2 (debug.txt). Review this information to ensure that every thing is correct. Step 10: Right-click on the build.xml file and select Run Ant. Move deploy (Default) from the Selected Targets section to the Available Targets section. Click OK. The files in the BPEL suitcase JAR file are replaced with files that include the URLs and properties appropriate to the next environment. Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com Note: 1. In addition to specifying these commands separately, you can also move attachplan, validateplan, and deploy (Default) to the Available Targets section together and click OK. This runs all three commands as a batch process. 2. Also manage Connection details for various environments while executing this command.
The Process: ReadFromAndWriteToFileïƒ
ReadFromAndWriteT oFile.zip
The same process will be followed in case of generateplan2 (for administrators) -------------------End----------------
Tushar Jain Managing Deployment Parameters in BPEL Process Manager [email protected] http://oracle-fusion-middlware.blogspot.com
Related Documents
Managing Deployment Parameters In Bpel Process Manger-tushar
December 2019 10
Business Process Using Bpel
June 2020 26
Managing In
October 2019 28
Parameters
July 2020 17
Parameters
November 2019 32
Deployment
November 2019 89More Documents from ""
Oracle Bpel Process Manger Performance Tuning-2
November 2019 42
