Worklight 6 upgrade going haywire

Question

We're currently in the process of upgrading our Studio and Server instances from Worklight 5.0.6 to Worklight 6. I'm setting up the server side on a freshly installed RHEL 6 image using the following middleware. Server installation instructions (outside what was already done in the image) were followed to a T from the official IBM docs for WL6

WebSphere Application Server Liberty Profile 8.5 DB2 V9.7 with fixpack 8 Worklight 6.0.0

Studio upgrade went smooth, so no issues there. The bug is happening server side when I'm trying to actually access the application console, and even the installed appcenter war. In both cases the JPA entity resource is coming up with nothing and so I get the following error when trying to access my console:

[WARNING ] CWNEN0070W: The javax.annotation.Resource annotation class will not be   
recognized because it was loaded from the null location rather than from a product 
class  loader.
[err] 22  WorklightPU  WARN   [Default Executor-thread-1] openjpa.Runtime - An error     
occurred while registering a ClassTransformer with PersistenceUnitInfo: name 'WorklightPU'

The installed image was create on a VM with WL6 and WLP pre-installed by the company. I installed DB2 manually, and created all the necessary users, groups, and configurations to ensure connectivity. I then ran the DB2 configuration ant task provided by WL6 to ensure the tables for WorkLight and the Appcenter are created correctly, build successful. I then also ran the install task as well. Build successful.

Here is the server.xml configurations that were added with sensitive information redacted, all created with the ant build scripts.

<!-- Declare the IBM Worklight Console application. -->
<application id="worklight" name="worklight" location="worklight.war" type="war">
    <classloader delegation="parentLast">
        <commonLibrary>
            <fileset dir="${shared.resource.dir}/worklight/lib" includes="worklight-jee-library.jar"/>
        </commonLibrary>
    </classloader>
</application>

And the JDBC DB connection configurations

<!-- Declare the jar files for DB2 access through JDBC. -->
<library id="worklight/DB2Lib">
    <fileset dir="${shared.resource.dir}/worklight/db2" includes="*.jar"/>
</library>

<!-- Declare the IBM Worklight Console database. -->
<dataSource jndiName="worklight/jdbc/WorklightDS" transactional="false">
    <jdbcDriver libraryRef="worklight/DB2Lib"/>
    <properties.db2.jcc databaseName="WRKLGHT" serverName="db2server.site.com" portNumber="50000" user="user" password="password"/>
</dataSource>

<!-- Declare the IBM Worklight Console Reports database. -->
<dataSource jndiName="worklight/jdbc/WorklightReportsDS" transactional="false">
    <jdbcDriver libraryRef="worklight/DB2Lib"/>
    <properties.db2.jcc databaseName="WLREPORT" serverName="db2server.site.com" portNumber="50000" user="user" password="password"/>
</dataSource>

If needed I can also edit this question to include necessary information from the worklight.properties file associated with my customized war. I greatly appreciate any help!

I was hoping this link would help me, but it's for a totally different issue (and older version of worklight, as the fix says "The fix for this APAR is currently targeted for inclusion in fixpack 5.0.6.0.") IBM Worklight 6.0 - "project not initialized" error

EDIT: Tracked this down to more than likely a DB issue. We're getting messages such as: Adding a gadget activity report failed And other errors related to the JDBC connections not being valid...even though they are the ones seutp by the WL ANT scripts

Answer 1

Managed to fix this ourselves by removing everything from the image and installing ourselves.