In this blog I’ll show you how to add a simple custom case activity to the case we’ve developed in my earlier blogpost here. I’ll update the GitHub code so that it will reflect the changes I made in the course of this writing.
One of the most popular use cases for Oracle Service Bus (OSB) is the mediation of synchronous service interactions. In this scenario, a client invokes the service through a proxy instead of the actual service endpoint, guaranteeing that the consumer is decoupled from the producer. This type of architecture allows producers to be changed without impacting the consumers, allowing greater agility for projects with volatile requirements.
Scaling down the database is a common requirement in Fusion Applications Cloning. For example, if a production environment is cloned towards a test or development environment which typically don’t require high availability on the database tier at all or at a smaller scale.
This blog describes how such a scale down can be accomplished with out-of-the-box capabilities of the Fusion Applications cloning tool.
The example below shows how you can start a Pivotal GemFireXD distributed system from IntelliJ IDEA. Here we will start a Locator which has Pulse enabled as well as one member. We use the following class method to achieve this from an IDE such as IntelliJ
1. Add the following to your maven POM file to ensure the correct libraries are present.
OIM R2 PS2 delivers a long time expected functionality: access policy harvesting. This new feature adds more flexibility to OIM access policies usage.
This is another post in the Oracle Identity Manager Academy from the Fusion Security Blog. for the entire post list click here.
Some of our OIM customers have a use-case of implementing a custom landing page. Such a landing page could be used for multiple purposes, for example – to display some static information like guidelines for using the system or dynamic information like system news, new features, releases etc.
OIM 11gR2 PS2 provides a convenient way of implementing this use-case and it is the subject of this post.
The basic idea could be summarized in the following steps:
ADF web applications often use session-scoped user context information that is also used in the ADF Business Components (ADF BC) layer. For example, the user language might be used to query language-specific data from the database. This article explains how this user context can be set up when accessing the ADF BC layer through its SOAP-based web service layer rather than through a web application.