Use the configLoader utility to load mediation specification files into ECE. These files are used by Diameter Gateway and RADIUS Gateway. See ECE Implementing Charging and "Configuring the configLoader Utility".

Location

ECE_home/bin

Syntax

{start|stop} configLoader {-help}

Parameters

-help

Displays the syntax for this utility.

Results

Results are written to the ECE_home/logs/configLoader.log file.

Use the customerLoader utility to load customer data incrementally into ECE, in batches or in bulk. See ECE Implementing Charging.

Location

ECE_home/bin

Syntax

{start|stop} customerLoader [-incremental customerupdaterfilename] [-help]

Parameters

start

Starts customerLoader.

stop

Stops customerLoader.

-incremental customerupdaterfilename

Incrementally loads customer data. Use this parameter to selectively synchronize the BRM database and the ECE cache. This is typically done to manage data migration errors.

-help

Displays the syntax for customerLoader.

Results

Results are written to the ECE_home/logs/customerLoader.log file

To verify that the customer objects were loaded in the ECE cluster distributed cache, use the query tool to form CohQL queries on the cache name that stores the respective object. For example, you would look in the Customer cache.

Use the encrypt.sh utility to encrypt passwords that ECE uses for connecting to BRM and Pricing Design Center (PDC).

For more information, see "About Managing External Application Passwords".

Location

ECE_home/bin

Syntax

encrypt.sh string storepassword [-help]

Parameters

string

Specifies the new password to encrypt.

storepassword

Specifies the password to the keystore.

-help

Displays the syntax for this utility.

Results

The utility returns a message containing the encrypted value for the new password.

Results are written to the ECE_home/logs/encrypt.log file.

Use the events_propagate_utility.pl utility to propagate failed customer data updates from the suspense queue to the BRM Oracle DM database queue.

For more information, see "Managing Failed Customer Data Updates".

Location

ECE_home/brm_utils/

Copy events_propagate.sql and events_propagate_utility.pl from the ECE installation directory (ECE_home/brm_utils/) to your BRM machine (for example, BRM_home/sys/test/).

Syntax Overview

The following actions are supported for events_propagate_utility:

• Syntax for Moving Events from Suspense Queue

• Syntax for Listing All Queues

• Syntax for Loading Data into Database

• Syntax for Purging Data from the Queue

• Syntax for Getting Help

Syntax for Moving Events from Suspense Queue

Moves events from the suspense queue to the BRM Oracle DM database queue.

perl events_propagate_utility.pl move -s queue_name -d queue_name [-l user_id@connection] 
                                      -n number_of_events

Parameters for Moving Events from the Suspense Queue

The following parameters are used to move events from the suspense queue to the BRM Oracle DM database queue:

-s queue_name

Specifies the suspense queue name.

-d queue_name

Specifies the BRM Oracle DM database queue name.

-l user_id@connection

Provides the user ID and connection for connecting to the database. If not provided, the script prompts for them. The script always prompts for the password.

-n number_of_events

Specifies the number of events that are being moved from the suspense queue.

Syntax for Listing All Queues

Lists all queues on a BRM machine.

perl events_propagate_utility.pl list [-l user_id@connection] 

Parameters for Listing All Queues

The following parameters are used to list all queues on a BRM machine:

-l user_id@connection

Provides the user ID and connection for connecting to the database. If not provided, the script prompts for them. The script always prompts for the password.

Syntax for Loading Data into Database

Loads data from the queue into the database.

perl events_propagate_utility.pl load [-l user_id@connection] 

Parameters for Loading Data into Database

The following parameters are used to load data into the database:

-l user_id@connection

Provides the user ID and connection for connecting to the database. If not provided, the script prompts for them. The script always prompts for the password.

Syntax for Purging Data from the Queue

Purges data from the suspense queue or BRM Oracle DM database queue.

perl events_propagate_utility.pl purge [-l user_id@connection] -q queue_name 

Parameters for Purging Data from Queues Events

The following parameters are used to purge data from the suspense queue and the BRM Oracle DM database queue:

-l user_id@connection

Provides the user ID and connection for connecting to the database. If not provided, the script prompts for them. The script always prompts for the password.

-q queue_name

Specifies the queue name on which data is purged.

Syntax for Getting Help

Displays the syntax for the events_propagate_utility script.

perl events_propagate_utility.pl help

Results

The events_propagate_utility script notifies you when it runs successfully. Otherwise, look in the logs.

Location

ECE_home/bin

Syntax

[-help] gridSync {start|stop|pause|replicate} [remoteClusterName]

Parameters

-help

Displays the syntax.

start

Starts the federation service to replicate the ECE cache data to the backup or remote production sites.

stop

Stops replicating ECE cache data to the backup or remote production sites.

pause

Pauses replication of ECE cache data to the backup or remote production sites.

replicate

Replicates all the existing ECE cache data to the backup or remote production sites.

remoteClusterName

Specify the name of the Coherence cluster in the backup site.

Results

Results are written to the ECE_home/logs/encrypt.log file.