Connect Oracle GoldenGate Microservices Architecture to Classic Architecture

To establish a connection to Classic Architecture from Microservices Architecture, the Distribution Service in Oracle GoldenGate Microservices Architecture must know where to place the remote trail file for reading.

To connect Oracle GoldenGate Microservices Architecture and Classic Architecture follow these steps:

Note:

For this procedure to work only the ogg protocol is supported and an existing Extract must be running in Microservices Architecture.

Task 1: Start Manager in Classic Architecture

1. Log in to GGSCI.

2. Use the command:

   START MANAGER

   For more information, see START MANAGER in Reference for Oracle GoldenGate.

Task 2: Add a Distribution Path

1. Launch the Distribution Service web interface.

2. Click the plus (+) sign next to Path. The Add Path page is displayed.

3. Enter the following details on the Add Path page:

   Table 15-3 Add Path Page Options

   Options	Description
   Path Name	Enter the name of the Distribution Path.
   Description	Enter the description of the Distribution Path.
   Source	Select Extract from the drop-down list. Enter the Extract name in the text box below it.
   Generated Source URI	Enter the location of the source trail file.
   Target	Select ogg as the target protocol from the drop-down list. Enter the following in the given order: Target Hostname: Name of the target host service to which the connection will be established. Target Manager Port: Port number of the Oracle GoldenGate Classic Architecture Manager port. Target sub-directory for the trail file: Name of the subdirectory where the trail file is to be stored. For example, .dirdat. Target trail file name: Name of the target trail file, such as ea.
   Generated Target URI	The location of the target trail file is displayed.
   Target Encryption Algorithm	Select NONE from the drop-down list. To encrypt the target trail file, select the appropriate encryption algorithm from the drop-down list.
   Enable Network Compression	Select this option if you want to enable network compression.
   Sequence Length	Select the required value from the drop-down list for target trail sequence length. The default value is 9.
   Trail Size (MB)	Specify the value of the trail file size, as per your requirements.
   Configure Trail Format	Select this option if you want the trail file in any of the following formats: TEXT SQL XML
   Encryption Profile	This is the encryption profile that was used to encrypt the trail file when it was generated. However, certain encryption methods are only available in Microservices Architecture and are not supported by Classic Architecture, so use this feature with caution.
   Target Type	Select Manager as the target type. Alternatively, you can select Collector or Receiver Service. When connecting Microservices architecture with other Microservices architecture, select the Receiver Service option. When connecting Microservices architecture with Classic architecture, select either the Manager or Collector option. If you select the Collector option, you need to start a static collector beforehand on the Classic architecture and use that static collector port as the value of the Target Manager Port field.
   Begin	Select the Position in Log option from the drop-down list.
   Source Sequence Number	Enter the sequence value of the source trail.
   Source RBA Offset	Enter the value of the RBA offset of the source trail if you want the path to start reading from a specific RBA.

4. Click Create Path or Create and Run, as required. Select Cancel if you need to get out of the Add Path page without adding a path.

After the path is created, you’ll be able to see the new path in the Distribution Service home page.