Starting and stopping the RFC Listener Manager on UNIX: The InfoSphere DataStage RFC Listener Manager is a UNIX

daemon that starts up automatically by default when the operating system is started. If you need to stop or start the RFC Listener Manager on UNIX, we recommend that you run the dsidocd.rc script for your platform with the stop or start comm and options. The location of the script for all UNIX platforms is given below: Platform Script HP-UX 11i (Itanium 64 bit) v2 $DSSAPHOME/DSSAPbin/dsidocd.rc Linux $DSSAPHOME/DSSAPbin/dsidocd.rc Example: To start the InfoSphere DataStage RFC Listener Manager: $DSSAPHOME//dsidocd.rc start To stop the InfoSphere DataStage RFC Listener Manager: $DSSAPHOME/DSSAPbin/dsidocd.rc stop If you shut down the RFC Listener Manager, the RFC Listener Manager shuts down all individual RFC Servers. Configuration files Because R/3 connection parameters and IDoc type properties are outside the scope of individual IBM InfoSphere DataStage jobs, they are not stored in job definiti on files in theInfoSphere DataStage repository. External configuration files store these parameters and properties. We recommend that you use the IDoc Extract GUI to modify settings for these configuration files. This section describes the variou s configuration files that are used by the server to manage R/3 connection parameters and IDoc type properties: v DSSAPConnections.config v IDocTypes.config

activation code : 0026449121A2cd 91297

kalasenavaru mqsatishmk@gmail.com satish1 mallamma username : satish_kalasenavaru 100gb 3months free unlimited --12.50 7.50 ---

v <IDocType>.config Note: On UNIX platforms, the dsenv file in the InfoSphere DataStage server directory must contain a umask setting so that users have read and write permissions on these configuration files. (Windows NT platforms handle this automatically.) DSSAPConnections.config file: The DSSAPConnections.config file stores SAP R/3 connection parameters and is located in the DSSAPConnections subdirectory of the IBM InfoSphere DataStage server directory. It contains all the informatio n specific to the individual physical SAP R/3 connections that have been configure d. SAP R/3 connections are typically configured during job design (see Defining the InfoSphere DataStage connection to SAP). However, you can also configure them using the IBM InfoSphere DataStage Administrator for SAP. These configuration files should never be directly edited (see Administrator for SAP Utility). The example below shows an SAP R/3 connections configuration file: DSSAPCONNECTIONS=<BEGIN> <BEGIN> DSPASSWORD=py~sZiv. SAPROUTERSTRING= DEFAULTLANGUAGE=EN DATAFILESPATH= SAPSYSNUM=02 DEFAULTUSERNAME=p45user DESCRIPTION=SALES logical system on ultra - P45 instance SAPGROUP= DSUSERNAME=dsuser1 SAPMESSERVER= DEFAULTCLIENT=800 ALLOWSAPTORUNJOBS=TRUE SAPAPPSERVER=R3sys1 LISTENFORIDocs=TRUE NAME=P45VERSION3 SAPSYSID= REFSERVERPROGID=idoctest3 USELOADBALANCING=FALSE DEFAULTPASSWORD=JSKM~ <END> <END> Fields of the DSSAPConnections.config file Each connection is delimited by <BEGIN>/<END> pairs. The fields within a connection block in the DSSAPConnections.config file are defined as follows: v NAME. A tag identifying the physical connection. v DSPASSWORD. An encrypted password used by a listener server to launch InfoSphere DataStage jobs. v DEFAULTLANGUAGE. One of the SAP mnemonics representing the native language of an RFC client connection. RFC client connections are used by the IDoc custom GUI and by the listener when sending status information back to R/3. v DEFAULTUSERNAME. The user name for connecting to R/3 as an RFC client. v DSUSERNAME. The user name used by a listener server to launch InfoSphere DataStage jobs. v DEFAULTCLIENT. The R/3 client number used to connect to R/3 as an R/3 client.

