1. Manuals
  2. Brands
  3. Oracle Manuals
  4. Network Card
  5. B31003-01
  6. User manual

Oracle B31003-01 User Manual

Oracle application server adapter for ims/tm user's guide
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Enlarged version
Oracle® Application Server
Adapter for IMS/TM User's Guide
10g Release 3 (10.1.3.1.0)
B31003-01
January 2007

Advertisement

Table of Contents
loading

Summary of Contents for Oracle B31003-01

  • Page 1 Oracle® Application Server Adapter for IMS/TM User’s Guide 10g Release 3 (10.1.3.1.0) B31003-01 January 2007...
  • Page 2 Oracle Application Server Adapter for IMS/TM User’s Guide, 10g Release 3 (10.1.3.1.0) B31003-01 Copyright © 2006, 2007, Oracle. All rights reserved. Primary Author: Jeanne Wiegelmann Contributing Authors: Yishai Hadas, Dror Harari, Adeeb Massad, Meera Srinivasan, Bo Stern, Shashi Suravarapu, Costi Zaboura, Sheela Vasudevan, Marian Jones The Programs (which include both the software and documentation) contain proprietary information;...

  • Page 3: Table Of Contents

    Preface ... vii Audience... vii Documentation Accessibility ... vii Related Documents ... Conventions ... Introduction OracleAS Adapter for IMS/TM Overview ... 1-1 OracleAS Adapter for IMS/TM Architecture... 1-2 Integration Flow from Oracle Application Server to a Legacy Application ... 1-2 Integrating OracleAS Adapter for IMS/TM with OC4J Integrating OracleAS Adapter for IMS/TM with OC4J...
  • Page 4 Integrating OracleAS Adapters for IMS/TM with Oracle BPEL Process Manager Overview of Integrating OracleAS Adapters for IMS/TM with Oracle BPEL Process Manager ... Configuring Oracle BPEL Process Manager to interact with the OracleAS Adapter for IMS/TM .. Setting up the Connection to the Oracle Connect Server ... 4-2 Checking Metadata Availability Using Oracle JDeveloper ...
  • Page 5 Starting the Daemon... 6-10 Setting Up Oracle Connect to Work Under IMS/TM... 6-10 Setting Up Oracle Connect for Reentrancy ... 6-11 Updating an Existing Oracle Connect Installation with IMS/TM... 6-12 Installing Oracle Studio... 6-13 Installing Oracle Studio from the CD-ROM... 6-14 Configuring Oracle Connect ...

  • Page 7: Preface

    This guide is the primary source of user and reference information on OracleAS Adapters for IMS/TM, which enables client applications to access transactions running under IMS/TM through the Sun J2EE Connector Architecture (J2CA) API. This document describes the features of OracleAS Adapters for IMS/TM that apply to the UNIX, Windows 2000, Windows XP, and Windows Server 2003 operating systems.

  • Page 8: Related Documents

    http://www.oracle.com/accessibility/ Accessibility of Code Examples in Documentation Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

  • Page 9: Introduction

    Oracle Application Server Adapter for IMS/TM (OracleAS Adapter for IMS/TM) enables you to connect Oracle Application Server to an Information Management System-Transaction Management (IMS/TM) system. This section provides an overview of the features and architecture of OracleAS Adapter for IMS/TM. This section contains the following topics: OracleAS Adapter for IMS/TM Overview ■...

  • Page 10: Oracleas Adapter For Ims/Tm Architecture

    OracleAS Adapter for IMS/TM Architecture OracleAS Adapter for IMS/TM Architecture OracleAS adapter includes the following components: J2CA 1.5 IMS/TM adapter: The J2CA IMS/TM adapter is a standard resource ■ adapter that is compliant with J2EE Connector Architecture, providing J2EE components connectivity. Oracle Connect: Oracale Connect runs on the legacy system and handles requests ■...

  • Page 11: Integrating Oracleas Adapter For Ims/Tm With Oc4J

    Integrating OracleAS Adapter for IMS/TM To deploy and integrate OracleAS Adapter for IMS/TM with Oracle Application Server Containers for J2EE (OC4J), you need to configure the J2CA 1.5 IMS/TM adapter. This section includes the following topics: Integrating OracleAS Adapter for IMS/TM with OC4J ■...

  • Page 12: Configuring The J2Ca 1.5 Ims/Tm Adapter

    Configuring the J2CA 1.5 IMS/TM Adapter The lifecycle contract provides the mechanism for the application server to manage the lifecycle of the resource adapter instance. Work management contracts enable the resource adapter to carry out its logic by using threads dispatched by an application server, rather than creating threads on its own. The handshake is done through a Work instance submission.

  • Page 13: Using The Cci Api To Develop Applications

    Table 2–1 (Cont.) OC4J Connection Properties Property serverName workspace portNumber userName (optional) password (optional) persistentConnecti (optional) keepAlive (optional) firewallProtocol (optional) connectTimeout (optional) encryptionProtocol (optional) encryptionKeyName (optional) encryptionKeyValue (optional) fakeXa Using the CCI API to Develop Applications You can develop applications to run adapter interactions using the Common Client Interface (CCI) API.

  • Page 14: Configuring Multiple Adapters

    Configuring Multiple Adapters Create a Connection object using the selected ConnectionFactory. A Connection is a handle to the underlying network connection to the EIS, which is identified in the oc4j-ra.xml file by the serverName property. Create a Connection object using the selected ConnectionFactory. Specify the interaction properties using an AttuInteractionSpec object.

  • Page 15: Troubleshooting Oracleas Adapter For Ims/Tm

    Troubleshooting OracleAS Adapter for Troubleshooting Oracle AS Adapter for IMS/TM involves checking various definitions and properties in Oracle Connect, including daemon status, workspace options, server parameters, and various system logs. This section contains the following topics: Troubleshooting the Daemon ■ Resolving Communication Errors ■...

  • Page 16: Task: Starting The Daemon

    Troubleshooting the Daemon Task: Starting the Daemon Activate INSTROOT.USERLIB(ATTDAEMN) as a started task to invoke the daemon. For example, in the SDSF screen enter the following: '/s ATTDAEMN' WhereINSTROOT is the high-level qualifier where Oracle Connect is installed. See Also: the ATTDAEMN JCL.

  • Page 17: Workspace Options

    Table 3–1 (Cont.) Daemon Options Option Description View Log Displays the daemon log. For details see on page 3-4. View Events Displays the daemon events log. Displays information about the computer where the Daemon Properties daemon is running, such as the physical address and any username and password needed to access the computer.

  • Page 18: Server Options

    Troubleshooting the Daemon Server Options Right-click a server to display the options available for the server, including the ability to display the server log. The following table lists the available options: Table 3–3 Server Options Option Status View Log View Events Kill server Refresh Daemon Logs...

  • Page 19: The Daemon Log Monitor

    The Daemon Log Monitor The daemon log displays activity between clients and the daemon, including clients logging in and logging out from the daemon. You can change the level of logging by clicking Properties. The following levels of logging are available: none: The log displays who has logged in and out from the daemon.

  • Page 20: Resolving Specific Errors

    Resolving Specific Errors Table 3–4 Scenarios When a Client Is Disconnected Idle (Not Processing a Client Scenario Request) Explicit Disconnect The server is immediately notified of the disconnect and either becomes (client explicitly available for use by another client or closes connection terminates (if it is not reusable).
  • Page 21 C009: IRPCD process has been terminated by user request. Cause: This message is informational only. The daemon successfully shut down. Action: No action required. C00A: Application %s not found. Cause: The requested workspace does not exist. Action: Check that the workspace defined in the oc4j-ra.xml file is also defined in the daemon configuration on the IBM OS/390 or z/OS platform.
  • Page 22 Resolving Specific Errors C010: Anonymous server logins are not allowed. Cause: Internal error. Action: Contact Oracle Support Services. C011: Client has already timed out. Cause: A server process was started on behalf of a client and the client has timed out before the server completed its startup.
  • Page 23 APF authorize all the steplibs in the server To set impersonation: script on OS/390 computer. In the WS Security tab of the Navigator workspace under the daemon node in the Configuration Explorer, check the Use specific workspace account and clear the Workspace account field of all values.
  • Page 24 Resolving Specific Errors Action: Check the TCP/IP subsystem on the computer by trying to ping it or run FTP or Telnet to or from it. C021: Required variable %s not found Cause: An environment variable required by the Oracle Connect server was not defined when the server started up.
  • Page 25 Action: Check whether you have sufficient system privileges. C027: Cannot create TCP service for %s Cause: An error occurred within the TCP/IP subsystem Action: Check the TCP/IP subsystem on the computer by trying to ping it or run FTP or Telnet to or from it. C028: Unable to register (%s, %d, tcp) Cause: This error may happen when a portmapper is used (host:a) but the portmapper is not available.
  • Page 26 Resolving Specific Errors C032: An IRPCD program is required Cause: Internal error. Action: Contact Oracle Support Services. C033: An IRPCD super-server is required for module events Cause: Internal error. Action: Contact Oracle Support Services. C034: An invalid super-server module ID was specified, %d Cause: Internal error.
  • Page 27 Action: A system or process quota limit has been exceeded. Either increase the quota or lower the Clients per server limit field value in the WS Info. section of the daemon configuration. "WS Info." on page C-7. See Also: C047: %s out of memory Cause: Not enough memory was available to Oracle Connect to complete a requested operation.
  • Page 28 Resolving Specific Errors Action: The server startup script failed. Action: The username given is not allowed to use the requested server. Use an authorized username. Action: A limit on concurrent clients for a server has been reached. Try again later. Action: If you use impersonation, then check the user profile on the client.
  • Page 29 Action: Grant administrative privileges to the user/account using the Administrator parameter of the Daemon Security or WS Security sections in the daemon configuration. "Daemon Security" See Also: page C-16. C075: Failed to register daemon in the TCP/IP service table Cause: Registration of the daemon in the TCP/IP services file has failed. Action: Check that the account running the daemon has the permissions to update the TCP/IP services file.
  • Page 30 Resolving Specific Errors J0036: %s: %s Cause: One of the following errors was received from the server: 0 - server.internalError, 1 - client.xmlError, 2 - client.requestError, 3 - client.noActiveConnection, 4 - server.resourceLimit, 5 - server.redirect, 6 - client.noSuchResource, 7 - client.authenticationError, 8 - client.noSuchInteraction, 9 - client.noSuchConnection, 10 - server.notImplemented, 11 - server.xaProtocolError, 12 - server.xaUnknownXID, 13 - server.xaDuplicateXID, 14 - server.xaInvalidArgument, 15 - client.autogenRejected, 16 -...
  • Page 31 J0072: Value must be of type Object[] Cause: In a PUT operation, the value must be mapped record array. Action: Change the value used in the operation to a valid value. J0078: In nonpersistent connection and non keep alive encryption is not supported - ignored Cause: Encryption is not supported for nonpersistent connections.
  • Page 32 Resolving Specific Errors 3-18 Oracle Application Server Adapter for IMS/TM User’s Guide...
  • Page 33 Integrating OracleAS Adapters for IMS/TM with Oracle BPEL Process Manager To deploy and integrate OracleAS Adapters for IMS/TM with Oracle BPEL Process Manager, you need to configure BPEL Process Manager. This section includes the following topics: Overview of Integrating OracleAS Adapters for IMS/TM with Oracle BPEL ■...

  • Page 34: Setting Up The Connection To The Oracle Connect Server

    Configuring Oracle BPEL Process Manager to interact with the OracleAS Adapter for IMS/TM Configuring Oracle BPEL Process Manager to interact with the OracleAS Adapter for IMS/TM This section includes the following topics: Setting up the Connection to the Oracle Connect Server ■...
  • Page 35 Configuring Oracle BPEL Process Manager to interact with the OracleAS Adapter for IMS/TM connection factory with this name exists on the OC4J server. If it does not, you need to create it, or change the name of the connection factory to the name of a connection factory that exists.
  • Page 36 Configuring Oracle BPEL Process Manager to interact with the OracleAS Adapter for IMS/TM <plt:partnerLinkType name="addPartnerLinkType"> <plt:role name="addRole"> <plt:portType name="tns:addPortType"/> </plt:role> </plt:partnerLinkType> /definitions> 4-4 Oracle Application Server Adapter for IMS/TM User’s Guide...

  • Page 37: Advanced Features Of Oracleas Adapter For Ims/Tm

    Advanced Features of OracleAS Adapter for Oracle Connect includes a number of tuning parameters that can improve performance. Specifically, the daemon can be configured to optimize communication between the IBM OS/390 or z/OS platform and a client. In addition, the binding environment can be tuned to optimize request handling.

  • Page 38: Editing The Workspace

    Configuring the Daemon for High Availability Figure 5–1 The New Daemon Workspace screen Specify a name for the new workspace and optionally provide a description. Specify whether you want default settings or copy the properties of an existing workspace. To copy the properties of an existing workspace, click Ellipsis and select the workspace which properties you want to copy.
  • Page 39 Perform the following steps to access these tabs: From the Start menu, select Programs, Oracle, and then select Studio. In the Configuration Explorer, expand the the computer defined in IBM OS/390 or z/OS Platform in Oracle Studio" Expand the Daemons node. The daemon configurations available on this computer are listed.
  • Page 40 Configuring the Daemon for High Availability The other modes can be set so that the server processes are reusable by setting the ■ number of times a process can be reused with the Reuse limit value (the maximum number of times a particular server process can be reused or how many clients it can serve before it is retired).

  • Page 41: Configuring A Binding Environment

    removed from the pool and allocated to a client). The default for this parameter is 0, meaning that new servers are created only when there are no other available servers. Set maximum number of servers: The maximum number of available server ■...

  • Page 42: Comm Category

    Configuring a Binding Environment miscellaneous Category ■ odbc Category ■ oledb Category ■ optimizer Category ■ queryProcessor Category ■ transactions Category ■ tuning Category ■ comm Category The following table lists the parameters that define the communication buffers: Table 5–2 comm Category Parameters Parameter comCacheBufferSize Specifies the size of a memory buffer on a client, which is...

  • Page 43: Miscellaneous Category

    Table 5–3 (Cont.) debug Category Parameters Parameter queryWarnings traceDir miscellaneous Category The following parameters define miscellaneous operations, including globalization support and the directory where temporary files are written. Table 5–4 misc Category Parameters Parameter codepage cvtSeverityLevel The data type conversion policy when a conversion error edit language nlsString...

  • Page 44: Odbc Category

    Configuring a Binding Environment Table 5–4 (Cont.) misc Category Parameters Parameter year2000Policy odbc Category The odbc parameters are not applicable for use with OracleAS Adapter for IMS/TM. oledb Category The oledb parameters are not applicable for use with OracleAS Adapter for IMS/TM. optimizer Category The optimizer parameters are not applicable for use with OracleAS Adapter for IMS/TM.

  • Page 45: Tuning Category

    Table 5–5 transactions Category Parameters Parameter convertAllToDistributed When set to true, converts all simple transactions into convertAllToSimple disable2PC logFile recoveryDelay useCommitConfirmTable tuning Category The tuning parameters are not applicable for use with OracleAS Adapter for IMS/TM. Migration Considerations You can migrate an adapter configuration from one platform to another. The configuration information is stored in the Oracle Connect repository on the source platform and is exported to an XML file which can then be imported to the target platform.

  • Page 46: Security Considerations

    Security Considerations Security Considerations Oracle Connect works within the confines of the platform security system. For example, on an OS/390 computer with RACF installed, and with the workspace server mode set to multi-tasking, a RACROUTE VERIFY is performed for each task in the address space, according to the client connection.

  • Page 47: Transaction Support

    When the client request accesses the legacy platform through the daemon, either ■ anonymous access is allowed or a valid user name and password must be provided for the computer in the user profile. The userName and password properties in the J2CA 1.5 IMS/TM adapter are used at this stage to access the daemon.
  • Page 48 Transaction Support 5-12 Oracle Application Server Adapter for IMS/TM User’s Guide...

  • Page 49: Installing And Configuring Oracleas Adapter For Ims/Tm

    Installing and Configuring OracleAS Adapter This section describes how to install Oracle Connect and Oracle Studio from the CD-ROM and how to configure Oracle Connect using Oracle Studio. Note: section, the J2CA 1.5 IMS/TM adapter must be installed with Oracle Application Server. Installing the J2CA 1.5 IMS/TM adapter is described in Oracle Application Server Adapter Installation Guide.

  • Page 50: Software Requirements

    Preinstallation Tasks Table 6–1 Oracle Connect Hardware Requirements Hardware Component Processor Memory CD-ROM Drive Disk Space (3380 and 3390 disks) Software Requirements The following table summarizes the software requirements for Oracle Connect. Table 6–2 Oracle Connect Software Requirements Software Component Operating System IMS/TM TP Monitor Oracle Application...

  • Page 51: Installing Oracle Connect On An Ibm Os/390 Or Z/Os Series Platform

    Table 6–4 Oracle Studio Software Requirements Software Component Operating System Microsoft Installing Oracle Connect on an IBM OS/390 or z/OS Series Platform Note: installed on the IBM OS/390 or z/OS platform, then follow the instructions described in Installation with IMS/TM" The other back-end adapters that run on an IBM OS/390 or z/OS platform are: OracleAS Adapter for CICS...

  • Page 52: Preinstallation Instructions

    Installing Oracle Connect on an IBM OS/390 or z/OS Series Platform Table 6–5 (Cont.) Preinstallation Information Topic Required Information Unit Output class JCL job card ISPF load library name Table 6–6 Required Permissions Permission Permission to define an APF-authorized library Permission to write to an active proclib, such as user.proclib Permission to update the security manager, such as RACF Optionally, permission to specify an output class for Oracle Connect output...

  • Page 53: Installing The Kit

    Note: output class for Oracle Connect output. Assigning a device that is set on HOLD prevents the loss of log information when Oracle Connect started tasks finish. Oracle Connect for the IBM OS/390 or z/OS platform is contained in the following datasets: OCL1012.TRANSMIT.KIT ■...
  • Page 54 Installing Oracle Connect on an IBM OS/390 or z/OS Series Platform da('nnn.TRANSMIT.LIB') [UNIT(unit) VOLUME(volume)] This extracts the nnn.TRANSMIT.LIB library from the nnn.TRANSMIT.KIT kit to the specified unit and volume. If a unit and volume are not specified, then the library is extracted to the current unit and volume. Run the PREPARE member of the nn.TRANSMIT.LIB library: ex PREPARE Follow the instructions in the Response column in...
  • Page 55 Table 6–9 Installation Prompts and Responses Screen DO YOU WANT TO USE SMS MANAGED STORAGE FOR THIS INSTALLATION Y/N [N]: THE SOFTWARE WILL BE INSTALLED UNDER THE HIGH LEVEL QUALIFIER THAT YOU WILL CHOOSE. ENTER THE HIGH LEVEL QUALIFIER ["QUALIFIER"]: ENTER THE STORCLASS FOR TEMP DATASETS ['STORCLASS']: ENTER THE UNIT NAME FOR INSTALLATION...

  • Page 56: Postinstallation Instructions

    Installing Oracle Connect on an IBM OS/390 or z/OS Series Platform Table 6–10 IMS/TM Adapter-Specific Installation Prompts and Responses Screen ENTER THE ISPF LOAD LIBRARY NAME [ISP.SISPLOAD] : PLEASE CONFIRM (YES/NO/QUIT) [YES] : ENTER THE OUTPUT CLASS FOR INSTALLATION OUTPUT [A] : DO YOU WANT TO USE THE DEFAULT JOB CARD Y/N [Y] The installation is completed.
  • Page 57 Installing Oracle Connect on an IBM OS/390 or z/OS Series Platform To define a DSN as APF-authorized, in the SDSF screen Note: enter the following command: "/setprog apf,add,dsn=INSTROOT.loadaut,volume=vol002" Where vol002 is the volume where you installed Oracle Connect and INSTROOT is the high-level qualifier where Oracle Connect is installed.

  • Page 58: Starting The Daemon

    Installing Oracle Connect on an IBM OS/390 or z/OS Series Platform Access to an Open OS/390 segment (that defines access to TCP/IP OA ■ sockets). ALTER authority on datasets under INSTROOT to access to read, write, allocate ■ and delete datasets under INSTROOT. The installation includes a PS, INSTROOT.DEF.GBLPARMS, that contains global ■...

  • Page 59: Setting Up Oracle Connect For Reentrancy

    Installing Oracle Connect on an IBM OS/390 or z/OS Series Platform GRNAME for the XCF group name and OTMANM for the IMS member name in that XCF group, as in the following example: EDIT IMS.PROCLIB(DFSPBIV1) - 01.03 command ===> 000082 AOIS =, 000083 GRNAME=IMSATT01, 000084 OTMA=YES, 000085 MAXPST=...

  • Page 60: Updating An Existing Oracle Connect Installation With Ims/Tm

    Updating an Existing Oracle Connect Installation with IMS/TM Using the LPA reduces real storage usage, because everyone shares the LPA copy, and fetch time. If you intend using impersonation, so that you can run in a Note: security context that is different than the context of the process that owns the server, then do the following: Place the INSTROOT.LOAD(ATYSVCW) member in an ■...

  • Page 61: Installing Oracle Studio

    Table 6–13 (Cont.) IMS/TM Adapter Installation Prompts and Responses Screen DO YOU WANT ORACLE CONNECT FOR LEGACY ADAPTER TO WORK WITH IMS/DB UNDER CICS (YES/NO) [NO]: ENTER THE CICS EXCI LOAD LIBRARY NAME [CICSTS13.CICS.SDFHEXCI]: PLEASE CONFIRM (YES/NO/QUIT) [YES]: DO YOU WANT ORACLE CONNECT FOR LEGACY ADAPTER TO WORK WITH CICS APP ADAPTER (YES/NO) [YES]: ENTER THE CICS EXCI LOAD LIBRARY NAME...

  • Page 62: Installing Oracle Studio From The Cd-Rom

    Configuring Oracle Connect If Oracle Studio is already installed because you are also Note: using another legacy adapter, then you do not need to reinstall it. The other legacy adapters are: OracleAS Adapter for Tuxedo ■ OracleAS Adapter for CICS ■...

  • Page 63: Securing Access To Oracle Connect

    Enter the name of the computer you want to connect to, or click Browse to select the computer from the list of computers that is displayed and which use the default port (2552). Specify the username and password of the user who was specified as the administrator when Oracle Connect was installed.
  • Page 64 Configuring Oracle Connect From the Start menu, select Programs, Oracle and then select Studio. Oracle Studio opens. Select Window from the menu bar and then select Preferences. The Preferences screen is displayed, as shown in the following figure: Figure 6–2 The Preferences screen Select the Studio node.

  • Page 65: Specifying Users With Administrative Rights

    Specifying Users with Administrative Rights By default, only the user who was specified during the installation as an administrator has the authorization to modify settings on that computer from Oracle Studio. This user can then authorize other users to make changes or to view the definitions for a selected computer.

  • Page 66: Setting Up Run-Time User Access To The Ibm Os/390 Or Z/Os Platform

    Configuring Oracle Connect Add users or groups of users by clicking Add User or Add Group for the relevant sections. The user or group that is added must be recognized as a valid user or group for the computer. Once a name has been added to a section, only the user or group who logs on with that user name has the relevant authorization.

  • Page 67: Modeling Interactions For Oracleas Adapter For Ims/Tm

    Enter the name and password used to access the computer and confirm the password. Click OK. Modeling Interactions for OracleAS Adapter for IMS/TM Modeling interactions for OracleAS Adapter for IMS/TM involves defining an Oracle Connect back-end adapter using Oracle Studio. All the definitions specified in Oracle Studio are written to the IBM OS/390 or z/OS platform.
  • Page 68 Configuring Oracle Connect Figure 6–7 The New Adapter screen Select Events. Click Finish. The back-end adapter is added to the list and the definition opens for editing. Note: Other adapters that are displayed in the Type list are not supported with the version of Oracle Connect installed at the site. Select the Properties tab and change any of the properties for the adapter, as required.

  • Page 69: Generating Outbound Interactions

    The Properties tab comprises fields, as listed in the following table: Table 6–14 Adapter Properties Property Description cachLastTpipe Cache the last transaction pipe used. cacheXcfConnection Cache the XCF connection information. maxSessions The maximum number of sessions allowed. The default value is 5. racfGroupId The RACF facility group identification.
  • Page 70 Configuring Oracle Connect Select ImsTm Import Manager from the Import type list as shown in the following figure: Figure 6–9 The New Metadata Import screen Click Finish. The Metadata Import wizard is displayed. Click Add. The Add Resources screen is displayed, which provides the option to select files from the local computer or copy the files from another computer.
  • Page 71 Figure 6–10 The Add Resources screen Right-click the computer and select Set Transfer Type. Enter the transfer type (ASCII or BINARY) and click OK. Expand the list of the added site until you find the necessary COBOL files. To change the high-level qualifier, right-click the computer and select Change Root Directory.
  • Page 72 Configuring Oracle Connect Figure 6–11 The Apply Filters screen Apply filters to the copybooks, as needed. The following table lists the available filters: Table 6–15 Available Filters Filter COMP_6 switch Compiler source Storage mode Ignore after column IgnoreFirst6 Replace hyphens (-) in record and field names with underscores (_)
  • Page 73 In the import wizard, click Next. The Add Interactions screen is displayed, as shown in the following figure: Figure 6–12 The Add Interactions screen Click Add to add an interaction for the IMS/TM adapter. Provide the information, as listed in the following table: Table 6–16 Interaction Parameters Parameter...

  • Page 74: Viewing The Xml Schema

    Configuring Oracle Connect Table 6–16 (Cont.) Interaction Parameters Parameter Description Interaction-Specific Parameters Add as many interactions as necessary and click Next to generate the metadata definitions for the adapter. Specify that you want to transfer the metadata from the Windows computer to the IBM OS/390 or z/OS platform and click Finish.

  • Page 75: Creating Xml Schemas

    Configuring Oracle Connect Figure 6–13 The Source tab Creating XML Schemas The XML schema describing the adapter interactions and the input and output records for these interactions are created automatically during the import procedure, as described in "Generating Outbound Interactions" on page 6-21.
  • Page 76 Configuring Oracle Connect 6-28 Oracle Application Server Adapter for IMS/TM User’s Guide...

  • Page 77: Advanced Tuning Of The Metadata

    Advanced Tuning of the Metadata Oracle Studio enables you to define outbound adapter interactions. In addition, Oracle Studio defines input and output structures used for these interactions. The interactions and input and output structures are maintained as metadata in the Metadata tab of Oracle Studio.

  • Page 78: Interaction Tab

    Metadata for the Back-end Adapter The General tab is shown in the following figure: Figure A–1 The General tab The General tab comprises fields, as listed in the following table: Table A–1 General tab Components Field Adapter definition name Description Authentication mechanism Max request size Max active connections...

  • Page 79: Schema General Tab

    Figure A–2 The Interactions tab The Interaction tab comprises fields, as listed in the following table: Table A–2 Interaction tab Components Field Interaction name Description Mode Input record Output record Interaction Specific Parameters Schema General Tab Use the Schema General tab to define the general details of the input and output record structures for the interaction.
  • Page 80 Metadata for the Back-end Adapter The Schema General tab is shown in the following figure: Figure A–3 The Schema General tab The Schema General tab comprises fields, as listed in the following table: Table A–3 Schema General tab Components Field Schema name Version Header...

  • Page 81: Schema Record Tab

    Schema Record Tab Use the Schema Record tab to define the input and output record structures for the interaction. The Schema Record tab is shown in the following figure: Figure A–4 The Schema Record tab The Schema Record tab comprises fields, as listed in the following table: Use the Fields List area to define single data items within a record.
  • Page 82 Metadata for the Back-end Adapter Table A–4 (Cont.) Schema Record tab Components Field Type Length Note: Use the See Also: for details about the mapping from COBOL data types to Oracle Connect data types. A-6 Oracle Application Server Adapter for IMS/TM User’s Guide Description The data type of the field.
  • Page 84 Metadata for the Back-end Adapter A-8 Oracle Application Server Adapter for IMS/TM User’s Guide...

  • Page 85: Back-End Adapter Data Type Support

    Back-end Adapter Data Type Support OracleAS Adapters for IMS/TM supports a number of data types that are used when defining metadata in Oracle Studio. The data types are mapped from the COBOL data types during the import procedure. Note: IMS/TM and Oracle Application Server is performed internally by Oracle Connect.
  • Page 86 Data Type Mapping Table 6–17 (Cont.) Data Type Mapping: COBOL and Oracle Connect Back-end Adapter COBOL Data Type NATIVE-4 NATIVE-8 PACKED-DECIMAL POINTER [SIGN [IS]] TRAILING [SIGN [IS]] TRAILING SEPARATE [CHARACTER] B-2 Oracle Application Server Adapter for IMS/TM User’s Guide Oracle Connect Data Type string string string...

  • Page 87: Advanced Tuning Of The Daemon

    Advanced Tuning of the Daemon The daemon configuration is managed using Oracle Studio. Daemon configuration is divided into the following groups: Daemon Control ■ Daemon Logging ■ Daemon Security ■ Workspaces ■ Daemon Control Using the Daemon Control tab, you define various daemon control options. The Daemon Control tab is accessed as follows: From the Start menu, select Programs, Oracle, and then select Studio.
  • Page 88 Daemon Control Figure 6–14 The Daemon Control tab The Daemon Control tab comprises fields, as listed in the following table: Table 6–18 Daemon Control tab Components Field Automatically recover from failure Maximum XML request size Maximum XML in memory Default language Call timeout C-2 Oracle Application Server Adapter for IMS/TM User’s Guide Description...

  • Page 89: Daemon Logging

    Table 6–18 (Cont.) Daemon Control tab Components Field Connect timeout Client idle timeout Daemon Logging Using the Daemon Logging tab, you define the daemon log file settings, the log file structure and the location where the log is saved. In addition, use it to define the data that is logged and traced in the file.
  • Page 90 Daemon Logging Figure 6–15 The Daemon Logging tab The Daemon Logging tab comprises fields, as listed in the following table: Table 6–19 Daemon Logging tab Components Field Daemon log file location Logging options Client requests for server Administration requests for daemon Daemon operations Daemon logins...

  • Page 91: Daemon Security

    Table 6–19 (Cont.) Daemon Logging tab Components Field System trace Timing Binary XML log level Server log filename format The following tokens can appear in the log file template and will be replaced accordingly: %A: workspace name ■ %D: date (yymmdd) ■...
  • Page 92 Daemon Security You can also change daemon settings using the Note: Configuration Explorer, by selecting a computer and scrolling the list to the required daemon. Right-click the daemon and select Edit Daemon. Changes made to the daemon configuration are not implemented. They are only implemented after the configuration is reloaded using the Reload Configuration option in the Runtime Manager.

  • Page 93: Workspaces

    Table 6–20 (Cont.) Daemon Security tab Components Field Selected users only Machine access Allow anonymous login Cached password Encryption methods The name is prefixed with ’@’, to utilize the operating system GROUP feature. Workspaces A daemon can include a number of workspaces. A workspace defines the server processes and environment that are used for the communication between the client and the server for the duration of the client request.
  • Page 94 Workspaces Expand the Daemons node to display the workspaces in the Runtime Explorer. Right-click the workspace and select Edit Workspace Configuration. The WS Info. tab opens. After making changes to the workspace, right-click the daemon and select Reload Configuration. You can also change daemon settings using the Note: Configuration Explorer, by selecting a computer and scrolling the list to the required daemon.

  • Page 95: Ws Server

    Table 6–21 (Cont.) WS Info tab Components Field Server type Workspace binding name Timeout parameters Client idle timeout Connect timeout WS Server Using the WS Server tab, you specify the features that control the operation of the servers started up by the workspace and allocated to clients. For example, you can configure the workspace to start up a number of servers for future use, prior to any client request, instead of starting each server when a request is received from a client.
  • Page 96 Workspaces Right-click the daemon and select End Unused Servers. Any servers in the connection pool are closed and new servers start with the new configuration. The WS Server tab is shown in the following figure: Figure 6–18 The WS Server tab The WS Server tab comprises fields, as listed in the following table: C-10 Oracle Application Server Adapter for IMS/TM User’s Guide...
  • Page 97 Table 6–22 WS Server tab Components Field Description Workspace server Specifies the type of new server processes that the daemon mode starts up. The daemon supports the following server modes: singleClient: Each client receives a dedicated ■ server process. The account in which a server process runs is determined either by the client login information or by the specific server workspace.
  • Page 98 Workspaces Table 6–22 (Cont.) WS Server tab Components Field Server availability C-12 Oracle Application Server Adapter for IMS/TM User’s Guide Description Specifies the number of servers in a pool of servers, available to be assigned to a client. The following options are available: Initial number of servers: The number of server ■...

  • Page 99: Ws Logging

    Table 6–22 (Cont.) WS Server tab Components Field resource limitations Server Priority WS Logging Using the WS Logging tab, you specify parameters to log, that occur with the workspace server process. The WS Logging tab is accessed as follows: From the Start menu, select Programs, Oracle, and then select Studio. Select the required computer from the Configuration Explorer.
  • Page 100 Workspaces You can also change daemon settings using the Note: Configuration Explorer, by selecting a computer and scrolling the list to the required daemon. Right-click the daemon and select Edit Daemon. Changes made to the daemon configuration are not implemented. They are only implemented after the configuration is reloaded using the Reload Configuration option in the Runtime Manager.
  • Page 101 Table 6–23 WS Logging tab Components Field Description Specific log file Defines the name and location of the server log file if you format want the data written to a file instead of SYSOUT for the server process. The parameter must specify the name and the high level qualifier.

  • Page 102: Ws Security

    Workspaces Table 6–23 (Cont.) WS Logging tab Components Field Server Client Audit WS Security Using the WS Security tab, you specify the level of security at the workspace level, as opposed to the daemon level, which is set in the Daemon Security tab. See Also: security.
  • Page 103 Right-click the daemon and select End Unused Servers. Any servers in the connection pool are closed and new servers start with the new configuration. The WS Security tab is shown in the following figure: Figure 6–20 The WS Security tab The WS Security tab comprises fields, as listed in the following table: Table 6–24 WS Security tab Components...
  • Page 104 Workspaces Table 6–24 (Cont.) WS Security tab Components Field Workspace users C-18 Oracle Application Server Adapter for IMS/TM User’s Guide Description Lists the users who are allowed to use the workspace. All users: Indicates that any user who has logged on ■...

  • Page 105: Globalization Settings

    OracleAS Adapters for IMS/TM provides the globalization support for the following languages: Arabic ■ English (the default) ■ French ■ German ■ Greek ■ Hebrew ■ Italian ■ Japanese ■ Korean ■ Portuguses ■ Simple Chinese ■ Spanish ■ Traditional Chinese ■...
  • Page 107 Table 6–25 (Cont.) NLS Language Codes ASCII Language Language Platforms Name Code (Default) German ISO-8859-15 Greek ISO-8859-7 Hebrew ISO-8859-8 Italian ISO-8859-15 Japanese SJIS EUC (Solaris) VMS-JP (VMS) Korean KSC5601 MS949 (Win) Latin ISO-8859-15 International Portuguese ISO-8859-15 Russian ISO-8859-5 Spanish ISO-8859-15 Turkish ISO-8859-9 Defining the Language and Codepage...
  • Page 108 Defining the Language and Codepage D-4 Oracle Application Server Adapter for IMS/TM User’s Guide...
  • Page 109 acxTrace parameter, 5-6 analyzerQueryPlan parameter, 5-6 application language parameter, 5-7 buffer size, comCacheBufferSize parameter, 5-6 CD-ROM drive requirements IBM S/390, 6-2 PC, 6-2 codepage parameter, 5-7 comCacheBufferSize parameter, 5-6 comm parameters comCacheBufferSize, 5-6 comMaxSocketSize, 5-6 comMaxXmlSize, 5-6 comMaxSocketSize parameter, 5-6 comMaxXmlSize parameter, 5-6 cvtSeverityLevel parameter, 5-7 daemon...
  • Page 110 IBM S/390 memory, 6-2 PC CD-ROM drive, 6-2 PC disk space, 6-2 PC memory, 6-2 PC processor, 6-2 UNIX, 6-2 IBM S/390 installing, 6-5 postinstallation, 6-8 preinstallation, 6-4 installing IBM S/390, 6-5 Windows, 6-14 interactions, modeling, 6-19 language parameter, 5-7 log files daemon options, C-3 logFile parameter, 5-6...
  • Page 111 trace information, logging, 5-6 traceDir parameter, 5-7 transactions environment parameters, 5-8 tuning environment parameters, 5-9 Windows, installing, 6-14 Workspace server mode, C-11 XML documents, maximum size, 5-6 See year2000Policy parameter year2000Policy parameter, 5-8 Index-3...
  • Page 112 Index-4...

Table of Contents