Provides step-by-step instructions to complete the creation and configuration of the ESACCTCL
enterprise server regionon which to run the ACCT Web-enabled client and server.
Start the Server Explorer
The
Server Explorer expandable ribbon is visible in Visual Studio on the top left side of the IDE by default when using
Enterprise Developer. However, if it is not visible:
- In Visual Studio, click
View > Server Explorer.
Attention: You might encounter an
Enterprise Server Sign On dialog box as you perform the steps required to create, configure, start, or stop an
enterprise server region from the
Server Explorer. If you do, ensure that the
Server requires credentials,
Use specific server credentials, or
Server is secured
box is
unchecked, and then click
OK.
Also, if prompted to disable password recovery, click
No.
Create the ESACCTCL
enterprise server region
- In the
Server Explorer,
right-click
Default, and then select
New Enterprise Server.
- In the
Name field, type
ESACCTCL . This is the name for the new
enterprise server region.
- Check
64-bit.
- Click the
browse button that corresponds to the
Template field.
- Double-click
CICSTemplate.xml. This populates the
Template field.
Note: If
CICSTemplate.xml is not on the list, browse to the
Common7\IDE\Extensions\Micro Focus\Enterprise Developer\1.0\Etc\ServerTemplates subdirectory of your Visual Studio installation
to locate the file.
- On the list next to
Associate with projects, check
ACCTCLNT .
- Click
OK .
After refreshing, the
Server Explorer shows the
ESACCTCL
enterprise server region listed under
Default .
Configure the ESACCTCL
enterprise server region
- Start
Enterprise Server Common Web Administration (ESCWA)
-
- From the
Server Explorer, right-click
Micro Focus Servers; then select
Administration. This starts the
ESCWA UI in a browser outside of the IDE.
- Click
Native.
- In the navigation pane, expand
to see the
ESACCTSV
enterprise server region in the list of servers.
- Define environment variables
-
- In
ESCWA click
Native.
- In the
ESCWA navigation pane, expand
Directory Servers > Default.
Note: The
Native page and navigation pane might be set up in this configuration by default when you start ESCWA as it is the default starting
configuration.
- In the center pane, hover the row for the
ESACCTCL entry in the list of servers, and click
Edit
.
This action opens the
General Properties page for the server.
- Click
General in the taskbar at the top of the properties pane to open the
General Properties page.
- Type the following into the
Configuration Information field:
[ES-Environment]
This indicates that the information that follows defines environment variables that are specific to the
region. Next, you define an environment variable to represent your project directory.
- On the next line down, type:
IDE_PROJECT_LOC=c:\tutorials\CICS\ACCTCLNT
To use a defined environment variable in the value definition of another environment variable or as the value in other ESCWA
fields, you precede the name of the variable with a dollar sign ($). You can use the IDE_PROJECT_LOC environment variable
to help define the next variable.
- On the next line down, type:
ES_DOCTEMPLATE_PATH=$IDE_PROJECT_LOC\html
This variable is used in the template definition for the DOCUMENT created in this tutorial: ACCTMP1, defined in the DFHWEB
resource group.
Note: When you create an
enterprise server region using the CICS template as you have done in this tutorial,
Enterprise Server generates and stores several environment variables based on the information in the associated project. For example, in this
region, the IDE_LOADLIB environment variable has been generated and is set to the directory you defined as the output directory
in the ACCTCLNT
Enterprise Developer project. Therefore, IDE_LOADLIB is equal to the
loadlib subdirectory of your project directory, or
c:\tutorials\CICS\
ACCTCLNT\loadlib . The definitions for generated environment variables do not show in the
Configuration Information field, however.
- Click
Apply .
- Create the
html project subdirectory
- The
html project subdirectory you specified in the path for the ES_DOCTEMPLATE_PATH environment variable does not exist on your local
disk. Before proceeding, using your preferred method, create this subdirectory to ensure ESCWA can find it when you deploy.
- Set the location of your resource definition file
- Earlier in this tutorial, you copied the resource definition file,
dfhdrdat , from the
Enterprise Developer installation area to your project area. Now you need to tell the ESACCTCL
region where to find that file.
- Click
CICS in the taskbar at the top of the properties pane to access the
CICS Configuration settings.
- In the
Resource Definition File Path field, type:
$IDE_PROJECT_LOC\system
- Click
Apply .
- Configure the TN3270 listener
- The endpoint address for the TN3270 listener defines the port number used when you connect to the
enterprise server region using the
Host Access for the Cloud TN3270 emulator.
- Click
This takes you to the
Communications Server Properties page.
- Scroll down to the
Listeners section.
- Click
(Edit) on the row of the
TN3270 listener.
- In the
Hostname or IP Address field, type
*.
- In the
Port field, type
5239.
- Click
Apply.