v SAPROUTERSTRING. The router string used to connect to R/3 as an RFC client. v SAPSYSNUM. The R/3 system number used to connect to R/3 as an RFC client. v REFSERVERPROGID. The program ID of a tRFC port used to connect to R/3 as an RFC server. The listener servers use this when connecting to R/3 to listen for IDocs. v DEFAULTPASSWORD. An encrypted password used to connect to R/3 as an RFC client. v SAPAPPSERVER. The host name of the system running the R/3 instance. v USELOADBALANCING. The load balancing specification. If true, client connections are made through a message server rather than an application server. v SAPMESSERVER. The message server host that handles the connection request when using load balancing. v SAPSYSID. The R/3 system name that handles the connection request when using load balancing. 42 Integration Guide v SAPGROUP. The group name of the application servers when using load balancing. IDocTypes.config file: When the listener manager starts, it starts a listener se rver for each connection described in this file. The previous example contains a sing le connection, PA45VERSION3. When an IDoc type is first associated with a connection during job design, the client GUI creates a directory in the IBM InfoSphere DataStage server directory called DSSAPConnections/<ConnectionName>/IDocTypes/<IDocTypeName>. v ConnectionName specifies one of the connections defined by the NAME= parameter in the DSSAPConnections.config file. v IDocTypeName is a directory that specifies the name of an IDoc type. For each configured connection, a corresponding subdirectory (DSSAPConnections/<ConnectionName>) is created. Each of these subdirectories contains an IDocTypes directory that contains a configuration file named IDocTypes.config and further subdirectories, one for ea ch IDoc type configured. The type is received from the respective connection. The IDocTypes.config file specifies the directory locations for writing each typ e of IDoc that has been configured for that connection. It has the same format as the DSSAPConnections.config file, but it contains different fields. For example: DSIDOCTYPES=<BEGIN> <BEGIN> USE_DEFAULT_PATH=FALSE IDOC_FILES_PATH=/u1/IDocs/MATMAS01 NAME=MATMAS01 <END> <BEGIN> USE_DEFAULT_PATH=TRUE IDOC_FILES_PATH= NAME=CREMAS01 <END> <END> The fields within an IDoc type block are defined as follows: v NAME. The name of the IDoc type. v USE_DEFAULT_PATH. A value of TRUE indicates that InfoSphere DataStage defines the default directory to serve as the PSA for this IDoc type. If TRUE, IDocs received by the listener are stored in the corresponding IDocTypeName directory in the IDocTypes directory. v IDOC_FILES_PATH. If USE_DEFAULT_PATH is FALSE, specifies the

