Configuring QuerySurge Connections: Oracle
When you create a QuerySurge Connection, the Connection Wizard will guide you through the process. Different types of QuerySurge connections require different types of information.
For an Oracle Connection, you will need the following information (check with a DBA or other knowledgeable resource in your organization):
- Database login credentials (ID and Password)
- Server Name or IP address of the Oracle Server (e.g. oracle1.myserver.com, or 192.168.0.255)
- The port for your Oracle database (1521 is the default port)
- The Oracle Service Name
Launch the Connection Wizard
- Log into QuerySurge as a QuerySurge Admin user.
- To configure a Connection, select Configuration > Connection in the Administrative View tree (at the left).
- Click on the Add button at the bottom left of the page to launch the Connection Wizard. Click Next.
Note: Using the Connection Wizard Advanced Mode, you can use the Wizard to build Connections using the Oracle SID or Oracle TNS syntax with the Oracle Service Name. Details are available here.
- Provide a name for your connection. Select Oracle as the Data Source. Click Next.
Note: An Oracle JDBC driver is bundled with QuerySurge, so you can install this driver from the QuerySurge Installer.
- Once you have selected your Data Source, the Wizard will tell you what information you are likely to need in order to create your Connection. Once you have collected this information, you are ready to click Next.
- Provide the connection information to your database. This includes the Server name or IP address, the port (the default port for your database product will automatically populate), the Oracle Service Name and the login credentials. Click Next.
Required fields for your Connection are marked by an *.
- Click on Test Connection.
Note: You must have an Agent running with the driver for this Connection deployed in order to test the Connection.
- Save the Connection.
- Congratulations! You’ve created a QuerySurge Connection. Make sure that you have deployed the driver for this Connection to all your QuerySurge Agents. (See Adding a JDBC Driver to your QuerySurge Agent for instructions.)