bpel engine source code
|
View:
New views
16 Messages
—
Rating Filter:
Alert me
|
 |
bpel engine source code
by rconfalonieri
::
Rate this Message:
|
||||
|
|
Re: bpel engine source code
by Philip Varghese-2
::
Rate this Message:
|
||||
|
|
Re: bpel engine source code
by Kiran Bhumana-2
::
Rate this Message:
|
||||
|
|
Re: bpel engine source code
by rconfalonieri
::
Rate this Message:
Hi Kiran,
thanks for replying. I am not too sure to have understood what you mean by changing the code dynamically, however my idea would be to add some APIs to add functionality, and further on, I might need to change the core engine itself. It may be (I do not really now right now exactly, as I am still in a design phase) that I'll have to modify the engine to let it communicate to other components we'll have in the system. Basically what we have, is an agent shell for supporting contract management and execution, and the execution is delegated to a component that is called workflow manager, which basically "wraps" the bpel engine. (all this work is carried on in the context of an european project IST-CONTRACT, I am putting the link just if you are curious to have a look at it  www.ist-contract.org and http://sourceforge.net/projects/ist-contract/).
thanks and all the best, roberto |
||||
|
|
Re: bpel engine source code
by Gopalan Suresh Raj
::
Rate this Message:
Some parts of this message have been removed.
Learn more about Nabble's security policy.
You would not need to invoke ant scripts from your java code to deploy your service assembly. Please find a simple Java program that exercises the Common Management and Monitoring API to deploy, start, stop, shutdown and undeploy a Service Assembly. To execute attached program, you will need to include <GF_INSTALL_ROOT>/jbi/lib/jbi-admin-common.jar See if this suffices to satisfy your requirement. Cheers Gopalan. rconfalonieri wrote: Hi Kiran, thanks for replying. I am not too sure to have understood what you mean by changing the code dynamically, however my idea would be to add some APIs to add functionality, and further on, I might need to change the core engine itself. It may be (I do not really now right now exactly, as I am still in a design phase) that I'll have to modify the engine to let it communicate to other components we'll have in the system. Basically what we have, is an agent shell for supporting contract management and execution, and the execution is delegated to a component that is called workflow manager, which basically "wraps" the bpel engine. (all this work is carried on in the context of an european project IST-CONTRACT, I am putting the link just if you are curious to have a look at it ;-) www.ist-contract.org and http://sourceforge.net/projects/ist-contract/). thanks and all the best, roberto Kiran Bhumana-2 wrote: --
package test; import com.sun.esb.management.api.deployment.DeploymentService; import com.sun.esb.management.api.runtime.RuntimeManagementService; import com.sun.esb.management.client.ManagementClient; import com.sun.esb.management.client.ManagementClientFactory; import com.sun.esb.management.common.ManagementRemoteException; /** * @author graj */ public class TestDeployment { /** * @param args */ public static void main(String[] args) { String applicationArchive = "C:/test/NetBeansProjects/SynchronousSample/SynchronousSampleApplication/dist/SynchronousSampleApplication.zip"; String host = "licalhost", userName = "admin", password = "adminadmin"; int port = 8686; // default RMI Port String targetName = "server"; String serviceAssemblyName = ""; try { // Get a client connection ManagementClient client = ManagementClientFactory.getInstance(host, port, userName, password); // Get the Deployment Service DeploymentService deploymentService = client.getDeploymentService(); // Deploy the Application serviceAssemblyName = deploymentService.deployServiceAssembly(applicationArchive, targetName); // Get the Runtime Management Service RuntimeManagementService lifecycleService = client.getRuntimeManagementService(); // Start the application serviceAssemblyName = lifecycleService.startServiceAssembly(serviceAssemblyName, targetName); // Stop the application serviceAssemblyName = lifecycleService.stopServiceAssembly(serviceAssemblyName, targetName); // shutdown the application serviceAssemblyName = lifecycleService.shutdownServiceAssembly(serviceAssemblyName, targetName); // undeploy the application serviceAssemblyName = deploymentService.undeployServiceAssembly(serviceAssemblyName, targetName); } catch (ManagementRemoteException e) { e.printStackTrace(); } } } --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
||||
|
|
Re: bpel engine source code
by Gabriel Badescu
::
Rate this Message:
|
||||
|
|
Re: bpel engine source code
by rconfalonieri
::
Rate this Message:
|
||||
|
|
Re: bpel engine source code
by rconfalonieri
::
Rate this Message:
Hi Gopalan,
thanks for replying. Yes, definetely I can use them to deploy the SA. However, before I have BPELs templates (which are associated to a contract), which I need to fill with custom information at runtime (such as IP addresses and Ports), and first compile them to generate the required service assemblies. FOr this reason, I was thinking to use the ant script, provided by netbeans, which I have modified a bit to let them be independent from netbeans. Actually I have done somth that is not very smart, i.e. I have run into the scripts to see the library needed, and copied the library to a /lib folder to be provided with all the system deplyment package we'll provide. Do you maybe know, or may point me a smarter approach? 
thanks and all the best, roberto |
||||
|
|
Re: bpel engine source code
by Gopalan Suresh Raj
::
Rate this Message:
Some parts of this message have been removed.
Learn more about Nabble's security policy.
I'm glad you found the code sample useful. Now to solve your other problem, instead of having to hard-code your connectivity information into each service unit and recompiling, have you looked at using the Application Configurations and Application Variables features (and Application Environment Verification) available in Open ESB? You might find these useful. Please peruse: http://wiki.open-esb.java.net/Wiki.jsp?page=ApplicationConfiguration http://wiki.open-esb.java.net/Wiki.jsp?page=HTTPBCEnhancedEnvironmentVariables http://wiki.open-esb.java.net/Wiki.jsp?page=SierraUpdateAppVerifier Cheers Gopalan. rconfalonieri wrote: Hi Gopalan, thanks for replying. Yes, definetely I can use them to deploy the SA. However, before I have BPELs templates (which are associated to a contract), which I need to fill with custom information at runtime (such as IP addresses and Ports), and first compile them to generate the required service assemblies. FOr this reason, I was thinking to use the ant script, provided by netbeans, which I have modified a bit to let them be independent from netbeans. Actually I have done somth that is not very smart, i.e. I have run into the scripts to see the library needed, and copied the library to a /lib folder to be provided with all the system deplyment package we'll provide. Do you maybe know, or may point me a smarter approach? :-) thanks and all the best, roberto Gopalan Suresh Raj wrote:Hello Robnerto You would not need to invoke ant scripts from your java code to deploy your service assembly. Please find a simple Java program that exercises the Common Management and Monitoring API to deploy, start, stop, shutdown and undeploy a Service Assembly. To execute attached program, you will need to include <GF_INSTALL_ROOT>/jbi/lib/jbi-admin-common.jar See if this suffices to satisfy your requirement. Cheers Gopalan. rconfalonieri wrote: Hi Kiran, thanks for replying. I am not too sure to have understood what you mean by changing the code dynamically, however my idea would be to add some APIs to add functionality, and further on, I might need to change the core engine itself. It may be (I do not really now right now exactly, as I am still in a design phase) that I'll have to modify the engine to let it communicate to other components we'll have in the system. Basically what we have, is an agent shell for supporting contract management and execution, and the execution is delegated to a component that is called workflow manager, which basically "wraps" the bpel engine. (all this work is carried on in the context of an european project IST-CONTRACT, I am putting the link just if you are curious to have a look at it ;-) www.ist-contract.org and http://sourceforge.net/projects/ist-contract/ ). thanks and all the best, roberto Kiran Bhumana-2 wrote: What sort of modifications are you referring to? Do you want to change the engine code dynamically through management APIs or do you want to change the engine code and install it again? Kiran B. rconfalonieri wrote: Hi all, I may be interested to modify to bpel engine code to adapt it to do some extra stuff, which I'll need in a project I'm involved into. As an example, I would like to be able to deploy BPEL processes to the server straight from the java code of my system. As I saw, that management and monitoring APIs do not provide such functionality. Right now I'm simply calling the ant script deployment from a Java funcion, but I'd like to know if there is the possibility to have access straight to the BPEL engine code and modify it. thanks and all the best, roberto -- Kiran Bhumana Open ESB Community ( http://open-esb.org ) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... -- Implement SOA today. Visit The Open ESB Community (http://open-esb.org/) Visit Web Cornucopia (http://blogs.sun.com/gopalan/) ? Grab this Headline Animator package test; import com.sun.esb.management.api.deployment.DeploymentService; import com.sun.esb.management.api.runtime.RuntimeManagementService; import com.sun.esb.management.client.ManagementClient; import com.sun.esb.management.client.ManagementClientFactory; import com.sun.esb.management.common.ManagementRemoteException; /** * @author graj */ public class TestDeployment { /** * @param args */ public static void main(String[] args) { String applicationArchive = "C:/test/NetBeansProjects/SynchronousSample/SynchronousSampleApplication/dist/SynchronousSampleApplication.zip"; String host = "licalhost", userName = "admin", password = "adminadmin"; int port = 8686; // default RMI Port String targetName = "server"; String serviceAssemblyName = ""; try { // Get a client connection ManagementClient client = ManagementClientFactory.getInstance(host, port, userName, password); // Get the Deployment Service DeploymentService deploymentService = client.getDeploymentService(); // Deploy the Application serviceAssemblyName = deploymentService.deployServiceAssembly(applicationArchive, targetName); // Get the Runtime Management Service RuntimeManagementService lifecycleService = client.getRuntimeManagementService(); // Start the application serviceAssemblyName = lifecycleService.startServiceAssembly(serviceAssemblyName, targetName); // Stop the application serviceAssemblyName = lifecycleService.stopServiceAssembly(serviceAssemblyName, targetName); // shutdown the application serviceAssemblyName = lifecycleService.shutdownServiceAssembly(serviceAssemblyName, targetName); // undeploy the application serviceAssemblyName = deploymentService.undeployServiceAssembly(serviceAssemblyName, targetName); } catch (ManagementRemoteException e) { e.printStackTrace(); } } } --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... --
|
||||
|
|
Re: bpel engine source code
by rconfalonieri
::
Rate this Message:
|
||||
|
|
Re: bpel engine source code
by sherry_weng
::
Rate this Message:
|
