ESB deployment/registration

Hi All,
We are trying to figure out the deployment/registration starteagy for ESB projects.As one can deploy BPEL using properties files for changing the runtime settings and use ant for command prompt deployment; as far as we can find ESB can only be registered from JDev.
Any pointers to best practice for ESB deployment and if it could be done that way we can deploy BPEL projects after substituing properties like server name etc.
Thanks
Message was edited by:
user591048

Sjoerd Michels made a nice post of how to build the whole soademo, included esb.
http://technology.amis.nl/blog/?p=1655
Dave Berry links to this post on the forum :
Dealing with changing service wsdl locations in the ESB
And the zipfile :
http://www.oracle.com/technology/products/integration/esb/files/esbdeploymentautomation.zip

Similar Messages

ESB Deployment Automation Fault

I'm using the ant ESB Deployment Automation tasks authored by Doug Gschwind and referenced in other threads. I get a build failed error when trying to extract an ESB deployment plan. The error states that the output file already exists but the directory where it resides cannot be written or the filename does not have a .xml extension.
My set up is:
D:\temp - contains ESBMetadataMigrationTaskdefs.xml, ESBMetadataMigration.jar, my ant project file and the output file (PMSProto1Plan.xml). Both the directory and file are not read only.
I had to install commons-httpclient and also JAXB (from Sun Java Web Services Developer Kit). I did note that I had to find jsr173_1.0_api.jar under my JDeveloper home. I used your sample exampleBuild.xml as the basis of my ant file.
My extract file looks like:
<?xml version="1.0" encoding="UTF-8"?>
<project name="ESBMetadataDeployment" default="usage" basedir=".">
<property name="esbProjectToDeploy" value="D:\Oracle\JDeveloper\jdev\mywork\CVSTest\LR\PMSProto1"/>
<property name="deploymentPlanFilename" value="${basedir}/PMSProto1Plan.xml/"/>
<import file="${basedir}/ESBMetadataMigrationTaskdefs.xml"/>
<target name="test.ExtractESBDeploymentPlan">
<extractESBDeploymentPlan sourceDir="${esbProjectToDeploy}" deploymentPlanFile="${deploymentPlanFilename}"/>
</target>
<target name="usage">
<exec executable="ant" dir="${basedir}" vmlauncher="false">
<arg value="-projecthelp"/>
</exec>
</target>
</project>
My ESBMetadataMigrationTaskdefs.xml looks like:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<project name="ESBMetadataMigrationTaskdefs">

<property name="commons.httpclient.home" value="C:/Program Files/ApacheGroup/commons-httpclient-3.0.1"/>
<property name="jaxb.v2.0.2.home" value="C:/Sun/jwsdp-2.0"/>
<property name="soa.suite.home" value="D:/product/10.1.3.1/OracleAS_2"/>
<property name="JDev.home" value="D:/oracle/JDeveloper"/>

<dirname property="imported.basedir" file="${ant.file.ESBMetadataMigrationTaskdefs}"/>
<taskdef resource="oracle/tip/esb/client/anttasks/antlib.xml">
<classpath>
<pathelement location="${imported.basedir}/ESBMetadataMigration.jar"/>
<pathelement location="${commons.httpclient.home}/commons-httpclient-3.0.1.jar"/>
<pathelement location="${soa.suite.home}/lib/xmlparserv2.jar"/>
<pathelement location="${soa.suite.home}/integration/esb/lib/commons-logging.jar"/>
<pathelement location="${soa.suite.home}/integration/esb/lib/commons-codec-1.3.jar"/>
<pathelement location="${soa.suite.home}/integration/esb/lib/oraesb.jar"/>
<pathelement location="${jaxb.v2.0.2.home}/jwsdp-shared/lib/activation.jar"/>
<pathelement location="${jaxb.v2.0.2.home}/jaxb/lib/jaxb-api.jar"/>
<pathelement location="${JDev.home}/integration/lib/jsr173_1.0_api.jar"/>
<pathelement location="${jaxb.v2.0.2.home}/jaxb/lib/jaxb-impl.jar"/>
</classpath>
</taskdef>
</project>
I'm using JDev 10.1.3.3.0.4157 and SOA Suite 10.1.3.3
Has anybody hit this issue before and hopefully a solution ? Thanks.

