Databases
StackOverflow2013
Postsdbo
POWorklight 6 upgrade going haywire
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWorklight 6 upgrade going haywire
    primarykey
    data
    text
    <p>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</p> <p>WebSphere Application Server Liberty Profile 8.5 DB2 V9.7 with fixpack 8 Worklight 6.0.0</p> <p>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:</p> <pre><code>[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' </code></pre> <p>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.</p> <p>Here is the server.xml configurations that were added with sensitive information redacted, all created with the ant build scripts.</p> <pre><code>&lt;!-- Declare the IBM Worklight Console application. --&gt; &lt;application id="worklight" name="worklight" location="worklight.war" type="war"&gt; &lt;classloader delegation="parentLast"&gt; &lt;commonLibrary&gt; &lt;fileset dir="${shared.resource.dir}/worklight/lib" includes="worklight-jee-library.jar"/&gt; &lt;/commonLibrary&gt; &lt;/classloader&gt; &lt;/application&gt; </code></pre> <p>And the JDBC DB connection configurations</p> <p> </p> <pre><code>&lt;!-- Declare the jar files for DB2 access through JDBC. --&gt; &lt;library id="worklight/DB2Lib"&gt; &lt;fileset dir="${shared.resource.dir}/worklight/db2" includes="*.jar"/&gt; &lt;/library&gt; &lt;!-- Declare the IBM Worklight Console database. --&gt; &lt;dataSource jndiName="worklight/jdbc/WorklightDS" transactional="false"&gt; &lt;jdbcDriver libraryRef="worklight/DB2Lib"/&gt; &lt;properties.db2.jcc databaseName="WRKLGHT" serverName="db2server.site.com" portNumber="50000" user="user" password="password"/&gt; &lt;/dataSource&gt; &lt;!-- Declare the IBM Worklight Console Reports database. --&gt; &lt;dataSource jndiName="worklight/jdbc/WorklightReportsDS" transactional="false"&gt; &lt;jdbcDriver libraryRef="worklight/DB2Lib"/&gt; &lt;properties.db2.jcc databaseName="WLREPORT" serverName="db2server.site.com" portNumber="50000" user="user" password="password"/&gt; &lt;/dataSource&gt; </code></pre> <p>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!</p> <p>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.") <a href="https://stackoverflow.com/questions/18530795/ibm-worklight-6-0-project-not-initialized-error">IBM Worklight 6.0 - "project not initialized" error</a></p> <p>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</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USZarathuztra
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWorklight 6 upgrade going haywire
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWorklight 6 upgrade going haywire
      1. USZarathuztra
      1. VTBountyStart
    3. VO
      singulars
      1. POWorklight 6 upgrade going haywire
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODo you have the JPA feature enabled in your Liberty profile? If yes, can you try w/out it?
      singulars
      1. POWorklight 6 upgrade going haywire
      1. USIdan Adar
    2. CODid you restart Liberty after upgrading?
      singulars
      1. POWorklight 6 upgrade going haywire
      1. USIdan Adar
    3. COAlso add logs...
      singulars
      1. POWorklight 6 upgrade going haywire
      1. USIdan Adar
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload