Completing an NLINK 6.x ADC to SAP Solution Installation

Follow these steps to complete an NLINK ADC to SAP Solution installation (NLINK versions 6.x and up).

Prerequisites

These instructions assume that the following steps are completed:

NLINK ADC to SAP Solution is installed
NLINK License has been downloaded and installed
NLINK ADC web application has been set up on IIS Server
- IIS 7.x on Windows Server 2008
- IIS 8.x on Windows Server 2012 R2

Step-by-step guide

The final steps to complete your ADC to SAP Solution installation include:

Set up sapnwrfc.ini with SAP information (optional)
Deploy customized meta-database file (optional)
Set up NLINK Environment Constants
Set up ADC Menu Groups (optional)
Test the SAP connection

Each of these steps is covered in detail below.

Set up sapnwrfc.ini with SAP Connection Information

If you are using a direct Application Server connection to your SAP system, you can skip this section. If you are using a load-balancing, SNC or SSO connection, then please read this section.The sapnwrfc.ini file contains SAP connection information organized into destination (DEST) entries. Each destination specifies one particular method of connection between NLINK and SAP.

Each destination has a number of parameters that indicate how NLINK should find the SAP system. There can be any number of destinations in a single sapNwrfc.ini file, as long as all the destination names are unique.

Some of the connectivity information has to be obtained from an SAP system administrator.

Each destination parameter has to be on its own line with an equals sign (=) between the parameter name and its value. See the sapnwrfc.sam sample file for full descriptions of the various destination types and their parameters.

To edit the sapnwrfc.ini file, choose Edit >> SapNwRfc.ini File from the menu in either the NLINK Management Module (NMM) or NLINK Configuration Module (NCM).

For Reference Only

The sapnwrfc.ini should be located in the NLINK config folder. This folder is a sub-folder named Config under the NLINK installation folder.

By default, the NLINK installation folder is C:\Program Files\Junot Systems for 32-bit Windows 2003, Windows 2008 or C:\Program Files (x86)\Junot Systems for x64 Windows 2003, Windows 2008 or Windows 2012.

A sample file named sapnwrfc.sam can be found in [NLINK installation folder]\Documentation.

The sapnwrfc.ini file must be in UTF-8 format.

Deploy Customized Meta-Database File

If you have contracted with Junot Systems to provide pre-configured ADC Transactions for you, then you should read this section.

The NLINK ADC to SAP Solution is delivered as a turn-key solution. For your pre-configured transactions to work, you must deploy the customized meta-database that is delivered separately. If you do not have your meta-database file, please contact Junot Systems support before proceeding.

Save your meta-database file (.nlk extension) on the hard drive of your NLINK Server machine. Make a note of its location.

Set Active Meta-Database

Start the NLINK Management Module (NMM). Select the Server node in the navigation tree and you will see the full path and filename of the current meta-database file in the Server Status window.

Right-click the Server node and choose Select Meta-Database. Navigate to your meta-database file and select it.

If option “Select Meta-Database” is grayed out, make sure the NLINK Server is not running.

On Windows 2008 Server, NMM must be running with Administrator privilege.

Set Up NLINK Environment Constants

The NLINK meta-database contains some deployment specific settings called NLINK Environment Constants. For example, the SAP connection details can be specified here.

The NLINK Environment Constants can be edited using NMM.

Open the list of Environment Constants by choosing Edit >> Environment Constants from the NMM menu. Some entries may have a default value, which you do not have to change. Any entries in red must receive a value before you will be able to start the NLINK Server.

ADC
ADC TCP Port	TCP/IP port used by NLINK Server to receive requests. Use default unless there is conflicts with some other software using same port.
ADC Menu
MENU_GROUP_01 … MENU_GROUP_07	Put values here that match values of Windows User Groups containing users that should get different ADC menu. See below for more details.
Error Handling
EMAIL_SMTP_SERVER	Usually this can be blank.
EMAIL_RECIPIENT_ADDRESS	Leave this blank to turn off error notifications. Otherwise enter a valid email address and NLINK will automatically send error notification emails to that address.
EMAIL_FROM_ADDRESS	If sending error notifications, enter a valid “from” address here.
EMAIL_FROM_NAME	If sending error notifications, enter a name here. You can then use this information to filter the messages in the receiving email account.
General
WRITE_AUDIT_FILE	Set this to TRUE or FALSE depending on whether you want NLINK to write an audit file of user movement through the Solution.
SAP
SAP_HOST	Enter the hostname of the SAP application server you want to connect to.
SAP_SYSTEM_NUMBER	Enter the SAP backend system number.
SAP_CLIENT	Enter the SAP client number, just as you would if you were logging on through SAPGUI.
SAP_USER_ID	Enter NLINK’s SAP user id.
SAP_PASSWORD	Enter NLINK’s SAP password.
SAP_LANGUAGE	Enter the SAP language, just as you would if you were logging on through SAPGUI (e.g., E for English).
SAP_QUERY_FUNCTION_NAME	If your system needs to use an alternate RFC to get around the SAP floating point issue, enter the name of that RFC here (e.g., Z_RFC_READ_TABLE). If you don’t need the alternate RFC, leave this blank.

If you do not have a customized ADC meta-database provided to you from Junot Systems, you will not see all of the Environment Constants listed in the preceding chart.

Set Up ADC Menu Groups

The NLINK ADC to SAP Solution uses Windows user ids and groups to manage access to the transaction screens. By default, you can configure up to seven user groups to receive different ADC menus, but you don’t have to use them all. You do need to set up at least one group—you can probably just use the default Windows group Users.

Set the group name(s) in the Environment Constants MENU_GROUP_01 to MENU_GROUP_07 (see previous section of this document).

Then choose Edit >> ADC Menu Setup from the NMM menu and add the same group name(s) to set up menu choices for each group.

Select user group to set up.
Available configured transactions show here. Double-click to add a menu choice for the selected transaction to the current user group.
Selected transactions show here. Set the Item Text as desired.

If you do not have a customized ADC meta-database provided to you from Junot Systems, you will not see the ADC Menu Setup option in the NMM.

Test SAP Connection

After setting the SAP connection parameters in the Environment Constants use the NMM to test the connection to SAP.

Open the Test External System Connection dialog by choosing Options >> Test External System Connection from the NMM menu.

Click the Test button. You can modify the External System Attribute values here and re-test. Any changes made to parameters will also affect corresponding values in NLINK Environment Constants.

Troubleshooting tips can be found here.