For what it is worth I can confirm that what user531376 describes is the correct answer to the problem. Add this line:
<delete file="${deploymentPlanFilename}" verbose="true"/>
to the ExtractESBDeploymentPlan target and you should be fine.
Maybe this blog post (shameless self-promotion) adds to your knowledge: http://technology.amis.nl/blog/?p=2371.
Happy building, Sjoerd

ESB Deployment without JDeveloper

Hi,
Can any one let me know how to deploy ESB Project (SOA Suite 10.1.3)
without using JDeveloper.
Essentially i am looking for 'ant' or 'obant' kind of utility for ESB deployment.
I have used obant for BPEL deployment but can't find anywhere how to use it for ESB deployment.
Regards
Vikas Sharma

ESB has an export/import facility. You can export from your dev environment, which will give you a zipfile.
This zip can be moved and imported into another ESB environment.
the export and import utilities are shipped with the ESB product.
Marc.

Regarding ESB Deployment without using JDeveloper

Hi,
I would like to deploy my ESB application without using JDeveloper. BPEL Designer automatically creating the build script to deploy the BPEL application. Is there any ant script available to deploy the ESB application in to Oracle integration server.? Please let us know.
Regards
Niraimathi R

Niraimathi,
I had the same question - see Re: Registering ESB Services without JDeveloper
Dave Berry from Oracle kindly gave me a sneak preview of the jars and tags required in order to register ESB services from ANT.
I now have a continuous build environment (using Cruise Control), linked into Subversion which deploys all my BPEL Processes and registers my ESB services.
I believe that the JARs and instructions on how to register ESB services using ANT will be available on OTN soon.
Kind Regards,
Mark.

Failure upon calling web service on the ESB deployed from jDeveloper

Hello!
I've created a database adapter and a routing service that calls the database adapter. When registering the services on the ESB, I get error when I try to call it, as the Wsdl references a wsdl file on http://localhost:8888...... As I see it, it should refer to in on the same server as the esb (soa suite) runs? I think this might be a deployment issue in jDeveloper, maybe ant? Any clue on this?
brgds, Paul Jørstad

Thank you very much for you reply!
But I do not get any further.. In the ESB control, the Soap Endpoint URI still says:
SOAP Endpoint URI
http://localhost:8888/event/xal/rs_product_p_get_complete_bom_flat
And in my wsdl file:
<soap:address location="http://oslsoad1/event/xal/rs_product_p_get_complete_bom_flat"/>
I've tried to de-register, and register the service.

ESB deployment structure

Hi,
While registering the esb in the integration server its getting deployed in the following format
ApplicationName_ProjectName
is there any way to make it as
ApplicationName/ProjectName (i.e project name should be the sub folder of the application folder)
your quick response is appreciated.
Regards,
Kishore.

Hi Abhi,
We need to deploy all the common artifacts(all the schemas used by the proiject ) into one ESB kind of project.In the remaining schemas we need to import the deployed schemas.
In this case for example we have the application CommonArtifacts in that we have project Schemas in which we will have all the schemas
CommonArtifacts/Schemas/schema1.xsd
CommonArtifacts/Schemas/schema2.xsd
CommonArtifacts/Schemas/schema3.xsd
CommonArtifacts/Schemas/schema4.xsd .... like this..
in the importing if we write like
<xsd:import schemaLocation="../../CommonArtifacts/Schemas/schema1.xsd"
namespace="http://www.orst.com/schema1"/>
the schema in which we are importing this will not get resolved because of the deployment folder structure
Do you understand the scenario ?
Regards,
Kishore.

ESB deployment - jaxb exception

[extractESBDeploymentPlan] javax.xml.bind.JAXBException: Unable to locate jaxb.properties for package oracle.tip.esb.client.metadata.deploymentplan.model
[extractESBDeploymentPlan]      at javax.xml.bind.ContextFinder.searchcontextPath(ContextFinder.java:205)
[extractESBDeploymentPlan]      at javax.xml.bind.ContextFinder.find(ContextFinder.java:149)
[extractESBDeploymentPlan]      at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:281)
[extractESBDeploymentPlan]      at oracle.tip.esb.client.metadata.deploymentplan.utils.DeploymentPlanUtils.getJAXBContext(DeploymentPlanUtils.java:37)
[extractESBDeploymentPlan]      at oracle.tip.esb.client.metadata.deploymentplan.utils.DeploymentPlanUtils.getMarshaller(DeploymentPlanUtils.java:65)
[extractESBDeploymentPlan]      at oracle.tip.esb.client.anttasks.ExtractESBDeploymentPlanTask.saveDeploymentPlan(ExtractESBDeploymentPlanTask.java:506)
[extractESBDeploymentPlan]      at oracle.tip.esb.client.anttasks.ExtractESBDeploymentPlanTask.execute(ExtractESBDeploymentPlanTask.java:541)
[extractESBDeploymentPlan]      at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
[extractESBDeploymentPlan]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[extractESBDeploymentPlan]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[extractESBDeploymentPlan]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[extractESBDeploymentPlan]      at java.lang.reflect.Method.invoke(Method.java:585)
[extractESBDeploymentPlan]      at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
[extractESBDeploymentPlan]      at org.apache.tools.ant.Task.perform(Task.java:348)
[extractESBDeploymentPlan]      at org.apache.tools.ant.Target.execute(Target.java:357)
[extractESBDeploymentPlan]      at org.apache.tools.ant.Target.performTasks(Target.java:385)
[extractESBDeploymentPlan]      at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
[extractESBDeploymentPlan]      at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
[extractESBDeploymentPlan]      at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
[extractESBDeploymentPlan]      at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
[extractESBDeploymentPlan]      at oracle.jdevimpl.ant.runner.AntLauncher.launch(AntLauncher.java:321)
[extractESBDeploymentPlan]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[extractESBDeploymentPlan]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[extractESBDeploymentPlan]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[extractESBDeploymentPlan]      at java.lang.reflect.Method.invoke(Method.java:585)
[extractESBDeploymentPlan]      at oracle.jdevimpl.ant.runner.InProcessAntStarter.runAnt(InProcessAntStarter.java:295)
[extractESBDeploymentPlan]      at oracle.jdevimpl.ant.runner.InProcessAntStarter.mav$runAnt(InProcessAntStarter.java:43)
[extractESBDeploymentPlan]      at oracle.jdevimpl.ant.runner.InProcessAntStarter$1.run(InProcessAntStarter.java:71)
Target 'AntTest' failed with message 'javax.xml.bind.JAXBException: Unable to locate jaxb.properties for package oracle.tip.esb.client.metadata.deploymentplan.model'.
BUILD FAILED
AntTestBuild.xml:11: javax.xml.bind.JAXBException: Unable to locate jaxb.properties for package oracle.tip.esb.client.metadata.deploymentplan.model
     at oracle.tip.esb.client.anttasks.ExtractESBDeploymentPlanTask.execute(ExtractESBDeploymentPlanTask.java:546)
