Book Image

Oracle JET for Developers

By : Raja Malleswara Rao Malleswara Rao Pattamsetti
Book Image

Oracle JET for Developers

By: Raja Malleswara Rao Malleswara Rao Pattamsetti

Overview of this book

This book will give you a complete practical understanding of the Oracle JavaScript Extension Toolkit (JET) and how you can use it to develop efficient client-side applications with ease. It will tell you how to get your own customized Oracle JET set up. You'll start with individual libraries, such as jQuery, Cordova, and Require.js. You'll also get to work with the JavaScript libraries created by Oracle, especially for cloud developers. You'll use these tools to create a working backend application with these libraries. Using the latest Oracle Alta UI, you'll develop a state-of-the-art backend for your cloud applications. You'll learn how to develop and integrate the different cloud services required for your application and use other third-party libraries to get more features from your cloud applications. Toward the end of the book, you'll learn how to manage and secure your cloud applications, and test them to ensure seamless deployment.
Table of Contents (17 chapters)
Title Page
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Packaging and publishing a mobile application


We can package and publish the Oracle JET-based hybrid mobile applications to Google Play or Apple App stores, using framework support and third-party tools.

Packaging a mobile application

An Oracle JET Hybrid mobile application can be packaged with the help of Grunt build release commands, as described in the following steps:

  1. The Grunt release command can be issued with the desired platform as follows:
      grunt build:release --platform={ios|android}
  1. Code sign the application based on the platform in the buildConfig.json component.
  1. We can pass the code sign details and rebuild the application using the following command:
      grunt build:release --platform={ios|android} 
            --buildConfig=path/buildConfig.json...