In this section: |
Configuring the adapter consists of specifying connection and authentication information for each of the connections you want to establish.
How to: Reference: |
The SET CONNECTION_ATTRIBUTES command allows you to declare a connection to one Hyperstage database server and to supply authentication attributes necessary to connect to the server.
You can declare connections to more than one Hyperstage database server by issuing multiple SET CONNECTION_ATTRIBUTES commands. The actual connection takes place when the first query referencing that connection is issued (see Overriding the Default Connection). You can include SET CONNECTION_ATTRIBUTES commands in an RPC or a server profile. The profile can be encrypted.
If you issue multiple SET CONNECTION_ATTRIBUTES commands:
You can configure the adapter from either the Web Console or the Data Management Console.
or
From the Data Management Console, expand the Adapters folder.
The Adapters folder opens.
The Add Adapter to Configuration pane opens.
The Hyperstage PG adapter is under the SQL group folder.
The following list describes the connection attributes for which you can supply values. To complete the attribute declaration, click the Configure button.
Logical name used to identify this particular set of connection attributes. The default is CON01.
Enter the location URL for the Hyperstage data source. The basic syntax is
jdbc:postgresql://host:port/database
where:
Is the computer name or IP address on which the Hyperstage database is located.
Is the port number used to access the Hyperstage database
Is the name of the database.
These are two examples:
jdbc:postgresql://localhost:8101/qatst
jdbc:postgresql://edaaix52:8101/qatst
Name of the JDBC driver: org.postgresql.Driver
The full path name to the Hyperstage installation directory. For example, C:\ibi\srv77\home\hs.
The full path name to the Hyperstage Tools directory. For example, C:\ibi\srv77\home\hs\bin.
There are two methods by which a user can be authenticated when connecting to a database server:
Primary authorization ID by which you are known to the data source.
Password associated with the primary authorization ID.
Select a profile from the drop-down menu to indicate the level of profile in which to store the CONNECTION_ATTRIBUTES command. The global profile, edasprof.prf, is the default.
If you wish to create a new profile, either a user profile (user.prf) or a group profile if available on your platform (using the appropriate naming convention), choose New Profile from the drop-down menu and enter a name in the Profile Name field (the extension is added automatically).
Store the connection attributes in the server profile (edasprof).
The Hyperstage adapter is under the SQL group folder.
The following list describes the connection attributes for which you can supply values. To complete the attribute declaration, click the Configure button.
Logical name used to identify this particular set of connection attributes. The default is CON01.
Enter the location URL for the Hyperstage data source. The basic syntax is
jdbc:mysql://host:port/database
where:
Is the computer name or IP address on which the Hyperstage database is located.
Is the port number used to access the Hyperstage database
Is the name of the database.
These are two examples:
jdbc:mysql://localhost:8101/qatst
jdbc:mysql://edaaix52:8101/qatst
You can reference additional Hyperstage connection properties in the URL. If you wish to do so, follow these guidelines: in the URL the first property must be preceded by the ? character, and the second and subsequent properties referenced in the URL must be preceded by the & character followed immediately by an | character, as illustrated in the following example.
Suppose that you wish to add the following connection properties:
sessionVariables=sql_mode=PIPES_AS_CONCAT zeroDateTimeBehavior=convertToNull
Enter the URL as follows:
jdbc:mysql://host/database?sessionVariables=sql_mode=P IPES_AS_CONCAT&| zeroDateTimeBehavior=convertToNull
Note: The URL must be entered as a single line, without a space after the | character.
Name of the JDBC driver: com.mysql.jdbc.Driver
The full path name to the Hyperstage installation directory. For example, C\ibi\Hyperstage.
Hyperstage Tools directory.
There are two methods by which a user can be authenticated when connecting to a database server:
Primary authorization ID by which you are known to the data source.
Password associated with the primary authorization ID.
Select a profile from the drop-down menu to indicate the level of profile in which to store the CONNECTION_ATTRIBUTES command. The global profile, edasprof.prf, is the default.
If you wish to create a new profile, either a user profile (user.prf) or a group profile if available on your platform (using the appropriate naming convention), choose New Profile from the drop-down menu and enter a name in the Profile Name field (the extension is added automatically).
Store the connection attributes in the server profile (edasprof).
For explicit authentication:
ENGINE SQLHYP SET CONNECTION_ATTRIBUTES [connection]/userid,password
For password passthru authentication:
ENGINE SQLHYP SET CONNECTION_ATTRIBUTES connection/
where:
Indicates the adapter. You can omit this value if you previously issued the SET SQLENGINE command.
For the Postgres version of the adapter, use SQLHYPG.
The name of the connection. You can give any name to the connection that you want.
Is the primary authorization ID by which you are known to Hyperstage.
Is the password associated with the primary authorization ID.
The following SET CONNECTION_ATTRIBUTES command connects to the Hyperstage database server named TEST with an explicit user ID and password:
ENGINE SQLHYP SET CONNECTION_ATTRIBUTES TEST/USERA,PWDA
The following SET CONNECTION_ATTRIBUTES command connects to the Hyperstage database server named TEST using password passthru authentication:
ENGINE SQLHYP SET CONNECTION_ATTRIBUTES TEST/
There are two methods by which a user can be authenticated when connecting to a Hyperstage database server:
When a client connects to the server, the user ID and password are passed to Hyperstage for authentication and are not authenticated by the server. To implement this type of authentication, start the server with security turned off. The server allows the client connection, and then stores an encrypted form of the client connection message to be used for connection to a Hyperstage database server at anytime during the lifetime of the server agent.
How to: |
Once all Hyperstage connections to be accessed have been declared using the SET CONNECTION_ATTRIBUTES command, there are two ways to select a specific Hyperstage connection from the list of declared connections:
ENGINE SQLHYP SET DEFAULT_CONNECTION [connection]
where:
Indicates the adapter. You can omit this value if you previously issued the SET SQLENGINE command.
For the Postgres version of the adapter, use SQLHYPG.
Is the connection name specified in a previously issued SET CONNECTION_ATTRIBUTES command. If omitted, then the local database server will be set as the default. If this connection name has not been previously declared, a FOC1671 message is issued.
Note:
The following SET DEFAULT_CONNECTION command selects the Hyperstage database server named SAMPLESERVER as the default Hyperstage database server:
ENGINE SQLHYP SET DEFAULT_CONNECTION SAMPLESERVER
Note: You must have previously issued a SET CONNECTION_ATTRIBUTES command for the datasource_name.
How to: |
This topic explains how to set the scope of logical units of work using adapters. This is accomplished by the SET AUTODISCONNECT command.
A connection occurs at the first interaction with the declared database server.
ENGINE SQLHYP SET AUTODISCONNECT ON {FIN|COMMAND|COMMIT}
where:
Indicates the adapter. You can omit this value if you previously issued the SET SQLENGINE command.
Disconnects automatically only after the session has been terminated. FIN is the default value.
Disconnects automatically after each request. Depending on how often the event occurs, the SET AUTODISCONNECT command may result in considerable overhead. Almost all of this overhead is not related to the server. It is related to the operating system and the data source.
Disconnects automatically only after COMMIT or ROLLBACK is issued as a native SQL command.
WebFOCUS |