Deployment roadmap for Mobile applications using Neptune DXP


The Deployment Roadmap outlines the essential steps involved in efficiently deploying applications and conducting tests using the Neptune DXP Mobile Client tools. Please note that this roadmap is not aimed at the deployment of performance or load test automation. The roadmap consists of modules that can be independently delivered by you, with or without support from Neptune Software.

Deployment Planning

The Deployment Planning guide helps you plan and schedule the activities for your deployment project. A meaningful role is defined below to perform deployments.


Deployment Project Manager


Basic project management skills


Define the organization’s needs and objectives for change management and gain organizational commitment to implementing Neptune Software test tools from management and end-users.

Table 1. Information regarding the duties, role and more
Role Skills Needed High-level Steps

The person who takes responsibility for deployment planning assumes the role of the deployment project manager; however, you will need to work closely with the tool specialist and senior engineer on the planning activity

To deliver this module, the deployment project manager needs basic project management skills

As the deployment project manager, your first step is to clearly define your organization’s needs and objectives for the target population of the application targeted devices type, and particularly OS types

Deployment Planning Guidelines

Deploying a Mobile Application requires considering the device types and operating systems (OS) used by the target users. Here are the key considerations:


  • OS Types: Determine the OS types (Android, iOS, Windows 10) of the target user population. Each OS has its own specifications and technologies.

    • Bringing Your Own Device (BYOD) Strategy: Consider allowing users to use their own devices with the targeted OS type for the initial rollout and future expansion.

    • Device Functionalities: Identify the required device functionalities for the applications. Based on the requirements, choose between Progressive Web Application (PWA) or Cordova-based Mobile Client.

      • PWA: If the requirements align with a PWA, there is no need for application packaging. PWAs are web apps that can be deployed using a URL and can provide features like offline support, push notifications, camera access, and geolocation.

        • Neptune DXP supports PWAs: Check the relevant documentation for configuration details.

      • Cordova-based Mobile Client: If the Cordova-based Mobile Client is the preferred path, use Cordova CLI application packaging.

        • Neptune can assist in setting up the baseline for using Cordova CLI if needed.

Infrastructure and Security

  • Architecture: Design a robust architecture for mobility, ensuring appropriate decoupling between systems of record and frontend layers exposed via UI or APIs. Check the relevant documentation for architecture setups.

  • Single Sign-On (SSO): Consider implementing SSO to provide seamless authentication for users. Neptune supports multiple SSO strategies, including custom ones. Review the available authentication methods in the Neptune DXP documentation.

  • Mobile Device Management (MDM): While optional, it is recommended to use an MDM solution for an additional layer of security. MDM can assist in distributing mobile client files and enhancing communication security. Neptune supports integrations with various MDM services using Cordova plugins.

  • Edge Security: Consider the following security measures for your deployment:

    • Content Delivery Network (CDN): Utilize CDN services like Cloudflare to handle traffic spikes and cache content, reducing the load on backend systems.

    • Web Application Firewall (WAF): Implement a WAF to protect against attacks like cross-site scripting or SQL injections, and customize the whitelist and blacklist rules to allow or restrict access to deployed Neptune DXP apps.

    • Internet/Application Gateway: Configure the gateway to regulate ingress and egress traffic to grouped workloads, considering connections to Neptune DXP Servers or API Gateways.

    • Firewall: Ensure the corporate firewall filters HTTP traffic within the private network, applying validation rules for API requests.

    • API Gateway: Use an API Gateway to proxy API requests made by Neptune DXP applications to microservices or SAP systems, reducing the load on backend Neptune DXP workloads and increasing security.

    • Identity Provider (IDP): Choose an appropriate IDP for user authentication, such as Microsoft Entra ID, LDAP, or SAML-based federated login services. Ensure that user groups, roles, and attributes are properly imported and configured in the IDP.

Deployment of Artifacts

Once all the considerations above are addressed and systems are running on the same version of Neptune DXP, follow these steps:

  • Move Transport Requests: Transfer all transport requests from QA to PRD in the same order they were imported into QA.

  • Neptune DXP - SAP Edition:

    • Export tiles, tile groups, media packages, media files, and other resources that are not part of transport requests.

    • Configure a new launchpad and mobile client, including tile groups, splash screens, and custom login screen.

  • Set User Population Policy: Define a policy for targeting a limited user population, whether as pilot users or the intended target population.