Registration for diagram and stream
Describes registering Diagrams and Streams.
1. Stream registration entry points
Upon initial login, the users will see the Replication Diagram page.
At this point, the users can register a stream through the Stream Registration button in the top right corner.
2. Stream registration modal screen
Below is the modal first screen of the Stream installation, click the Next button to proceed to the next step.
3. Enter stream information
Enter the name the users want to register as a stream, the SRC DB to register, and the information of the TAR DB.
Stream Name
Stream name
DB Type
Type of each DB (Tibero / Oracle)
DB Name
Connection name of each DB
IP
Connection ip of each DB
Port
Connection port of each DB
Monitoring User Name
Username of the Monitoring User created in each DB
Monitoring User Password
User password of Monitoring User created in each DB
4. DB Connection Check
Check the connection of each DB based on the information created in Stream Information, and check the cluster status and number of nodes.
If any DB fails to connect, the users cannot proceed to the next step.
4.1. Additional Database Information
If each SRC/TAR DB is a cluster, the users need to enter additional information because the information about the remaining nodes are required. At this point, the users don't need to enter the Monitoring User Name and Password again, as the previously entered information is fixed.
And it is mandatory to perform a Connection Check for each Node.
When the users press the Connection Check button, the users should see a green Confirm text to indicate success, and all Connection Checks should be executed and successful for each Node.
5. Additional Information
Enter the Agent Process information that the users want to connect to the Stream the users want to register.
Information about the installed agents can be found in the prs_instance.map file in the $PRS_HOME/config path.
Add Agent
tA button to add an agent information input list.
Agent Id
Agent id of the agent that the users want to register with the stream
IP
Agent ip of the agent that the users want to register with the stream.
Port
Agent port of the agent that the users want to register with the stream.
The users can see the header of the list and the Delete button in each list.
The Delete button in the header resets the input and list count for all lists, and the Delete button in each list deletes the corresponding list.
6. Replication Diagram
Select the Diagram for which the users want to register the Stream.
Create New Replication Diagram
Select when the users want to create a new diagram.
Enter the name of the diagram the users want to create.
Insert into an Existing Replication Diagram
Select to select a diagram that is already registered.
Select the Diagram the users want to register.
7. Complete Stream Registration
If Stream registration was successful, the users'll see this screen.
Click the Next button to proceed with the Instance installation and registration. If the users don't want to, they can stop the step by clicking Cancel or the modal's top-right X button, but since the basic unit of synchronization in ProSync is the Instance, it is recommended that the users complete the Instance installation (registration) after registering the Stream.
If the Stream registration fails, the users can go back to the previous step via the Prev button and edit the information to register again.
Below is an example of a Stream registration failure.
8. Main screen after completing Stream and Diagram registration
After successful Stream registration, the users can see the successful registration on the main screen as shown below.
However, Diagram and Stream exist to understand the configuration and flow of synchronization, so if the users do not install and register an instance, the Status is Empty and synchronization does not proceed.
Instances must be installed in order for the synchronization to proceed and the status to be known.
Caution
There can only be one Stream in the same direction with the same Source - Target Database combination.
In other words, if a Stream with DB A as the source and DB B as the target already exists, the users cannot configure another Stream in the same direction (DB A → DB B).
However, Streams in the opposite direction (DB B → DB A) can be configured separately.
Last updated