WSO2 Tutorial - BPS

In this tutorial of the WSO2 path I'm working with the BPS version 3.0.0 and WSO2 Developer Studio version 3.0.0.

The objective of this tutorial is to show how to implement a simple process and deploy it in the BPS.

I'll use here a standard default installation of the server (no external DB for process management and so on)

TEIID 8.1 tutorial - Part 15 - Support Update

In this new tutorial of the TEIID series I'll show how to update the original table from the VDB view.

Usually when operating with TEIID designer the "orange" view model proposes just to read/select from the source table.

To be able to Update/Insert/Delete from the original table we must enable the "Support Update" checkbox as shown in the figure below.



In the video I'll show the whole procedure.

WSO2 Tutorials

I'll start a new tutorial line dedicated to the WSO2 product suite.

Here is what I'm preparing:
1) Business Process Server - example process and deploy
2) API Manager - publishing of an API and usage from the store
3) API Manager - TEIID SOAP service publishing

More will come.

GeoServer 2.2.5 + JBoss 7.1.1 and Oracle

As I posted some time ago, I'm using GeoServer version 2.2.5 on a JBoss 7.1.1 installation; now I'm working with an Oracle Database so I've added the Oracle extension. And added it in the "$WAR/WEB-INF/lib/" the jar that is downloaded as a separate package (mind to download the same version for the GeoServer you are using).

I had this problem accessing oracle tables:

09:23:34,911 ERROR [org.geoserver.ows] (http--10.20.1.50-8280-17) : java.lang.NoClassDefFoundError: oracle/jdbc/OracleConnection
at org.geotools.data.oracle.OracleDialect.unwrapConnection(OracleDialect.java:544) [gt-jdbc-oracle-8.7.jar:]
at org.geotools.data.oracle.OracleDialect.setGeometryValue(OracleDialect.java:517) [gt-jdbc-oracle-8.7.jar:]
at org.geotools.jdbc.JDBCDataStore.setPreparedFilterValues(JDBCDataStore.java:3168) [gt-jdbc-8.7.jar:]
at org.geotools.jdbc.JDBCDataStore.setPreparedFilterValues(JDBCDataStore.java:3147) [gt-jdbc-8.7.jar:]
at org.geotools.jdbc.JDBCDataStore.selectAggregateSQLPS(JDBCDataStore.java:3372) [gt-jdbc-8.7.jar:]
at org.geotools.jdbc.JDBCDataStore.getAggregateValue(JDBCDataStore.java:1292) [gt-jdbc-8.7.jar:]
at org.geotools.jdbc.JDBCDataStore.getCount(JDBCDataStore.java:1250) [gt-jdbc-8.7.jar:]
at org.geotools.jdbc.JDBCFeatureSource.getCountInternal(JDBCFeatureSource.java:432) [gt-jdbc-8.7.jar:]
at org.geotools.data.store.ContentFeatureSource.getCount(ContentFeatureSource.java:451) [gt-data-8.7.jar:]
at org.geotools.jdbc.JDBCFeatureStore.getCountInternal(JDBCFeatureStore.java:183) [gt-jdbc-8.7.jar:]
at org.geotools.data.store.ContentFeatureSource.getCount(ContentFeatureSource.java:451) [gt-data-8.7.jar:]
at org.geotools.data.store.ContentFeatureCollection.size(ContentFeatureCollection.java:356) [gt-data-8.7.jar:]
at org.geoserver.wms.GetFeatureInfo.execute(GetFeatureInfo.java:297) [wms-2.2.5.jar:2.2.5]
at org.geoserver.wms.GetFeatureInfo.execute(GetFeatureInfo.java:168) [wms-2.2.5.jar:2.2.5]
at org.geoserver.wms.GetFeatureInfo.run(GetFeatureInfo.java:117) [wms-2.2.5.jar:2.2.5]
at org.geoserver.wms.DefaultWebMapService.getFeatureInfo(DefaultWebMapService.java:374) [wms-2.2.5.jar:2.2.5]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_25]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_25]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_25]
at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_25]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:318) [spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]

The problem is due to a classloading mechanism of the AS.

TEIID 8.1 tutorial - Part 10 - TEIID SOAP service + WSO2 + SoapUI

In this tutorial I'll be publishing the book SOAP web service using the API manager from WSO2.

To demonstrate that it works I'll be using as usual SoapUI

The API Manager is composed of two components the Publisher and the Store.

Obviously I need to start from the publisher and create the API: you ger the WSDL endpoint from the JBoss consolle in the webservices TAB.

The API start as CREATED so I need to set into PUBLISHED state.

The API is ready to be used, so is turn of the Store where is quite easy to subscribe to the API.
The main idea is that I'm a developer that uses some of the API published on the Store and I can have different applications that make use of the API and can register to use them with different "Tier" levels that means how much requests I can issue in a given time.

TEIID and nodejs with node-postgres

Ok after a bit of tribulation I managed to access TEIID from nodejs.

It is really simple as the Ramesh's blog stated, but since I had a few problems making it work I try to give a bit of explanation more.

I have TEIID 8.2 on Jboss 7.1.1 and use node v0.8.16 and pg 0.13.1

The code to make connection is:

teiid: Access Teiid from node.js

teiid: Access Teiid from node.js: Are you writing a "node.js" application and would like to access Teiid VDB from it? If "yes", this is currently po...


The post from Ramesh is very interesting.
I'm working on that using TEIID 8.2 on JBoss 7.1.1 with the 0.13.1 version of node-postgres but having some difficulties.
Will keep you updated.

Testing a datasource on JBoss 7.1.1 in domain mode

I'm trying to test a deployed datasource in JBoss 7.1.1 in a domain configuration.

No info found around help in doing this job, also the web console is not working as expected (I also use TEIID 8.2 and probably the new web console mangled up a few things) and surely having a domain installation does not help things up.


All the things found around suggest to use this command

/subsystem=datasources/data-source=reportsDS:test-connection-in-pool

Being in a domain mode I do not have /subsystem so I tryed to get the subsystem from somewhere.

Getting it from profile ...

/profile=ha/subsystem=datasources/data-source=reportsDS:test-connection-in-pool

But the result are below and are not the expected

{
"outcome" => "failed",
"failure-description" => "JBAS010850: No handler for operation test-connection-in-pool at address [
(\"profile\" => \"ha\"),
(\"subsystem\" => \"datasources\"),
(\"data-source\" => \"reportsDS\")
]",
"rolled-back" => true
}

So I tryed with the following (that is logical since the previous was issued on a definition (profile) and not something truly running) against the host/server

/host=master/server=teiid1/subsystem=datasources/data-source=reportsDS:test-connection-in-pool

This time the result is successful

{
"outcome" => "success",
"result" => [true]
}

If needed by anyone.