user-defined directory that serves as the PSA for this type. <IDocType>.config file: The <IDocType>.config exists in every IDocTypeName directory that is configured as a destination for a particular IDoc type, either by default or that you explicitly specify. IDocType is the type name of the IDoc. This configuration file contains all the information that is specific to that IDoc directory location. For example: IBM InfoSphere Information Server Pack for SAP R/3 43 IDOC_COUNT=100 DSUSERNAME=johnharvey DSPASSWORD=py~sZiv. AUTORUN_ENABLED=TRUE ARCHIVE_IDOC_FILES=FALSE USE_DEFAULT_LOGON=FALSE The fields in the IDocType.config file are defined as follows: v IDOC_COUNT. The value indicating the number of IDocs to be collected in the PSA. They are collected before a job is launched by a listener server to process the IDoc. v DSUSERNAME. The user name used by the listener server to connect to IBM InfoSphere DataStage to launch a job. If USE_DEFAULT_LOGON is TRUE, DSUSERNAME is ignored. v DSPASSWORD. The encrypted InfoSphere DataStage password used with DSUSERNAME. If USE_DEFAULT_LOGON is TRUE, DSPASSWORD is ignored. v AUTORUN_ENABLED. If set to TRUE, InfoSphere DataStage jobs associated with the IDoc type are launched automatically by the listener server when IDOC_COUNT is reached. If AUTORUN_ENABLED is set to FALSE, InfoSphere DataStage jobs are not started by the listener server, and IDOC_COUNT is ignored. v ARCHIVE_IDOC_FILES. If set to TRUE, the cleanup process moves the IDocs to a default location rather than deleting them from the PSA. v USE_DEFAULT_LOGON. If this field is set to TRUE, the listener server uses the DSUSERNAME/DSPASSWORD combination in the DSSAPConnections.config file that is configured for the connection. If it is set to FALSE, it uses the DSUSERNAME and DSPASSWORD combination in this <IDocType>.config file. For more information about the management of these configuration files, see the Administrator for SAP Utility section. IDoc extract for SAP R/3 Enterprise stage IDocs that are received by a listener server from R/3 are saved to disk. IBM InfoSphere DataStage jobs do not directly read IDocs from an SAP R/3 system. Instead, they are read from the directory specified in the configuration file fo r the particular IDoc type (see Configuration files for more information). You can use the IDoc Extract stage to start jobs automatically using a request from a listener s erver, or you can use the InfoSphere DataStage Director Client or dsjob to start them. The IDoc Extract stage is a passive stage that has output links but no input lin ks. Each output link from the IDoc Extract stage is mapped to a single IDoc data segment. You should create links for each IDoc segment whose data is of interest when you design a job. If you process only segments E1MARAM and E1MAKTM, for example, the data contained in other segments is ignored. Segments are records within an IDoc that can be child or parent segments. They include administrative fields such as the IDoc number, the segment number, and the number of the parent segment. Child segments have a many-to-one relationship to parent segments. The selection of E1MARAM, which has child segments, does not imply that all its child segments are included. Only the segment fields of E1MARAM are processed. 44 Integration Guide The segment fields for E1MARAM correlate with the column definitions for the

output link on which E1MARAM is associated. The segment fields for E1MAKTM become the column definitions for a second output link. Use the custom GUI to define the column metadata definitions. When a segment is chosen for a link, the GUI displays the available segments fields that you can select for output. The G UI then automatically translates the R/3 metadata for the selected segment fields t o equivalent InfoSphere DataStage metadata definitions and populates the column grid. Examples Note: InfoSphere DataStage uses the segment definition name, for example, E2MAKTM001, rather than the segment type name. The distinction between the two is beyond the scope of this document. For more information, consult your SAP documentation. The R/3 metadata is translated to InfoSphere DataStage metadata. When the job is run, the stage reads unprocessed IDocs of the specified type fro m the appropriate location in the PSA. Unprocessed IDocs are identified by a bookmark file that is maintained for each IDoc type. (See the next section and P SA maintenance for details about bookmarks.) When subsequent jobs are run, only those IDocs that arrived following the curren t bookmark are processed. This prevents a job from repeatedly processing the same set of IDocs. If a job fails, you can use the reset functionality for the job to restore the b ookmark to its original state. Test Mode. To prevent the bookmark for the job from being updated, you can process IDocs in Test Mode (set on the General tab of the Stage page). For more information, see About the Stage General page. The parameters that are needed by InfoSphere DataStage to connect to an SAP database are defined on the General tab on the Stage page. 46 Integration Guide To connect to an R/3 Enterprise system: 1. DataStage Connection to SAP. The InfoSphere DataStage connection to the R/3 Enterprise system that is defined on the InfoSphere DataStage server machine and shared by all InfoSphere DataStage users connected to that machine. The fields in this area are read-only and are obtained from the connection that you selected. Name The name of the selected connection to the SAP R/3 system that generates the IDocs to be extracted by this stage. Select... Click the button to choose an InfoSphere DataStage connection to the SAP R/3 system. The selected connection provides all needed connection and default logon details that are needed to communicate with the corresponding SAP R/3 system. Description Additional information about the selected connection. Application Server The name of the host system running SAP R/3. If the selected connection uses load balancing, Message Server is used instead. System Number The number assigned to the SAP R/3 system used to connect to SAP R/3. If the selected connection uses load balancing, System ID is used instead. 2. SAP Logon Details. The fields in this area are read-only unless you clear the Use connection defaults box.

