RPS Datapump Application

The RPS Datapump application JadeRpsDataPump runs on the RPS node from the schema in which the RPS mapping is defined. It connects to the RDBMS database and applies transactions to it, implementing the incremental object replication.

You can specify a non-GUI user-defined Datapump application that assumes the data pump role, by specifying the appropriate values in the Schema and Application combo boxes in the Data Pump Application group box on the Configure RPS Node dialog on an RPS node. (For details, see "Configuring your RPS Node", later in this chapter.)

The user-defined Datapump application can be used to set up the application and global environment needed to execute column-mapping methods. The user-defined Datapump application must call the Application class rpsDataPumpInitialize method from its initialize method. This method registers the callbacks required to implement incremental object replication. It must also call the Application class rpsDataPumpFinalize method from its finalize method to perform any terminate functions for the Datapump application.

When you specify a user-defined Datapump application, any objects required for application start-up and user validation must be present in the RPS system, which may require the RPS system to be Full database replication mode. For example, if the system uses packages, the global instance of the schema from which the package is imported must be present for the application to start up.

To identify whether a process is executing as a Datapump application on an RPS node, call the Process class isUserDataPump method, which returns true if the process is executing as a Datapump application; otherwise false.

The Datapump application is initiated in the schema in which the RPS mapping is located, so that the packages are initialized and context-switching occurs if imported methods are called on the imported class.

The following actions start the RPS Datapump application.

Automatic startup.

Check the Auto Start Datapump check box on the Configure RPS Node dialog on the RPS node. (For details, see "Configuring your RPS Node", later in this chapter.)

To allow the Datapump application to be started automatically, it must be able to log on to the RDBMS without user intervention. In SQL Server, you can accomplish this by running the RPS node under a Windows login that has the required access rights and database permissions and then setting the DSN properties appropriately.

Programmatically, by calling the JadeDatabaseAdmin class rpsStartDataPump method, which must be run on an RPS node.

Manual startup.

Select the Start Datapump command in the RPS menu in the Jade RPS Manager window. (For details, see "Starting the Data Pump" under "Using the RPS Manager Application", later in this chapter.)

Extracting data from and loading data into the relational database.

This allows a user-defined Datapump application to initialize global and app for column‑mapping method values and allows package initialization for imported classes.

On startup, the Datapump application checks that the:

RPS node database type is compatible with the RDBMS database that is being used; for example, if the RPS mapping is to SQL Server 2008 or later and the RDBMS database is SQL Server 2005, an error prevents the Datapump application from running.

RPS node database type is compatible with the ODBC driver being used; for example, if the mapping is SQL Server 2008 or later, the SQL Server 2008 or later Native Client ODBC driver must be used.

Control information from the JADE database matches the control information in the RDBMS database. If it does not, check the connection information to ensure that the correct database is being used.

To resynchronize the database, see "Resetting the Relational Database Identifier", later in this chapter.

Table and columns defined in the RPS mapping match the RDBMS database. If they do not, correct the RDBMS database and restart the Datapump application.

To stop the Datapump application, select the Stop Datapump command from the RPS menu in the Jade RPS Manager window. (For details, see "Stopping the Data Pump" under "Using the RPS Manager Application", later in this chapter.) In addition, you can stop the Datapump application programmatically, by calling the JadeDatabaseAdmin class rpsStopDataPump method.

JADE does not initialize any packages for RootSchema applications running in user schemas, including the default RPS Datapump application in the RootSchema. If you require this initialization, you must initialize packages in your application code (using the Process class initializePackages and finalizePackages methods).

For details about specifying the location of errors file created when the Datapump application on an RPS node terminates abnormally, see "Fault Handling when the Datapump Application Terminates Abnormally", later in this chapter.

The [JadeRps] section of the JADE initialization file contains parameters that enable you to control the timeout occurring between an RPS server and an SQL Server. These parameters are read when Datapump application is started.

Parameter	Specifies the number of seconds to wait for…
ConnectionTimeout	Connection between an RPS server and an SQL server. The default value is 15 seconds. Specify zero (0) if you do not want the connection to time out.
LoginTimeout	Log-in to the SQL server from the RPS server. The default value is 15 seconds. Specify zero (0) if you do not want the log-in to time out.
QueryTimeout	A query result. The default value is 60 seconds. Specify zero (0) if you do not want the query to time out or -1 to not make the query call to set time out (which saves a call to the SQL Server).

Parameter

Specifies the number of seconds to wait for…

ConnectionTimeout

Connection between an RPS server and an SQL server. The default value is 15 seconds. Specify zero (0) if you do not want the connection to time out.

LoginTimeout

Log-in to the SQL server from the RPS server. The default value is 15 seconds. Specify zero (0) if you do not want the log-in to time out.

QueryTimeout

A query result. The default value is 60 seconds. Specify zero (0) if you do not want the query to time out or -1 to not make the query call to set time out (which saves a call to the SQL Server).