To allow BRM components to communicate with each other, you use entries in configuration or properties files. The basic connection entries in the files identify the host names and port numbers of each component.

These connection entries are set when you install BRM and when you install each client application. You can change them if you change your configuration. Depending on how you install BRM, you might have to change some entries to connect BRM components.

Figure 13-1 shows how entries in configuration files link components.

In Figure 13-1, the client application is a utility that uses a configuration file entry to point to the CM. (A Java client has a similar entry in its properties file.) The following sample entry includes the CM host name, CM_System, and port number, 11960:

cm_ports    ip    CM_System    11960

The CM configuration file has corresponding entries:

• The cm_name entry identifies the host name as CM_System

  - cm    cm_name    CM_System

• The cm_ports entry identifies the port number as 11960:

  - cm    cm_ports    11960    pin

The CM configuration file includes an entry that points to the DM. This entry includes the DM host name and port number:

- cm    dm_pointer    0.0.0.1    ip    DM_System    11950

The DM configuration file includes corresponding information:

• The dm_name entry identifies the host name as DM_System. This entry is optional: if you remove or disable it, BRM uses gethostname to find the IP address of the DM computer:

  - dm dm_name DM_System

• The dm_port entry identifies the port number as 11950:

  - dm dm_port 11950

The DM configuration file specifies the database number, which is in 0.0.n.n / 0 format:

- dm dm_db_no 0.0.0.1 / 0

Queue Manager (QM) components (for example, LDAP Manager) use the same types of configuration entries, but they have different names. For example, instead of dm_max_fe, the entry is named qm_max_fe.

The QM configuration files include the following entry:

• The qm_port entry identifies the host address and the port number:

  - qm_process qm_port host_name port [tag_number]

  where:

  • qm_process is the system process such as dm_ldap, dm_email, dm_fusa, dm_vertex, cm_proxy, and dm_invoice.

  • host_name is the host name or the IP address where the system process is deployed.

  • port is the port number.

  • tag_number is a sequential number that identifies the host_name and port pair. You use this parameter when configuring multiple qm_port entries.

There are additional entries in configuration files, but these entries are the most basic. For more information on connection entries in configuration files, see the comments in the configuration files.

The configuration and properties files specify identifying numbers for databases and DMs. The default numbers, listed in Table 13-1, are systematic to make numbers relatively easy to maintain and extend.

The DM numbers are in the form A.B.C.D. Make the number assignments meaningful as follows:

• Use A to separate divisions of your company (use 0 if you have none).

• Use B to distinguish different BRM installations (use 0 if you have only one).

• Use C to indicate the type of DM. For example:

  • 0 for data

  • 1 for transaction processing of credit or debit card

  • 2 for email

  • 3 for taxation

    Note:

    Start numbering your custom DMs at 100, such as 0.0.100.1.

• Use D to indicate the instance of a particular DM division, installation, or type.

  Table 13-1 Database and Port Number Entries

  Program	Database Number	Port Number
  Oracle DM (dm_oracle)	0.0.0.1	12950
  Second Oracle DM for a multischema system (dm_oracle)	0.0.0.2	12951
  Each additional dm_oracle for multischema systems	0.0.0.n	12950 + (n – 1)
  Paymentech data manager for credit card, dm_fusa	0.0.1.1	12810
  Paymentech data manager for direct debit, dm_fusa	0.0.1.2	12810
  Each additional dm_fusa	0.0.1.n (n > 2)	12813+
  Email notification manager: dm_email	0.0.2.1	12821
  Each additional dm_email	0.0.2.n	12820 + n
  Activity Log Data Manager of a BRM satellite: dm_opstore	0.0.4.1	12841
  Each additional dm_opstore	0.0.4.n	12840 + n
  LDAP: dm_ldap	0.0.5.1	12851
  Each additional dm_ldap	0.0.5.n	12850 + n
  Wireless Provisioning DM, dm_prov_telco	0.0.10.2	10970
  Connection Manager (CM) or Connection Manager Master Process (CMMP)	NA	11960
  Each additional CM or CMMP	NA	11960 + n
  Credit-card or online-processing batch simulators (answer_b)	NA	5678
  Credit-card or online-processing online simulators (answer_s)	NA	5679

Use the following DM pin.conf file entries in Table 13-2 to connect a DM to the BRM database. These entries are used by multiple DMs, such as the Oracle DM.

Some BRM utilities, such as load_tax_supplier, require you to create a configuration file to tell the utility how to connect to the BRM system. The configuration file must be in the same directory as the utility executable file.

To create a configuration file for a utility:

1. Copy the sample configuration file in BRM_home/source/apps/sample.

   Use this file, which contains all of the configuration entries needed for connecting to BRM, as a template for any utility configuration file.

2. Edit the configuration entries to reflect your BRM environment. Follow the guidelines in the configuration file.

3. Save the file as pin.conf in the directory with the utility executable file.

Table 13-3 shows the common utility pin.conf entries:

In addition, the pin.conf entries in Table 13-4 are used by multithreaded application (MTA) utilities:

BRM supports Internet Protocol Version 6 (IPv6) and Version 4 (IPv4) addressing.

When entering an IPv6 address in the IP address fields of the BRM client applications, enter the normalized form of the IPv6 address; for example, 2607:f0d0:1002:0051:0000:0001:0000:00ff.

For example, if the IPv6 Address is 2001:db8::8a2e:370:7334, its normalized form will be 2001:0db8:0000:0000:0000:8a2e:0370:7334.