ApiManagerDS uses JNDI name which does not comply with WF standard/convention for JDNI namings ( "jdbc/ApiManagerDS").

Such JNDI is only possible because our DS is hot deployed as apiman-ds.xml.
It is likely that in real environment user will want to leverage WF's management to define the DS. In that case the jndi has to start with either "java:/" or "java:jboss:/" prefix.

Ths we should use something like "java:/jdbc/ApiManagerDS" or in case of WF it is possible to use System properties inside persistence.xml and allow dynamic configuration.