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 web application has been set up on IIS Server
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 (On-Premise SAP Systems only)
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).
The sapnwrfc.ini file should be located in the NLINK Config folder. By default, the NLINK config folder is C:\Program Data\Junot Systems (for NLINK v7x).
For NLINK Server v6x or earlier, the Config folder is a sub-folder under the NLINK installation folder, which 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 the 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.
Your NLINK meta-database may not have all these entries, and/or may have additional entries specific to your configuration.
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. |
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. If you do not see this Environment Constant, set the address directly in the System Properties. |
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. |
SAP (On-Premise Systems) | |
SAP_DESTINATION | Enter the destination (from the sapnwrfc.ini file) you want to connect to. |
SAP_CLIENT | Enter the SAP client number, just as you would if you were logging on through SAPGUI. |
SAP_LANGUAGE | Enter the SAP language, just as you would if you were logging on through SAPGUI (e.g., EN for English). |
SAP_USER_ID | If not using logon passthrough, specify an SAP User for NLINK to use for all communication. This is a required field, so even if you are using logon passthrough you will need to put something here (e.g., “notused”). If you are configuring your own transactions, you also need this user in order to run the SAP Wizards in the NLINK Configuration Module. |
SAP_PASSWORD | Enter the password for the NLINK User specified above, or leave empty if using passthrough. |
SAP_ALT_RFC_READ_TABLE | 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. |
SAP_DATA_DICT_USER_ID | Optionally specify an SAP User for NLINK to use for various technical communications, e.g., determing function module signatures. This may allow you to offload some technical authorizations to this single user instead of having to add them to all the business users. |
SAP_DATA_DICT_PASSWORD | Enter the password for the NLINK Data Dictionary User specified above, or leave empty if not used. |
SAP (S/4Cloud Systems hosted by SAP, or On-Premise Systems using SAP REST APIs) | |
SAP_SERVER_URL | Enter the base url for the SAP APIs, e.g., https://some.address.here:port/sap/opu/odata/sap/ |
AUTH_URL | Enter the public ping url, e.g., https://some.address.here:port/sap/bc/ping?sap-client=xxx where xxx is the client number |
SAP_LANGUAGE | Enter the SAP language, just as you would if you were logging on through SAPGUI (e.g., EN for English). |
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
Please see Defining ADC Menu Group Validations (ADC5) for various options regarding ADC Menu Groups.
If you do not see the ADC Menu Setup option in the NMM, and you have just switched your Active Meta-Database from a default meta-database to an ADC Solution meta-database, please close the NMM and re-open it.
Test SAP Connection (On-Premise Systems only)
After setting the SAP connection parameters in the Environment Constants use the NMM to test the connection to SAP. Please see Test SAP Connectivity with the NMM for step-by-step instructions.
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.