An application developer wants to test the application inside Worklight Studio but with an external Liberty profile. Using the RUN As > Build Settings and command, the application developer configured the Worklight Server with the external Liberty profile.
Deploy Target -
Before the application developer can connect the application in Worklight Studio to an existing Liberty profile, which of the following must the application developer verify?
Correct Answer:
C
🗳️
To configure WebSphere Application Server Liberty profile for the Worklight Server administration manually, you must modify the server.xml file.
Add the following global JNDI entries in the server.xml file:
<jndiEntry jndiName="ibm.worklight.admin.jmx.host" value="localhost"/>
<jndiEntry jndiName="ibm.worklight.admin.jmx.port" value="9443"/>
<jndiEntry jndiName="ibm.worklight.admin.jmx.user" value="WorklightRESTUser"/>
<jndiEntry jndiName="ibm.worklight.admin.jmx.pwd" value="WorklighRESTUserPassword"/>
<jndiEntry jndiName="ibm.worklight.topology.platform" value="Liberty"/>
<jndiEntry jndiName="ibm.worklight.topology.clustermode" value="Standalone"/>
Where:
ibm.worklight.admin.jmx.port is the HTTPS port. You can find its value in the httpEndpoint element of the server.xml file.
References -
https://www.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/admin/t_configuring_liberty_profile_for_wladmin_manually.html
An application developer is testing an adapter that is retrieving data from a remote database. The developer can find no problems with the adapter and seems to be retrieving data from the database as designed. The quality assurance team insists that users are seeing each other's data.
Which adapter configuration setting does the application developer need to set to resolve this issue?
Correct Answer:
B
🗳️
In order to support stateful backend HTTP adapter procedures can be configured to work in a connectAs="endUser" mode. This mode means that a separate instance of HTTP session will be created for each client session.
References:
https://www.ibm.com/developerworks/community/blogs/worklight/entry/ configuring_http_adapters_for_stateless_stateful_backend_connectivity_and_user_identity_propagation?lang=en
An application developer is concerned about how many requests may hit the adapter being created. The developer wants to ensure that the adapter can handle enough requests, but yet not allow requests to overwhelm the system.
What can the application developer do to limit the number of requests that an adapter will handle?
Correct Answer:
D
🗳️
Tuning Back-end Connections -
maxConcurrentConnectionsPerNode The maximum number of concurrent requests that can be performed on the back-end application from the Worklight server node. The worklight server will create a thread pool with maxConcurrentConnectionsPerNode size for that purpose. This maxConcurrentConnectionsPerNode parameter is set in the adapter.xml in the connectivity entry.
References:
https://www.ibm.com/developerworks/community/blogs/worklight/entry/tuning_worklight_server?lang=en
An application developer is attempting to update specific portions of a hybrid application by utilizing the direct update feature.
Which components can the application developer update using the direct update feature without having to rebuild and deploy a new binary of the application?
Correct Answer:
A
🗳️
When you want to deliver a Worklight hybrid application that consists mainly of HTML5 with CSS and JavaScript, and you must change the hybrid part of the application to provide new features or to fix a defect, you do not have to ask the application users to update it on their devices. You can use the Worklight direct update mechanism to deploy new HTML with CSS and JavaScript for your application without changing the application version on the mobile device.
Incorrect:
Not D: Delivering a new version of native code
The main reason that you would want to deliver a new version of an application is probably because your application uses native code and you want to provide new features or deliver fixes that require changes in the native code. You might also need to provide a new native version of the application, even if your Worklight application is completely written by using web technologies, to accommodate new mobile operating systems supported only in later versions of IBM Worklight. You cannot use the direct update mechanism in either of these cases. You must build and deploy a new version of the application.
Reference: http://www.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.dev.doc/devenv/c_update_apps_wl_ac.html