CODEWITHSUNDEEP
ibm-mobilefirst
Sami
Sami

Reputation: 564

Worklight Environment specific build for external server

We are using WL 6.2.0.1 Enterprise edition and we have four environments (DEV-QA-UAT and PROD) where each one of them has a different server path like Dev: (https://mobile-dev.company.ca) QA: (https://mobile-qa.company.ca) ....

When we do the build for our project targeting the external server, this URL is being added to the WL/Device binaries which makes each build unique for that environment.

Is there a way that we can modify the server path after doing the build so in this way we have one base build and we can move it across the environments without doing the build again.? like a WL property that can be added.

Upvotes: 0

Views: 106

Answers (2)

Andrew Ferrier
Andrew Ferrier

Reputation: 17752

It's only a partial answer, but you might find some useful tips in these slides from slide 25 onwards.

Upvotes: 0

Idan Adar
Idan Adar

Reputation: 44516

  • By default when performing a Run As > Run on Worklight Development Server this will inject to worklight.plist (for iOS) and wlclient.properties (all other environments) the protocol, host and port values of the development server.

  • When you want to build your application so that the injected server values will be of a remote server, you will perform a Run As > Build Settings and Deploy Target, where you will supply those values. When repeating this action with different values, the new values will be injected instead... The UI supports 1 remote server at a time to enter details for.

    So I'm thinking that you could put aside ready worklight.plist/wlclient.properties files to drop into the generated native project(s).

Upvotes: 1

Related Questions