SOA 12c–Creating ESS Job metadata (JDeveloper)

In the previous post, We have seen how to use EM Console to create the Job metadata. This did not provide the much information about development and deployment details of ESS application. So in this post, we will use JDeveloper to create ESS Job metadata to call the Service Bus proxy services however the steps remain same for BPEL services too.

Before proceeding with actual creation of job metadata, we will know the terms Hosting and Client Applications.

Hosting Application

ESS Jobs always execute in context of hosting application. When we configure domain for ESS, we get EssNativeHostingApp which is pre-deployed native hosting application that is well suited for custom remote jobs like EJB and web service jobs. However, we can’t execute custom Java jobs.

Client Application

Client applications are typically J2EE application used to submit jobs, query job status and optionally perform updates to ESS metadata. We cannot add ESS job metadata (using MAR archive) directly to the pre-deployed native hosting application and have to deploy through a client application or using metadata API.

Enter Job name. Since we are going to call a OSB Synchronous service select the corresponding Job type as shown below. Make sure that location includes essmeta directory.

Note that MW_HOME env variable has to be set as shown below to be able to see and select Job Type.

Click Web service icon to select the WSDL.

Select Service Bus as web service type and click search icon.

Enter Service Bus Proxy Service WSDL as shown below and click OK. Make sure that you give the URL of concrete WSDL.

Verify that Service and Port Type are automatically populated. Select the operation and parameterize payload using ESS_REQ as shown below. This context is used to access ESS Parameters defined for Job. Hence we need to create CustomerId parameter. Click OK.

If the EAR file generated from this application is to be deployed, certain MDS partition entries must be specified in this file, so add the following contents. The data source referenced here is automatically created when we configure the domain to include ESS. The namespace mentioned over here (highlighted below) should match the package structure we used for creating job definition.

Though we add only ESS Job Support and ESS Client Support features during application creation, we see ESS Host Support as well in Project feature section as shown below.

Unable to see the Job definitions in ESS while submitting requests, when used package structure (which is effectively a namespace) that does not contain /oracle/apps/ess. Section 1.2.10 of this documentation clearly mentioning that the job definition must be created in the namespace /oracle/apps/ess/custom.

Unable to refer the WSDL from SOA_MDS or File System in the Web Service chooser during Job definition creation and is resulting into the following error as shown below.

The data source mds-ESS_MDS_DS is to be targeted to AdminServer as shown below,so that we will be able to select data source during deployment.

Initially thought, there is no need of ejb-jar.xml in this ESS application as it’s used predominantly to specify Application Name. But was getting following error during deployment when this file is not present in application or the file has empty contents. So at minimum, this file should have the contents as mentioned above.

Related

8 Responses to “SOA 12c–Creating ESS Job metadata (JDeveloper)”

Hi Siva,Thanks for your post. I am trying to create a job definition for a secured https web service but while browsing the WSDL, I keep getting the error as ‘Enter a valid WSDL URL’ .Is it something i am missing while configuring an https service?

Hi Siva,
Thanks for your amazing post, i have this problem in my JDeveloper12c after creating Custom Application and Project, i did exactly as you mentioned, but when i try to create Job Definition, i see Job Type list empty.

I am stuck at screen 9, couldnt proceed further, could you please help me fix the issue. I tried using 12.1.3 and 12.2 versions of Jdeveloper.

Hi, Thanks for posting the steps.Need one help.How do move this jobs from one environment to other.For e.g. In DEV environments we have jdev to deploy the jobs.How do we deploy the jobs if we don’t have connectivity from Jdeveloper ( i mean Production).i would like to know the Test 2 Production strategy for ESS.Thanks in advance.

Hi, I tried this but during the deployment of EAR, as per this blog I should select mds-ESS_MDS_DS metadata. However I only see mds-owsm an mds-soa repositories as options. I am using SOA 12.1.3.Could there be something wrong with my setup?