In my maven i configured the maven-glassfish-plugin and tried to deploy my application. I received the following message:

[INFO] Unable to start domain "webui". IOException: Cannot run program "C:\prog\glassfishv3\glassfish\bin\asadmin": Crea
teProcess error=193, %1 is not a valid Win32-Application

The plugin tries to execute in my glassfish installation the application asadmin. In this directory there are to files with this name. a windows version with the .bat extension and a unix version without a extension. To solve this problem delete or rename the file without an extension to asadmin.sh. Now windows will send the request to the bat file.

Unable to deploy application

After i solved this issue i encountered a second problem. I configured the plugin to use the passwordfile that’s generated in the domain config.

<groupId>org.glassfish.maven.plugin</groupId>
<artifactId>maven-glassfish-plugin</artifactId>
<version>2.1</version>
<configuration>
<glassfishDirectory>${glassfishDirectory}</glassfishDirectory>
<user>${glassfish-user}</user>
<passwordFile>${passwordFile}</passwordFile>
<debug>true</debug>
<echo>true</echo>
<domain>
<name>${project.artifactId}</name>
<adminPort>4848</adminPort>
</domain>
<components>
<component>
<name>${project.artifactId}</name>
<artifact>${project.build.directory}/${project.build.finalName}.war</artifact>
</component>
</components>
</configuration>


This works to start and stop the domain but for deploying an application it doesn’t accept the password file. To solve this problem i created a personal password file in my userhome containing the password of my domain in this case ‘admin’ and changed in my settings.xml the value of passwordFile to my personal password file:

here the configuration in my settings.xml

<properties>
<!-- Glassfish -->
<glassfishDirectory>C:/prog/glassfishv3/glassfish</glassfishDirectory>
<passwordFile>${user.home}/passwd.local.file</passwordFile>
<glassfish-user>admin</glassfish-user>
<userPassword>admin</userPassword>
</properties>


here the content of my passwd.local.file

AS_ADMIN_PASSWORD=admin


Permalink | No comments | del.icio.us | Technorati | digg | dzone | StumbleUpon | Software development

I have installed the following components:

• Oracle 11g Database
• OC4J Container 10.1.3.5.0
• Oracle Fusion Middleware MapViewer 11.1.1.2
• Oracle Spatial Demo Data Set

upgraded the SQL Developer to version 2.1 and installed the GeoRaptor plugin to visualize oracle spatial data

Step 1: “Validate Demo Data and working of GeoRaptor”
Step 2: “Validate Working of MapViewer jsp client”
Step 3: “Validate Working of MapViewer JavaScript client”
Step 4: “Include the JavaScript client in APEX page”

Step 1 – Validate Demo Data and working of GeoRaptor
After installing the software i tested the working of georaptor if it could visualise the counties supplied in the demo data

Now the data is available in the database we can can configure mapviewer (if not already done after installation).

Step 2 – Validate Working of MapViewer jsp client
Go you the mapviewer application http://[server]:[port]/mapviewer/ in my case: http://oracle11g:8888/mapviewer/. Don’t click on the link. That will send you to the 10g version. Let the redirection preform to enter the 11g application.

Click on the Admin link in the top left and login with oc4jadmin account.

Create a data source to access the demo data.

After defining the data source you can check if the data is available for the application by clicking on the tab ‘Meta Data’

Here you can check what map’s, themes and styles are present in the defined data source. If you specified everthing correct you will see the maps and themes from the demo data.

Now it’s time to show a map on the screen!!

Start the MapViewer jsp client by selecting the Demo tab and click on the link mapclient.

On the following page you have to enter DataSource, BaseMap, X,Y position, Zoom level. After entering the requesten info you click on Submit and you will see the following map:

Step 3 – Validate Working of MapViewer JavaScript client

Enter the flowing url in your browser: http://[server]:[port]/mapviewer/fsmc/omaps.jsp in my case: http://oracle11g:8888/mapviewer/fsmc/omaps.jsp

This application ask again for the datasource and other data to display the map. After suppling the information and pressing the Proceed button you will be presented a map with control buttons to navigate over the map.

Step 4 – Include the JavaScript client in APEX page

Step 4.1 Create page on in you APEX application

Step 4.2 Configure the Page Attributes:
* Header Text
* Body Attribute

Enter the following text in Header Text:

