BI Report: Apply button missing

1.  Navigate to folder containing the report layout and click on Edit button

2.  The following window will open, click on 'Parameters' button

3.  The pop up that opens will allow you to set the visibility of 'Apply' button.

OIM: Release a claimed task

Detailed Steps:

1. Login into BPM worklist URL (http://hostname:port_number/integration/worklistapp).

a. Please note that ‘port_number‘ is soa server’s port(8001).

2. In the left hand navigation tree, click on ‘Administrative Tasks’

3. Click on the ‘pencil icon’ on the top of the navigation tree to edit the inbox settings. Specifically, we are adding more column in the main window.

4. Click on  the down arrow next to the ‘magnifying glass’ icon on top of the main window and select ‘Advanced’

a. This is used to specify the search filter. This is a one-time activity, search filter can be saved as a view.

5. Specify the search condition

6. As per the search conditions, this will give you all the tasks which satisfy all the following conditions:

a. Are raised for disconnected provisioning.

b. Are acquired by a user with user login as ‘RAGNI’

c. Are in ‘assigned’ status.

7. All tasks will be displayed, satisfying the search criterion.

8. You can select the claimed task and, and from the ‘Actions’ dropdown select ‘Release’ to un-

claim

OIM: ORA-12899: value too large for column "WFMESSAGEATTRIBUTE"."STRINGVALUE" (actual: 2003, maximum: 2000)

The request fails with an error message: ORA-12899: value too large for column "WFMESSAGEATTRIBUTE"."STRINGVALUE" (actual: 2003, maximum: 2000)

The root cause is simple, OIM allows justification of 4000 characters but SOA supports justification of maximum of 2000 characters

We need to restrict justification to 2000 characters in OIM. 

Justification is a inputText field in ADF’s terms and one of the fields property is ‘Maximum Length’. 

Solution: Create a SB,  update the maximum length property to 2000 and test.

Quick Tip#3: Storing JSON data in Oracle Database

For the last couple of years, I have used JSON as my go to data format. Many a times, I had to store the JSON in the database. I used the same approach of storing it as a VARCHAR2/CLOB/BLOB and then validating the data via API. Also there was no check on what else could exist in that column(junk value or error insertion) resulting in even more validations for my data.

Now, Oracle has come up with JSON support in databases 12.1.0.2 version, which is really helpful for some one storing the json values in db.

Here is the link to the article, which explains the same in details.

https://blogs.oracle.com/jsondb/storing-json-in-the-oracle-database

Awesome work, Oracle.  

OAM: Learning the basics - Part 5 - SAML

SAML (Security Assertion Markup Language), is the leading SSO protocol and is paramount in understanding the Single Sign Sign(SSO) workings. SAML is the language by which Identity Provider and Service Provider communicates(XML based) to establish the user's identity.

*image copied from google.

Previous Post: http://iamsecurity-tips.blogspot.com/2017/07/oam-learning-basics-part-4-proxy.html

OAM: Learning the basics - Part 4 - Proxy, Forward Proxy, Reverse Proxy

Proxy: Proxy means that someone is action on behalf of someone else.

Forward Proxy: Here the proxy server is acting on behalf of the client, i.e. the content server is unaware that the request is coming from the ‘Client’.  For the ‘Content Server’, the ‘Client’ does not exist. 

Reverse Proxy: Here the proxy server is acting on behalf of the content server. i.e. the Client is unaware the response is returned from the ‘Content Server’. For the client, the ‘Content Server’ does not exist.

Next Post: http://iamsecurity-tips.blogspot.com/2017/07/oam-learning-basics-part-5-saml.html
Previous Post:  

SOA: JBO-29000: Unexpected exception caught: oracle.bpel.services.workflow.client.WorkflowServiceClientException, msg=javax.naming.NameNotFoundException: Unable to resolve 'TaskQueryService'.

Check soa-infra.war's status from admin console. Restart the same.