I know that I can turn off the logging on server.xml for the developer edition.
But we are running WL enterprise 6.2.0.1, where can I find the server.xml to turn off the adapters logging.?
I do not think this has to do with your project specifically.
In the application server's server.xml (if you followed the deployment instructions for Worklight projects as provided in the Knowledge Center) you should have an entry specifying your Worklight project.
In this same file, you need to configure the logging level for com.worklight.
See here: Logging mechanisms
Maybe this will work:
<logging traceSpecification="com.worklight.*=info=disabled"/>
You need to play with it per the WebSphere documentation (as it is not related to Worklight per-se).
Related question (you need to do the opposite of the written in the answer): IBM Worklight 6.0 - How to enable/view WL.Logger.debug in adapters?
Related
We are using mobilefirst 6.3 in a production Websphere liberty profile.
Is there a way in mobilefirst to change the default log file, without using some custom java functions to log? we want to have the logs from our adapters separately from the server logs.
This is not related to IBM MobileFirst Platform, but to WebSphere Liberty which MFP is deployed to. It's an important distinction to make - all logging goes through the hosting application server, not through MFP.
To my knowledge and after reading the Liberty documentation - this is not possible in a straight-forward, official, capacity.
What you could perhaps do is:
Understand from the messages.log file which logs you'd like to filter. All log lines begin with a specific tag like FW123456
Write a script that will scan the messages.log file for occurrences of required tag
Copy the specific log line and save it in a different file
I tried the integration of these products based on this article and I hit the same problem already documented in the article.
"invocation of javascript function 'getRSSFeeds' has failed: Could not initialize class com.ibm.websphere.objectgrid.ObjectGridManagerFactory
FWLSE0101E: Caused by: [project ExtremeScaleInWorklight]java.lang.NoClassDefFoundError: Could not initialize class com.ibm.websphere.objectgrid.ObjectGridManagerFactory"
It seems that it is caused by a Java class collision of log4j.
My solution was to create a separate Liberty server and install the WXS client for Liberty. This solved the problem, but then I cannot use the WL Development Server anymore which turns the development less efficient.
What is the best way to develop this kind of solution?
I have seen this integration of products on several slides, but I can't find an official guide on how to achieve this. Is there any?
Have You tries to get the IBM WebSphere eXtremeSCale Liberty profile developer tools 8.6 also installed in your WL Development Server ?
SO WXS has two components Client ( libraries) and Serer side components. They can be housed in the same JVM -- for tests, in production this does not really make sense. Serer side hosts storing of objects and enforcing the 'grid management' policies that you may employ using the xml confg files.
perhaps you can use IBM WebSphere eXtremeSCale Liberty profile developer tools 8.6 also installed in your WL Development Server and include then in the classpath.
we are devloping an application using IBM worklight.
we have a requirement that the worklight server may be deployed in other location(that is ip will be changing).
can the app be configured to communicate to the other server through some settings page with out being reinstalled ?
Yes and No.
The official response is that this is not a supported configuration. IBM Worklight will not support this if done.
Technically, you have 2 options:
Use the Worklight Settings page (enabled by default in application-descriptor.xml; Android and iOS only)
In iOS it is external to the app, accessible via Preferences.app
In Android it is accessible via the Options Menu (which is not present starting API Level 13 or so)
This feature is not meant for end-user consumption; you must enter URLs manually. This is not encouraged for anything other than testing
This feature is not customizable
Create your own app-level settings page and follow this: Re-route/Divert some WL.Client Adapter Invocation traffic to WL Server through different URL (for PCI payment and security requirements)?
Again, this is not encouraged. There will not be support provided if this path is chosen
If you feel this is important to your customer, you can submit an RFE and explain your use case for future consideration by Worklight product designers.
I would like to debug the server part of my Worklight application (java). AFAIK Worklight 5.0.6 uses an embedded Jetty HTTP server. I wonder how it's possible to enable remote debugging for this process so I can set breakpoints, watch scope variables and so on?
Thank you in advance,
spyro
In Worklight 5.0.6, where the Jetty application server is used, Java debugging is not possible.
A possible solution, in case you are an IBM Worklight customer is to deploy Worklight on WAS Liberty, where you should be able to do this.
Maybe I dont know the right search terms to query with, but I cannot find instructions on how to configure glassfish 3.1 to allow me to use an external websphere mq7 server for my jms/mdb project. Can someone help me get this configured? I'll repay the community by writing a good howto document if there isn't one out there already.
Came across this in my own semi-related Google search... didn't answer my question (nor did anything else) so I posted some instructions here.
You can download WebSphere MQ 7 client from IBM.
After extraction or installation you will find a websphere mq rar adapter which you can deploy onto glassfish. You can use this mq rar adapter to make connections to WebSphere MQ 7.