ASP Clients

If you are using the standard ASP Generator, as supplied with Component Enabler, your only option is to use the CEWindowsAPIJavaStyle interface. This is because the generated ASP files contain calls to the interface in the old Java Style, and it is not practical to change these calls every time you re-generate.

If, however, you use a Custom ASP Generator, you might want to change both your infrastructure files, and your custom generator to use the CEWindowsAPI interface calls.

Refer to Old Call to New Call Reference for a list of old calls, and their new equivalents.

Converting to the CEWindowsAPIJavaStyle Interface.

To use the CEWindowsAPIJavaStyle interface, you just need to change the 'Server.CreateObject' call in global.asa.

To use the .NET Framework runtime environment, change the call to:

SetobjLINC = Server.CreateObject("LINCEnvironment.JavaStyledotNET.1")

To use the Java runtime environment with the JVM, change it to:

SetobjLINC = Server.CreateObject("LINCEnvironment.JavaStyleJavaSUN.1")

To use the Java runtime environment with the JIntegra JVM, change it to:

SetobjLINC = Server.CreateObject("LINCEnvironment.JavaStyleJavaJIntegra.1")

Note: You must still have the 'old' program Ids registered for the Java runtime environment to work.

If your global.asa has logging enabled, you should use the newer format for getting the log object.

For example,

Change

Set objLog = Server.CreateObject("Log.Java.1")

To

set objLog = objLINC.getLogObject()

This replaces the CreateObject call to get the log object.

The call must also be moved after the call to the CreateObject call for objLINC.

For example:

Set objLINC = Server.CreateObject("LINCEnvironment.JavaStyleJavaMS.1") 
set objLog = objLINC.getLogObject() 
      if not objLog.def.getLogLevel() = 7 then  
            objLog.def.setLogLevel(7) 
            objLog.def.setFlags(62)Æ
            objLog.def.setOutputFile ("c:\temp\activelinc3.log") 
      end if
Set Session("objLog") = objLog

All other calls can remain the same.

If the IIS web servers are running on 64-bit Windows Server OS, and AB Suite Development Environment and .NET SDK are not installed on the IIS server machines, then during installation of Component Enabler on the IIS web servers, the Component Enabler uses .NET Framework 4.7.2 version of Gacutil.exe and Regasm.exe to register the CEdotNET assemblies. This leads to IIS running CEdotNET as a 64-bit application.

When CEdotNET runs as a 64-bit application the application cannot connect to the IIS web server using JavaStyledotNET. The Ispec specified in loadIspec or the Ispec sent back from the transaction are not loaded.

To resolve this problem, IIS should run CEdotNET as a 32-bit application.

To run CEdotNET as a 32-bit application in IIS, perform the following:

  1. Copy newer versions of Gacutil.exe and Regasm.exe from any new .NET Framework SDK version, and paste them at C:\NGEN_CE\Bin.

  2. Run iisrest to restart IIS, to ensure that the CEdotNET assemblies are not in use.

  3. Open Command Prompt in Run as administrator mode, and perform the following:

    1. Change the directory to C:\NGEN_CE\Bin.

    2. Rename Gacutil.exe and Regasm.exe present in .NET Framework version 1.1 to ensure that Gacutil.exe and Regasm.exe are picked from C:\NGEN_CE\Bin.

    3. Run UnregisterCEdotNET.bat.

    4. Run RegisterCEdotNET.bat

  4. In IIS, create an application pool and perform the following:

    1. Set the Pipeline of the application pool to Classic.

    2. Move the ASP application into the application pool.

    3. In Advanced Settings, change Enable 32-bit Applications to True for the application pool.

  5. Use regedit to open the Registry Editor and provide IUSR Read access to the key HKEY_USERS\S-1-5-20\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones.