Cloud Functions adapter
OpenWhisk is now called Cloud Functions.
IBM Cloud Functions is a Function-as-a-Service (FaaS) platform that allows the execution of code in a serverless and scalable environment. One of the usecases of the Cloud Functions platform is in the developing and running of serverless Mobile backend code. Learn more about Cloud Functions platform on IBM Cloud here.
Mobile Foundation adapters are used perform any necessary server-side logic, and to transfer and retrieve information from back-end systems to client applications and cloud services. Mobile Foundation now provides an adapter for Cloud Functions.
Cloud Functions adapter
IBM Mobile Foundation starting with iFix 220.127.116.11-MFPF-IF20170710-1834 provides an Cloud Functions adapter. This adapter is available to be downloaded and deployed from the Download Center in the Mobile Foundation Console.
After you download and deploy the adapter, you should configure it to connect to Cloud Functions.
Configure adapter to connect to Cloud Functions
To configure the adapter to connect to Cloud Functions, go to the Adapter Configuration page and provide the username and password from the authorization key of Cloud Functions. The username and password for Cloud Functions can be obtained by running the following CLI command:
./wsk property get --auth KEY
The above command returns the authorization key separated by a colon, to the left of the colon is the username and to the right of the colon is the password.
The username and password obtained as above should be provided in the Cloud Functions adapter configuration page, and the configuration should be saved. The client apps can now call the adapter API to invoke the Cloud Functions back-end code.
To modify the Cloud Functions adapter the adapter source code can be downloaded from this Github Repo.
Inclusive terminology note: The Mobile First Platform team is making changes to support the IBM® initiative to replace racially biased and other discriminatory language in our code and content with more inclusive language. While IBM values the use of inclusive language, terms that are outside of IBM's direct influence are sometimes required for the sake of maintaining user understanding. As other industry leaders join IBM in embracing the use of inclusive language, IBM will continue to update the documentation to reflect those changes.