I am running in WLPlatform version 7.1.0, for some reason after upgrading from 7.0 to 7.1 I am noticing strange problem where build setting and deploy target for remote WL server is not working correctly.
That is change in wlclient.properties file still reflect older values for server how ever port and server context is updated correctly.
wlServerProtocol = http
wlServerHost = {still shows my local server name}
wlServerPort = 9080
wlServerContext = /xxx/
Any idea what I am missing here.
This is a known defect in MobileFirst Platform Foundation 7.1, schedule to be fixed soon: PI48848 INCORRECT SERVER HOST IS WRITTEN IN WORKLIGHT.PLIST/WLCLIENT.PROPERTIES, IF SERVERHOST IS DIFFERENT THAN LOCALHOST.
You can open a PMR (support ticket) and request the fix once it is ready.
Related
I have few adapters deployed in remote uat server.
I want to access them n develop mobile web app in my local worklight server.
Im using IBM Mobilefirst 7.1.0
I tried setting host and contxt path of uat server in mobilewebapp build settings and run the app in my local server. But query call is throwing 404 error.
Can anyone help me in accessing remote adapters in local server.
It would've been easier to help you had you provided information such as where are you setting that connection info and what are you setting... since you're getting 404, this would typically mean that you have incorrectly inputted the connection info.
In MobileFirst Studio, right-click on the application folder and select Run As -> Remote Target and Build Settings. There you need to input the server address:
Host: https://your-server-ip-address:port-number
Context root: /myproj (typically the project name, unless you've specified otherwise in the server.xml of the remote application server).
Previously I had a different version of WAS (8.5.5.3) this morning I installed WAS (8.5.5.6) on my laptop. Also I reinstalled MFP Server to point to new WAS
I started using 'Server configuration tool' then but somehow the tool remembers the old path '/opt/ibm/Websphere/Liberty' and all other old settings
Even I tried removing 'runtime' and 'application' and recreated but still 'tool' picks up the same old details by default
Is there any way to clear the old details (or cache) of 'Server configuration tool' ?
Thanks
Sathish kumar
In the current versions of MFP, there is no link between the application server you selected in Install Manager to deploy Application Center, and the application server that is presented first by the Server Configuration Tool when you deploy an MFP Server. The Server Configuration Tool looks at the list of application servers installed with Install Manager and presents them in the order in which it did find them.
I have a server which has been upgraded from IBM Worklight 6.0 to IBM Mobilefirst 6.3
The server is currently running older versions of my mobile application, which do not have AppAuthenticity enabled.
When I uploaded the newer version of Application, AppAuthenticity option became enabled ONLY for one (windows) environment, while others stayed disabled.
After a restart, Windows Environment version became like others, while iPAD environment started giving option to change the AppAuthenticity.
I listed the application through WLADM CLI, and it gave me below error:
XML validation error, reading from
https://URL/wladmin/management-apis/1.0/runtimes/worklight/applications/MYAPPS?locale=en_US:
cvc-complex-type.4: Attribute 'downloadLink' must appear on element
'applicationEnvironmentDataAccess'.
Please note, the application if ran alone on other server is working fine with same Application-descriptor and WAR file, only when Old and new versions are uploaded on same server, this problem comes.
Are you saying your server has a single .war file with 2 apps on it, one from 6.0 and one from 6.3?
There are very different Application Authenticity Protection implementations in 6.0 and 6.3. These cannot co-exist in the same single .war file.
You need to deploy to your application server 2 .war files - one for handling the 6.0 app and another for handling the 6.3 app.
Relevant user documentation can be read here: http://www-01.ibm.com/support/knowledgecenter/SSHS8R_6.3.0/com.ibm.worklight.upgrade.doc/devenv/c_upgrade_to_srvr_in_production_env.html
As Idan said, the 6.0 and 6.3 app can not be handled together, since I only wanted to enable the App Authenticity in the newer version, what I did as a workaround was to connect via WLADM tool and disable the App Authenticity for Older Versions via command line.
Below are the commands one needs to use:
\Worklight\shortcuts>wladm --url=https://server.url/wladmin --user=admin --passwordfile=password.properties
to verify the application's current Authenticity :
app version %CONTEXT% %APP_NAME% %Environment_Name% %versionCode% get authenticitycheckrule
To Disable
app version %CONTEXT% %APP_NAME% %Environment_Name% %versionCode% set authenticitycheckrule DISABLED
I am developing a hybrid app in Worklight 6.2. I have a WorkLight Server installed Red Hat Linux 6 base as remote server.
I have give the servers ip address, port number and context root as"/worklight" in the "build settings and deploy target".
Then i added my adapter file and wlapp file into the remote servers "app" folder. I haven't made any changes in the server.xml file.
Now when i call the procedure from my app i am getting "[IPADDRESS:PORT/worklight/apps/services/api/MyApp/ipad/query] failure. state: 404, response: The server was unable to process the request from the application. Please try again later."
What am i missing and What changes do i have to make to make the request to work.?
The steps you are describing are not clear.
Make sure you are following the steps as provided in the IBM Worklight Knowledge Center.
First make sure the Worklight Server deployment to the application server was done correctly
You can verify this then by loading the Worklight Console (there will be no deployed projects)
Then follow the Worklight project (.war, .wlapp, .adapter) deployment to the Worklight Server instructions
You can verify this then by loading the Worklight Console (there will be 1 deployed application)
I am trying to deploy multiple adapters to a Worklight Server in a production environment. When refreshing the console, the deployed adapters are missing.
What is the problem?
Can you please take a look at your Worklight Server log to see if any errors are displayed. I have seen in the past similar behavior when adapter procedures relied on security-tests, but the security tests were not defined properly in the authenticationConfig.xml file on the server side. In the server log I saw the following error:
"Failed to deploy adapter. This may be due to a JavaScript error in your adapter implementation"
If this is the case please update your authenticationConfig.xml on your production server to match the properties you have defined in your development environment. Also do these adapters deploy successfully in your development environment when running locally?
Make sure that the Studio the adapter was created in and the Server the adapter is deployed to are of the exact same build number
This is reason #1 for adapters to get deployed and then immediately get removed.