The table below describes the function of each field.

Follow these steps to add a new node. Repeat this procedure for each SLC on the system.

1. If the fields on the All Nodes tab are populated with node data, click Clear.

2. In the Node Name field, enter the name of the new node (required).

3. Note: To ensure you can view statistics for the node, the node name must match the host name exactly.

4. In the IP Address field, enter the IP address of the node (required).

5. In the Description field, enter a description of the node (optional).

6. Click Save.

7. Result: The new Node details are saved to the database.

Follow these steps to change a node.

1. On the All Nodes tab, find the required node. See Using the Find Screens.

2. Change the details of the node as required.

3. Note: If you change the IP address of the node, you will create a new node. The original node will remain.

4. Click Save.

5. Result: The changes will be saved to the database.

Follow these steps to delete an existing node record.

1. On the All Nodes tab, find the required node. See Using the Find Screens.

2. Click Delete.

3. Result: You will see a delete confirmation prompt.

4. Click OK.

5. Result: The record will be deleted from the database.

Note: You cannot delete a node if there are references to it within SMS.

The table below describes the function of each field.

Check each SMS node has all of the following:

• Valid primary address (or hostname)

• Node Number of 1-16 (there must be at last one SMS node with 1 as its node number)

• Validator option selected

Each SLC has two node numbers associated with it:

• One in the range 17 to 255 for the inferior master (in an unclustered configuration)

• One in the range 256 to 511 for the update loader.

Each inferior master should have:

• Valid primary address (or hostname)

• Node Number in the range 17 to 255

• Empty Validator option.

Each update loader should have:

• Valid primary address (or hostname)

• Node Number in the range 256 to 511 (the node number of update loaders should start with 301 and work upwards)

• Empty Validator option.

Follow these steps to add a new replication node. Repeat this procedure for each SLC on the system.

1. If the fields on the Replication Nodes tab are populated with node data, click Clear.

2. In the Node Number field, enter the number of the node.

3. From the Primary Node IP Address drop down box, select the IP address for the primary node.

4. If you will be replicating on more than one platform, select the secondary node from the Secondary Node IP Address drop down box.

5. In the Description field, enter a description of the replication node.

6. If this replicator node is an smsMaster, select the Validator check box.

   In all other circumstances ensure the Validator check box is deselected.

7. Click Save.

   Result: The details will be saved to the database.

Follow these steps to change a replication node.

1. On the Replication Nodes tab, find the node to edit. See Using the Find Screens.

2. Change the details of the node as required.

3. Click Save.

   Result: The changes are saved to the database.

Follow these steps to delete an existing replication node.

1. On the Replication Nodes tab, find the node to delete. See Using the Find Screens.

2. Click Delete.

   Result: The confirmation prompt will appear.

3. Click OK.

   Result: The record will be deleted from the database.

Note: You cannot delete a node if there are references to it within the SMS.

A filter allows certain preselected table groups to be extracted from a block-selection. This is essential as a block-selection will select all the table groups from any table having multiple table groups, whereas only one may be selected per table.

Filters are used to define node types which allow block-creation of nodes identical in terms of their replication groups.

When allocating replication groups to nodes, either as block selections or individual sub-groups, it is important to note any inter table dependencies.

A dependency arises when a table has a foreign key from another table. This requires that both tables must be selected for replication. The tables may be selected at the same time and need not be selected in any particular order. If a dependency is not fulfilled, the User will be prompted to add it to the selection retroactively.

This table describes the function of each field.

A replication table has one or more replication groups. A replication group can be assigned to one or more replication nodes.

Example:

• Replication Group A resides on Node 1, Node 2 and Node 3

• Replication Group B resides on Node 1 and Node 3

Primary nodes can be defined for a specific replication group. The primary is the highest priority destination node for the data defined in the replication group. This enables the IN to assign particular services to specific nodes, but still provide a failover to other nodes as required.

This only sets the node as the primary for the specific group involved and is independent of other groups. A node may be defined as a primary for one group without being a primary for another group.

Example:

• Replication Group A resides on Node 1, Node 2 and Node 3, where Node 3 is the primary for group A.

• Replication Group B resides on Node 1 and Node 3, where Node 1 is the primary for group B.

Primary nodes are not required unless a service is running with different priority on different nodes.

This table describes the function of each button specific to this screen.

Follow these steps to allocate a new replication group using the Table Replication tab.

Note: You can also use the Replication Node Types tab to allocate replication groups.

1. On the Table Replication tab, click Clear.

2. Expand the tree in the Allocated Replication Groups box to the required node name and select it.

   Result: The group list specific to the selected node will be displayed in the Available Replication Groups box.

3. Expand the tree in the Available Replication Groups box.

   Result: This displays the lower sub-groups.

4. Click on the group name in the Available Replication Groups list to select it.

   Notes:

   • To select multiple groups at table, module or application root level, press and hold the Ctrl key while selecting.

   • To select a block of groups, hold press and hold the Shift key while selecting.

5. Keeping the mouse depressed, drag the icon across to the Allocated Replication Groups list. Drop on the required node name by releasing the mouse button.

   Result: The replication group will be displayed under the selected node.

6. If a multiple selection is made, assign a common filter to the replication group on the Node Type Filter Selection screen.

7. Select the node type from the drop-down list.

8. Click OK.

   Result: The replication group will be allocated to the selected node, if there are no dependencies on unselected replication groups.

9. If dependencies exist, the Missing Dependency screen will prompt you to add the dependent group.

10. Click Yes.

    Result: The dependent replication group will also be added under the node.

11. Click Save.

    Result: The details will be saved to the database.

Follow these steps to configure the statistics replication group.

1. In the Table Replication tab, Available Replication Groups box, under SMF_STATISTICS_DEFN, select the replication group for each application on the platform.

   Note: The SMF_STATISTICS_DEFN group contains all definitions.

2. Select the target node, for example SLC, for the application.

3. Click Add to allocate the group to the node name.

   Result: The statistics replication group will be configured for the application.

4. Repeat steps 1 through 3 for each application, if required.

5. Click Save.

6. Click Create Config File.

   Result: The Replication Confirmation prompt will appear indicating that the replication.config file has been created.

7. Click OK.

Follow these steps to change the primary status of an allocated group:

1. In the Table Replication tab, expand the tree in the Allocated Replication Groups box.

   Result: This displays the lower sub-groups.

2. Click on the group name in the Allocated list. Keep the mouse button depressed.

   Notes:

   • To select multiple groups at table, module or application root level, press and hold the Ctrl key while selecting.

   • To select a block of groups, hold press and hold the Shift key while selecting.

3. Click the right mouse button.

   Result: A pop-up menu will appear.

4. Select Set/Clear Primary.

   Result: The primary flag will be associated to the allocated replication group.

   If the primary flag is already associated to the allocated replication group, it will be removed.

5. Click Save.

   Result: The details will be saved to the database.

6. Click Create Config File.

   Result: A Confirmation prompt will appear.

7. Click OK.

   Note: If there are problems with this replication then the system will display an error message. If this occurs, see Service Management System Technical Guide.

Follow these steps to delete an allocated group.

1. In the Table Replication tab, expand the tree in the Allocated Replication Groups box.

   Result: This will display the lower sub-groups.

2. Click on the required group name in the Allocated list and right-click to view the menu options.

3. Click Delete.

   Result: The selected replication group will be removed from under the node.

4. If dependencies exist, the Delete group dependency violation warning will display a list of the dependent groups.

5. Select all listed dependencies and repeat steps 2 and 3.

   Result: The selected replication groups and their dependencies will be removed from under the node.

6. Click Save.

   Result: The details will be saved to the database.

7. Click Create Config File.

   Result: A Confirmation prompt will appear.

8. Click OK.

   Note: If there are problems with this replication then the system will display an error message. If this occurs, see Service Management System Technical Guide.

Do not delete allocated groups from the VWS. The VWS replication node is configured automatically when a billing engine is added on the CCS BE Configuration Screen. For more information, see Charging Control Services User's Guide.

This table describes the function of each field.

Follow these steps to add a new node type filter:

1. In the Replication Node Types tab, click Clear.

2. In the New Node Type field, enter the name of the new node type (required).

3. Click New Type to allocate the selected replication group to the required node name.

   Result: The replication group will be displayed under the selected node.

   Note: If the specified node type already exists, it cannot be added again.

4. Click Save.

   Result: The details will be saved to the database and the Save Complete message is displayed.

5. Click OK.

   Note: If there are problems with this replication then the system will display an error message. If this occurs, see Service Management System Technical Guide.

Follow these steps to delete a node type filter.

1. In the Replication Node Types tab, click Clear.

2. Expand the tree in the Allocated Replication Groups box to required node and right-click to view the menu options.

3. Click Delete.

   Result: The selected node type filter will be removed.

   Note: If dependent/children groups exist, the node type filter will not be deleted until the dependencies are deleted.

Follow these steps to allocate a new replication group using the Replication Node Types tab.

Note: You can also use the Table Replication tab to allocate replication groups.

1. In the Replication Node Types tab, click Clear.

2. Expand the tree in the Allocated Replication Groups box to the required node name and select it.

   Result: The group list specific to the selected node will be displayed in the Available Replication Groups box.

3. Expand the tree in the Available Replication Groups box.

   Result: This displays the lower sub-groups.

4. Click on the group name in the Available Replication Groups list to select it.

   Notes:

   • To select multiple groups at table, module or application root level, press and hold the Ctrl key while selecting.

   • To select a block of groups, hold press and hold the Shift key while selecting.

5. Click Add to allocate the selected replication group to the required node name.

   Result: The replication group will be displayed under the selected node.

6. If a multiple selection is made, assign a common filter to the replication group on the Node Type Filter Selection screen.

7. Choose Node Type from the drop-down list.

8. Click OK.

   Result: The replication group will be allocated to the selected node, if there are no dependencies on unselected replication groups.

9. If dependencies exist, the Missing Dependency screen will prompt you to add the dependant group.

10. Click Yes.

    Result: The dependant replication group will also be added under the node.

11. Click Save.

    Result: The details will be saved to the database.

Follow these steps to remove an allocated group using the Replication Node Type tab:

1. In the Replication Node Type tab, expand the tree in the Allocated Replication Groups box.

   Result: This displays the lower sub-groups.

2. Click on the group name in the list to select it.

   Note: To select multiple groups at table, module or application root level, press and hold the Ctrl key while selecting.

   To select a block of groups, hold press and hold the Shift key while selecting.

3. Click Remove to de-link the selected replication group from the node name.

   Result: The replication group will be removed from under the selected node, if there are no dependencies on unselected replication groups.

4. If dependencies exist, the Delete group dependency violation warning will display a list of the dependent groups.

5. Select all listed dependencies and repeat step 3.

   Result: The selected replication groups and their dependencies will be removed from under the node.

6. Click Save.

   Result: The details will be saved to the database.

   Note: If there are problems with this replication then the system will display an error message. If this occurs, see Service Management System Technical Guide.