a. User Name. The user name that is used to connect to SAP. b. Password. A password for the specified user name. c. Client Number. The number of the client system used to connect to SAP. d. Language. The language used to connect to SAP. e. Use connection defaults. Clear this box to remove the default SAP Logon Details settings so you can use different logon information. If selected, the displayed logon details are obtained from the selected connection and are disabled. 3. Enter an optional description to describe the purpose of the stage in the Description field. 4. Test Mode. The check box that specifies whether the job runtime component updates the bookmark file for this stage. If you select this check box, the job runtime does not update the bookmark file for this stage. Therefore, each time the job is run, this stage reads all the IDocs that it read when the job was previously run. Use Test Mode as you develop a job and need to test it repeatedly with the same set of input data without causing the bookmark to be updated. Selecting Test Mode also prevents the job from being run automatically as new IDocs of this type arrive. The listener server does not launch a job in test mod e even if its IDoc type is designated for automatic execution. The Administrator can archive processed IDocs rather than permanently remove them by moving them to a subdirectory of the PSA for the IDoc. Currently, the only way to reprocess IDocs is to reset an aborted job or set the job to Test Mode. You cannot reprocess archived IDocs. IBM InfoSphere Information Server Pack for SAP R/3 47 For a newly created stage, the connection for the stage defaults to the last one you selected for another stage of this type. If only one InfoSphere DataStage connec tion to an R/3 Enterprise system is defined on the InfoSphere DataStage server machine, a new stage defaults to that connection regardless of whether you previously created an IDoc Extract stage. Selecting the InfoSphere DataStage connection to SAP: When you click Select on the General tab of the Stage page, the Select InfoSpher e DataStage Connection to SAP dialog opens. This dialog lets you choose a InfoSphere DataStage connection to the R/3 Enterprise system. The selected connection provides all needed connection and default logon details that are needed to communicate with the corresponding R/3 Enterprise system. The IDoc Listener Settings options function in the same way as the corresponding options in the IDoc Listener Settings of the InfoSphere DataStage Administrator for SAP utility. In addition, the Number of servers for this connection field select s the number of listening processes for the IDoc connection in the InfoSphere DataStag e IDOC Manager. This property improves the performance during IDoc extraction. Use SAP R/3 transaction SMSQS to configure multiple IDoc connections. Add, Properties, Import into, Export and Remove are administrative connection operations. They let you manage the list of connections that is maintained on th e InfoSphere DataStage server machine from the Select DataStage Connection to SAP dialog. They function in the same way as the corresponding buttons on the DataStage Connections to SAP page of the InfoSphere DataStage Administrator for SAP utility. Stage Options page: Use the IDoc Extract Stage Options page to specify design-time connection detail s. Name The name of the selected connection to the SAP R/3 system that generates

