Previous Topic Next topic Print topic


Deploying Native Applications

The software components required for successful HCOSS application deployment are:

Development Machine
  • Has Studio Enterprise Edition for Windows installed
  • If SQL Server 2008 or 2012 is not installed, you must have Microsoft SQL Server 2008 or 2012 Native Client installed
Development SQL Server Machine
  • Has SQL Server 2008 or 2012 installed
  • Can be the same machine as the development machine, but not required to be
Deployment Machine
  • Has Server Enterprise Edition for Windows installed
  • If SQL Server 2008 or 2012 is not installed, you must have Microsoft SQL Server 2008 or 2012 Native Client installed
Deployment SQL Server Machine
  • Has SQL Server 2008 or 2012 installed
  • Can be the same machine as the deployment machine, but not required to be

Deploy an Application Compiled Without DBRMLIB

To deploy a Studio Enterprise Edition HCOSS application that was not compiled using the DBRMLIB directive, meaning that you did not bind the DBRM files for your application, complete the steps presented in the topic Deploying COBOL Applications. The steps presented there are necessary to successfully deploy your application to the deployment machine.

In addition, you must also install Microsoft SQL Server 2008 or 2012 Native client on your deployment machine so your SQL Server application can communicate with a SQL Server instance.

Development Machine
  • Build and test the HCOSS application with a development SQL Server machine.
Deployment Machine
  • Follow the steps defined in Deploying COBOL Applications, moving your HCOSS application as specified
  • Create a connection to the deployment SQL Server machine
  • Test the HCOSS application with the deployment SQL Server machine

Deploy an Application Compiled With DBRMLIB

To bind a Studio Enterprise Edition HCOSS application using the DBRMLIB directive and deploy it to a deployment machine, you have two choices. For both, you must also install Microsoft SQL Server 2008 or 2012 Native client on your deployment machine so your SQL Server application can communicate with a SQL Server instance:

Bind the application from your development machine
Development Machine
  • Build and test the HCOSS application with a development SQL Server machine
  • Create a connection to the deployment SQL Server machine
  • Bind the HCOSS application to the deployment SQL Server machine using the connection you created
Deployment Machine
  • Follow the steps defined in Deploying COBOL Applications, moving your HCOSS application as specified

  • Create a connection to the deployment SQL Server machine
  • Test the HCOSS application with the deployment SQL Server machine
Bind the application from your deployment machine
Development Machine
  • Build and test the HCOSS application with a development SQL Server machine.
Deployment Machine
  1. Follow the steps defined in Deploying COBOL Applications.
  2. To ensure that your HCOSS application is properly migrated, install the following software:
    • Microsoft SQL Server 2008 or 2012 Native Client
    • Microsoft .NET 3.5 framework
  3. Copy your HCOSS application from the development machine to the appropriate directory structure on the deployment machine.
    Important: You must create some or all of the required directory structure manually.

    Specifically, copy database request modules (DBRMs), that is, the DBRMName.hcodbrm files, from the development machine to the equivalent directory on the deployment machine. The location of your DBRM files varies on your development machine depending on your HCOSS options, and the specified DBRMLIB directive. The location on your development machine is:

    localHCOSSFiles\DBRMDataSets\DBRMLIBName

    Where localHCOSSFiles represents the value of the Local HCOSS Directory HCOSS option, and DBRMLIBName represents the value of the DBRMLIB directive.

    Note: If no value is provided for the DBRMLIB directive, the default value is DBRMLIB. SQL(DBRMLIB) is the equivalent of SQL(DBRMLIB=DBRMLIB).

    On the deployment machine, you must put the DBRM files into a subdirectory of the default directory: %APPDATA%\Micro Focus\NetExpress\6.0\HCOSS\DBRMDataSets. The subdirectory name must match the DBRMLIB name.

    For example, assuming the following:

    Studio Enterprise Edition version 6.0
    Development machine Windows user ID devuser
    Deployment machine Windows user ID exeuser
    DBRMLIB directive SQL(DBRMLIB=REX.PROJECT.DEMO)
    Value of Local HCOSS Directory HCOSS option on both machines Default setting, %APPDATA%\Micro Focus\NetExpress\6.0\HCOSS\DBRMDataSets

    You then copy the generated DBRM files using the following directory specifications:

    Development Machine Deployment Machine
    c:\Users\devuser\AppData\Roaming\Micro Focus\NetExpress\6.0\HCOSS\DBRMDataSets\REX.PROJECT.DEMO c:\Users\exeuser\AppData\Roaming\Micro Focus\NetExpress\6.0\HCOSS\DBRMDataSets\REX.PROJECT.DEMO
  4. Start HCO for SQL Server from > HCO for SQL Server.
  5. Using the Manage Connections tool, create a connection to the deployment SQL Server machine. For more information, see the Manage Connections Tool topic.
    Important: Be sure that the login credentials you use grant you the permissions necessary to successfully perform the tasks outlined in both the Schema Update Execution and Bind Script Execution sections of the DSN Bind Utility topic.
  6. Using the Manage Packages and Plans tool, bind the DBRM to your deployment SQL Server machine by creating and executing a BIND PACKAGE script command. For complete details, see the Manage Packages and Plans topic.
  7. Test your HCOSS application on the deployment SQL Server machine.
    Note: When running from the command line, if your installation directory contains spaces, do not enclose the directory specification in quotes when you add it to the PATH environment variable.
Previous Topic Next topic Print topic