Installation Guide

Planet 8
Version 6.0.5
About
This guide contains all needed technical information on how to install and upgrade Planet 8.
Installation is delivered as normal SAP transport files. The transport may be imported in a system
where Neptune UXP or Planet 8 is already installed.

Pre-installation activities
▪ If the previous version of the Neptune App Store 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.

Installation
▪ Download and unpack the trial version.

Add the main transport files to the SAP transport system:

K90xxxx.NAD & R90xxxx.NAD

Normally the path to the SAP-directory is found with transaction AL11. In most systems the
transport directory is: /usr/sap/trans.

▪ 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 que to your system.
▪ Go to Extras->Other Requests->Add

▪ Type in the transport number: NADK90xxxx

▪ 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 and while it’s running you can see this icon as the status

▪ 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

Post-installation activities
1. 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.

2. 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.

3. 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 neptune and each of its subnodes and in the context menu select Activate Service
4. 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.

5. Authorizations:
• When upgrading from Neptune DXP v.5.5.X and higher →Skip to point 6
 • When upgrading from Neptune DXP v. 5.3.6 - 5.4.7 → It is recommended to follow
the instructions given in this point to use the newest authorization object, but it is
optional to skip to point 6.
• For new installations and upgrade from versions before 5.3.6 the following is
required:
The installation package comes with a folder named “Authorization”. This folder
contains an authorization role, which may be imported either as a transport (*.NAD files,
or it may be uploaded from file (*.SAP) in transaction PFCG. After the role is imported
into the system, please make a copy of the standard role /NEPTUNE/DEVELOPER, make
any adjustments you find necessary, and finally assign it to the developers and
administrators. /NEPTUNE/DEVELOPER contains all required authorizations for the
Neptune transactions and the Neptune Cockpit. Optionally several roles can be created
and assigned to restrict access. After importing the transport with the role, it might be
necessary to run program PFCG_TIME_DEPENDENCY for user master comparison if this
is not already scheduled to run as a background job in the target system.

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

7. 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).

8. 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.

9. If upgrading from Neptune DXP version 4.x to 5.x, it is required to update the license key. Please
reach out to [email protected] to get your updated key.

10. To avoid unnecessary system log messages, please find the certificate named
neptune-cert.bin in the installation package and upload it into the system Personal
Security Environment (system PSE). The certificate can also be downloaded here.

Certificate import instructions:

10.1. Start transaction STRUST
10.2. Change
10.3. Import Certificate for System PSE
10.4. Add to Certificate List
10.5. Save
 As a general note, please also make sure to update the systems Cryptolib as
described here.

11. We recommend:
11.1. The Neptune launchpad is backed into a mobile client. New features and bugfixes in
the Neptune launchpad, will not be available to already build mobile clients. Under normal
circumstances, the mobile clients build with previous Neptune versions should run fine. But
we do recommend building mobile clients with the upgraded Neptune version, and
ship/install the newly build mobile clients on user devices.

11.2. Installing SAPGUI 7.40 Patch level 16 or higher

11.3. When Neptune applications run inside SAP GUI on Windows, Internet Explorer is
used to render the pages. Only IE11 is supported. Make sure that IE is upgraded to the
 latest version.

11.4. For the best user experience, we recommend that you use Google Chrome to run
Neptune Cockpit & the browser based App Designer.

11.5. Setting up SSO2 logon. Please adjust RZ10 (or RZ11 for immediate effect)
11.5.1. login/accept_sso2_ticket = 1
11.5.2. login/create_sso2_ticket = 2

Reverse Proxy Notice

The paths to the Neptune Cockpit & the Neptune WEB App Designer have been changed in v.6.0.0.
Now both services are run in the webapp path as a default:

• /neptune/webapp/neptune/cockpit
• /neptune/webapp/neptune/cockpit_app_designer.

Review any Reverse Proxy technology in place to update the rules accordingly. Please see the
guidelines at https://community.neptune-software.com/blogs/reverse-proxy.

Frequently Asked Questions

Q: My JS Editor / Run in Designer does not work, what should I do?
A: please check out the following guide: https://community.neptune-software.com/blogs/neptune-
javascript-editor-does-not-work

Q: How can I setup single sign-on?

A: Please check out: https://community.neptune-software.com/blogs/single-sign-on

Q: How can I check the status of my installation?

A: Please run report /NEPTUNE/INSTALLATION_CHECK (transaction SE38).

Q: A lot of the icons are missing in the App Designer?

A: Activate the ICF node sap/public/bc/icons (transaction SICF).

Q: Where can I find more answers to my questions?

A: Please have a look at “Support vs Community.pdf” which is included in the installation package.