Neptune DXP - SAP Edition installation - On Prem

If the previous version of the Neptune DXP Marketplace has been installed, please delete ABAP class ZCL_NAD_APPSTORE_CLIENT. This class uses deprecated components and must be deleted before installation Neptune. This ABAP class lies in the customer namespace and must be removed manually.

If you are installing Neptune DXP for the first time, or you are upgrading from a UXP 4.X system, please reach out to licensing department to get your license key ready for when you need it. Please include the system installation number(s) in an e-mail to licensing@neptune-software.com.

Please note that with a Frontend/backend split (dedicated Gateway server), the same version of Neptune DXP should be installed on both/all instances.

Download and unpack the trial version.

Add the transport NADK90xxxx to the SAP transport system: Files: K90xxxx.NAD & R90xxxx.NAD

Find the path to the SAP transport directory. Use transaction AL11. In most systems the transport directory is: /usr/sap/trans.

Upload the NADK90xxxx transport files to the SAP transport directory. If the component EA-APPL is installed in your system, upload can be done with transaction CG3Z.

Otherwise, the files can be uploaded by running function module ARCHIVFILE_CLIENT_TO_SERVER in transaction SE37.

The files may also be moved on OS level.

Start transaction STMS and open the import queue to your system.

Double-click your target system

Go to Extras→Other Requests→Add

Add transport request NADK90xxxx to the import queue.

Locate the transports in the STMS transport list. Mark NADK90xxxx. Import the transport.

You need to specify the Target Client (the Client where you are running Neptune). If you are using more than one client, please remember to run the program /NEPTUNE/INSTALLATION_CHECK in each client after the transport has been completed.

Please also tick the "Ignore Invalid Component Version" checkbox in the Options tab.

The import should start.

You can also monitor the progress of the import by selecting the row and clicking on the Import Monitor.

If the import has completed successfully, you should see a similar screen in the Import Monitor.

Please ignore any warnings for the import (code 4/6). If you get an error (code 8/12) please register a ticket at http://support.neptune-software.com

Import the transports for the SAPUI5 library versions to be installed on your system. From version 5.5.0 the main installation transport does not contain any SAPUI5 libraries. For creating a mobile client, it is required to have installed an SAPUI5 library, however for desktop scenarios it is possible to use CDN versions of SAPUI5.

Important information to customers without Internet access: Neptune Cockpit and Neptune App Designer now uses UI5 CDN versions. If no Internet access is present, a local UI5 v1.71 is used as a fallback. You must therefore install UI5 v.1.71, before running Neptune Cockpit and Neptune App Designer. Download UI5 v.1.71 from our download site and install it before running the Neptune Cockpit or the Neptune App Designer.

Open SAP transaction SICF

Click the Execute icon on the following screen with default parameters set to navigate to the next screen.

In the Define Services screen expand the neptune node under Virtual Hosts /Services.

Right-click on the neptune node and each of its sub-nodes and in the context menu select Activate Service.

Explanation of ICF nodes:

If you are planning to use Progressive Web Apps (PWA) or anonymous logon/public access for your apps/launchpad, please also create and activate two subnodes under /neptune/ called “public” and “server”. These nodes should both have a set username and password in logon data. These nodes should both have a set username and password in logon data, and it is recommended to use a dedicated service user, so the password does not expire.

If you are calling Rest APIs from an external system (for instance Neptune DXP - Open Edition), it is recommended to add a subnode under the api node with Security Session “Completely restricted”:

Start the transaction /NEPTUNE/DESIGNER and select Run in Browser the NEPTUNE_FLIGHT app to initialize the environment, and to verify that the sample app is running as expected.

Authorizations:

Run program /NEPTUNE/INSTALLATION_CHECK in every client you will run Neptune.

Make sure you have the hostname/ip for your SAP system in your host file or set a public URL in the Cockpit System settings (transaction /NEPTUNE/COCKPIT).

A pre-requisite for using the App Designer in the Cockpit is that stateless lock handling is set up. Please refer to this guide for details.

If upgrading from Neptune DXP version 4.x to 5.x, it is required to update the license key. Please reach out to licensing@neptune-software.com to get your updated key.

To avoid unnecessary system log messages, a certificate needs to be uploaded into the system Personal Security Environment (system PSE) in transaction STRUST. The certificate can be downloaded from the Neptune DXP Portal. Please select the certificate that corresponds to when your license contract was signed:

Certificate import instructions:

We recommend:

/neptune/webapp/neptune/cockpit

/neptune/webapp/neptune/cockpit_app_designer