I am trying to build an ESB project with a deplyoment plan, or rather I'm trying to generate a deplyoment plan first.
I am stuck on this jaxb exception and would really appreciate some help.
I am using the correct jaxb version (I've tried several different version), I've set classpath in jdev (10.1.3.4) and the lib directories are correct in the ESBMetadataMigrationTaskdefs.xml:
<taskdef resource="oracle/tip/esb/client/anttasks/antlib.xml">
<classpath>
<pathelement location="${esbdeployment.home}/ESBMetadataMigration.jar"/>
<pathelement location="${commons.httpclient.home}/commons-httpclient-3.1.jar"/>
<pathelement location="${soa.suite.home}/lib/xmlparserv2.jar"/>
<pathelement location="${soa.suite.home}/integration/esb/lib/commons-logging.jar"/>
<pathelement location="${esbdeployment.home}/commons-codec-1.2.jar"/>
<pathelement location="${soa.suite.home}/integration/esb/lib/oraesb.jar"/>
<pathelement location="C:\esbdeploymentautomation\jaxb-ri-20120516\lib\activation.jar"/>
<pathelement location="C:\esbdeploymentautomation\jaxb-ri-20120516\lib\jaxb-api.jar"/>

<pathelement location="C:\esbdeploymentautomation\jaxb-ri-20120516\lib\jaxb-impl.jar"/>
</classpath>
</taskdef>
</project>

The SOA Suite may give you better support for this kind of ESB related questions.
-Eric

Deployment of ESB for 10.1.3.4 (trying to amend Endpoint properties)

I have downloaded the new deployment code (esbdeploymentautomation) to enable you to deploy an ESB between environments.
I am deplying an ESB process from Dev to Systest.
I have amended the build_tst.properties file to include all the relevant info and the build.properties.
At the bottom of this file I have added
# Values required for replace tasks.
code_dir=C:\Project\Client\jdev\jdev\mywork\dii\esbInt110Flow
search_text=/u01/esb/out/XX/int110_01
replace_text=/u01/esb/XX/INT110/out
These lines are trying to change the Endpoint property of a FileAdapter where the directories are different in the new environment.
I run extract.sh and it successfully creates a deploymentPlan_tst.xml. Great!!
I can then successfully run the deploy.sh and it deploys my ESB into the new environment but it doesn't change the Endpoint property.
When you look at the log files generated it doesn't even appear to try and run the replaceToken process.
Any ideas if this replaceTokens actually works?
When the extract.sh is run it also generates logging which seems to suggest the replaceTokens runs after the DeployESBSuitcase:
*Build sequence for target(s) `ExtractESBDeploymentPlan' is [ExtractESBDeploymentPlan]*
*Complete build sequence is [ExtractESBDeploymentPlan, DeployESBSuitcase, replaceTokens, usage, UndeployESBEntities, ]*
But from what I can see when you finally run the deploy.sh it only runs the DeployESBSuitcase process and nothing else.
The only reason for using this automaytion process is so that we can amend Endpoint properties and URLs as we deploy but this is the part that doesn't seem to work....
Help!!
Regards
Stuart

You need to run the replaceToken before the deployESBSuitecase.
Here is my example, it does a find and replace on host name
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<project name="ESBDeploymentProject" default="usage">

<property environment="env"/>
<property name="esbProjectToDeploy" value="${basedir}/deployment"/>
<property name="deploymentPlanFilename" value="${esbProjectToDeploy}/deploymentPlan.xml"/>
<property name="ImportFilename" value="${env.ORACLE_HOME}/Deployment/deploy/lib/ESBMetadataMigrationTaskdefs.xml"/>

<echo>Property Files ${env.ORACLE_HOME}/Deployment/deploy/resources/esb.${env.paramtarget}.properties</echo>
<property file="${env.ORACLE_HOME}/Deployment/deploy/resources/esb.${env.paramtarget}.properties" />
<property name="targetDeploymentPlanFilename" value="${esbProjectToDeploy}/${esb.deployTargetPlan}"/>
<target name="param-target-chk" unless="env.paramtarget">
<fail message="Target deployment environment parameter not set" />
</target>

<echo>Import ${ImportFilename}</echo>
<import file="${ImportFilename}"/>

<target name="DeployESBProject" depends="param-target-chk">
<deployESBProjects
esbMetadataServerHostname="${soa.suite.hostname}"
esbMetadataServerPort="${soa.suite.port}"
userName="${soa.suite.admin.username}"
password="${env.soapassword}">
<esbProject directory="${basedir}"/>
</deployESBProjects>
</target>

<target name="UndeployESBEntities" depends="param-target-chk">
<undeployESBEntities
esbMetadataServerHostname="${soa.suite.hostname}"
esbMetadataServerPort="${soa.suite.port}"
userName="${soa.suite.admin.username}"
password="${env.soapassword}">
<system guid="ED8243D1B9A211DCAF33D38D99DD8682"/>
<service guid="63085310B9A311DCAF33D38D99DD8682"/>
</undeployESBEntities>
</target>

<target name="ExtractESBDeploymentPlan">
<mkdir dir="${esbProjectToDeploy}"/>
<delete file="${deploymentPlanFilename}" verbose="true"/>
<extractESBDeploymentPlan
sourceDir="${basedir}"
deploymentPlanFile="${deploymentPlanFilename}"/>
</target>
<target name="ModifyESBDeploymentPlan" depends="param-target-chk">

<copy file="${deploymentPlanFilename}" tofile="${targetDeploymentPlanFilename}"/>
<replaceregexp file="${targetDeploymentPlanFilename}"
match="http://[^/]*/"
replace="http://${soa.suite.hostname}:${soa.suite.port}/"
byline="true" />
</target>
<target name="DeployESBSuitcase"
depends="param-target-chk, ExtractESBDeploymentPlan, ModifyESBDeploymentPlan">
<deployESBSuitcase
esbMetadataServerHostname="${soa.suite.hostname}"
esbMetadataServerPort="${soa.suite.port}"
sourceDirectory="${basedir}"
deploymentPlanFilename="${targetDeploymentPlanFilename}"
forcedDeployment="true"/>
</target>

<target name="usage">
<echo>
======== Environment =====================================================
SOA_DA_HOME = ${env.SOA_DA_HOME}
CLASSPATH = ${env.CLASSPATH}
ANT_HOME = ${env.ANT_HOME}
ENVIRONMENT = ${env.paramtarget}
======== Properties =====================================================
basedir = ${basedir}
SOA Suite server = ${soa.suite.hostname}:${soa.suite.port}
OC4J instance = ${soa.suite.oc4j.instancename}
==============================================================================
</echo>
<exec executable="ant" dir="${basedir}" vmlauncher="false">
<arg value="-projecthelp"/>
</exec>
</target>
</project>
cheers
James

Ant Deployment of ESB

i need to build ant scripts for ESB deployment. i can generate the deployment pane, but i am not able to build the DeployESBSuitcas.i got the error like belos
[deployESBSuitcase] ESB System Artifact <D:\sagar\ESB\sample\sample_system.esbsys> appears to be incomplete.
[deployESBSuitcase] Please verify that you have registered this ESB project at least once
[deployESBSuitcase] via JDeveloper's Register with ESB function
[deployESBSuitcase] at oracle.tip.esb.client.anttasks.DeployESBSuitcaseTask.composeQNameKeyedSystemContentMap(DeployESBSu
itcaseTask.java:201)
[deployESBSuitcase] at oracle.tip.esb.client.anttasks.DeployESBSuitcaseTask.applyDeploymentPlanToEsbArtifacts(DeployESBSu
itcaseTask.java:382)
[deployESBSuitcase] at oracle.tip.esb.client.anttasks.DeployESBSuitcaseTask.execute(DeployESBSuitcaseTask.java:494)
[deployESBSuitcase] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[deployESBSuitcase] at org.apache.tools.ant.Task.perform(Task.java:364)
[deployESBSuitcase] at org.apache.tools.ant.Target.execute(Target.java:341)
[deployESBSuitcase] at org.apache.tools.ant.Target.performTasks(Target.java:369)
[deployESBSuitcase] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[deployESBSuitcase] at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
[deployESBSuitcase] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
[deployESBSuitcase] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
[deployESBSuitcase] at org.apache.tools.ant.Main.runBuild(Main.java:668)
[deployESBSuitcase] at org.apache.tools.ant.Main.startAnt(Main.java:187)
[deployESBSuitcase] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
[deployESBSuitcase] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
BUILD FAILED
D:\sagar\ESB\sample\deployESB.xml:75: ESB System Artifact <D:\sagar\ESB\sample\sample_system.esbsys> appears to be incomplete
Please verify that you have registered this ESB project at least once
via JDeveloper's Register with ESB function
could you please help me in this issue..
thanks
Hari
Edited by: user10222248 on 12 Feb, 2009 3:44 AM
Edited by: user10222248 on 12 Feb, 2009 3:47 AM

Hi,
Can you confirm whether you are able to successfully register your ESB project through JDeveloper? As I can understand from the error description that there are few issues found in sample_system.esbsys file.
Regards,
Sathya

Problem while registering ESB Process with integration server

Hi All,
I am facing an error while registering the ESB Process in Intergration Server. I am getting the following error in ESB.
"Registration of ESB Process (Process Name) is failed, Exception: Connection Refused. connect Check the Integration Server Connection is correctly configured and the Integration Server is up and Running"
I am able to deploy the BPEL process from the Jdeveloper using the same Integration Server Connection parameter. Also I have checked the Intergration server and its up and running.
Any Help or Pointers to this issue is helpful.
Thanks in advance,
Saravana

Yes, but you are getting connection refused which is more thank likely cause by the application server connection failure.
If you should see a details button when testing the connection can you please provide result of this.
It looks like you have entered a wrong port, hostname, or oc4j instance.
If you go to your OS
cd SOA_HOME/opmn/bin
run the command
opmnctl status -l
you will see all the ports for your instance. Now revisit both the application server and Integration server settings mad make sure they are set correctly. Especially the hostname and the port for the application server
Also make sure your proxies are correct in JDeveloper
Tools -> preferences -> web browser & proxy

BPEL deployment plan in 10.1.3.4

Hello guys,
I've downloaded the MLR patch to upgrade to 10.1.3.4 and wondering where to find and how to use the BPEL deployment plan.
According to Robert Zimmerman's presentation titled Oracle BPEL Process Manager Update - April 22 (http://www.oracle.com/technology/tech/soa/cab/oraclesoacab-webinar-04-22-08bpel_10_1_3_4_update.pdf), this release includes the new BPEL deployment plan, similar to the "old" ESB deployment plan.
Any help is appreciated.
Kind regards,
H

Hello Heidi,
Thanks for the quick reply.
That chapter is not quite what I was looking for, but nevertheless you pointed me to the right document. I was looking for chapter 3.10.10 "Automatically changing URLs and properties for Dev, Test and Prod.-environments".
Cheers,
Harm

BPEL deployment automation

Hi all.
I've been reading about the efforts regarding esb deployment automation:
Dealing with changing service wsdl locations in the ESB
Now, I'd like to know about the latest best practices regarding BPEL deployment automation for different environments.
I was wondering if there's some already tested ant configuration for deploying multiple BPEL projects at the same time using a specific bpel.xml
Thanks
Denis

I created an article on this issue:
http://orasoa.blogspot.com/2006/08/using-ant-in-bpel-environment.html

Register java service on ESB bus

Hi, I have from a wsdl generated java classes, and implemented som logic in them so that the implementation method returns something. Now, I want to register it as a webserivce on the ESB. I can deploy it using the generated "webservices.deply" in jDeveloper, and then it is deployed on the application server, and I'm also able to test it with success. But how do I make it available on the ESB?

Hi,
Using the Ant deployment tasks for ESB might help (especially the ones using deployment plans), see: Re: Regarding ESB Deployment without using JDeveloper and http://www.oracle.com/technology/products/integration/esb/files/esbdeploymentautomation.zip.
Regards, Ronald

Publish ESB without username/password of connection using Jdeveloper

Hi,
I have used jdeveloper10.1.3.3 to developer BPEL Process and ESB services.
I have created a Application Server Connection in jdeveloper with hostname, url path and RMI Port right, but without username and password.
I have created a Integration Server Connection mapping the connection above. I tested this Integration Server and the result was:
Application Server: FAILED
BPEL Process Manager Server: OK
ESB Server: OK
After the test of Integration Serve Connection , I tried register my ESB project using the action "Register witn ESB" from Jdeveloper and the result was the error:
"Reload services from ESB Server failed while trying to query service definitions from server."
After the registry, I saw in the ESB Crontol that the ESB Service was publish.
Question:
Is possible resgistry a ESB service with URL connection correct, but without username and password of Application Server Conncetion from Jdeveloper?
Is there any configuration for validat of username and password of Application Server Connection in the publish of ESB service?
Is a bug of jdeveloper?
Thanks,
Fabrício.

Hello. I'm pretty sure you cannot register an ESB with no username/password - it uses the username/password information in the integration server connection properties to login and deploy. We were surprised that BPEL uses ant build properties so you can specify the name/password, ESB does not - it only uses the integration server connection info.
In 10.1.3.4 (which we don't have yet) the ability to use ant for ESB deploys has been added.
Daren
Edited by: djcasey on Jan 30, 2009 11:12 AM

ESB - Register esb with command line?

Hi,
Is there a possibility to register ESB via command line?
I want to install an esb project on different environments and i'm searching how. What's the best way to do this?
Thanks,
Els

The way to do this is using the esbDeploymentAutomation. This can be found in the $SOA_HOME/integration/deployment. There should be a zip file that has all the information in it.
it does require you having fairly good ant skills.
here is just an example of mine.
cheers
James
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<project name="ESBDeploymentProject" default="usage">

<property environment="env"/>
<property name="esbProjectToDeploy" value="${basedir}/deployment"/>
<property name="deploymentPlanFilename" value="${esbProjectToDeploy}/deploymentPlan.xml"/>

<property file="${env.SOA_DA_HOME}/Deployment/deploy/resources/environment.${env.param.target}.properties" />
<property name="targetDeploymentPlanFilename" value="${esbProjectToDeploy}/${esb.deployTargetPlan}"/>
<target name="param-target-chk" unless="env.param.target">
<fail message="Target deployment environment parameter not set" />
</target>


<import file="${env.SOA_DA_HOME}/deployment/deploy/lib/ESBMetadataMigrationTaskdefs.xml"/>

<target name="DeployESBProject" depends="param-target-chk">
<deployESBProjects
esbMetadataServerHostname="${soa.suite.hostname}"
esbMetadataServerPort="${soa.suite.port}"
userName="${soa.suite.admin.username}"
password="${soa.suite.admin.password}">
<esbProject directory="${basedir}"/>
</deployESBProjects>
</target>

<target name="UndeployESBEntities" depends="param-target-chk">

</target>

<target name="ExtractESBDeploymentPlan">
<mkdir dir="${esbProjectToDeploy}"/>
<delete file="${deploymentPlanFilename}" verbose="true"/>
<extractESBDeploymentPlan
sourceDir="${basedir}"
deploymentPlanFile="${deploymentPlanFilename}"/>
</target>
<target name="ModifyESBDeploymentPlan" depends="param-target-chk">

<copy file="${deploymentPlanFilename}" tofile="${targetDeploymentPlanFilename}"/>
<replaceregexp file="${targetDeploymentPlanFilename}"
match="http://[^/]*/"
replace="http://${soa.suite.hostname}:${soa.suite.port}/"
byline="true" />
</target>
<target name="DeployESBSuitcase"
depends="param-target-chk, ExtractESBDeploymentPlan, ModifyESBDeploymentPlan, UndeployESBEntities">
<deployESBSuitcase
esbMetadataServerHostname="${soa.suite.hostname}"
esbMetadataServerPort="${soa.suite.port}"
sourceDirectory="${basedir}"
deploymentPlanFilename="${targetDeploymentPlanFilename}"
forcedDeployment="false"/>
</target>

<target name="usage">
<echo>
======== Environment =====================================================
SOA_DA_HOME = ${env.SOA_DA_HOME}
CLASSPATH = ${env.CLASSPATH}
ANT_HOME = ${env.ANT_HOME}
ENVIRONMENT = ${env.param.target}
======== Properties =====================================================
basedir = ${basedir}
SOA Suite server = ${soa.suite.hostname}:${soa.suite.port}
OC4J instance = ${soa.suite.oc4j.instancename}
==============================================================================
</echo>
<exec executable="ant" dir="${basedir}" vmlauncher="false">
<arg value="-projecthelp"/>
</exec>
</target>
</project>

ESB deployment/registration

Similar Messages

Maybe you are looking for