Skip to main content

Using the Installer Wizard

The Installer Wizard allows you to create a Foundation namespace and production that contain all the mappings and libraries needed for healthcare interoperability. Creating an interoperability namespace using System Administration > Configuration > System Configuration > Namespaces also creates a Foundation namespace and production, so you can use whichever method you prefer. If you use the System Administration menu, you can either use the default Foundation production or remove it and create your own production. However, only Foundation productions are started when you select the Start All button on pages accessed through the Health menu.

The business host Ens.Activity.Operation.Local that is automatically added to a Foundation production is used for activity monitoring, and can be removed if you do not need this functionality.

To install and activate a Foundation production using the Installer Wizard:

  1. Log in to the Management Portal for your instance as a user with the %HS_Administrator role.

  2. Click Health in the menu on the left.

  3. Click the Installer Wizard link in the banner at the top of the page.

  4. Click Configure Foundation.

  5. For Local Name, enter the name that will identify the Foundation production. This name will become the namespace that contains the class definitions for the production. The maximum length for this string is 50 characters. The local name is referred to below as <LOCAL_NAME>.

  6. The Network Name is the network-wide, unique name for the Foundation production. It defaults to Network_Host_Name:<LOCAL_NAME>.


    Network_Host_Name defaults to the machine’s host name if you do not explicitly set it in the Configure Network Host Name option in the Installer Wizard. Network_Host_Name should always be set in the Installer Wizard before you begin configuring your instance.

    A DNS entry is a better choice of Network_Host_Name, as it provides more flexibility. In a mirror, it is important that Network_Host_Name be set to the VIP (or DNS entry) of your mirror before you use the Installer Wizard to configure your productions.

  7. For Description, enter an optional short description.

  8. If the system is a mirror member and you want to mirror the database, select Mirror Database. For additional about mirroring with Health Connect, see the considerations for healthcare products described in Managing Mirroring.

  9. For Production, enter the package and class name that you will use for this production in the form Package.Class. The default is <LOCAL_NAME>PKG.FoundationProduction. For example, “HSFOUNDATIONPKG.FoundationProduction”. Adding PKG to <LOCAL_NAME> makes it easy to differentiate between namespace and code package names, and prevents naming collisions.

  10. For Template, choose Generic Production.

  11. The default location for the production database, IRIS.DAT, is installDir/mgr/localName. To specify a location for the database other than the default, enter the alternate location in the Alternate Database Location field. If you specify an absolute location, then that location will be created if it does not exist. Your database will be in alternateDatabaseLocation/localName. If you specify a relative location then the database will be created in installDir/mgr/hslib/alternateDatabaseLocation/localName.

  12. Click Save. This production is now displayed in the list of configurations.

  13. In the row for the production you just created, click Activate. A window pops up, asking if you want to proceed. It is at this step that your Foundation production is created.

  14. Click Start to start the activation process.


    If you close the dialog box before it displays a message that indicates completion, you will not see any error messages that may occur in the creation of your production.

    The result of the activation process is a new namespace that contains a Foundation production and other related classes. If you used the default values, the namespace for this production will be <LOCAL_NAME>, and the production name will be <LOCAL_NAME>PKG.FoundationProduction. So, for example, if you enter HSFOUNDATION in the Local Name field, you will create an HSFOUNDATION namespace that contains a FoundationProduction in the HSFOUNDATIONPKG package.

FeedbackOpens in a new tab