the IDocs to be extracted by this stage. Select... Click the button to choose an InfoSphere DataStage connection to the SAP R/3 system. The selected connection provides all needed connection and default logon details that are needed to communicate with the corresponding SAP R/3 system. Description Additional information about the selected connection. Application Server The name of the host system running SAP R/3. If the selected connection uses load balancing, Message Server is used instead. System Number The number assigned to the SAP R/3 system used to connect to SAP R/3. If the selected connection uses load balancing, System ID is used instead. Use this connection for design time Specifies a separate connection to SAP R/3 that is to be used only at design time for extracting metadata from the SAP R/3 system. This connection is not used at runtime. 48 Integration Guide Separate connections for design time and runtime are required to support SAP Exchange Infrastructure (SAP XI). The DataStage connection to SAP defined on the Stage General page is used to connect to SAP XI at job runtime. IDoc Data Directory Path The path that is used to generate and store IDoc data or to read IDoc data files when the SAP R/3 system is not available. This path is set in the IDoc Type properties in the field Directory containing temporary IDoc files for this type and connection. Enable offline IDoc processing Select to specify that IDocs are to be read from and stored to the path in IDoc Data Directory Path when the SAP R/3 system is not available at job runtime. Selecting IDoc types After you provide a InfoSphere DataStage connection to SAP on the General tab of the Stage page, you select an IDoc type on the IDoc Type tab of the Stage page. Configure an IDoc type as follows. The subsequent sections describe these steps in detail. 1. Click Select to open the Select IDoc Type dialog for selecting an IDoc type. 2. Select a type, and click OK. 3. A prompt can appear about an unconfigured IDoc type. Click Yes to configure the IDoc type for use with InfoSphere DataStage. 4. Define the IDoc type configuration properties on the IDoc Type Properties dialog. 5. The selected IDoc type and its component segment types are now visible on the IDoc Type tab of the Stage page. The Select IDoc Type dialog displays all the released IDoc types defined on the R/3 Enterprise system. It has the following components: v Connection. The connection name for the R/3 system whose IDoc types are being shown is indicated at the top of the dialog. v Description. A description of the R/3 system. v IDoc Types. A list of all the released IDoc types defined on the R/3 system. v Find. Click to open a Find IDoc Type dialog. It lets you search for IDoc Types that contain user-specified substrings in their name or description. v Properties. Click to view and change the InfoSphere DataStage configuration for the selected IDoc type. v OK. When you select an IDoc type and click OK, the system checks whether anyone on the InfoSphere DataStage system configured the IDoc type for the current connection. If not, you see the following message: This IDoc type has not been configured for use with InfoSphere

DataStage. Would you like to set these options now? Click Yes to set the options to default values. The IDoc Type Properties dialog opens (see the following section). Defining IDoc type properties When you confirm the default values after selecting an IDoc type, the IDoc Type Properties dialog opens. IBM InfoSphere Information Server Pack for SAP R/3 49 The IDoc Type Properties dialog contains various parameters set to default value s. The default settings are usually appropriate. 1. Name is the name of the selected IDoc type (read-only) with its description i n the Description field. 2. Directory containing temporary IDoc files for this IDoc type and connection is the path name for storing IDoc files for this IDoc type and connection. Initially, the directory is set to a default location, and the edit box is readonly. To enter your own directory, clear the Use default directory box. If Use default directory is selected, the default path name is displayed, and th e control is read-only. 3. Click Browse to browse for an alternate directory to store IDoc files for thi s IDoc type and connection. If Use default directory is cleared, this button is enabled. 4. Click Use default directory to browse for an alternate directory for storing IDoc files for this IDoc type and connection. If cleared, Directory containing temporary IDoc files for this IDoc type and connection and Browse are enabled, and you can specify an alternate directory. Otherwise, InfoSphere DataStage uses a default location. If the directory does not exist, and you save changes to the IDoc type configuration, the system tries to create the directory. If it cannot, you must choose another directory. If the directory has already been configured for this IDoc type using a differen t InfoSphere DataStage connection to SAP, you are warned that stages that read IDocs of this type process IDocs arriving from all connections that share this directory for the type. After you acknowledge this message, the values displayed in the dialog for the other configuration details are refreshed to match those already defined for the type through the other connections. Any changes you make to the configuration details for an IDoc type whose PSA is shared between two or more connections affect all connections processing this type from this PSA. 5. Click Archive processed IDoc files to archive processed IDocs rather than permanently remove them. The archive location is at the same level as the PSA for the IDoc. It is the responsibility of the Administrator to oversee the permanent storage o f archived IDocs, for example, moving them to an alternate disk location or removable storage media. You cannot restore processed IDocs. 6. If Run jobs that extract IDocs of this type after receiving n IDocs is select ed, jobs are automatically run that read IDocs of this type each time another n IDocs of this type are received by the IDoc listener server. (The default is one .) If the number of IDocs of this type is expected to be small and to arrive frequently, increase the number of IDocs that must arrive before jobs are automatically run. Alternately, you can disable automatic jobs invocation for this IDoc type by clearing the check box. In this case, use the InfoSphere DataStage Director

Client to schedule jobs. Note: See Setting batch size for manual IDoc extraction on page 38 for additional information. 7. The DataStage Logon Details for Running the Jobs area specifies the InfoSphere DataStage logon user name and password, and whether to use the defaults for the connection. 8. Specify a specific job to run automatically in the Assign job section: 50 Integration Guide v Select Run specific job to specify the project name and job name that is to run automatically when the stage receives the number of IDocs in the Run jobs that extract IDocs of this type after receiving field. In the Project Name field, choose the name of the project that is to run automatically. The Project Name field includes up to two project names: The most recent, saved project associated with this IDoc type The current project v Clear Run specific job to automatically run all jobs that extract this IDoc type when the stage receives the specified number of IDocs. 9. After you select an IDoc type and optionally define IDoc Type configuration properties, the Select IDoc Type dialog closes, and you return to the IDoc Type tab of the Stage page, with the properties of the selected IDoc type now visible . The IDoc Components area shows the control record and all the segments defined for the IDoc type with their descriptions. (The control record, one for each IDoc, is an administrative record that contains a standard set of fields describing the IDoc as a whole.) This area contains the following information: v Name. Shows the hierarchical relationship among the segments using a tree structure with their descriptions. (A segment type can appear only once within an IDoc type. The names for the segments are the segment definition names, not the segment type names. You can infer the segment type name from the segment definition name.) v Assigned Output Link. After particular segments in the IDoc Type are assigned to the output links of the stage, the IDoc Components control shows the names of the links in the Assigned Output Link column of the control. This gives you an overview of which segments are being extracted by the stage. The General tab of the Output page shows the segment type or control record for each output link as described in subsequent sections. Specifying SAP R/3 versions When an R/3 system is upgraded to a later version, you can add new fields to the segment definitions used by the IDoc types that are currently defined on the system, thus changing segment metadata for the IDoc types. To prevent third party applications that receive IDocs from the R/3 system from having to change to accommodate the new segment definitions, you can specify that IDocs of a particular IDoc type that are sent through a particular port use the segment definitions from an earlier version of the R/3 system. If this is already done in your SAP application, set R/3 Version on the IDoc Typ e Properties dialog to the same value that is set for the IDoc type in the R/3 sys tem itself (See Connection and Logon Details page). R/3 Version lists the version that is the same or earlier than that of the R/3 s ystem that is specified in the connection. It defaults to the current version of the R /3 system. Version 46E and Later. By default, the IDoc Extract product only knows about R/3 46D or earlier. If you have an R/3 system that is later than 46D, the program re ads the version from the R/3 system and automatically adds it to the list.

IBM InfoSphere Information Server Pack for SAP R/3 51 Missing Versions. But suppose the R/3 system is Version 46F. The combo box then includes the 46F, but may be missing 46E. If you want to specify 46E, type the value directly into the edit control of the combo box. When you click OK, the system verifies that the specified R/3 Version is unknown , and prompts: R/3 version "46E" is not among the versions currently known to DataStage. Would you like "46E" to be added to the list of known versions? If you click Cancel, the IDoc Type Properties dialog stays open. If you enter an incorrectly formatted version and click OK, the following error appears: "xx" is not a valid R/3 version. A correctly formatted version must consist of t wo digits followed by an upper case letter. If you enter a version number that is later than that of the R/3 system specifie d in the connection, you see the following error: R/3 Version "xxx" is greater than "xxx", the version of the connection. The R/3 version for the IDoc type must not be greater than the version of the connection. If you change the port version of the connection for the stage or the R/3 versio n of the IDoc type for the stage, the stage automatically refreshes itself using appropriate IDoc metadata. If the either of these versions is changed before you open the stage editor, the act of opening the stage editor produces the followin g warning: Either the port version has changed for connection "xxx", or the R/3 version in the configuration for IDoc type "xxx" has changed. The IDoc metadata for the stage w ill now be fixed. Defining IDoc extract output links After you select an IDoc type, you assign the control record or a segment to eac h output link. Begin the selection process from the General tab on the Output page . After you choose the output link from the Output name box, the following steps summarize how output links function. The subsequent sections describe these steps in detail. 1. Click Select to open the Select IDoc Component to Extract dialog. The IDoc Component to Extract, Description, and Fields in Component information is displayed after you select a control record or a segment for the link. 2. The selected segment type and its fields now appear on the General tab of the Output page. The administrative fields common to all segment types appear at the beginning of the list. 3. Columns are automatically generated for each link when the segment type is selected. 4. You can delete unnecessary columns (administrative fields that are rarely use d are not visible). 52 Integration Guide 5. Columns for missing fields can be added by clicking Add Columns on the Columns tab of the Output page.

