Created On:  03 October 2012

Problem:

Server for COBOL (formerly known as Application Server for Net Express) was using a different license mechanism and networked licensing (ASLMFNET). Is it possible to set up a similar networked licensing with COBOL Server 2.1 or Enterprise Server 2.1?

Resolution:

Here are the steps to set up networked licensing with COBOL Server 2.1 to run native (non .NET) applications.

[Server side]
1. Install COBOL Server 2.1 on the server
2. Install the license
3. Copy mfcesd.exe (MF CES Daemon) and mfcesdchk.exe (this checks if MF CES Daemon is running)
    a. In 32-bit Windows – from C:\Program Files\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT to C:\Program Files\Micro Focus\COBOL Server\bin
    b. In 64-bit Windows – from C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT to C:\Program Files (x86)\Micro Focus\COBOL Server\bin
4. Extract msvcr100.dll and msvcr100d.dll from the attached SafeNetLic.zip into the “bin” folder of COBOL Server 2.1 – if these files are not found in C:\Windows\System32
5. Extract ces.ini from the attached SafeNetLic.zip into the “bin” folder of COBOL Server 2.1
6. Modify the value of lshost in ces.ini with the IP address or name of the server
7. Create a network share off the “bin” folder of COBOL Server 2.1 with Read permission to Everyone
8. Create a network share off the “bin64” folder of COBOL Server 2.1 with Read permission to Everyone – if running 64-bit applications

[Client side]
MF CES Daemon is required to run prior to run an application as it interacts with the MF License Manager for checking out a license. There are 2 recommended ways of starting MF CES Daemon and running the application:
1. Run a batch file to start MF CES Daemon and individual applications – Use and modify the attached the runit.bat file as follows:
    a. Set MFCES_INIT_LOCATION to point to the ces.ini file (e.g. \\ServerName\Share_bin\ces.ini)
    b. Set PATH to point to the location of the runtime files:
        i.  Replace \\ServerName\Share_bin to the network share created in Step 7
        ii. Remove “rem” in front of the next PATH setting and replace \\ServerName\Share_bin64 with the network share created in Step 8 – if running 64-bit applications
   c. Set PATH to point to the location of the applications in the next PATH setting by replacing Location_of_Apps with the actual location
   d. Change the last line by replacing YourApp with the name of the application to be executed

-OR-

2. Install MF CES Daemon (only once) as a Windows service and run individual applications:
    a. Install and start MF CES Daemon as a Windows service:
        i.   Set MFCES_INIT_LOCATION as a system variable and to point to the ces.ini file (e.g. \\ServerName\Share_bin\ces.ini)
        ii.  Copy mfcesd.exe on the client machine’s local drive
        iii. Open a Command Prompt session
        iv. CD to the location of mfcesd.exe
        v.  Issue the following command to install MF CES Daemon as a Windows service:
            mfcesd -i
        vi. Issue the following command to start the MF CES Daemon service:
            mfcesd -start
    b. Set PATH as a system variable and to point to the location of the runtime files:
        • If running 32-bit applications, set PATH to point to the network share created in Step 7
        • If running 64-bit applications, set PATH to point to the network share created in Step 8 followed by the one created in Step 7
    c. Set PATH as a system variable to point to the location of the applications also
    d. Run the application

Notes:
    • ces.ini must be on a network location, and that is why we recommend creating it in the “bin” folder of COBOL Server 2.1
    • The above instructions are applicable to Enterprise Server 2.1
    • If you are running COBOL Server 2.0 or Enterprise Server 2.0, you will need to upgrade to version 2.1; otherwise, you still can follow the exact same instructions except that you will need to use mfcesd.exe and mfcesdchk.exe from the attached SafeNetLic.zip
    •
 The above instructions are specific to version 2.1 only. If you are running a higher version, you will need to follow the instructions from the documentations, and you must not use the files from the attached SafeNetLic.zip 

Incident #2592091