![]() You may need to import new certificates to your MAF application's cacerts file if the HTTPS server contains certificates not present in your MAF application's cacerts file. Make sure that the cacerts file packaged in the MAF application that you publish for your end users to install contains the same CA root certificates as the HTTPS server that end users connect to when they use your MAF application. Obtain a newer version of the plugin if the plugin was created using an earlier release of Cordova.ģ.4 Migrating to a New cacerts File for SSL in MAF 2.1.3 MAF applications in 2.1.3 use Cordova 3.6.3 on Android and Cordova 3.7.0 on iOS. Version of the plugin is supported by MAF. To complete the migration and make sure that your migrated MAF application can use the plugins it used previously, verify that the: For more information, see "Using Plugins in MAF Applications" in Developing Mobile Applications with Oracle Mobile Application Framework (OEPE Edition). For example, enable additional core plugins and register external plugins in the MAF Application Editor, and specify the plugins used by features in the MAF Features Editor. This release of MAF registers plugins in the same editor, but due to changes to Apache Cordova the functionality is different.Įxamine the application once it has migrated and make any appropriate changes. MAF applications developed using earlier releases of MAF registered plugins in the MAF Application Editor. formatter=įor more information about the logging.properties file, see "How to Configure Logging Using the Properties File" in Developing Mobile Applications with Oracle Mobile Application Framework (OEPE Edition).ģ.3.1.1 What Happens When you Migrate an Application Replaces the following entries in the application's logging.properties file Replaces instances (if any) of the following import statement in the application's Java source files: For more information about the maf.properties file, see "How to Enable Debugging of Java Code and JavaScript" in Developing Mobile Applications with Oracle Mobile Application Framework (OEPE Edition). Renames the configuration file that specifies the startup parameters of the JVM from cvm.properties to maf.properties. When you open an application that you migrated from a pre-MAF 2.1.0 release in MAF 2.1.3 for the first time, OEPE makes the following changes: If you migrate a MAF application that compiled with an earlier version of Java, note that MAF 2.1.0 and later requires JDK 8 and compiles applications using the Java SE Embedded 8 compact2 profile. MAF applications that you create in MAF 2.1.0 and later use JDK 8. For more information about how to connect to the SQLite database, see the " Using the Local SQLite Database" section in Developing Mobile Applications with Oracle Mobile Application Framework (OEPE Edition). Review, and migrate as necessary, any code in your migrated MAF application that connects to the SQLite database. Read the subsequent sections in this chapter that describe how these changes impact the migration of your MAF application to MAF 2.1.0 or later.įinally, MAF 2.1.0 delivered an updated SQLite database and JDBC driver. For SSL, it delivers a cacerts file that contains new CA root certificates. ![]() It also changed the way that OEPE registered plugins in your MAF application. MAF 2.1.0 used newer versions of Apache Cordova and Java. Without this change, your end users may see errors when accessing services in the application.įor more information, see the " Specifying REST Service Connections" section in Developing Mobile Applications with Oracle Mobile Application Framework (OEPE Edition). Setting the preemptive property to true on these policies inserts a basic authentication header into the first request to a secured REST web service.Īlso, if your MAF application uses Web SSO authentication, you must configure the oracle/http_cookie_client_policy security policy for all REST/HTTP web service connections used by the application. If you migrate an application to MAF 2.1.3 that was created in MAF 2.1.0 or previously migrated to MAF 2.1.2, MAF will have made already made the changes required by migration to JDK 8, management of Cordova plugins, and a new cacerts file.įor MAF applications that you migrate to MAF 2.1.3 (irrespective of the release from which you migrate), we recommend that you set the preemptive property to true on the following security policies: Use the information in this chapter if you migrate an application created in a pre-MAF 2.1.0 release to MAF 2.1.3. The MAF 2.1.0 release introduced significant changes described in this chapter. 3.1 Migrating an Application to MAF 2.1.3
0 Comments
Leave a Reply. |