**************************8 InfoSphere DataStage connections to SAP R/3 page This page displays all the connections to SAP that are currently defined on the InfoSphere DataStage server machine. Add, Properties, Import into, Export, and 74 Integration Guide Remove let you manage the list of connections that is maintained on the InfoSphere DataStage server machine. They function the same as the corresponding buttons on the Select DataStage Connection to R/3 dialog. The following steps let you define a InfoSphere DataStage connection to SAP. The subsequent sections describe these steps in detail. 1. Run the InfoSphere DataStage Administrator for SAP on a InfoSphere DataStage client machine. 2. Click Add > New to define the properties for the new connection. 3. Enter a connection name, a description, and SAP connection and logon details. 4. Optionally, use load balancing. 5. Enter an IDoc listener program ID (the same ID must be defined for the tRFC port in the SAP database). 6. Define the properties for running jobs automatically as IDocs arrive on the DataStage Job Options for IDocs page. 7. Click Add to test the connection and logon properties and add the connection. An IDoc listener server starts automatically after the new connection is added. 8. Configure the SAP system to access InfoSphere DataStage by doing the following: a. Log on to the SAP R/3 system. b. Create a tRFC port, and assign it the IDoc listener program ID that was set for the connection. c. Create a logical system to represent InfoSphere DataStage. d. Attach the tRFC port to the logical system. 9. Click IDoc Types to see the IDoc types for the selected connection. It opens the IDoc Types dialog where you can set the properties of IDoc types. The InfoSphere DataStage Connections to R/3 page has the following components: v Add. Click to open a popup menu with the New and Import items. Do the following: 1. Click New to open the Connection Properties dialog, which lets you define the properties for the new connection. Here you can specify Connection Name, Description, and SAP connection and default logon details for the new connection (See Defining InfoSphere DataStage connections to SAP R/3). 2. Click Import to open a standard Open File dialog that lets you select the export file to be imported. This lets you import a new connection (see Importing new connections). v Properties. Click to open the Connection Properties dialog, showing the properties of the selected connection. This is the same dialog that is opened when you click New on the Select DataStage Connection to SAP dialog, but in this context the connection Name is read-only, and the Add button is replaced by an OK button. v Import into. Click to import IDoc type configurations into the selected connection that already exists. A standard Open File dialog appears so you can select a file to be imported (see Importing IDoc type configurations). v Export. Click to save the configuration information for the selected connectio n and all its associated IDoc types into a file (see Exporting connections). v Remove. Click to delete the selected connection after your confirmation. v IDoc Types. Click to see the IDoc types for the selected connection. It opens the IDoc Types dialog (see IDoc Types dialog). This button does not appear on the Select InfoSphere DataStage Connection to SAP dialog. IBM InfoSphere Information Server Pack for SAP R/3 75

v IDoc Log. Click to open the IDoc Log dialog. This dialog displays log messages reported by the IDoc listener for the connection (see the section IDoc Log dialog). This button does not appear on the Select InfoSphere DataStage Connection to SAP dialog. If Listen for IDocs received through this connection is cleared on the IDoc Listener Settings page, the Import Into, IDoc Types, and IDoc Log buttons on thi s page are disabled when you select that connection. Also, if this same option is cleared, Import and Export operations apply only to the properties for the connection. They do not involve IDoc Type configurations. (This is useful for connections that are only used for ABAP or BAPI stages, rather than IDoc stages. )