Asymmetric deployment mfp
- 1. IBM MobileFirst Asymmetric deployment December 22, 2016 Jorge Iglesias IBM Cloud and Mobile Technical Specialist
- 2. © 2016 IBM Corporation 2 Asymmetric deployment with runtimes and administration services in different server or cluster Cell Node 1 Node 2 Cluster 1 Cluster 2 Cluster (n) MobileFirst Operation Console MobileFirst Operation Console MobileFirst Server Administration Service MobileFirst Server Administration Service MobileFirst Server Live Update Service MobileFirst Server Live Update Service MobileFirst Push Service MobileFirst Push Service MobileFirst Runtime (n) MobileFirst Runtime (n) Live Uodate Admin Push Runtime (n) + Characteristics of this topology: • One or several administration components can be deployed in one or several servers or clusters of the cell. Each instance of MobileFirst Operations Console communicates with one administration service and one live update service. • One or several runtimes can be deployed in other servers or clusters of the cell. • One MobileFirst Operations Console manages several runtimes deployed in the other servers or clusters of the cell. • One runtime is managed by only one MobileFirst Operations Console. • Each administration service uses its own administration database schema. • Each live update service uses its own live update database schema. • Each runtime uses its own runtime database schema.
- 3. © 2016 IBM Corporation 3 Asymmetric deployment with runtimes and administration services in different server or cluster + This topology is advantageous, because it enables the runtimes to be isolated from the administration components and from other runtimes. + It can be used to provide performance isolation, to isolate critical applications, and to enforce Service Level Agreement (SLA) Node 1 Node 2 Cluster 1 Cluster 2 Cluster (n) MobileFirst Operation Console MobileFirst Operation Console MobileFirst Server Administration Service MobileFirst Server Administration Service MobileFirst Server Live Update Service MobileFirst Server Live Update Service MobileFirst Push Service MobileFirst Push Service MobileFirst Runtime (n) MobileFirst Runtime (n) Live Uodate Admin Push Runtime (n)
- 4. © 2016 IBM Corporation 4 Asymmetric deployment with runtimes and administration services in different server or cluster + Topology constraints • The deployment manager must be running while MobileFirst Server is running. • The deployment manager is used for the JMX communication between the runtime and the administration service. • The administration service and the live update service must be installed on the same application server. • The runtime can be installed on different servers than the administration service, but it must be on the same cell. • Start Order - The runtime application must start after the administration service application. You can set the order at Startup behavior section. For example, set the Startup Order to 1 for the administration service and 2 to the runtime.
- 5. © 2016 IBM Corporation 5 Asymmetric deployment with runtimes and administration services in different server or cluster + Application server settings • The administrative security and the application security must be enabled. Click Security > Global Security
- 6. © 2016 IBM Corporation 6 Asymmetric deployment with runtimes and administration services in different server or cluster + Server class loader policy • The server class loader policy must support parent last delegation. The MobileFirst Server WAR files must be installed with parent last class loader mode. • Click Servers > Server Types > WebSphere application servers, and click on the server that is used for IBM MobileFirst Platform Foundation.
- 7. MobileFirst Server administration service configuration details
- 8. © 2016 IBM Corporation 8 Asymmetric deployment with runtimes and administration services in different server or cluster + MobileFirst Server Administration service configuration details • Data source - data source for the administration service and map it to: • For more information about the databases, see Setting up databases. Property Target Resource JNDI Name jdbc/mfpAdminDS MFP administration service MobileFirst Server Administration Service
- 9. © 2016 IBM Corporation 9 Asymmetric deployment with runtimes and administration services in different server or cluster + MobileFirst Server Administration service configuration details • The administration service WAR file is in mfp_install_dir/MobileFirstServer/mfp-admin-service.war • You can define the context root as you want. However, usuallyit is /mfpadmin • Start Order - The runtime application must start after the administration service application. You can set the order at Startup behavior section. For example, set the Startup Order to 1 for the administration service and 2 to the runtime. MobileFirst Server Administration Service
- 10. © 2016 IBM Corporation 10 Asymmetric deployment with runtimes and administration services in different server or cluster + Class loader + For all MobileFirst Server applications, the class loader must have the parent last delegation. To set the class loader delegation to parent last after an application is installed, follow these steps: • Click the Manage Applications link, or click Applications > Application Types > WebSphere entreprise applications. • Click the MobileFirst Server application. By default the name of the application is the name of the WAR file. In the Detail Properties section, click the Class loading and update detection link. • In the Class loader order pane, select the Classes loaded with local class loader first (parent last) option. Click OK. • In the Modules section, click the Manage Modules link. Click the module. • For the Class loader order field, select the Classes loaded with local class loader first (parent last) option. • Click OK twice to confirm the selection and back to the Configuration panel of the application. Click Save to persist the changes. MobileFirst Server Administration Service
- 11. © 2016 IBM Corporation 11 Asymmetric deployment with runtimes and administration services in different server or cluster + Mandatory JNDI properties - JMX communication with the runtime • For more information about the JNDI properties, see List of JNDI properties for MobileFirst Server administration service. Property Value mfp.admin.jmx.dmgr.host Deployment manager host name. mfp.admin.jmx.dmgr.port the SOAP port on the deployment manager mfp.topology.platform set the value as WAS mfp.topology.clustermode set the value as Cluster mfp.admin.jmx.connector set the value as SOAP MobileFirst Server Administration Service
- 12. © 2016 IBM Corporation 12 Asymmetric deployment with runtimes and administration services in different server or cluster + Mandatory JNDI properties - If the push service is installed Property Value mfp.admin.push.url The url of the push service. If not specified, the push service is considered disabled mfp.admin.authorization.server.url The url of the OAuth authorization server used by the push service. Recommend to set this property if you install multiple runtimes. If not set properly, the admin service is not able to contact the push service and the administration of push services in the Operations Console will not work mfp.push.authorization.client.id The id of the confidential client that handles push service OAuth authorization. mfp.push.authorization.client.secret The secret of the confidential client that handles push service OAuth authorization. mfp.admin.authorization.client.id The id of the confidential client that handles admin service OAuth authorization. mfp.admin.authorization.client.secret The secret of the confidential client that handles admin service OAuth authorization MobileFirst Server Administration Service Note: the authorizations clients users may not be defined in LDAP or ext. Repositories.
- 13. © 2016 IBM Corporation 13 Asymmetric deployment with runtimes and administration services in different server or cluster + Mandatory JNDI properties - for the communication with the configuration service Property Value mfp.config.service.user The username used to access the config service mfp.config.service.password The password used to access the config service MobileFirst Server Administration Service
- 14. © 2016 IBM Corporation 14 Asymmetric deployment with runtimes and administration services in different server or cluster + Security Role to user/group mapping • For more information about the map roles, see the configurtion user authentification. Rol Description mfpadmin Admin role for MobileFirst Server mfpdeployer Deployer role for MobileFirst Server mfpmonitor Monitor role for MobileFirst Server mfpoperator Operator role for MobileFirst Server MobileFirst Server Administration Service
- 15. MobileFirst Server live update service configuration details
- 16. © 2016 IBM Corporation 16 Asymmetric deployment with runtimes and administration services in different server or cluster + MobileFirst Server Live Update service configuration details • Data source - data source for the administration service and map it to: • For more information about the databases, see Setting up databases. Property Target Resource JNDI Name jdbc/ConfigDS MFP live update service MobileFirst Server Live Update Service
- 17. © 2016 IBM Corporation 17 Asymmetric deployment with runtimes and administration services in different server or cluster + MobileFirst Server Live Update service configuration details • The live update service WAR file is in mfp_install_dir/MobileFirstServer/mfp-live-update.war. • The context root of the live update service must define in this way: /<adminContextRoot>config. - For example, if the context root of the administration service is /mfpadmin, then the context root of the live update service must be /mfpadminconfig. MobileFirst Server Live Update Service
- 18. © 2016 IBM Corporation 18 Asymmetric deployment with runtimes and administration services in different server or cluster + Class loader + For all MobileFirst Server applications, the class loader must have the parent last delegation. To set the class loader delegation to parent last after an application is installed, follow these steps: • Click the Manage Applications link, or click Applications > Application Types > WebSphere entreprise applications. • Click the MobileFirst Server application. By default the name of the application is the name of the WAR file. In the Detail Properties section, click the Class loading and update detection link. • In the Class loader order pane, select the Classes loaded with local class loader first (parent last) option. Click OK. • In the Modules section, click the Manage Modules link. Click the module. • For the Class loader order field, select the Classes loaded with local class loader first (parent last) option. • Click OK twice to confirm the selection and back to the Configuration panel of the application. Click Save to persist the changes. MobileFirst Server Live Update Service
- 19. © 2016 IBM Corporation 19 Asymmetric deployment with runtimes and administration services in different server or cluster + Security Role to user/group mapping Rol Description configadmin At least one user must be mapped to this role. The user and its password must be provided to the following JNDI properties of the administration service: mfp.config.service.user mfp.config.service.password MobileFirst Server Live Update Service
- 20. MobileFirst Operations Console configuration details
- 21. © 2016 IBM Corporation 21 Asymmetric deployment with runtimes and administration services in different server or cluster + MobileFirst Operations Console configuration details • The console is packaged as a WAR application for you to deployto the application server. You need to make some specific configurations for this application • The console WAR file is in mfp_install_dir/MobileFirstServer/mfp-admin-ui.war • You can define the context root as you want. However, usually it is /mfpconsole MobileFirst Operations Console
- 22. © 2016 IBM Corporation 22 Asymmetric deployment with runtimes and administration services in different server or cluster + Class loader + For all MobileFirst Server applications, the class loader must have the parent last delegation. To set the class loader delegation to parent last after an application is installed, follow these steps: • Click the Manage Applications link, or click Applications > Application Types > WebSphere entreprise applications. • Click the MobileFirst Server application. By default the name of the application is the name of the WAR file. In the Detail Properties section, click the Class loading and update detection link. • In the Class loader order pane, select the Classes loaded with local class loader first (parent last) option. Click OK. • In the Modules section, click the Manage Modules link. Click the module. • For the Class loader order field, select the Classes loaded with local class loader first (parent last) option. • Click OK twice to confirm the selection and back to the Configuration panel of the application. Click Save to persist the changes. MobileFirst Operations Console
- 23. © 2016 IBM Corporation 23 Asymmetric deployment with runtimes and administration services in different server or cluster + Mandatory JNDI properties • For more information about the JNDI properties, see JNDI properties for MobileFirst Operations Console. Property Value mfp.admin.endpoint The typical value for this property is *://*:*/<adminContextRoot> MobileFirst Operations Console
- 24. © 2016 IBM Corporation 24 Asymmetric deployment with runtimes and administration services in different server or cluster + Security Role to user/group mapping • Any user that is mapped to a security role of the console must also be mapped to the same security role of the administration service • For more information about the map roles, see the configurtion user authentification. Rol Description mfpadmin Admin role for MobileFirst Server mfpdeployer Deployer role for MobileFirst Server mfpmonitor Monitor role for MobileFirst Server mfpoperator Operator role for MobileFirst Server MobileFirst Operations Console
- 25. MobileFirst Server Push service configuration details
- 26. © 2016 IBM Corporation 26 Asymmetric deployment with runtimes and administration services in different server or cluster + MobileFirst Server Push service configuration details • Data source - data source for the administration service and map it to: • For more information about the databases, see Setting up databases. Property Target Resource JNDI Name jdbc/imfPushDS MFP Push MobileFirst Server Push Service
- 27. © 2016 IBM Corporation 27 Asymmetric deployment with runtimes and administration services in different server or cluster + MobileFirst Server Push service configuration details • The push service is packaged as a WAR application for you to deploy to the application server. You need to make some specific configurations for this application. • The push service WAR file is in mfp_install_dir/PushService/mfp-push-service.war. • You must define the context root as /imfpush. Otherwise, the client devices cannot connect to it as the context root is hardcoded in the SDK. MobileFirst Server Push Service
- 28. © 2016 IBM Corporation 28 Asymmetric deployment with runtimes and administration services in different server or cluster + Class loader + For all MobileFirst Server applications, the class loader must have the parent last delegation. To set the class loader delegation to parent last after an application is installed, follow these steps: • Click the Manage Applications link, or click Applications > Application Types > WebSphere entreprise applications. • Click the MobileFirst Server application. By default the name of the application is the name of the WAR file. In the Detail Properties section, click the Class loading and update detection link. • In the Class loader order pane, select the Classes loaded with local class loader first (parent last) option. Click OK. • In the Modules section, click the Manage Modules link. Click the module. • For the Class loader order field, select the Classes loaded with local class loader first (parent last) option. • Click OK twice to confirm the selection and back to the Configuration panel of the application. Click Save to persist the changes. MobileFirst Server Push Service
- 29. © 2016 IBM Corporation 29 Asymmetric deployment with runtimes and administration services in different server or cluster + Mandatory JNDI properties • For more information about the JNDI properties, see List of JNDI properties for MobileFirst Server push service. Property Value mfp.push.authorization.server.url The URL OAuth authorization server used by the push service mfp.push.authorization.client.id The id of the confidential client that handles push service OAuth authorization. mfp.push.authorization.client.secret The secret of the confidential client that handles push service OAuth authorization. mfp.push.services.ext.security Security plugin: com.ibm.mfp.push.server.security.plugin.OAuthSecurityPlug in mfp.push.db.type Database type, default: DB MobileFirst Server Push Service Note: the authorizations clients users may not be defined in LDAP or ext. Repositories.
- 30. © 2016 IBM Corporation 30 Asymmetric deployment with runtimes and administration services in different server or cluster + Mandatory JNDI properties - If MobileFirst Analytics is configured Property Value mfp.push.analytics.endpoint The url of the analytics service. If not specified, the analytics service is considered disabled mfp.analytics.username The username to access the analytics server mfp.analytics.password The password to access the analytics server mmfp.push.services.ext.analytics com.ibm.mfp.push.server.analytics.plugin.AnalyticsPlugin MobileFirst Server Push Service
- 31. MobileFirst Server Artifacts service configuration details
- 32. © 2016 IBM Corporation 32 Asymmetric deployment with runtimes and administration services in different server or cluster + MobileFirst Server Artifacts configuration details • The artifacts component is packaged as a WAR application for you to deploy to the application server. You need to make some specific configurations for this application. • The WAR file for this component is in mfp_install_dir/MobileFirstServer/mfp-dev-artifacts.war. • You must define the context root as /mfp-dev-artifacts MobileFirst Server Artifacts
- 33. © 2016 IBM Corporation 33 Asymmetric deployment with runtimes and administration services in different server or cluster + Class loader + For all MobileFirst Server applications, the class loader must have the parent last delegation. To set the class loader delegation to parent last after an application is installed, follow these steps: • Click the Manage Applications link, or click Applications > Application Types > WebSphere entreprise applications. • Click the MobileFirst Server application. By default the name of the application is the name of the WAR file. In the Detail Properties section, click the Class loading and update detection link. • In the Class loader order pane, select the Classes loaded with local class loader first (parent last) option. Click OK. • In the Modules section, click the Manage Modules link. Click the module. • For the Class loader order field, select the Classes loaded with local class loader first (parent last) option. • Click OK twice to confirm the selection and back to the Configuration panel of the application. Click Save to persist the changes. MobileFirst Server Artifacts
- 35. © 2016 IBM Corporation 35 Asymmetric deployment with runtimes and administration services in different server or cluster + MobileFirst Server Push service configuration details • Data source - data source for the administration service and map it to: • For more information about the databases, see Setting up databases. Property Target Resource JNDI Name jdbc/mfpDS MFP Runtime MobileFirst Runtime
- 36. © 2016 IBM Corporation 36 Asymmetric deployment with runtimes and administration services in different server or cluster + MobileFirst Runtime configuration details • The runtime is packaged as a WAR application for you to deploy to the application server. You need to make some specific configurations for this application. • The runtime WAR file is in mfp_install_dir/MobileFirstServer/mfp-server.war. • You can define the context root as you want. However, it is /mfp by default. • Start Order - The runtime application must start after the administration service application. You can set the order at Startup behavior section. For example, set the Startup Order to 1 for the administration service and 2 to the runtime. MobileFirst Runtime
- 37. © 2016 IBM Corporation 37 Asymmetric deployment with runtimes and administration services in different server or cluster + Class loader + For all MobileFirst Server applications, the class loader must have the parent last delegation. To set the class loader delegation to parent last after an application is installed, follow these steps: • Click the Manage Applications link, or click Applications > Application Types > WebSphere entreprise applications. • Click the MobileFirst Server application. By default the name of the application is the name of the WAR file. In the Detail Properties section, click the Class loading and update detection link. • In the Class loader order pane, select the Classes loaded with local class loader first (parent last) option. Click OK. • In the Modules section, click the Manage Modules link. Click the module. • For the Class loader order field, select the Classes loaded with local class loader first (parent last) option. • Click OK twice to confirm the selection and back to the Configuration panel of the application. Click Save to persist the changes. MobileFirst Runtime
- 38. © 2016 IBM Corporation 38 Asymmetric deployment with runtimes and administration services in different server or cluster + Mandatory JNDI properties - JMX communication with the administration service • For more information about the JNDI properties, see List of JNDI properties for MobileFirst runtime. Property Value mfp.admin.jmx.dmgr.host Deployment manager host name. mfp.admin.jmx.dmgr.port the SOAP port on the deployment manager mfp.topology.platform set the value as WAS mfp.topology.clustermode set the value as Cluster mfp.admin.jmx.connector set the value as SOAPº mfp.authorization.server embedded MobileFirst Runtime
- 39. © 2016 IBM Corporation 39 Asymmetric deployment with runtimes and administration services in different server or cluster + Mandatory JNDI properties - If MobileFirst Analytics is installed Property Value mfp.analytics.url The url of the analytics service. If not specified, the analytics service is considered disabled mfp.analytics.console.url The url of the analytics server console (UI) mfp.analytics.username The username to access the analytics server mfp.analytics.password The password to access the analytics server MobileFirst Runtime