Tuesday, 16 February 2016

Oracle Enterprise Scheduler -ESS - Quick Scheduling the SOA/BPEL service

Hello Folks,

Yet another new feature in Oracle SOA Suite 12C is Oracle Enterprise scheduler Service (ESS). ESS is also part of MFT (Brand new feature to utilize utmost file transfer functionality in SOA 12C-Managed File Transfer- Will discuss in my next blog).

We used to have lot of challenges while scheduling any service. Third party vendors created many tools for scheduling s service (To get this functionality adopted) but some vendors could achieve this some people end up with no result, It’s good that Oracle added this in this new release, which is very useful in middleware space.

ESS features in middleware:
Schedule periodic notifications for faulted instances.
Schedule any job without manual triggering.
Long running services.
Immediate triggering in the background.
Run once at future time or at recurring schedule.

ESS Demo: Quick service scheduling.
To schedule any service there are two parts of it.
1         Define the job to be scheduled.
2     Submit he job based on the required time intervals.

Here we will see how to schedule a simple SOA service/WS. 
Below is the Home page of ESS.

 Open ESS App page, Drop down the Scheduling service group.

Go to Job MetadataàJob Definitions.

Click on NEW to Create/Define new schedule.
Enter the names and package name, Job Type (Based on the service you can select this type of a job). Click on the Select Web Service

Enter the valid WSDL, which need to be defined /scheduled.
Select the type of the web service.

Once you select SOA as a Web Service Type- You will see coming service and port type. Select appropriate port type of this service. You will have opened extended popup to give the input payload. You can give the payload to test.    
Give the payload and say OK.

Now the Job has been defined. You need to submit the schedule next.

Now the job definition is completed. Its time to Submit the job defined.

Drop down Scheduling Service GroupàJob RequestsàSubmit Job Requests.

Enter the submission notes to track the job details among different jobs.
Enter the Job definition name and then search. 

Upon selecting the defined job we can see the service section filled with job metadata.

In the schedule part we can see three parts of it.
1 ONCE:  Once is the one time job submission (You can select the job time-date-year)

2 Use existing schedule- If you already created schedules then we just browse the schedule and select it. 

3 Specify schedule: This one is to schedule the job with multi frequency, based on time zone with start date. Can save this schedule to use it in second part again when needed.

Once this is done we can see the job is submitted.

In actions drop down part, we can see the request log, submitted composite flow trace and other features to modify the properties.

Upon successful job submission the job schedule page will be showing the status and count and other statistics.

That’s it for ESS. This is the most simple and very useful feature in SOA 12C.

Happy Learning...!!!!!!!!!!!! Fun Sharing.........!!!!!!!!!

Tuesday, 2 February 2016

NXSD Tester :- Test your files against NXSD neither deploying the SOA code nor JDeveloper(Command line tool)

Hello Folks,

Here is the exciting command line tool to test the FTP/File adapter NXSD to test the files.
In any middleware tool,
 If you want to test your nXSD(Native schema ) wrt files, you have only two options.

      1. Deploy the code to Server and put the Input testing files to file pickup location and run the code.
            2. Use JDeveloper to test the file wrt the nXSD.

Here I found another option to test the files against nXSD(Native schema). (Source: Oracle).
I have used the some libraries to test the NXSD. Here you see all the mandatory JAR to be used in below tool.

List of JARs.
      1. bpm-infra.jar
      2. mail.jar
      3. test-translator.jar
      4. translator.jar
      5. xml.jar
      6. xmlparserv2.jar

You can find all the JARs in weblogic folder post instillation.

Step by Step procedure:

     1. Have the java installed.
      2. Set the list of jars added to the class path.
      3. Run  java xlator.util.Translate –help to check the dependency . You should be able to run the command.

    1. Add the mandatory JAR files to one folder.
    2. Place the NXSD and Input file on the same folder to test.
    3. Open CMD in that folder path.
    4.  Run the below commands to test the files. (Note: You need to set the classpath before run these commands otherwise you will not be able to run)

Command 1: java xlator.util.Translate -inbound -schema (NXSD_Schema.xsd) -root (Root-Element Name) -input (InputFile.txt) -output (FileName.xml) 
You will get the tested output XML file if the Input files follow the schema.

Command 2: Run this command to test the file with de-batching as series of output files.
java xlator.util.Translate -inbound -debatch 1 -schema (NXSD_Schema.xsd) -root (Root-Element Name) -input address-csv.txt -output (FileName.xml)
You will get the series of tested output XML files if the Input files follow the schema & if you have the multiple records in the Input file.

Happy learning….!!!!!!!! Fun Sharing….!!!!!!!!!!!!!!!