HP NonStop Data Transformation Engine Resource Adapters Reference Guide Abstract This manual provides information about using the HP NonStop™ Data Transformation Engine (NonStop DTE) Resource adapters. Product Version NonStop Data Transformation Engine 6.7.
Document History Part Number Product Version Published 528271-001 NonStop Data Transformation Engine 6.7.1 June 2004 528271-002 NonStop Data Transformation Engine 6.7.
Contents About This Document Related References........................................................................................... 6 Chapter 1 - Resource Adapters Overview ....................................................................................................... 8 Importers.................................................................................................. 9 System Requirements ........................................................................................
Contents Text File Importer ........................................................................................... 33 Supported Character Sets ............................................................................. 34 Running the Text File Importer ...................................................................... 34 Delimited Format ....................................................................................... 47 Sink Adapter .........................................................
Contents Using mtsmaker without a Database/Query File.................................................. 75 General Parameter Rules................................................................................... 76 List of Parameters ........................................................................................... 77 Database Name (-B) .................................................................................... 78 Data Source (-D) .........................................................
About This Document This document contains information about the Mercator Resource adapters and their related importers. This document assumes that the reader knows the Windows environment, has used the Mercator Design Studio, and understands words such as mapping, type trees, and other basic Mercator terminology. Related References For more information about all products or about topics frequently discussed in this document, refer to the Mercator Online Library or the SDK Online Library.
About This Document Related References Related Reference Description Command Server Reference Guide Using the Command Server to execute maps on various operating system platforms. Execution Commands Reference Guide Using executions commands to control how a map is run by the Command Server or through the Platform API. Functions and Expressions Reference Guide Creating component rules in the Type Designer and map rules in the Map Designer using expressions, functions, and reserved words.
Chapter 1 - Resource Adapters This chapter introduces the Mercator Resource Adapters. You can use the adapters with a Command Server, Event Server, Platform API, or map in a map rule. Overview Resource adapters are used to retrieve and route data. They provide access to databases, files, messaging systems, enterprise applications and other data sources and targets. Each adapter includes a set of adapter commands that can be used to customize its operation.
Chapter 1 - Resource Adapters System Requirements Source and target data may be in a file, from a specific application, in a database, from a message queue, from an archive file, or from other possible sources. The Integration Flow Designer, Map Designer, Type Designer, and Database Interface Designer (the client components of the Design Studio) are integral to using the resource adapters. Each input of data and each output of data requires content definition settings.
Chapter 1 - Resource Adapters General Rules for Adapter Commands General Rules for Adapter Commands Following is a list of the general rules that apply when specifying adapter commands: ♦ Each command must begin with a hyphen. ♦ Command characters can be upper-case, lower-case, or mixed-case. ♦ Command strings are parsed in left-to-right order. ♦ The order of commands is not important. ♦ Command files can contain multiple lines.
Chapter 1 - Resource Adapters Adapter Command Aliases The following is a portion of the syntax summary for the IBM MQSeries messaging adapter command available for use with data sources: -QMN queue_manager_name -QN queue_name This example illustrates that both the Queue Manager Name adapter command (-QMN) and the Queue Name adapter command (-QN) are required for data sources.
Chapter 1 - Resource Adapters Multiple Adapter Versions Multiple Adapter Versions For some adapters, multiple-versions are provided to support different releases of the resource with which the adapter is communicating. They are controlled by the adapters.xml file, which is provided in the default installation directory. The adapters.xml file lists the multiple-version of the adapter, with the specified version uncommented. You must edit the adapters.
Chapter 1 - Resource Adapters Multiple Adapter Versions To comment out an adapter 1 Open the adapters.xml file (located in the default installation directory) in an editing program such as UltraEdit, Visual Slick, and so on. 2 Locate the adapter line (name) that you want to comment out. 3 Type the XML comment syntax around the adapter line (name). For example: before xml syntax added PAGE 14Chapter 1 - Resource Adapters Configuring Java-Based Adapters Configuring Java-Based Adapters Jar files included with Mercator software and installed in the install_home\ directory are normally added to the CLASSPATH environment variable automatically as in the case of the Command Server and the Event Server. You must modify the CLASSPATH environment variable for all Java-based adapters that rely on external .jar files in order to execute properly. This can be done directly, or by adding the .
Chapter 1 - Resource Adapters Encoding and Decoding Data Encoding and Decoding Data There are a number of adapters which only manipulate data (for example, Base64, SOAP), while others provide transport (for example, HTTP). Chaining these adapters together provides greatly enhanced functionality.
Chapter 1 - Resource Adapters Encoding and Decoding Data Encoding Data can be encoded using a specified adapter. The encoding adapter is called before the transport adapter in an output card, PUT or GET where request data is passed as the third parameter. The following characteristics exist for the –ENCODE command: ♦ The –ENCODE command is used within the command line of a transport adapter, or another encoding adapter. ♦ The -ENCODE command cannot be used in an input card.
Chapter 1 - Resource Adapters Encoding and Decoding Data Transporting After specifying either an encode or decode command, data can be transported using a specified adapter. The transport adapter is called: ♦ Before the decoding adapter in an input card or GET ♦ After the encoding adapter in an output card or PUT ♦ Between the encoding and decoding adapters in a GET where request data is passed as the third parameter. The –TRANSPORT command is used in the command line of an encoding or decoding adapter.
Chapter 1 - Resource Adapters Encode/Decode Scenarios Encode/Decode Scenarios The following scenarios apply when using the encode/decode commands in an input card, output card, or in a GET function.
Chapter 1 - Resource Adapters Transport Encode/Decode Examples Transport Encode/Decode Examples The following examples show how the transport adapter encodes or decodes the data when used in an input card, an output card, or in a GET function. SOAP Input card Adapter SOAP Command -ENV –TRANSPORT 'HTTP(-URL http://www.mysite.com)' Meaning The HTTP adapter is called for the transport, then the data is passed to the SOAP adapter to decode.
Chapter 2 - Resource Adapters Use Using the Resource Adapters Resource adapters can be specified: ♦ As a resource in the Map Designer ♦ In map rules and component rules when using the functions RUN, GET, or PUT ♦ From the execution settings in the Integration Flow Designer ♦ On the command line for a Command Server or API ♦ From an application using the Platform API Note A wide range of execution commands is available with the Command Server or Platform API.
Chapter 2 - Resource Adapters Use Using an Adapter in the Map Designer On an input card, a Source setting of File defines the input source as a file and the Source > FilePath setting is used to define the Name and Path of the input file. If the input data is coming from a database, the GET > Source > Command setting might include commands specifying the database name, user ID, password, and so on. See the following example, to learn how to specify the FTP adapter as a data source in the Map Designer.
Chapter 2 - Resource Adapters Use 3 Using an Adapter in a Map or Component Rule Click OK. The Source > Command value for the FTP input card above is: -TS –URL FTP://sales@host/c:/forms/myfile.txt When this map is run, a file named myfile.txt is retrieved from a remote host named sales. The Summary Trace adapter command –TS specifies that the adapter will create a summary trace file to report adapter activity information during the FTP process.
Chapter 2 - Resource Adapters Use Using an Adapter in the Integration Flow Designer Use adapter commands in functions in component rules in the Type Designer and map rules in the Map Designer. Examples ♦ The following example shows a map rule using a DBQUERY function with database adapter commands to specify particular adapter settings.
Chapter 2 - Resource Adapters Use Using an Adapter in the Integration Flow Designer If the Execution Mode setting is Event Server, edit the Event Server Settings for that system component. If the Execution Mode setting is Command Server, edit the Command Server Settings. Note For documentation purposes, we refer to these settings as execution settings (regardless of the execution mode selected). You can use the adapter as a source to retrieve files or as a target to transfer files.
Chapter 2 - Resource Adapters Use 5 Using an Adapter in the Integration Flow Designer Click OK. The TIB/Rendezvous input card Source > Command setting for the RVCM input card above is: -SBN rvcm.test.in -CONFIRM -T -CMN input_CM –LFN rvcmcfmin.lgr -LSN 100 This example input card retrieves incoming messages with the subject name defined as rvcm.test.in using the Subject Name adapter command (-SBN rvcm.test.in).
Chapter 2 - Resource Adapters Use On the Command Line 100 seconds for a message receipt, as specified using the Listen adapter command (-LSN 100). On the Command Line In addition to using a command string on the command line, you can also use adapter commands in command files, batch files, shell scripts, or with the Platform API.
Chapter 2 - Resource Adapters Use On the Command Line ♦ not using an .mdq file Use a command string that includes all of the database adapter commands necessary to specify the desired settings for a map. An .mdq file is not used. Command Line Examples The following examples show various ways to use the database-specific adapter commands on the command line. Note The following examples for data sources and targets are for Oracle database adapters using UNIX-specific syntax.
Chapter 2 - Resource Adapters Use On the Command Line Password adapter command (-PASSWORD), the Table Name adapter command (-TABLE), and the Update adapter command (-UPDATE) override those settings obtained from the .mdq file. ♦ Override both a data source and a target adapter command: mercator XferMsgs -ID1 "'-MDQ /share/prod.
Chapter 2 - Resource Adapters Use Functions Functions For detailed information about using the GET, PUT and all other functions, refer to the Functions and Expressions Reference Guide. Using the GET Function The GET function returns messages from the adapter as a single text item.
Chapter 2 - Resource Adapters Use Using Wildcards Using the RUN Function In a RUN function, use adapter commands with the appropriate Input Source Override execution command or the Output Source Override execution command to override particular settings. The following example shows using a RUN function to specify adapter commands without using a database/query file (.mdq): RUN ("somemap.
Chapter 2 - Resource Adapters Use Scope Settings and FetchUnit Interpretation ♦ input card 2 is called with the MID property set to 123XYZ456. ♦ the file created from output card 1 is named OUTXYZ.TXT.
Chapter 2 - Resource Adapters Use Using Global Transaction Management Source > Scope Settings Target > Scope Settings M, C M, B, C No No Logical ROMA BSP M, B, C M, B, C Yes Yes Message Shell Script M, B, C M, B, C No No Logical Siebel M, B, C M, B, C No No Logical Socket M, B, C M, B, C Yes Yes Message (5.x, M, B, C M, B, C Yes Yes Message (6.
Chapter 2 - Resource Adapters Use File Adapter File Adapter The File adapter is a listener for the event server that supports file triggering. The GET and PUT commands are internal for this adapter. The only parameter available for the file adapter is the filename specified in the FilePath card setting.
Chapter 2 - Resource Adapters Use Text File Importer Supported Character Sets The Text File Importer supports the following character sets: Western Character Sets (International and Non-International Versions) ♦ ASCII ♦ EBCDIC ♦ UTF – 8 ♦ UNICODE Little Endian ♦ UNICODE Big Endian Japanese Character Sets (International Version) ♦ SJIS ♦ EUC ♦ UNICODE Big Endian ♦ UNICODE Little Endian ♦ UTF - 8 Running the Text File Importer The Text File Importer automatically generates type trees that describe the fo
Chapter 2 - Resource Adapters Use Text File Importer The Importer Wizard–Text File dialog box appears. 4 Either enter the name of the file you wish to import or click select a different file name. 5 Click Next.
Chapter 2 - Resource Adapters Use Text File Importer The next Importer Wizard-Text File dialog box appears. 6 Specify the language and the character set of the input file. Click Next. Note Choices for the language will be Western for the non-international versions, and Western and Japanese for the International versions. See Supported Character Sets for a complete list of supported character sets.
Chapter 2 - Resource Adapters Use Text File Importer ASCII If ASCII is selected, the data displays in the Data preview as it is in the text file. All the non-printable characters are replaced by their symbols.
Chapter 2 - Resource Adapters Use Text File Importer UTF-8 If UTF-8 is selected all multi-byte characters are represented by their hex values.
Chapter 2 - Resource Adapters Use Text File Importer UNICODE Little Endian, Big Endian and EBCDIC If either UNICODE Little Endian, Big Endian or EBCDIC are selected the data displays in their hex values.
Chapter 2 - Resource Adapters Use 7 Text File Importer Either enter the name of the type tree you wish to create or click to select an existing type tree file. (browse) Optionally, enable the Merge with existing tree check box if you want to merge trees and select one of the following Merge Options: Replace existing types with types imported or Do not overwrite existing types. In this example, the trees will not be merged. Note The destination will be overwritten if the type tree already exists.
Chapter 2 - Resource Adapters Use Text File Importer The next Importer Wizard-Text File dialog box appears. 9 Double-click a row of data to create types. Note The maximum number of rows is 3000.
Chapter 2 - Resource Adapters Use Text File Importer The Group Properties dialog box appears. Note The following examples are for a fixed row format. Delimited row format examples are illustrated in the Delimited Format section. 10 Select Fixed or Delimited in the Row Format group box. 11 Define group properties.
Chapter 2 - Resource Adapters Use Text File Importer To define Group Properties You can define group properties when using the Text File Importer. 1 Highlight data in the Data preview. 2 Right-click and select a property. For example, click on Terminator to select that property.
Chapter 2 - Resource Adapters Use Text File Importer The following example illustrates being defined as the terminator. Note that the terminator is color-coded red. 3 After defining the group properties, click Next. The Fixed Format dialog box appears.
Chapter 2 - Resource Adapters Use Text File Importer To define Item Properties You can now define the item properties. 1 Highlight data in the data preview pane and drag it to the Types pane. Additionally, you can double-click on the rule bar to select your types. Click Finish. The Importer Wizard – Text File dialog box re-appears enabling you to select on another row of data to create types. When you are finished creating types, go to the next step. 2 Click Next.
Chapter 2 - Resource Adapters Use Text File Importer The type tree displays in the Importer Wizard – Text File dialog box. 3 Click Finish. The Importer Wizard closes. To view your new type tree, open the file you created in the Type Designer.
Chapter 2 - Resource Adapters Use Text File Importer Delimited Format If Delimited is selected in the Row Format group box, the Delimited Format dialog box appears. 1 Select either Custom or Use Delimiter to generate types. If Custom is selected, highlight the text in the control and use the drag and drop functionality to generate a type. If Use Delimiter is selected, the Delimiter browse button allows the user to provide the delimiter to parse the text.
Chapter 2 - Resource Adapters Use Text File Importer The Symbols dialog box appears. Define your delimiter in the Value field. For our example, a semi-colon (;) was typed into the Value field. Click OK. The Delimited Format dialog box appears.
Chapter 2 - Resource Adapters Use Text File Importer The delimiter value will appear in the Delimiter field. Types are automatically generated in the Data preview. 3 Click Finish and then click Next. The type tree displays in the Importer Wizard – Text File dialog box.
Chapter 2 - Resource Adapters Use 4 Sink Adapter Click Finish. The Importer Wizard closes. To view your new type tree, open the file you created in the Type Designer. Sink Adapter The Sink adapter is used as a temporary data destination for an output map card which then discards the mapped data. This capability is useful when a temporary destination is needed to accept output data as part of the map execution without writing the output to a stationary destination.
Chapter 2 - Resource Adapters Use Application Adapter This adapter can be used with the Command Server, Event Server, Platform API, or in a map rule. For example, using the Map Designer, select Sink for the Target setting in an output card dialog box. Note The Sink adapter does not require any additional card settings or adapter commands. You can use the Output Target Override execution command (-OA) with the Sink adapter alias.
Chapter 3 - Source and Target Card Settings Each input of data and each output of data require content definition settings. These settings are specific to input and output cards, although some settings are common to both cards. For detailed information about source and target settings, see the Map Designer Reference Guide. Source Settings The Source settings identify the source of the input data.
Chapter 4 - Troubleshooting Resource Adapters If you receive an error while attempting to use an adapter, use one of the following troubleshooting tools to assist you: ♦ adapter trace command ♦ return codes and error messages (see General Adapter Messages for more information) Note See the associated adapter documentation for specific information.
Chapter 5 - Database-specific Adapter Information This chapter discusses the database-specific adapter information. The use and operation of these adapters is covered in each database-specific adapter reference guide and help file. Overview Using the Database Interface Designer with the database adapters, data stored in a database under the control of a Relational Database Management System (RDBMS) can be easily identified, defined, and accessed as the source or target for a map.
Chapter 5 - Database-specific Adapter Information Overview Restrictions and Limitations The Database Interface Designer and database adapters offer options and functions for accessing and manipulating data contained within a database.
Chapter 5 - Database-specific Adapter Information Using Database-specific Adapters Using Database-specific Adapters Database-specific adapter commands can be used in any of the following ways: ♦ when specifying adapter settings for sources and targets ♦ with functions in map and component rules ♦ on the command line using execution commands to override source or target settings See General Rules for Adapter Commands and Chapter 2 - Resource Adapters Use for more information.
Chapter 5 - Database-specific Adapter Information Name List of Commands DBLOOKUP Adapter Command Syntax Source Target DBQUERY GET PUT √ √ √ √ √ Commit by Card* -CCARD √ √ √ √ √ Commit by Statement -CSTMT [number] √ √ √ √ √ Delete -DELETE Database Name* -DBNAME database_name Connect String (Oracle only) -CONNECT connect_string √ Database Adapter -DBTYPE database_adapter Type √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ Data Source ODBC, DB2 -SOURCE datasour
Chapter 5 - Database-specific Adapter Information Name List of Commands DBLOOKUP Adapter Command Syntax Source Target DBQUERY GET PUT Trace -TRACE[+] [full_path] √ √ √ √ √ Trace Error -TRACEERR[+] [full_path] √ √ √ √ √ Trigger (Oracle 8, -TRIG trigger_string Microsoft SQL Server 7 only) √ √ Update -UPDATE [OFF|ONLY] User ID -USER user_ID √ Variable -VAR name=value… √ √ √ √ √ √ √ √ * A card setting exists.
Chapter 5 - Database-specific Adapter Information List of Commands Bad Data (-BD or -BADDATA) Use the Bad Data adapter command (-BADDATA) for a target or in a PUT function so that if the situation occurs in which any inserts, updates, or procedure calls fail to execute, the data that could not be processed is written to a file you specify and processing continues.
Chapter 5 - Database-specific Adapter Information List of Commands Commit by Card (-CC or -CCARD) Use the Commit by Card adapter command (-CCARD) to commit or roll back the transaction when the card has been processed. This command can be used for a source or target, or in a DBLOOKUP, DBQUERY, GET, or PUT function.
Chapter 5 - Database-specific Adapter Information List of Commands Commit by Statement (-CS or -CSTMT) Use the Commit by Statement adapter command (-CSTMT) to commit or roll back the transaction after the execution of every statement, or, optionally, after a specified number of statements.
Chapter 5 - Database-specific Adapter Information List of Commands Database Name (-DN or -DBNAME) Use the Database Name adapter command (-DBNAME) to specify the name of a database defined in the .mdq file that is specified using the Database/Query File adapter command (-MDQ). The Database Name adapter command can be used for a source or target, or in a DBLOOKUP, DBQUERY, GET, or PUT function. -DBNAME database_name Note The database_name you supply is case-sensitive.
Chapter 5 - Database-specific Adapter Information List of Commands Data Source (-DS or -SOURCE) Use the Data Source adapter command (-SOURCE) to specify the name of the ODBC, Microsoft SQL Server, Sybase SQL Server, DB2, or Informix data source. This command can be used for a source or target, or in a DBLOOKUP, DBQUERY, GET, or PUT function. -SOURCE datasource|server\\database Value Description datasource Specify the ODBC, DB2 (Windows/UNIX), or Informix data source.
Chapter 5 - Database-specific Adapter Information List of Commands command is for the temporary file to be created in the same directory as the map. The temporary file is then deleted after the map completes. -FILE [directory] Value Description directory Specify the directory in which the temporary file should be created.
Chapter 5 - Database-specific Adapter Information List of Commands Password (-PW or -PASSWORD) Use the Password adapter command (-PASSWORD) to specify the password that authenticates the user logon. This command can be used for a source or target, or in a DBLOOKUP, DBQUERY, GET, or PUT function. -PASSWORD password Note If you specify the parameter as $(env_var)where env_var represents the name of an environment variable, the actual value of the password is retrieved from this environment variable.
Chapter 5 - Database-specific Adapter Information List of Commands Row Count (-RC or -ROWCNT) (For ODBC, Oracle, DB2 for Windows, and DB2 for UNIX adapters only) Use the Row Count adapter command (-ROWCNT) to specify the number of rows to be retrieved in one fetch from the database by the database adapter. This command can be used for a source or in a DBLOOKUP, DBQUERY, or GET function. -ROWCNT specifies the number of rows to be retrieved from the database.
Chapter 5 - Database-specific Adapter Information List of Commands SQL Statement (-S or -STMT) Use the SQL Statement adapter command (-STMT) either for a source or in a GET function to specify an SQL statement or a call to a stored procedure using either the database-independent or native call syntax to be executed. This execution will provide the input data to a map.
Chapter 5 - Database-specific Adapter Information List of Commands The default is for a database trace file to be produced in the directory in which the map is located, using the full name of the map file and a .dbl extension (map_name.dbl). Optionally, you can append the trace information to an existing database trace file, specify a file name, or specify the full pathname for the file. -TRACE[+] [full_path] Value Description + Append trace information to an existing trace file.
Chapter 5 - Database-specific Adapter Information List of Commands Trigger (-TR or -TRIG) Note This command is available only for the Oracle 8 and Microsoft SQL Server 7 database adapters. Use the Trigger adapter command (-TRIG) for a source to specify the trigger string for a trigger specification. For more information about specifying database triggers, refer to the Database Interface Designer Reference Guide.
Chapter 5 - Database-specific Adapter Information Value List of Commands Description W when_clause [[table.column_name1]…] This is an expression that will be evaluated when the other events have occurred. If this expression evaluates to TRUE, the conditions of the trigger specification are met and the map is launched. If the expression is not TRUE, the state is restored as it was prior to any events occurring. This expression may contain any SQL expressions that are valid for the target database.
Chapter 5 - Database-specific Adapter Information List of Commands Update (-UP or -UPDATE) Use the Update adapter command (-UPDATE) to enable update mode which causes update operations to be performed for tables or views based upon the defined update keys and key columns to update. For information about defining updating keys and key columns to be updated, refer the Database Interface Designer Reference Guide.
Chapter 5 - Database-specific Adapter Information List of Commands Variable (-V or -VAR) Use the Variable adapter command (-VAR) for a source at runtime to pass a value for a variable defined in the SQL SELECT statement. It can also be used in a DBLOOKUP, DBQUERY, or GET function.
Chapter 6 - Generating Type Trees Using mtsmaker This chapter discusses using the mtsmaker application to generate type trees. Overview The mtsmaker application helps generate type trees for a query, table, view, or stored procedure when you do not have connectivity between the Database Interface Designer and your non-Windows database. Use mtsmaker to produce type tree script files (.mts) on your non-Windows database host system that you will subsequently transfer to your development PC in binary mode.
Chapter 6 - Generating Type Trees Using mtsmaker Generating a Tree Script Generating a Tree Script When using mtsmaker, tree scripts can be created in either of two modes: ♦ by using a database/query file (.mdq) ♦ by not using an .mdq file Control how you want the tree script file to be generated by specifying various mtsmaker parameters. Using mtsmaker with a Database/Query File You can use a database/query file (.
Chapter 6 - Generating Type Trees Using mtsmaker Generating a Tree Script Example of Using mtsmaker with an .mdq File The following is an example of using mtsmaker with a database/query file to generate a tree script file for a table: mtsmaker -m mdqfile.mdq -b mydbase -t mytable -f tree.mtt -o mtsfile.mts –x f Using mtsmaker without a Database/Query File Type trees can be generated without using database/query files.
Chapter 6 - Generating Type Trees Using mtsmaker General Parameter Rules Example of Using mtsmaker Without an .mdq File The following is an example of generating a tree script for a query without using a database/query file and specifying an Oracle connect string with the Data Source parameter (–D). Note The -D parameter can also be used to specify a data source for ODBC, Sybase SQL Server, or DB2, as appropriate.
Chapter 6 - Generating Type Trees Using mtsmaker List of Parameters List of Parameters The following table lists: the mtsmaker parameters that can be used for generating type trees; the parameter syntax; and whether each one can be used (√) with or without a database/query file. Parameter Name Parameter Syntax Database Name -B database_name With .mdq Without .
Chapter 6 - Generating Type Trees Using mtsmaker List of Parameters Database Name (-B) Specify the name of the database as defined in the .mdq file. -B database_name Data Source (-D) Specify the name of the ODBC, DB2, Oracle, or Sybase SQL Server data source. -D {datasource|connect_string|server\\database} Option Description datasource Specify the ODBC or DB2 data source. connect_string Specify the Oracle host connect string. server\\database Specify the Sybase SQL Server data source.
Chapter 6 - Generating Type Trees Using mtsmaker List of Parameters Category Type (-N) Specify the name of the category type from which the types defining the table or query will stem. -N type_name Tree Script File (-O) Specify the name of the tree script file (.mts) to be generated by mtsmaker and used by the Type Tree Maker to create the type tree. -O mts_file_name Password (-P) Specify the password used to connect to the data source.
Chapter 6 - Generating Type Trees Using mtsmaker List of Parameters SQL Statement (-S) Specify an SQL statement or a call to a stored procedure using either the database-independent or native call syntax that is passed to the database management system to determine the content and format of the database output. This statement should be the same as the statement you are using to generate input for your map. However, you may exclude SQL WHERE clauses because they do not affect the format of the result.
Chapter 6 - Generating Type Trees Using mtsmaker List of Parameters If using the following query from an mdq file, select * from BigTable where Identifier=#ID# then specify the following option on the mtsmaker command line: -V ID=2 In this way, the query to be executed would be as follows: select * from BigTable where Identifier=2 Note that variable name values are read by default from the MDQ file, unless overridden on the command line.
Chapter 6 - Generating Type Trees Using mtsmaker List of Parameters Option Description SQLSVR Microsoft SQL Server database Version 6.5 only SQLSVR7 Microsoft SQL Server database Version 7.
Chapter 7 - Troubleshooting Database-specific Adapters If you receive an error while attempting to use a database adapter, use one of the following troubleshooting tools to assist you: ♦ adapter Trace (-T or -TRACE) or the Trace Error (-TE or -TRACEERR) command ♦ return codes and error messages (see Database-specific Adapter Messages for more information) Resource Adapters Reference Guide 83
Chapter 8 - Messaging-specific Adapter Information The use and operation of these adapters is covered in each messaging-specific adapter reference guide and help file. Overview Messaging-specific adapters are a collection of middleware drivers used to provide a means of specifying data sources and targets for Mercator maps. Each adapter includes a set of commands to customize its operation.
Chapter 8 - Messaging-specific Adapter Information Overview ♦ Many-to-one Messages can flow from many data source messages to a single data target message using a map. ♦ Many-to-many Messages can flow from many data source messages to many data target messages using a map. Additionally, message flow can be sequenced between applications and used to integrate non-messaging environments.
Chapter 8 - Messaging-specific Adapter Information Adapter Transactions Adapter Transactions Map definitions provide settings to control the scope of messaging adapter transactions. It is important to understand how connections to messaging systems are controlled and how this relates to transactional scope. Transactional Control Scope is a setting that can be specified for a source or target in a map to determine transaction commitment.
Chapter 8 - Messaging-specific Adapter Information Messages as a Data Target Example of Data Processing Modes In addition to the burst mode on a per card basis, the map itself may be set to operate iteratively, thereby invoking multiple source card bursts in a single map invocation.
Appendix A - Return Codes and Error Messages Adapter return codes and messages provide information on the adapter operations, adapter command syntax errors, and reasons for unsuccessful transactions. Note See the associated adapter documentation for specific error message information. General Adapter Messages The following is a listing of all the codes and messages that are common among all resource adapters.
Appendix A - Return Codes and Error Messages General Adapter Messages Return Code Message -12 Invalid type specified -13 Connection failed -14 File open failed -15 File write failed -16 File read failed -17 File position function failed -18 Invalid object specified -19 Null object specified -20 Illegal function call -21 Unexpected end-of-file -22 Only one top level element allowed -23 Not a top level element -24 3rd party function failed -25 Attempt was made to resize non-resi
Appendix A - Return Codes and Error Messages Database-specific Adapter Messages Database-specific Adapter Messages After database adapter activity completes, messages display indicating the results. These messages may also be recorded in the appropriate files as specified, which may include audit logs, trace files, and execution summary.
Appendix A - Return Codes and Error Messages Database-specific Adapter Messages Return Code Message -1005 Failed to connect to the database -1006 Failed to prepare the SQL statement -1007 Failed to obtain definition of column -1008 Failed to bind parameters to the SQL statement -1009 Failed to execute the SQL statement -1010 Failed to open a cursor -1011 Failed to insert a row into the database -1012 Failed to read file -1013 Failed to open file -1014 The input buffer was of incorrect
Appendix A - Return Codes and Error Messages Database-specific Adapter Messages Return Code Message -1035 Failed to create an execution thread -1036 Failed to get extended error text -1037 Table is not accessible -1038 Failed to disconnect from the database -1039 Failed to free the database connection -1040 Failed to free the environment -1041 MDQ file is invalid -1042 Failed to close file -1043 No database connection could be found -1044 No database type was specified with -DBTYPE -
Appendix A - Return Codes and Error Messages Database-specific Adapter Messages Return Code Message -1063 No suitable presentation could be found for a column -1064 No suitable presentation could be found for a column -1065 Internal error -1066 No more rows were returned -1067 No trigger was defined for the input -1068 Data was unexpectedly terminated -1069 Required command line options missing -1070 The database command line was invalid -1071 Could not find environment variable -1072
Appendix A - Return Codes and Error Messages Database-specific Adapter Messages Return Code Message -1090 The map contains outdated DB parameters.
Appendix A - Return Codes and Error Messages Database-specific Adapter Messages Return Code Message -1302 A trigger event could not be registered -2002 Insufficient data passed to output card Resource Adapters Reference Guide 95
Index command aliases, 11 configuring java-based adapters, 14 database-specific messages, 90 FetchUnit interpretation, 31 general messages, 88 general rules, 10 multiple versions of, 12 Scope settings, 31 Source settings, 52 Target settings, 52 using wildcards in, 30 adapters.xml file editing, 13 multiple adapter versions, 12 aliases, 11 Application adapter, 51 Audit Card (-A or -AUDIT) adapter command, 58 . .
Index E Database Adapter (-Z) mtsmaker parameter, 81 Database Interface Designer installation, 54 Database Name (-B) mtsmaker parameter, 78 Database Name (-DN or -DBNAME) adapter command, 62 Database/query File (-M) mtsmaker parameter, 78 database-specific adapter messages, 90 database-specific adapters troubleshooting, 83 define group properties, 42 Delete (-D or -DELETE) adapter command, 61 J java-based adapters, 14 M mdq file (-M or -MDQ) adapter command, 64 as input to mtsmaker, 74 specifying adapte
Index R adapter command, 65 Query Name (-Q) mtsmaker parameter, 79 T Table Name (-T) mtsmaker parameter, 80 Table Name (-TB or -TABLE) adapter command, 67 Text File Importer, 33 defining group properties, 43 defining item properties, 45 delimited format, 47 supported character sets, 34 using, 34 Trace (-T or -TRACE) adapter command, 67 Trace Error (-TE or -TRACEERR) adapter command, 68 Tree Script File (-O) mtsmaker parameter, 79 troubleshooting database-specific adapters, 83 troubleshooting resource ada
