Validated July 26, 2021 with OAC 6.1
Oracle Analytics instances may require a proxy to reach data sources for various reasons including security, routing and privacy. For use cases requiring sophisticated functionality, Oracle's Connection Manager provides database transparency, high-availability, protocol conversion and enhanced security, scalability and performance.
This post is a step-by-step guide for deploying Connection Manager on Linux with a simple starter configuration specifically for Oracle Analytics using Private Access Channel. It is part of the Oracle Analytics Private Access Channel Series. Refer here for a post for Oracle Analytics without Private Access Channel.
Refer to Understanding Oracle Connection Manager Architecture for details on the architecture shown below.
The primary uses of Connection Manager for Oracle Analytics are private egress, transparency, and protocol conversion.
Private Egress provides access to private databases.
Private Access Channel is the preferred method for private egress. This post is for Private Access Channel cases with complex data sources requiring a proxy. Real Application Clusters and Autonomous Databases on dedicated infrastructure are two such cases.
Transparency hides the details of connecting to unsupported databases or those with complex connection criteria. It allows users to think that they are connecting to a single-instance Oracle database using just a host, port, and service name. Connection Manager stores the connection complexities for all users and applications. When it receives a request, it connects to the target database for session creation. The database receives the actual user, application and network address for its session details.
Protocol Conversion converts TCP traffic to TCPS used by Autonomous Databases. This feature along with transparency further simplifies the user experience by hiding the need for Secure Socket Layer wallets and associated networking parameters. Connection Manager stores complex TCPS wallet placement and handshake parameters for all users and applications. When it receives a request, it forwards it on to the SSL-protected database for session creation.
Additional uses of Connection Manager are access control and anonymity.
Access Control provides solutions for database access when a database subnet allows ingress only from designated application subnets. A Connection Manager instance in such a subnet receives connection requests and connects to the databases on the application's behalf.
Anonymity builds on transparency by hiding the application from the database. The database only receives Connection Manager's proxy user and network address for its session details.
July 26, 2021 with OAC 6.1
May 25, 2021 with OAC 5.9
February 9, 2021 with OAC 5.9
Before You Begin
Deploying Required Components
Installing and Configuring Connection Manager
Validating Connection Manager
|OAC||Oracle Analytics Cloud|
|OCI||Oracle Cloud Infrastructure|
|FQDN||Fully Qualified Domain Name|
|PAC||Private Access Channel|
|OSN||Oracle Services Network|
|RAC||Real Application Clusters|
|DNS||Domain Name System|
|VCN||Virtual Cloud Network|
A user account in an OCI tenancy for managing compute and networking components.
A user account in an OAC instance for creating data visualization connections.
Domain Name System (DNS) provides a worldwide, distributed directory service for translating a fully qualified domain name (FQDN) to its associated numerical IP address.
The default DNS in OCI provides resolution for resource names within the same VCN. Refer here for a post describing various DNS scenarios and the components necessary to resolve resource names outside of your VCN.
The examples here have CMAN in the same VCN as OAC. Thus no DNS or Gateways are required.
A networking gateway is required to connect to a CMAN residing outside of OAC's VCN. Refer here for a post describing various gateway scenarios and the components necessary for network traffic between resources in different VCNs.
An existing OAC instance with PAC enabled with CMAN's domain defined as a data source.
The OAC cluster resides in the Oracle Services Network (OSN) with a public ingress endpoint and PAC private egress endpoints in its VCN.
The OAC has both a private ingress endpoint and PAC private egress endpoints in its VCN.
Note: The appendix contains a complete list of the commands shown in this post.
The following components are required before installing and validating CMAN.
|SUBNET||Hosts the CMAN instance||Link|
|COMPUTE INSTANCE||Hosts the CMAN application||Link|
|ACCESS RULES||Facilitates network traffic between OAC and CMAN||Link|
|PORT RULES||Allows network traffic to the CMAN listening port||Link|
The following tables show components both needed and previously deployed (greyed out).
This post uses OAC's VCN named VCN1.
Create or use an existing public subnet in the VCN chosen above. This post uses a subnet named APP-Subnet.
Create a small Linux instance to initially host CMAN in the APP-Subnet.
On your client prepare an SSH alias. If you do not have direct access to the CMAN's private IP address create another Linux instance with a public IP to act as a bastion.
Define egress and ingress rules for network traffic between OAC and CMAN.
|SECURITY LIST||TYPE||CIDR||PROTOCOL||PORT||ATTACHED TO||NOTE|
|VCN1-APP-SL||INGRESS||10.0.0.0/27||TCP||1521||VCN1-APP-SN||Ingress to CMAN from the OAC SN|
|VCN1-APP-SL||EGRESS||188.8.131.52/32||TCP||443||VCN1-APP-SN||Egress to YUM Repository for CMAN install|
|VCN1-OAC-SL||EGRESS||10.0.0.64/27||TCP||1521||VCN1-OAC-SN||Egress to CMAN subnet|
Refer to sections two and three in this post to install and configure CMAN.
Validating the introductory deployment of CMAN involves starting it and successfully connecting to it from OAC. Start CMAN using the Connection Manager Control Utility.
You see something like:
This section validates that CMAN is listening and that OAC can reach the listener. Saving the connection is not possible yet as we have not yet defined a database.
Click Create then Connection from the OAC home screen. Select Oracle Database as the Connection Type. Complete the dialog as shown in the example below.
Enter any Connection Name as this connection is not saved.
Accept Basic as the Connection Type.
Enter your CMAN FQDN as the Host.
Enter your CMAN Port e.g. 1521
Enter any Service Name
Enter any Username and Password
If OAC can reach the CMAN listener you see:
If OAC is unable to reach the CMAN listener you see:
Click Cancel to close the dialog.
PAC sends the connection request to CMAN. PAC's security rules allow the egress on port 1521 and CMAN's allow the ingress.
PAC'S flow is the same for both public and private OAC.
This post provided a step-by-step guide for deploying Connection Manager on Linux with a simple starter configuration specifically for Oracle Analytics using Private Access Channel. You are now ready to create a connection to a private data source using Connection Manager.
For other posts relating to analytics and data integration visit http://www.ateam-oracle.com/dayne-carley
Below are scrollable lists of commands used in this post. The client commands may be downloaded here or send them to your clipboard by clicking in the text area and then clicking the copy button.
Below is a scrollable list of all commands run on the CMAN host. The commands may be downloaded here.