I try to configure MFP Server 7.1 with Attribute Store over Extreme Scale.
MFP 7.1/Liberty 8.5.5.6/WXS 8.6/JSDK 1.8
Without specific zmfp.attrStore.*` properties the MFP Server works fine. If i add the following properties, i have the following error and no runtime available in the console.
The properties:
<jndiEntry jndiName="worklight/mfp.session.independent" value='"true"'/>
<jndiEntry jndiName="worklight/mfp.attrStore.type" value='"eXtremeScale"'/>
<jndiEntry jndiName="worklight/mfp.attrStore.xs.endpoint" value='"192.168.1.41:2809"'/>
<jndiEntry jndiName="worklight/mfp.attrStore.xs.username" value='"xcadmin"'/>
<jndiEntry jndiName="worklight/mfp.attrStore.xs.password" value='"*******"'/>
<jndiEntry jndiName="worklight/mfp.attrStore.xs.gridname" value='"MFPGrid"'/>
<jndiEntry jndiName="worklight/mfp.attrStore.xs.mapname" value='"MFPGrid.NCI"'/>
The error:
Impossible to establish a REST connection to:
service:jmx:rest://localhost:7443/IBMJMXConnectorREST
If i remove the properties mfp.attrStore.* the MFP Server works fine again.
logs files, server.xml, jvm.options available here: https://ibm.app.box.com/attrstore
There is a defect in eXtreme scale that breaks totally the Liberty SSL configuration but there is a workaround as documented in https://www-01.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.dev.doc/devref/t_stateless_att_store_XS.html.
You have done the right workaround configuration but unfortunately something is missing in the workaround explanation : it works only with the IBM JDK and not at all with the Oracle JDK. So you must use the IBM JDK, preferably 1.7 (not sure 1.8 works well with eXtreme Scale).
Related
Have installed mobile first 7.1 ,Have pushed the adapters successfully.But while making adapter call,getting error com.microsoft.jdbc.sqlserver.SQLServerDriver not found In Work light or Project Work space.
After search have tried many option , have added the sqljdbc4.jar file in server/lib folder of project, also added in lib of JDK. Also added the path of sqljdbc4.jar as Class Path in System Variable.
PS- My environment is as follows, IBM MobileFirst 7.1, jdk1.8.0_181, windows 10
I have a problem when deploying my Worklight project on the server . It shows the following Error Message :
FWLSE3041E: No MBean found for Worklight project 'MyProject'. Possibly the Worklight runtime web application for Worklight project 'MyProject' is not running. If it is running, use JConsole to inspect the available MBeans.
and when I tried to preview my application it showed this message :
SRVE0777E: Exception thrown by application class 'com.worklight.core.auth.impl.AuthenticationFilter.verifyServletInitialized:420'
I had the same issue using Worklight 6.2 CLI, but recreating the project did not work.
One issue that I had was that worklight did not build a .war-file properly, so I copied the .war-file from a backup.
Edit: This happens regularly in our project now, and we have no idea why. We fix it by invoking any procedure, which makes it work until you restart the server. Worklight must be building something when invoking a procedure that it does not do when building.
I Solved The problem by creating a new Worklight Project and copied all my files , it works just fine :) I used Worklight 6.1 instead of 6.2
I solved this by fixing a recently created security test in
server/conf/authenticationConfig.xml
The problem was I mispelled the Realm name I previously defined.
I solved this problem by deleting the application from the worklight server and rebuild it.
Delete WorklightServerConfig folder in workspace and rebuild your application.
I was able to fix this in MobileFirst 7.0 (Fka Worklight) by opening the Servers view, Window -> Show View -> Servers. Then expanding the MobileFirst Development Server and right click on the project in question, chose delete.
Once you do that go back to the applications' directory in the "apps" directory and right click -> Run As -> Run On MobileFirst Development Server
This should rebuild and deploy the project on the server.
I solved the problem by using ibm jdk not open jdk. My solution is to make sure the env parameters are correct
export JAVA_HOME = $your_ibm_jdk
export PATH + $your_ibm_jdk/bin:$PATH
run java -version to make sure the setting work
I have some server with corrupted WL 6.1.0.0 install - the IIM does not show it in history, so I can not apply a fixpack in traditional way.
I need to update WL 6.1.0.0 to 6.1.0.1, in some non-traditional way.
Initially I thought that FixPack 001 major task is to update in /opt/IBM/Worklight/WorklightServer/ files worklight-ant-builder.jar, worklight-ant-deployer.jar, worklight-jee-library.jar (besides WAR application update, which I don't need - we don't use App Center Console, and WL applications are built with Studio 6.1.0.1 - no need to update)
I planned to copy the JAR files from the updated server, but comparing with another server which was updated (via IIM) to 6.1.0.1 I see that these files are just the same (however About menu tells 6.1.0.1 server version).
App Center Console is not used on the 6.1.0.0 server (actually I uninstalled it via WAS web admin console)
So, my question is: how to update WL 6.1.0.0 to 6.1.0.1 manually, possibly in non-supported way?
I'm not familiar with a manual way, however you should probably read and execute the recommended steps that are written in this user documentation topic: Upgrading from Worklight Server V6.1.0 to V6.1.0.1 in a production environment.
Highly suggested to also take a look at the parent topic.
We're using Worklight 6.1.0.0 / WebSphere 8.0.0.2 (ND/aix).
This seemed pretty close to my question too, but for version 6.0.
I've successfully done uninstall/install to our worklight console war package. However, there is some extra work on re-deploying adapters and such. I was looking for a way to just update the console. Among the ant tasks there is a target 'minimal-update', which sounds like what I'm looking for (is it?). However when all other pieces fell into place, I have an error for mapping the datasources:
ADMA0007E: A validation error occurred in task Mapping resource references to resources. The Java Naming and Directory Interface (JNDI) name is not specified for resource reference jdbc/WorklightDS in module Worklight with EJB name .
Contents of the 'minimal-update' task is pretty much the same as for 'install'.
I tried that as update from websphere admin console (but i should use the ant task - right?), that gave me a wizard screen to map jdbc/WorklightDS from package to jdbc/WorklightDS on server. This left me wondering how could I tell this using the ant task.
The ant target minimal-update of the sample configuration files documented at http://pic.dhe.ibm.com/infocenter/wrklight/v6r1m0/topic/com.ibm.worklight.deploy.doc/devref/c_ant_tasks_sample_config_files.html is meant to update a WAR file already deployed (and not uninstalled). In particular, on WAS, it assumes that the JNDI datasources are in place.
If you have uninstalled the WAR file, you should use the target install instead, provided that your databases were created for Worklight 6.1.
If they were created for a previous version of worklight you must upgrade their schema as well running the target 'databases' (and if it's a production installation, you might want to read all the steps in detail at http://pic.dhe.ibm.com/infocenter/wrklight/v6r1m0/topic/com.ibm.worklight.upgrade.doc/devenv/c_upgrade_to_srvr610_in_production_env.html )
I have just upgrade my Eclipse client running Juno to Worklight 5.0.6 developer edition (5.0.6.20130311-0918)
The projects upgrade fine, but when building them and deploying to the local worklight server I get a constant 'persistency data access problem' This occurs across all of my projects and has only been seen since the update.
Any idea on what is causing this problem and how to solve?
I would add a screen shot of the issue but I am not allowed
Based on your comment - in 5.0.6, the database schema has changed, so you have missing tables now. In the Developer Edition of Worklight, upgrade is not supported (this is handled when purchasing a license and using the IBM Installation Mananger for installing Worklight).
Do you mean "HSQL"? What is "Web SQL?"
In any case you will need to clean your database so that it will be re-created, this time with the missing tables.
If you use the default database provided by Worklight (HSQL), go to your Eclipse Workspace and delete the WorklightServerHome folder. Then, re-build your application.