<script language="Javascript"
src="http://oracle11g:8888/mapviewer/fsmc/jslib/oraclemaps.js">
</script>
<script type="text/javascript">
function on_load_mapview()
{
var baseURL = "http://"+"oracle11g:8888"+"/mapviewer";
// Create a MVMapView instance
var mapview = new MVMapView(document.getElementById("map"), baseURL);
// Add a map tile layer
mapview.addMapTileLayer(new MVMapTileLayer("mvdemo.demo_map"));
// Set the initial map center
mapview.setCenter(MVSdoGeometry.createPoint(-120,36));
// Set Zoomlevel
mapview.setZoomLevel(1);
// Add navigation controles
mapview.addNavigationPanel('east');
// Add a scale bar
mapview.addScaleBar();
// Show map
mapview.display();
}
</script>

Here we load the oraclemaps.js for the communication with the MapViewer. Don’t forget to change the url’s to fit with your environment.

Enter the following text in HTML Body Attribute
onload="on_load_mapview()"

This will call the function on_load_mapview() specified in the header of this HTML page.

Step 4.3 Create a HTML region with the following HTML:
<div id="map" style="width: 1200px;height: 600px"></div>
Now your application is ready to run! Hopefully you will have the same result as i have presented below:

Permalink | One comment | del.icio.us | Technorati | digg | dzone | StumbleUpon | Software development

ORA-29273: HTTP request failed
ORA-06512: at "SYS.UTL_HTTP", line 1577
ORA-24247: network access denied by access control list (ACL)
ORA-06512: at line 1

His is the result of the improved security in 11g. When you want to create a connection to a remote server with one of the util packages: TCP,HTTP,SMTP besides the privileges on the package you need to configure the connection in a Access Control List (ACL). In a ACL you can configure in detail the allowed connections by entering the following parameters:

• Server name or IP
• Port number range
• Database user/role
• Start date
• End date

The package DBMS_NETWORK_ACL_ADMIN enables you to create and configure ACL’s.

The ACL is a nice security feature but when migrating applications to 11g it’s something you will encounter.

More information:

• dbms_network_acl_admin documentation
• Article writen by Arup Nanda

Permalink | No comments | del.icio.us | Technorati | digg | dzone | StumbleUpon | Software development

• fault-policies.xml, fault-policies.xsd
• fault-bindings.xml, fault-bindings.xsd

You have to enable the fault policy by adding the files to your sca component, or you can add a reference in the sca component to hem, for example when they are placed in the mds.

fault-bindings.xml
Examples of fault-bindings.xml files can be found in oracle’s documentations:

• Fault policy on composite level, the chapter is called fault-buildings.xml but they are talking about fault-bindings.xml don’t let this confuse you
• Fault policy on component level

fault-policies.xml
An detailed fault-policies.xml file can be found here.

Mediator
The Fault Management Framework is only applicable for mediators that processes their rules parallel, see documentation Fault Policies Mediator. If an error is matched in the fault policy an possible predefined fault action in the mediator will be ignored. Be aware of this when you are defining your fault policies and error handling.

Example
I have made a simple sca component to show the working of the framework. This sca component has two components {BPEL and Mediator} which are exposed as services to the outside world.

They will pass the message to a BPEL that throws a remote exception so we can test the working of the configured fault policies and bindings. In this case a simple available exception but in real it could be an custom defined Business exception to trigger the fault handling. We will see also the way to recover an BPEL instance and a Mediator instance.

The fault-policies.xml that’s configured in this project

This fault-bindings.xml that’s configured in this project

If you would like to define on component level the fault policies the fault-bindings.xml would look like this

Testing the composite
We deploy the composite and test if all the instances are cached by the defined fault policy.

Mediator Routing
First i invoked the service that’s connected to the mediator routing.

De defined fault policy works fine because the instance is been marked recoverable. By clicking on the link ‘Recoverable’ you get a popup where you can modify the payload (if needed) and select a recover action.

BPELRouting
Second i tested the service that’s connected to the BPELRouting component.

We have here also the same link to recover this instance.

That’s the end of a simple example to get started with the Fault Management Framework.

This example has been executed on
Fusion Middleware 11g (11.1.1.2.0)

Reference documentation

• Using Mediator Error Handling
• Using Fault Handling in a BPEL Process

Permalink | 19 comments | del.icio.us | Technorati | digg | dzone | StumbleUpon | Software development

I have made the following sca component that returns a greeting. The input is quite simple a name and a greeting type (‘Hello’ or ‘Bye’). The message is routed depending on the greeting type to a BPEL which response the greeting with a return greeting.

A quite simple component not useful but good for this example. I deployed this component by uploading the generated Jar file to the server. Then i tested it by manual sending to requests from the enterprise manager:

<ns1:process>
<ns1:input>Arnold</ns1:input>
<ns1:greeting>Hello</ns1:greeting>
</ns1:process>


I have also tested the Bye greeting by sending the following request from the enterprise manager:

<ns1:process>
<ns1:input>Arnold</ns1:input>
<ns1:greeting>Bye</ns1:greeting>
</ns1:process>


To automate the tests i created a test suite where i added the same test scenario’s an Hello Message and a Bye message. You see here the flow defined in JDeveloper for the ‘Bye’ case.

The blue circle in the exposed service shows us that an initial message is defined. On the wire between the exposed service and the Mediator you see a document with a green arrow. This shows that there are actions defined on this wire. It could be an emulation but in our case an response assert to validate the response message from the Mediator to the exposed service.

Initiation message

Response Assert

To activate the test we have to redeploy the application.

After deployment go to the enterprise manager and loging

Select the application that’s available in the soa-infra

Select the tab UnitTest and check the items you want to test. I this case all of them.

Start the test by giving it a name. You can also change some test parameters but in this case we leave them default.

Refresh to see the results of the unit test.

After time i expected to have two successful completed unittests. But the test case that tests the bye path fails.

You can see directly why this testcase failed. In the testcase we expect the value ‘Bye Theo’ but it found ‘Hello Theo’. To check out what went wrong you click on the link of the faulted testcase. In this case ID 1005.

You get an overview of all the instances that are connected to the testcase that’s executed.

We see that for instance 1005 (the faulted instance initiated by the ‘bye’ test case). Looking closer to the flow we see that the BPELHelloWorld has been executed instead of the BPELByeWorld. So we click on the mediator that has routed the message to the wrong BPEL.

We see now in detail the execution of the mediator. We see the evaluation of the different xpath expressions.

The first evaluation results False but why? I have tested the same application in two way’s:

1. I have executed only the bye testcase ( test fails result=’Hello Theo’)
2. I have manual tested the webservice ( test passes result = ‘Bye Theo’ )

Making your SOA composites including their unit test goes rapidly but in this case there is still some work to do with the testframework.

This test has been preformed with the following components:

1. Weblogic Server 11g rel 1. (10.3.2.0)
2. Fusion Middleware 11g Rel 1 (11.1.1.2.0)

UPDATE (09-12-2009)

On request of Tom i have added this screen print with the requested information.

I have also put the project online to download

Permalink | 2 comments | del.icio.us | Technorati | digg | dzone | StumbleUpon | Software development

The way we work is quite simple: every quarter we decide upon what questions we want to have answered. As you can imagine, SOA Suite 11g is quite prominent there. Each and every question has to be answered by delivering a workshop, white paper or presentation. These are collected and presented to an audience consisting of people from the participants. That way we not only build the knowledge, but spread it within our companies as well. And, all of us can use that material to train others, both inside and outside of the companies.

Usually the results are qualitatively really good. Some are extremely good. Such a one has just been posted on OTN, which is a nice feat anyway. You can find the article Jumpstart for OSB development here. We look forward to share a lot more results in the future.

Permalink | No comments | del.icio.us | Technorati | digg | dzone | StumbleUpon | Software development

You can download the new release from sourceforge. Also check out the documentation for all new features and how to upgrade to the latest release.

Please send feedback to: feedback at javalid dot org or post on this thread. Thanks!

For more information visit: http://www.javalid.org

Have fun with the new release!

Permalink | No comments | del.icio.us | Technorati | digg | dzone | StumbleUpon | Software development

* Introduction of a new type of validation annotations on class level, including several of these annotations (@NotNullAll, @NotNullOrNullAll etc)
* Added automatic resolving of messages (for user feedback) if needed
* Added new date validation annotations (e.g. @DateBefore, @DateAfter)
* Configuration minimized, annotations are registered by default now (for core and extensions)
* Added Spring AnnotationValidatorBeanPostProcessor (contributed by Scott Battaglia) which allows for validation of Spring Beans in an automated way.
* Advanced caching introduced (introspection is done only once when objects are encountered the first time), this improves speed.
* @JvGroup is not required anymore, only if you need more complex validation with multiple groups
* Core rewritten to allow more advanced validation features in the future

A lot more has changed than what is listed above, check the release notes for this.

You can download the new release from sourceforge. Also check out the documentation for all new features and on how to upgrade to the latest release.

For details please visit http://www.javalid.org

Permalink | No comments | del.icio.us | Technorati | digg | dzone | StumbleUpon | Software development

The Oracle BPEL Fault Policy Framework by default only handles the faults which are getting returned on an invoke-activity.
So we have our own custom fault and the knowledge we can only let this fault getting catched by the framework by use of an invoke.
So we need atleast for this testscenario 2 bpel processes. One mainprocess which calls a subprocess, and this subprocess will throw the custom business fault.
This fault will get propogated back to the mainprocess and in here we will be able to let the framework handle the fault.

BPEL Processes

Mainprocess

Subprocess

Just a simple invoke of the subprocess from the mainprocess. The subprocess with throw a fault, and this fault will be catched in the mainprocess.
The fault to be thrown

From the console start the mainprocess and wait till it comes back with a fault message

Click the activity to see the thrown fault

[2009/02/13 16:24:41]
"{http://nl.iteye/integration/faults/business}BusinessFault" has been thrown. 

<businessfault xmlns="http://nl.iteye/integration/faults/business">
<part name="payload">
    <businessfault xmlns="http://nl.iteye/integration/faults/business">
      <faultcode>999</faultcode>
      <faultmessage>Something went wrong!</faultmessage>
    </businessfault>
  </part>
</businessfault>

Ok nice!
So the custom fault we defined in the subprocess reaches the mainprocess.
Now we need to config the fault policy framework so it will get active on our custom business fault.
From the fault we pasted above we need the faultname (BusinessFault) and the namespace (http://nl.iteye/integration/faults/business).

Edit /bpel/domains/default/config/fault-policies/DefaultPolicy.xml and add the next fault :

   <faultname xmlns:flt="http://nl.iteye/integration/faults/business" name="flt:BusinessFault">
            <condition>
                    <action ref="ora-human-intervention"/>
            </condition>
   </faultname>

For testing we will just let this fault getting handled by human-intervention.
Now restart the components

opmnctl stopall
opmnctl startall

Now start the mainprocess again and wait till it fails.

It looks like the framework got active (activity yellow marked) on our custom business fault.

Go to the activities-tab

And click the activity which faulted.

Now we can edit some of the values and let the subprocess get re-invoked.

So, at this moment we’re able to throw our custom business faults and let them getting catched by the framework.
Since the fault is only getting catched on the invoke of a partnerlink, we aren’t able to let our custom business fault getting throwned to the process in which we maybe want do something with the data for which we actually throwed the custom business fault.
So maybe we want to stay in the subprocess and somehow get the custome business fault thrown inhere, let the framework catch it and update the values of this subprocess with new values an re-execute the subprocess.

The next solution will get this done.
The mainprocess won’t get changed but in the subprocess we will invoke a new process called AllBusinessFaults.

New subprocess 2

AllBusinessFaults

The AllBusinessFaults will throw the custom business fault we ‘request’ back on the invoke in this subprocess. Now it wil get catched by the framework and we will be able to change the values of the subprocess instead of the mainprocess.

By using the AllBusinessFaults bpel service like a sort of composite service, we can add the custom business faults in it and throw the one we would like to get thrown.
This will work if the collection of custom business faults isn’t that big.
I’m sure there will be better solutions for this, but for the scenario i wanted to describe in here it was good enough for me.

Question
In the examples i provided i don’t use the fault-part of a synchronous invoke to propegate the soap-fault back to the caller, i just throw the fault. The bpel engine itself throws the fault back to the first-level. Whats best practice on this one ?

Sources
BPEL Sources (First part of article with mainprocess/subprocess)
BPEL Sources (Second part of article with mainprocess/subprocess/allbusinessfaults)

Resources
Oracle BPEL 10.1.3.3 Fault Policy Management
my blog

Permalink | 5 comments | del.icio.us | Technorati | digg | dzone | StumbleUpon | Software development

I already noticed Mule-IDE, but this version wasnt really actively updated, till i noticed a new update on this blog today. Though you can get most work done by running some mule maven archetype and eclipse for the editting of the xml/java, i’m still curious if the ide gives some extra functionality.

Information
Download
Screencast

Will check it out to see if it’s usefull for my mule development.

I will mirror a few of my posts from my own blog which can be found overhere.

Permalink | No comments | del.icio.us | Technorati | digg | dzone | StumbleUpon | Software development