Tip
UNIX/Linux connections are only supported from Oracle,DB2 and Greenplum data warehouses. If the UNIX/Linux connection returns a blank screen or an error message in the Results pane after the connection is browsed, take necessary action through the Server (SSH) tab next to the main Builder and Scheduler tabs. This tab is displayed after browsing the UNIX connection.
This topic describes in greater detail the connection Properties as they apply to UNIX connections. From a UNIX connection you can only do flat file loads.
Sample Oracle UNIX connection screen
Sample DB2 UNIX connection screen
General
Options | Description |
---|---|
Connection Name | Name used to label the connection within WhereScape RED. |
Connection Type | Indicates the connection source type or the connection method, such as Database, ODBC, Windows, Unix. Select the UNIX connection type. |
Unix/Linux Host
Options | Description |
---|---|
UNIX/Linux Host Name | IP address or host name that identifies the UNIX machine. |
Script Shell | Path to the POSIX-compliant UNIX/Linux shell to use for generated scripts. For UNIX hosts, set to /bin/ksh. For Linux hosts set to /bin/sh. |
Loader Host Identification | IP Address or host name(s) that identifies the Loader/ Multiple hosts can be entered with using a comma (,) to delimit. |
Work Directory | Windows directory used by WhereScape RED to create temporary files for minimal logged extracts. The directory must exist and allow write access. There must be a different work directory for each WhereScape RED Scheduler running on the same machine to avoid file conflicts. Typically C:\Temp or a sub-directory of C:\Temp is used. |
Database ID | Database Identifier (e.g. Oracle SID or TNS Name, Teradata TDPID) or Database Name (e.g. as in DB2 or SQL Server). For UNIX/Linux exports and loads, if the ORACLE_SID environment variable is set in your UNIX/Linux environment, this will be the variable used. If this environment variable is not set then the value from the UNIX/Linux connection object will be used. |
Database Server/Home Directory | Optional to specify the Database Home Directory if it is different from the standard home directory. |
Connection Protocol | Telnet or Secure Shell (SSH) protocol to use to connect to the UNIX/Linux machine. For SSH, the Secure Shell (SSH) Command property is enabled to specify how to connect. |
Secure Shell (SSH) Command | Command to execute to connect to a UNIX/Linux machine using the Secure Shell (SSH) protocol such as C:\Program Files(x86)\PuTTY\plink.exe -ssh $HOST$ -l $USER$ -pw $PASSWORD$ |
Pre-Login Action, Login Prompt, Password Prompt, Post-Login Action, and Command Prompt. | These fields are only used to create a Telnet connection to the host machine. WhereScape RED uses the Telnet connection in the drag and drop functionality. They are not used in the actual production running of the Data Warehouse and is only necessary if you wish to use the drag and drop functionality. |
Pre-Login Action | Response or command to send BEFORE logging in to the UNIX/Linux machine. Typically this is NOT necessary but it can be used to indicate that the UNIX/Linux Login Prompt is preceded by a line-feed (\n). However it is preferable that the UNIX/Linux login displays the Login Prompt without anything preceding it. [Optional] |
Login Prompt | The UNIX login prompt, or the tail end of the login prompt, e.g. ogin as:. |
Password Prompt | The UNIX password prompt, or the tail end of the password prompt, e.g. ssword:. |
Post-Login Action | Not often used but may be necessary to respond to a login question. It is preferable that the UNIX login goes straight to the command prompt. |
Command Prompt | Enter the UNIX/Linux command prompt, or the tail end of that prompt, typically >. Note To ascertain some of the above fields, you have to log in to the UNIX system. |
Credentials
Options | Description |
---|---|
UNIX/Linux User ID | User Account to login to the UNIX/Linux Host. |
UNIX/Linux User Password | Password to login to the UNIX/Linux Host. |
DSS User ID | Database user to connect to the WhereScape RED metadata repository. |
DSS User Password | Database password to connect to the WhereScape RED metadata repository. |
Other
Options | Description |
---|---|
Default Path for Browsing | Optional default Path for browser pane filter. When a path has been selected in this field, it becomes the initial point for browsing and it is also expanded on open in the right-hand browser pane. |
New Table Default Load Type | The default Load Type for new Load tables created using this connection as a source. Select the desired default load type from the list, e.g. Database Link Load, Script based load, Integration Services Load or Externally Loaded. Note The available options in this drop-down list is configured from Tools > Options > Available Load Types. |
New Table Default Load Script Template | The default Script Template to use when a Script based load type is defined for a Load table object that is sourced from this connection. |
Data Type Mapping Set | XML files have been created to store mappings from one set of data types to another. Setting this field to (Default) will cause RED to automatically select the relevant mapping set; otherwise, you can choose one of the standard mapping sets from the drop-down list or create a new one. |
To validate the fields
- Right-click on the connection name.
- Select Telnet window.
To test the drag and drop functionality
- From the menu strip select Browse > Source Tables
- Drill down to the area required.
- Drag an item to the middle pane, (having first selected the object in the left pane).
Connection Failures
In the event that a telnet connection cannot be established to the UNIX host, the following message normally appears in the results pane, after approximately 30 seconds.
Attempt the connection again and using the Window menu option select the Telnet window. This displays the login session and should provide an insight as to why the connection is not being completed.
If the situation cannot be resolved, a telnet trace can be acquired. Select the Tools > Options menu option and click on the Trace all Unix sessions check box. Then try to do the connection or browse again. A log file called WslMedTelnet.log is created in the WhereScape program directory. Edit the log file and ensure there are no passwords visible and then contact WhereScape support using the WhereScape forum at www.wherescape.com.
Closing the Connection
To close the collection, right-click in the browser pane and select Close UNIX/LINUX session: