Feeds:
Posts
Comments

Here is a small example of a way to enable or disable a command button using a standard functionality of an ADF.
Take for example the next scenario: You want to reject a form, and you must enter a reject reason.

For that we will use a commandButton (for the reject action) and an inputText (for the reject reason).
Change both objects’ attributes as follows:

inputText:

  • Set the AutoSubmit property to ‘true':

    AutoSubmit

CommandButton:

  • Set the PartialTriggers property to the Reject InputTextId Id:

    PartialTriggers

  • Set the Disabled property to have a condition base on the InputText value:
    In my example: #{empty bindings.RejectReason.inputValue}

    Reject Reason

 

Run the page and test it.

Good Luck!

When you create a new ADF Business component that uses a DB connection (like Business component From Table, Entity Object etc..), you can see that automatically the wizard connects you to a predefined DB connection.
Usually, if you have only one DB connection defined it’s not a problem. But when you have more than one connection, you want to control the required connection.

 

To change or control the default connection, follow the next steps -

Right click on your project and choose Project Properties:

Project Properties

Continue Reading »

In this post I will explain a simple way to use JS (JavaScript) in an ADF page.
To implement javaScript function you will need few things:

  1. Define a JavaScript code
  2. Link the Component that will refer to that JS code (InputText, Command Button etc..)
  3. Obviously, understand the purpose of using JS in your ADF application

 

So let’s define first the JS code.
Go to the page definition source and drag the resource object under the document tag. Choose Javascript as the resource type:

Resource

 

Continue Reading »

The below error can happen when you run any kind of a process that uses JDBC:

ORA-28267: Invalid Namespace Value In SOA Suite 11.1.1.7
ORA-02063

This is a bug!
The cause of the problem is when using Oracle JDBC Driver file (ojdbc6dms.jar) and calling a DB object (procedure, function etc…) that issues SQL over a DB link from 11g to 10g DB.

There is no patch for that at the moment.
I found a workaround, that was approved by oracle:

Under the below folders, replace the ojdbc6dms.jar file with ojdbc6.jar file:
$MID_HOME/wlserver_10.3/server/ext/jdbc/oracle/11g
$MID_HOME/oracle_common/modules/oracle.jdbc_11.1.1

You can find the ojdbc6.jar driver in the below link:
http://www.oracle.com/technetwork/database/features/jdbc/index-091264.html

It is also suppose to be under $MID_HOME/wlserver_10.3/server/lib. You can just copy it from there.

There is one exception: No JDBC metrics will be produced. If you need it, you will have to open SR.

Good Luck!

Many people are asking if creating a BPEL process template is possible on 11g.
The answer is NO. Sorry…
It is very annoying as it was possible on 10g.
I guess the reason is because of the way we creates a BPEL process within the composite application.
There is an option to create a project & application template, but not a component one.

The good news is that it will be possible on 12c version.

You can get help with renaming a BPEL process as a workaround in the below oracle post:
https://blogs.oracle.com/middleware/entry/renaming_bpel_process_names

 

Good luck

In this post I will explain what is the correct and standard way to deploy an ADF application (project) from JDeveloper.
Usually, when we want to deploy, let’s say – a SOA or a BPM project, we have to right click on the project, and deploy it to the required managed server. It can work the same way for an ADF project, but it is not the recommended way.

So, the next steps will guide through the right procedure:

Continue Reading »

While trying to run a deployed composite you are getting the below error:

java.lang.Exception: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: oracle.fabric.common.PolicyEnforcementException: PolicySet Invalid: WSM-02557 oracle.wsm.policymanager.accessor.BeanAccessor The documents required to configure the Oracle Web Services Manager runtime have not been retrieved from the Policy Manager application (wsm-pm), possibly because the application is not running or has not been deployed in the environment. The query “&(policysets:global/%)(@appliesTo~=”WS-Client()”)” is queued for later retrieval. at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:813) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:385) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:302)

This error is a bit tricky because you might consider it as a bug.
There are 2 possible reasons for this error:

  1. Mismatch or missing listen address in the Admin/Managed server.
  2. The local host(pc) name is different than the host name you’ve defined while installing SOA Suite (or other Middleware components).
    You can see example for that while trying to test you processHost

Both reasons causes the server to NOT listen the correct address.
The solution, is to update the host name listen address under the installed Admin/Managed servers:
Go to WL console -> Environment -> Servers -> Under the configuration tab click the Admin server -> fill the Listen Address.
Repeat it for all other managed servers, and restart the servers.

Note: If there is a mismatch between your host and PC name, you might consider to fill out the local host IP address and not the DNS.

Good Luck

Follow

Get every new post delivered to your Inbox.