Showing posts with label cloud. Show all posts
Showing posts with label cloud. Show all posts

Wednesday, 4 July 2018

Oracle Fusion Application : Create Custom ESS Job to run BIP Report


In this post I will list the steps required to create a new custom ESS job to be used to run a BIP report which takes a parameter input.

Assuming that you have already created a BIP report, lets begin!

1. Login to Oracle Application Cloud
2. Navigate to Setup & Maintenance
3. In Search Task, search for 'Enterprise Scheduler Jobs for Financial and Supply Chain Management%'









4. Click on the task
5. On the Manage Job Definition Tab you will see a Action icon like below









6. Click on Action and select Create














7. On the Job Definition page above,  fill the details like below:

Display Name: Test ESS Job [a meaningful name]
Name: Test_ESS_Job [Identifier without spaces]
Path: fscmess/testjobs/ [relative folder which will be created under path /oracle/apps/ess/custom/]
Description: Custom ESS Job
Job Application Name: FscmEss
Enable submission from Enterprise Manager: Unchecked
Job Type: BIPJobType
Bursting report: Checked if you have bursting for your report else Unchecked
Class: (Auto populated)
ReportID: /Custom/Samples/Test BIP Report.xdo [path of your report on BI Catalog]
Allow multiple pending submissions: False
Enable submission from Schedule Process: Checked

8. On the parameter tab below click on Actions > Create
9. Enter the details like below

Parameter Prompt: Identifier
Data Type: String
Read Only: Unchecked
Page Element: Text Box
Default value:
Tool Tip:
Required: Checked
Do not Display: Unchecked

10. Save and Close
11. Done

To submit/run this job:

1. Navigate to Schedule Processes > Schedule New Process > Search (Test Ess Job)
2. Select
3. Enter parameter id and submit.
4. Refresh to view the status of the process.
5. Check your report output in process log.



Helpful?? Please comment

Happy Learning!!

Sunday, 8 April 2018

Oracle ICS : Difference between Orchestration and Map Data Style/Pattern


When you are creating an integration in Integration Cloud there are 4 styles/patterns of integration that you can create. This is in the version 18.1.3.0.0 of Integration Cloud.

In this post, I will explain to you the difference between going with;
   a. Map Data
   b. Orchestration



The other 2 are for ICS to/from integration which I will explain in a different post.

Now, when creating integrations your requirement may vary as to how you want to interact with/between two or more services.

On that note:

a. Map Data: This style is used when you only want to talk between 2 services. Here 2 services mean one which is talking to the source(trigger) and the other which is talking to the target system(invoke).

So either you would be having:

    i. One way exchange:

Ex: Read from a Queue/File/DB/WebService and send to another Queue/File/DB/WebService.
Read the data, transform/filter/enrich it and then send it to the target service. No response required  from target. In this case you have only one map(transformation).

    ii. Synchronous exchange:

Ex: Take input from the source, call a service with that input and get a response back. Enrich/filter/transform the data received and send it to the source.
Here you have 2 mappings: Request and Response.

You will also have a fault map which you can use in case there is any fault in the target service.

Your use depends on the type of service and business requirement you are trying to achieve.

b. Orchestration: Orchestration style is used when you want to invoke multiple services and perform actions(condition/looping/transform/logging/alerting/notifying etc) in between, finally to achieve one business requirement/outcome.

Simple Ex: Read data from a DB table, loop through each record and based on condition write to 2 different files and SFTP them.

In Orchestration style we can achieve a great amount of data processing and application of business rules using the available actions(or activities).

Not all actions which were part of OSB are there presently, but they may be added in future releases.


Helpful?? Please Comment.

Happy Learning!!



Saturday, 7 April 2018

Oracle ICS : Create SOAP connection using WSDL URL


If you are new to ICS and want to create a SOAP WSDL connection, follow the below steps:

1. Login to your Oracle Integration Cloud domain.
















2. On the Home page click on 'Create Connections' green box















3. On the 'Connections' page, right-hand corner click on 'Create'






4. On the 'Select Adapter' pop-up, search for SOAP adapter and click on 'Select'













5. You will be directed to the 'Create New Connection' dialog. Fill as below:

  a. Name - Enter a unique name for your connection (Not more than 50 char).
  b. Identifier - (No need to enter) It will be added as you key in the connection name.
  c. Role - Leave default -Trigger & Invoke
  d. Description - Enter a short description if required.















6. Click on Create.











7. A connection is created (with status at 8%). Now we will configure it (to 100%).

8. (Optional) If you to receive notifications when there a change/issue with this connection, you can enter the email address in the 'Email Address' box.

9. Click on 'Configure Connectivity' button on the right side.

10. On the Properties dialog box enter/paste the web-service WSDL URL that you want to invoke.
(Upload is when you are using a abstract WSDL to create your own service)















If the web-service WSDL requires the additional properties mentioned, select the ones necessary.

11. Click on OK
12. Scroll down of the page and click on 'Configure Security'
13. Select the type of security policy* that is required for the service and enter the values as required.

By default, the security is set to 'Username Password Token' type.

  a. Basic Authentication: When service requires username/password only to be called.
  b. Username Password Token: When the service requires username/password as WSS token
  c. No Security
  d. SAML

*You can check the security policy by loading the WSDL in the browser.

14. Done, now Save and then Test your connection.

You can either
  a. Validate and Test (Validates your entire WSDL), or
  b. Test (Syntax validation)






15. Close
16. Your connection is created and configured 100%. It will have a ✅






Done.


Helpful?? Please Comment.

Happy Learning!!



OSB 12c : Dynamic Routing to Business/Proxy Service

Dynamic routing is a kind of  Content-based Routing pattern, which is used when the BusinessService/ProxyService path is required to be de...