Micro Focus Enterprise Developer 3.0 for Visual Studio 2017 > Programming > Mainframe Programming > JCL Support > Micro Focus Batch Scheduler Integration > Configuring the Server

Configuring the Server

The MFBSIEMX module must be defined as an Event Manager user exit and the variable MFBSI_DIR must be specified similar to that shown in the Configuration Information field as shown next:

Where:

ES_EMP_EXIT_n - n must be a number ranging from 1 to 9, based on the number of Event Manager user exits for the region:
- This should be set to 1 if MFBSIEMX is the only Event Manager user exit for the region.
- When multiple Event Manager user exits are defined, they must be specified in a sequence starting with ES_EMP_EXIT_1 - for example:
```
ES_EMP_EXIT_1=mfbsiemx
ES_EMP_EXIT_2=mfmonemx
ES_EMP_EXIT_3=...
```
mfbsiemx must be in lowercase on UNIX and Linux environments.
MFBSI_DIR identifies the base folder to be used by MFBSI. This is the folder where the MFBSIJCL log files, any semaphore files (JOB#####.sem) and substituted JCL members are written into.

The MFBSIJCL component that is submitting jobs to the enterprise server requires the MFBSI_DIR environment variable with the same folder setting.

There are two ways to specify MFBSI_DIR for a specific enterprise server region:

By specifying a folder that has the name of enterprise server region as the last part of the MFBSI_DIR path - this is the Micro Focus-recommended way and the easiest way to configure MFBSI_DIR.
Note: This was the only way to configure MFBSI_DIR in previous releases of this product. Starting with the 3.0 release of Enterprise Developer and Enterprise Server, this constraint has been relaxed.

Alternatively:
You can set MFBSI_DIR to any path on your file system. In this case, you must specify the target region name either on the MFBSIJCL command line (by specifying REGION=ESRegionName) or in the configuration file (on a line that starts with REGION=ESRegionName).

See the following examples of how to specify MFBSI_DIR:

Important:

Ensure that the Enterprise Server admin user and the user authority which runs MFBSIJCL have a write access to the MFBSI_DIR location.
MFBSI_DIR supports long and spacey folder names. However, Micro Focus recommends that you avoid them.

Micro Focus recommends that you use the default settings for MFBSIJCL to specify the region name as part of MFBSI_DIR:

To set MFBSI_DIR to a path that ends up with a folder that has the same as the enterprise server region name and with the default settings for MFBSIJCL:

set MFBSI_DIR=x:\MF\…\MFBSI\ESRegionName

To set MFBSI_DIR to any folder:

To specify the region name at the MFBSIJCL command line, execute:
```
set MFBSI_DIR=x:\MF\...\MYDIR
mfbsijcl ...  REGION=ESRegionName
```
To specify the region name in the default mfbsi.cfg file:
1. Ensure mfbsi.cfg includes the following line:
```
REGION=ESRegionName
```
2. Set MFBSI_DIR to the location of mfbsi.cfg:
```
set MFBSI_DIR=x:\MF\...\MYDIR
```
To specify the region name in a custom configuration file, custom.cfg, located in x:\MF\...\MFBSICFG\:
1. Ensure custom.cfg includes the following line:
```
REGION=ESRegionName
```
2. Set MFBSI_DIR as follows:
```
set MFBSI_DIR=x:\MF\...\MYDIR
```
3. Specify the custom configuration file when executing MFBSIJCL as follows:
```
mfbsijcl ... CFG=x:\MF\...\MFBSICFG\custom.cfg
```
  Or, without specifying the CFG parameter:
```
mfbsijcl ...
export MFBSI_CFG=x:\MF\...\MFBSICFG\custom.cfg
```

After making these settings in the region configuration, restart the server and check the console log for the message CASAM3006I/CASAM3001I to verify successful initialization of MFBSIEMX. Log entries are similar to:

CASAM3006I Event Filter for (mfbsiemx) has been enabled. Filter string: "1:1,3&3:*&4:1,2"
CASAM3001I Event Manager exit enabled (mfbsiemx)

Server initialization creates a file named ESRegionName.Started in the MFBSI_DIR location. When the server shuts down, a file named EESRegionName.Shutdown replaces this file (where ESRegionName is the name of the region being used.

In order to restart any submitted jobs, you need to add some additional configuration settings in your enterprise server instance - see Job Restart.