1. Manuals
  2. Brands
  3. Oracle Manuals
  4. Software
  5. Application Server 10.1.3.4
  6. User manual

Oracle Application Server 10.1.3.4 User Manual

Adapters for ims/db release 3 (10.1.3.4)
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Enlarged version
Oracle® Application Server
Adapters for IMS/DB User's Guide
10g Release 3 (10.1.3.4)
E13832-01
December 2008

Advertisement

Table of Contents
loading

Related Manuals for Oracle Application Server 10.1.3.4

Summary of Contents for Oracle Application Server 10.1.3.4

  • Page 1 Oracle® Application Server Adapters for IMS/DB User’s Guide 10g Release 3 (10.1.3.4) E13832-01 December 2008...
  • Page 2 Oracle Application Server Adapters for IMS/DB User's Guide, 10g Release 3 (10.1.3.4) E13832-01 Copyright © 2005, 2008, Oracle and/or its affiliates. All rights reserved. Primary Author: Jeanne Wiegelmann, David Goldman Contributors: Yishai Hadas, , Adeeb Massad, Dror Harari, , Meera Srinivasan, Bo Stern, Shashi Suravarapu, Costi Zaboura, Sheela Vasudevan This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.

  • Page 5: Table Of Contents

    Contents Preface ................................. xi Audience............................... xi Documentation Accessibility ........................xi Related Documents ............................ xii Conventions ..............................xii Introduction OracleAS Adapter for IMS/DB Overview ................... 1-1 OracleAS Adapter for IMS/DB Architecture ..................1-2 Integration Flow from Oracle Application Server to the Legacy Application ......1-2 Installing and Configuring the OracleAS Adapter for IMS/DB Preinstallation Tasks..........................
  • Page 6 Securing Access to Oracle Connect ....................2-15 Setting Password Access to Oracle Studio ................2-15 Specifying Users with Administrative Rights ..............2-16 Setting Up Run-Time User Access to the IBM z/OS Platform.......... 2-17 Modeling Interactions for OracleAS Adapter for IMS/DB............2-19 Setting Up the IMS/DB Data Source....................
  • Page 7 Runtime Configuration ........................5-9 6 Configuring an OracleAS Adapter for IMS/DB for Outbound Interactions Creating Outbound Interactions with the OracleAS Adapter for IMS/DB ........6-1 Requirements ............................6-1 Adding the IMS/DB Hospital Data Source ..................6-1 Prepare the System..........................6-1 Set up Machine Access to Oracle Connect..................
  • Page 8 Tuning............................... 8-10 XML..............................8-10 Migration Considerations........................8-11 Security Considerations ........................8-11 Setting Design Time Security ......................8-12 Setting Runtime Security........................ 8-12 Transaction Support..........................8-13 Advanced Tuning of the Metadata Metadata for the IMS/DB Data Source ....................A-1 General Tab ............................A-2 Columns Tab............................
  • Page 9 Flattening Hierarchical Data Using SQL ..................D-4 Using an Alias ..........................D-4 Globalization Settings Defining the Language and Codepage....................E-1 Index...

  • Page 11: Preface

    Preface This guide is the primary source of user and reference information on OracleAS Adapters for IMS/DB, which enables client applications to access transactions running under IMS/DB through the Sun J2EE Connector Architecture (J2CA) API. This document describes the features of OracleAS Adapters for IMS/DB. This preface covers the following topics: Audience ■...

  • Page 12: Related Documents

    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 13: Introduction

    Introduction Oracle Application Server Adapter for IMS/DB (OracleAS Adapter for IMS/DB) provides connectivity and runs interactions on an Information Management System - Data Base (IMS/DB) system. This section provides an overview of the features and architecture of OracleAS Adapter for IMS/DB. This section contains the following topics: OracleAS Adapter for IMS/DB Overview ■...

  • Page 14: Oracleas Adapter For Ims/Db Architecture

    OracleAS Adapter for IMS/DB Architecture OracleAS Adapter for IMS/DB Architecture OracleAS Adapter for IMS/DB includes the following components: J2CA 1.5 IMS/DB adapter: The J2CA IMS/DB adapter is a standard resource ■ adapter that is compliant with J2EE Connector Architecture, therefore, providing J2EE components connectivity.

  • Page 15: Installing And Configuring The Oracleas Adapter For Ims/Db

    Installing and Configuring the OracleAS Adapter for IMS/DB This section describes how to install Oracle Connect and Oracle Studio, and how to configure Oracle Connect using Oracle Studio. In addition to the installation procedures described in this Note: section, the J2CA 1.5 IMS/DB adapter must be installed with Oracle Application Server.

  • Page 16: Software Requirements

    Installing Oracle Connect on an IBM z/OS Series Platform Table 2–1 Oracle Connect Hardware Requirements Hardware Component Requirements Processor An IBM zSeries computer. Memory The minimum requirement is 4MBfor each connection. A connection is defined as a connection to a server process or daemon.

  • Page 17: Installation Worksheet

    Installing Oracle Connect on an IBM z/OS Series Platform If you have an Oracle Connect back-end adapter already Note: installed on the IBM z/OS platform, follow the instructions described in "Updating an Existing Oracle Connect Installation with IMS/DB" on page 2-11. The other back-end adapters that run on an IBM z/OS platform include: OracleAS Adapter for CICS...

  • Page 18: Preinstallation Tasks

    Installing Oracle Connect on an IBM z/OS Series Platform Table 2–5 Installation Checklist Step Comment/Outputs tso profile noprefix Ensures that the user name is not used as part of the dataset name allocated in the next steps. Allocate dataset: {HLQ}.TRANSMIT.KIT 130 tracks (3390), format=FB, record length=80, block size=3120 Allocate dataset: {HLQ}.TRANSMIT.LOAD...

  • Page 19: Importing The Installation Kit

    Installing Oracle Connect on an IBM z/OS Series Platform Importing the Installation Kit Perform the following steps on the mainframe to import Oracle Connect installation kit to the mainframe: Run the following command: tso profile noprefix The user name will not be used as part of the dataset name. On some systems this is the default.
  • Page 20 Installing Oracle Connect on an IBM z/OS Series Platform Table 2–6 Installation Prepare Job Prompts and Responses Screen Response DO YOU WANT TO USE SMS MANAGED If you want to manage the storage using SMS, then answer STORAGE FOR THIS INSTALLATION Y/N [N] : Y, otherwise answer N.
  • Page 21 Installing Oracle Connect on an IBM z/OS Series Platform Table 2–7 Installation Prompts and Responses Screen Response DO YOU WANT TO USE SMS MANAGED If you want to manage the storage using SMS, then answer STORAGE FOR THIS INSTALLATION Y/N [N] : Y, otherwise answer N.

  • Page 22: Post-Installation Instructions

    Installing Oracle Connect on an IBM z/OS Series Platform Table 2–8 IMS/DB Adapter Installation Prompts and Responses Screen Response ENTER DBD LIBRARY NAME Enter the IMS DBD Library name for IMS on your system ENTER PSB LIBRARY NAME Enter the IMS PSB Library name for IMS on your system ENTER RES LIBRARY NAME Enter the IMS RES Library name for IMS on your system ENTER PROC LIBRARY NAME...
  • Page 23 Installing Oracle Connect on an IBM z/OS Series Platform To define a DSN as APF-authorized, in the SDSF screen Note: enter the 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 24: Starting The Daemon

    Installing Oracle Connect on an IBM z/OS Series Platform Access to an Open z/OS 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 25: Setting Up Oracle Connect To Update Ims/Db Data

    Updating an Existing Oracle Connect Installation with IMS/DB If you intend on using impersonation, so that you can run Note: in a 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 26: Installing Oracle Studio

    Installing Oracle Studio Follow the instructions in the Response column in for each entry in the Screen column. Table 2–11 IMS/DB Adapter Installation Prompts and Responses Screen Response ENTER DBD LIBRARY NAME Enter the IMS DBD Library name for IMS on your system ENTER PSB LIBRARY NAME Enter the IMS PSB Library name for IMS on your system ENTER RES LIBRARY NAME...

  • Page 27: Installing Oracle Studio On Windows

    Configuring Oracle Connect Memory: 256 MB ■ Disk space: 120 MB of free disk space ■ You can install Oracle Studio on the following operating systems: Windows XP with Service Pack 2 or higher ■ Windows 2003 Windows Vista Linux OS with GTK ■...

  • Page 28: Setting Up The Ibm Z/Os Platform In Oracle Studio

    Configuring Oracle Connect Securing Access to Oracle Connect ■ Modeling Interactions for OracleAS Adapter for IMS/DB ■ The following tasks assume you have permission to access Note: the IBM z/OS platform and that the Oracle Connect daemon is running on this computer. Check with the system administrator to ensure these requirements are fulfilled.

  • Page 29: Securing Access To Oracle Connect

    Configuring Oracle Connect The computer is displayed in the Configuration Explorer. Securing Access to Oracle Connect Oracle Studio includes mechanisms to secure access to Oracle Connect both during modeling and at run time. During modeling, the following security mechanisms can be applied: Setting Password Access to Oracle Studio ■...

  • Page 30: Specifying Users With Administrative Rights

    Configuring Oracle Connect Figure 2–3 The Change Master Password Screen Leave the Enter Current Master Password field blank and type a new master password. Confirm the password. Click OK. 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.

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

    Configuring Oracle Connect Figure 2–4 The Administration Authorization screen The screen has the following sections: Administrators: Administrators can view and modify all the definitions in Oracle Studio for the selected computer. On initial entry to Oracle Studio, every user is defined as a system administrator.
  • Page 32 Configuring Oracle Connect Right-click the NAV user profile and select Edit User. The NAV user profile editor is displayed as shown in the following figure: Figure 2–5 The User Editor pane In the User editor, click Add. The Add Authenticator screen is displayed as shown in the following figure: Figure 2–6 The Add Authenticator screen Select Remote Machine from the Resource Type list.

  • Page 33: Modeling Interactions For Oracleas Adapter For Ims/Db

    Modeling Interactions for OracleAS Adapter for IMS/DB Modeling Interactions for OracleAS Adapter for IMS/DB Modeling interactions for OracleAS Adapter for IMS/DB involves defining an Oracle Connect back-end adapter using Oracle Studio. All the definitions specified in Oracle Studio are written to the IBM z/OS platform. This section contains the following: Setting Up the IMS/DB Data Source ■...
  • Page 34 Modeling Interactions for OracleAS Adapter for IMS/DB Figure 2–7 The New Data Source screen Click Next. The Data Source Connect String screen for the selected data source type is displayed. Enter the connect string for the selected data source, as follows: If you select IMS-DBCTL, then the following screen is displayed: Figure 2–8 The Data Source Connect String screen (for IMS-DBCTL) Where:...

  • Page 35: Configuring The Data Source Driver

    Modeling Interactions for OracleAS Adapter for IMS/DB VTAM NetName: The VTAM netname of the specific connection being used ■ by EXCI (and MRO) to relay the program call to the CICS target system. For example, if you issue the following command to CEMT: CEMT INQ CONN On the display screen that the netname is BATCHCLI (this is the default connection supplied by IBM upon the installation of CICS).
  • Page 36 Modeling Interactions for OracleAS Adapter for IMS/DB Click the Properties tab. For IMS/DB under CICS, the following configuration properties are available: cicsProgname: This parameter specifies the ATYDBCTL program that is ■ supplied with Oracle Connect to enable updating the IMS data source. To use the ATYDBCTL program, copy the program from NAVROOT.LOAD to a CICS DFHRPL library (such as CICS.USER.LOAD) and then define the ATYDBCTL program under CICS using any available group such as ATY group:...

  • Page 37: Configuring The Data Source Driver Advanced Properties

    Modeling Interactions for OracleAS Adapter for IMS/DB xcfGroup: The XCF group in the connect string, this parameter specifies the ■ Cross System Coupling Facility collection of XCF members the connection belongs to. A group may consist of up to eight characters, and may span between multiple systems.
  • Page 38 Modeling Interactions for OracleAS Adapter for IMS/DB Table 2–12 (Cont.) Data Source Advanced Configuration Field Description Syntax name A section name in the NAV.SYN file that describes SQL syntax variations. The default syntax file contains the following predefined sections: OLESQL driver and the SQL Server 7 OLE DB provider ■...

  • Page 39: Importing Metadata For The Ims/Db Data Source

    Modeling Interactions for OracleAS Adapter for IMS/DB Table 2–12 (Cont.) Data Source Advanced Configuration Field Description All parent columns Select this for virtual views to include all the columns in the parent record. This parameter is valid only if you are using virtual array views.
  • Page 40 Modeling Interactions for OracleAS Adapter for IMS/DB From the Import Type list select, there should be only one choice in the list, which depends on the type of IMS data source that you selected. The New Import wizard is shown in the following figure: Figure 2–10 The Metadata Import dialog box Click Finish.

  • Page 41: Applying Filters

    Modeling Interactions for OracleAS Adapter for IMS/DB If the files are on another computer, right-click My FTP Sites and select Add. Optionally, double-click Add FTP site. The Add FTP Site screen is displayed. Set the FTP data connection by entering the server name where the DBD files reside and, if not using anonymous access, enter a valid username and password to access the machine.
  • Page 42 Modeling Interactions for OracleAS Adapter for IMS/DB Perform the following steps to apply filters. Apply filters to the copybooks, as needed. The following is theApply Filters editor. Figure 2–13 Apply Filters Screen The following COBOL filters are available: COMP_6 switch: The MicroFocus COMP-6 compiler directive. Specify either ■...

  • Page 43: Selecting Tables

    Modeling Interactions for OracleAS Adapter for IMS/DB Ignore first 6 columns: Ignore the first six columns in the COBOL copybooks. ■ Ignore labels: Ignore labels in the DBD files. ■ The following PSB filters are available: Ignore after column 72: Ignore columns 73 to 80 in the COBOL copybooks. ■...

  • Page 44: Import Manipulation

    Modeling Interactions for OracleAS Adapter for IMS/DB Figure 2–15 Match DBD to COBOL Screen Match each table selected from the DBD file with the COBOL copybook that contains the relevant table structure. Select the files and tables from the dropdown lists for each DBD entry.
  • Page 45 Modeling Interactions for OracleAS Adapter for IMS/DB Figure 2–16 Import Manipulation Screen The upper area of the screen lists the DDM Declaration files and their validation status. The metadata source and location are also listed. The Validation tab at the lower area of the screen displays information about what needs to be resolved in order to validate the tables and fields generated from the COBOL.
  • Page 46 Modeling Interactions for OracleAS Adapter for IMS/DB – Setting column-wise normalization for fields with dimensions (arrays). You can create new fields instead of the array field where the number of generated fields will be determined by the array dimension. – Creating arrays and setting the array dimension.
  • Page 47 Modeling Interactions for OracleAS Adapter for IMS/DB Figure 2–17 Field Manipulation Screen You can carry out all of the available tasks in this screen through the menu or toolbar. You can also right click anywhere in the screen and select any of the options available in the main menus from a shortcut menu.
  • Page 48 Modeling Interactions for OracleAS Adapter for IMS/DB Table 2–14 (Cont.) Field Manipulation Screen Commands Command Description Test import tables Select this table to create an SQL statement to test the import table. You can base the statement on the Full table or Selected columns.
  • Page 49 Modeling Interactions for OracleAS Adapter for IMS/DB Table 2–14 (Cont.) Field Manipulation Screen Commands Command Description Create array This command allows you to add an array dimension to the field. Select this command to open the Create Array screen. Enter a number in the Array Dimension field and click OK to create the array for the column.
  • Page 50 Modeling Interactions for OracleAS Adapter for IMS/DB Table 2–14 (Cont.) Field Manipulation Screen Commands Command Description Select this command or use the button to add a field to the table. If you select a row with a field (not a child of a field), you can add a child to that field.
  • Page 51 Modeling Interactions for OracleAS Adapter for IMS/DB Table 2–14 (Cont.) Field Manipulation Screen Commands Command Description Combining sequential fields Select Combining sequential fields to combine two or more sequential fields into one simple field. The following dialog box opens: Enter the following information in the Combining sequential fields screen: First field name: Select the first field in the table to include ■...

  • Page 52: Metadata Model Selection

    Modeling Interactions for OracleAS Adapter for IMS/DB Table 2–14 (Cont.) Field Manipulation Screen Commands Command Description Mark selector Select Mark selector to select the selector field for a variant. This is available only for variant data types. Select the Selector field form the following screen.
  • Page 53 Modeling Interactions for OracleAS Adapter for IMS/DB – Include row number column: Select one of the following: true: Select true, to include a column that specifies the row number in the virtual or sequential view. This is true for this table only, even in the the data source is not configured to include the row number column.

  • Page 54: Import The Metadata

    Modeling Interactions for OracleAS Adapter for IMS/DB Figure 2–18 The Metadata Model Selection editor Import the Metadata This section describes the steps required to import the metadata to the target computer. It continues the Metadata Model Selection step. You can now import the metadata to the computer where the data source is located, or import it later (in case the target computer is not available).

  • Page 55: Setting Up An Oracle Connect Adapter

    Modeling Interactions for OracleAS Adapter for IMS/DB Figure 2–19 The Import Metadata screen After performing the import, you can view the metadata in the Metadata tab in Oracle Studio. You can also make any fine adjustments to the metadata and maintain it, as necessary.

  • Page 56: Generating Outbound Interactions

    Modeling Interactions for OracleAS Adapter for IMS/DB Select Events. Click Finish. The back-end adapter is added to the Configuration view and the Configuration properties open in the Editor. Other adapters that are displayed in the Type list are not Note: supported with the version of Oracle Connect installed at the site.
  • Page 57 Modeling Interactions for OracleAS Adapter for IMS/DB Use the Metadata Import wizard in Oracle Studio to generate interaction metadata, as follows: From the Start menu, select, Programs, Oracle, and then select Studio. In the Design perspective, Configuration view expand the Machines folder. In the Configuration view, expand the computer defined in "Setting Up the IBM z/OS Platform in Oracle Studio"...
  • Page 58 Modeling Interactions for OracleAS Adapter for IMS/DB The option to use a previously saved query is not Note: applicable. Click Next. The Define Interaction screen is displayed enabling you to build the query. If the database query option was selected in step a, then the Note: Define Interaction screen is displayed, enabling you to build a SELECT statement only, as indicated in the Query type field.

  • Page 59: Modifying Existing Interactions

    Modeling Interactions for OracleAS Adapter for IMS/DB Table 2–17 (Cont.) Interaction Parameters Parameter Description The nullable value (true or false). Nullable The default value for the parameter. Default This field is not applicable. Context Field Bind to Sqls This field is not applicable. Click Finish to generate the interaction, including the record schema required to support the interaction input and output.
  • Page 60 Modeling Interactions for OracleAS Adapter for IMS/DB Depending on the changes made to the SQL, when you close the editor, or when clicking Save, the Context Selection screen is displayed. Select the required adapter from the Adapters list and select Update interaction-related records.

  • Page 61: Integrating Oracleas Adapter For Ims/Db With Oc4J

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

  • Page 62: Configuring The J2Ca 1.5 Ims/Db Adapter

    Configuring the J2CA 1.5 IMS/DB 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 63: Using The Cci Api To Develop Applications

    Using the CCI API to Develop Applications Table 3–1 (Cont.) OC4J Connection Properties Property Description Sets the TCP/IP address or host name where the Oracle serverName Connect daemon is running. The daemon runs on the computer specified at the beginning of "Setting Up the IBM z/OS Platform in Oracle Studio"...

  • Page 64: Configuring Multiple Adapters

    Configuring Multiple Adapters Create a Connection object using this ConnectionFactory. Specify the interaction properties using an AttuInteractionSpec object. The AttuInteractionSpec object has the following format: AttuInteractionSpec(java.lang.String name, int verb, int timeOut) The following table describes the properties that can be specified: Table 3–2 Interaction Spec Properties Property...

  • Page 65: Integrating Oracleas Adapters For Ims/Db With Oracle Bpel Process Manager

    Integrating OracleAS Adapters for IMS/DB with Oracle BPEL Process Manager To deploy and integrate OracleAS Adapters for IMS/DB with Oracle BPEL Process Manager, you need to configure BPEL Process Manager. This section includes the following topics: Integrating OracleAS Adapters for IMS/DB with Oracle BPEL Process Manager ■...

  • Page 66: Configuring Oracle Bpel Process Manager

    Configuring Oracle BPEL Process Manager Configuring Oracle BPEL Process Manager This section includes the following topics: Setting up the Connection to the Oracle Connect Server ■ Checking Metadata Availability Using Oracle JDeveloper ■ Configuring the WSDL for Outbound Applications ■ Setting up the Connection to the Oracle Connect Server Perform the following steps to set up the connection to the Oracle Connect server: Open the Oracle BPEL Admin window.
  • Page 67 Configuring Oracle BPEL Process Manager create it, or change the name of the connection factory to the name of a connection factory that exists. The following is an example of a WSDL for outbound applications: <?xml version = '1.0' encoding = 'UTF-8'?> <definitions name="findAccount"...
  • Page 68 Configuring Oracle BPEL Process Manager <xsd:restriction base="xsd:string"> <xsd:maxLength value="8"/> </xsd:restriction> </xsd:simpleType> </xsd:attribute> <xsd:attribute name="CA_TRAN_AMT" type="xsd:int"/> <xsd:attribute name="CA_TRAN_REF" type="xsd:int"/> <xsd:attribute name="CA_TRAN_TYPE" type="xsd:int"/> </xsd:complexType> <xsd:element name="CA_OUTPUT__CA_ACCT_DATA__CA_CUST_INFO" type="CA_OUTPUT__CA_ACCT_DATA__CA_CUST_INFO"/> <xsd:complexType name="CA_OUTPUT__CA_ACCT_DATA__CA_CUST_INFO"> <xsd:sequence> <xsd:element minOccurs="0" maxOccurs="4" name="CA_CUST_PHONE"> <xsd:simpleType> <xsd:restriction base="xsd:string"> <xsd:maxLength value="14"/> </xsd:restriction> </xsd:simpleType> </xsd:element> </xsd:sequence>...
  • Page 69 Configuring Oracle BPEL Process Manager <input name="Input_findAccount" message="tns:request"/> <output name="Output_findAccount" message="tns:response"/> </operation> </portType> <binding name="findAccountJCABinding" type="tns:findAccountPortType"> <jca:binding XMLRecordConverterCallout="oracle.tip.adapter.fw.record.oracle.AttuXMLRecordConver terImpl"/> <operation name="findAccount"> <jca:operation FunctionName="findAccount" InteractionSpec="com.oracle.adapter.AttuInteractionSpec" ExecutionTimeout="120"/> <input/> <output/> </operation> </binding> <service name="findAccountService"> <port name="findAccountPort" binding="tns:findAccountJCABinding"> <jca:address adapterInstanceJndi="eis/legacy/findIMSAccount"/> </port> </service> <plt:partnerLinkType name="findAccountPartnerLinkType"> <plt:role name="findAccountRole">...
  • Page 70 Configuring Oracle BPEL Process Manager 4-6 Oracle Application Server Adapters for IMS/DB User's Guide...

  • Page 71: Bpel Process Manager Examples

    BPEL Process Manager Examples This chapter contains the following topics: Getting Started ■ Deploy a BPEL Outbound Process ■ Getting Started This topic describes the components necessary to work with the samples and how to prepare your system. Prerequisites The following are installation and configuration requirements for using the examples. Personal computer running Microsoft Windows XP or Windows Server 2003 with ■...

  • Page 72: Deploy A Bpel Outbound Process

    Deploy a BPEL Outbound Process Deploy a BPEL Outbound Process This section describes how to create a BPEL outbound process that connects to a OracleAS adapter for IMS/DB. For information on how to configure an IMS/DB adapter for outbound, see Modeling Interactions for OracleAS Adapter for IMS/DB.

  • Page 73: Design-Time Configuration

    Deploy a BPEL Outbound Process Configuring an OracleAS Adapter for IMS/DB for Outbound Interactions an explanation on how to create the findDoctor interaction and for an explanation on the WSDL. Design-Time Configuration This section describes the design-time steps necessary to deploy two BPEL outbound processes.

  • Page 74: Create A Database Adapter To Read The Doctor Table

    Deploy a BPEL Outbound Process Click Next to review the input/output schema elements or click Finish. Create a Database Adapter to Read the Doctor Table You create a database adapter to read the DOCTOR table. SOA executes the SQL statement defined in the interaction and passes it to a resource adapter. The resource adapter then processes the information and returns the data.

  • Page 75: Design A Bpel Outbound Process To Read The String

    Deploy a BPEL Outbound Process Step 4, File Directories Directory Names are Specified as: Select Physical Path Directory for Incoming Files (physical path): Enter the full path to the folder where you want the incoming files, for example C:\temp. Step 5, File Filtering: Includes Files with Name Pattern: Enter *xml Step 6, File Polling: Polling Frequency: enter 1 then select seconds from the list.

  • Page 76: Create A Partner Link To The Database Adapter

    Deploy a BPEL Outbound Process Figure 5–4 Outbound Receive Properties Do the following in the Edit Receive dialog box: Enter a name for the Receive activity, in this example it is Receive_1. ■ Make sure to create the variable. Click the first button to the right of the ■...

  • Page 77: Edit The Invoke_1 Activity

    Deploy a BPEL Outbound Process In the Service Explorer, expand the connection you are using, then expand adapters and then applications, and continue to browse until you find the WDSL file you are using. Select the file and click OK. The WSDL File field in the Create Partner Link dialog box displays the path to the WSDL file you selected.

  • Page 78: Edit The Assign_1 Activity

    Deploy a BPEL Outbound Process Edit the Assign_1 Activity You use the assign activity to assign a value to the resource adapter. Do the following to edit the Assign_1 activity. Double-click the Assign_1 activity to edit it. The Assign dialog box is displayed. Figure 5–7 Assign Dialog Box Click the Create list and select Copy Operation.

  • Page 79: Runtime Configuration

    Deploy a BPEL Outbound Process Click OK. The Copy Operation tab in the Assign window updates to show the rule. The following figure shows how the final process looks: Figure 5–9 Final Outbound Process Runtime Configuration This section describes how to test the project and run it to see that the outbound process is executed successfully.
  • Page 80 Deploy a BPEL Outbound Process 5-10 Oracle Application Server Adapters for IMS/DB User's Guide...

  • Page 81: Configuring An Oracleas Adapter For Ims/Db For Outbound Interactions

    Configuring an OracleAS Adapter for IMS/DB for Outbound Interactions This chapter provides an example for creating an OracleAS adapter for IMS/DB. In this case it describes the steps necessary to create an adapter that will get find the names of a doctor and a patient from an IMS/DB data source. To work with an OracleAS adapter for IMS/DB, you must also configure a BPEL endpoint connection.

  • Page 82: Set Up Machine Access To Oracle Connect

    Adding the IMS/DB Hospital Data Source Set up Machine Access to Oracle Connect You begin by configuring access to the Mainframe computer with your IMS/DB data. You configure this access with Oracle Connect. Open Oracle connect and follow the directions Setting Up the IBM z/OS Platform in Oracle Studio.

  • Page 83: Import The Metadata

    Adding the IMS/DB Hospital Data Source In the Type field, select IMS-DLI and then click Finish. You do not need to add any additional connection information. For detailed information on adding the IMS/DB data source, see Configuring the Data Source Driver.

  • Page 84: Create The Finddoctor And Findpatient Interactions

    Create the findDoctor and findPatient Interactions Create the findDoctor and findPatient Interactions You use a database adapter to create the interactions used to get the data that you need. The interactions are used as services when you set up the endpoint in JDeveloper.
  • Page 85 Create the findDoctor and findPatient Interactions Expand the computer you just added and then expand the NAV binding. Right-click the adapter you are using and select Show in Metadata. Right-click Interactions and select New. Enter the following information for in the wizard, then click Finish. Name: findDoctor ■...
  • Page 86 Create the findDoctor and findPatient Interactions 6-6 Oracle Application Server Adapters for IMS/DB User's Guide...

  • Page 87: Troubleshooting Oracleas Adapter For Ims/Db

    Troubleshooting OracleAS Adapter for IMS/DB Troubleshooting Oracle AS Adapter for IMS/DB 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 ■...

  • Page 88: 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 command: '/s ATTDAEMN' Where INSTROOT is the high-level qualifier where Oracle Connect is installed. "Starting the Daemon"...

  • Page 89: Workspace Options

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

  • Page 90: Server Options

    Troubleshooting the Daemon Table 7–2 (Cont.) Workspace Options Option Description Disable Disables the selected workspace. Refresh Refreshes the display. Server Options Right-click a server to display the options available for the server, including the ability to display the server log. The options available at the server level are listed in the following table: Table 7–3 Server Options...

  • Page 91: The Daemon Log Monitor

    Troubleshooting the Daemon Display the required log by right-clicking the level you want (daemon, workspace or server) and selecting View Log. Each log is displayed in a different tab. You can flick between logs by clicking the required tab. The Daemon Log Monitor The daemon log displays activity between clients and the daemon, including clients logging in and logging out from the daemon.

  • Page 92: Resolving Communication Errors

    Resolving Communication Errors Resolving Communication Errors When Oracle Studio disconnects from the IBM z/OS computer, the computer is displayed in Oracle Studio with an X in a red circle. If this situation occurs, try to access the computer later. The following table describes the various scenarios that may exist when Oracle Application Server disconnects from the IBM z/OS computer.
  • Page 93 Resolving Specific Errors Action: Check whether the daemon has privileges to use the TCP/IP services on the current computer with the port specified in the oc4j-ra-xml file for the adapter. C008: Setting server event handler failed. Cause: Internal error. Action: Contact Oracle Support Services. C009: IRPCD process has been terminated by user request.
  • Page 94 Resolving Specific Errors Action: Edit the user profile in Oracle Studio to specify a valid username and password for the IBM z/OS platform. See Also: "Setting Up Run-Time User Access to the IBM z/OS Platform" on page 2-17. C010: Anonymous server logins are not allowed. Cause: Internal error.
  • Page 95 Resolving Specific Errors APF authorize all the steplibs in the server To set impersonation: script on z/OS computer. For example: setprog... ada622-volume adavol CICS.CICS.SDFHEXCI - p390dx INSTROOT.load - 111111 INSTROOT.loadaut - 111111 INSTROOT is the high level qualifier where Oracle Connect is installed.
  • Page 96 Resolving Specific Errors Action: Check that the name specified for the computer in the oc4j-ra-xml file is correct. Action: Check that a domain name server (DNS) is available to look up the host name. Action: Check the TCP/IP subsystem on the computer by trying to ping it or run FTP or Telnet to or from it.
  • Page 97 Resolving Specific Errors C026: Failed to bind server to port %s Cause: An Oracle Connect server or daemon was not able to bind to the specified port. Action: Check whether another program is holding the port that was specified in the oc4j-ra-xml file for the adapter.
  • Page 98 Resolving Specific Errors Action: Contact Oracle Support Services. C031: Cannot register a non-module RPC %s Cause: Internal error. Action: Contact Oracle Support Services. 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.
  • Page 99 Resolving Specific Errors Action: Check the network connection by trying to ping the host computer or run FTP or Telnet to or from it. C045: Failed to create a service thread Cause: The server failed to create a thread to service a client request. Action: A system or process quota limit has been exceeded.
  • Page 100 Resolving Specific Errors Action: The resolution to this error is highly dependent on the particular cause. The following are some typical causes and resolutions. Action: Some process creation quota was exceeded. Either try again later or increase the quota or the other relevant system resources. Action: The server startup script failed.
  • Page 101 Resolving Specific Errors Action: Contact Oracle Support Services. C074: No authorization to perform the requested operation (%s) Cause: User/account has insufficient privileges. Action: Grant administrative privileges to the user/account using the Administrator parameter of the Daemon Security or WS Security sections in the daemon configuration.
  • Page 102 Resolving Specific Errors J0035: Internal Error: Invalid redirection address %s returned by daemon Cause: Internal error. Action: Contact Oracle Support Services. 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 -...
  • Page 103 Resolving Specific Errors J0071: Bad key for mapped record, #element or #element[] is required Cause: In a PUT operation, the value must be mapped record array. Action: Change the key used in the record to a valid key. J0072: Value must be of type Object[] Cause: In a PUT operation, the value must be mapped record array.
  • Page 104 Resolving Specific Errors 7-18 Oracle Application Server Adapters for IMS/DB User's Guide...

  • Page 105: Advanced Features Of Oracleas Adapter For Ims/Db

    Advanced Features of OracleAS Adapter for IMS/DB Oracle Connect includes a number of tuning parameters that can improve performance. Specifically, the daemon can be configured to optimize communication between the IBM z/OS platform and a client. In addition, the binding environment can be tuned to optimize the request handling. This section contains the following topics: Configuring the Daemon for High Availability ■...

  • Page 106: Editing The Workspace

    Configuring the Daemon for High Availability Right-click IRPCD and select New Workspace. The New Daemon Workspace screen is displayed. Specify a name for the new workspace and optionally, provide a description. Specify whether you want it to have default settings or copy the properties of an existing workspace.
  • Page 107 Configuring the Daemon for High Availability 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. This mode enables servers to run under a particular user account and isolates clients from each other (because each receives its own process).
  • Page 108 Configuring the Daemon for High Availability Figure 8–1 The Server Mode Tab When using any of the server modes you can specify a pool of server processes. These server processes are started when the daemon starts and are maintained in a pool. The server processes are available for use by new client requests from the pool, saving initialization time.
  • Page 109 Configuring the Daemon for High Availability A one-client server can be reused after its (single) client has disconnected. Reuse of servers enhances startup performance because it avoids the need to repeat initialization. This parameter is not available if the Limit server reuse parameter is not selected. This parameter is not available if the server mode value is singleClient.

  • Page 110: Configuring A Binding Environment

    Configuring a Binding Environment sub-tasks by specifying this parameter. If you set 10 servers and 10 prestarted sub-tasks then 100 tasks are started (10 sub-tasks for each process). Configuring a Binding Environment Each binding configuration includes the following information: Environment settings, which are used to configure the environment used by any of ■...

  • Page 111: Debug

    Configuring a Binding Environment Modeling ■ ODBC ■ OLEDB ■ Optimizer ■ Query Processor ■ Parallel Processing ■ Transactions ■ Tuning ■ ■ Debug The following table lists the parameters that define debugging and logging operations: Table 8–2 Debug Parameters Parameter Description ACX trace...

  • Page 112: General

    Configuring a Binding Environment Table 8–2 (Cont.) Debug Parameters Parameter Description Transaction extended Select this for the transaction manager to write additional logging information about transactions to the log. General The following table lists the parameters that define various operations the directory where temporary files are written: Table 8–3 General Parameters...

  • Page 113: Modeling

    Configuring a Binding Environment Table 8–4 Language Settings Parameters Parameter Description Language Identifies the application language. A default codepage is selected based om the value specified for this parameter. See also: Appendix E, "Globalization Settings". For use with globalization support to identify the codepage for Code Page the workspace.

  • Page 114: Tuning

    Configuring a Binding Environment Table 8–5 (Cont.) Transaction Parameters Parameter Description Commit on destroy Select this to commit all single-phase commit transactions opened for a data source, if a connection closes while the transaction is still open. Disable 2PC Select this to disable two-phase commit capabilities, even in drivers that support two phase commit.

  • Page 115: Migration Considerations

    Security Considerations Table 8–6 (Cont.) XML Category Parameters Parameter Description XML date format Enter the date format to use for XML. The options are: ISO (the default): The date format is: ■ YY-MM-DDThh:mm:ss[.ss..] ODBC: The date format is: YYYY-MM-DD ■ HH:MM:SS[.NNN...] Replace invalid XML Select this to replace invalid XML characters with a ’?’.

  • Page 116: Setting Design Time Security

    Security Considerations The client’s first message to the server includes a pre-defined shared key, includeing the key name and value in the connection string. The server gets the key value for the key name passed from the client from the native object store (NOS).

  • Page 117: Transaction Support

    Transaction Support Access by the client must be through a valid port, according to the port range ■ entered in the Server section of the workspace Server Mode tab in Oracle Studio. For more information, see the explanation of the workspace Server Mode page C-11.
  • Page 118 Transaction Support If RRS is not running, OracleAS Adapter for IMS/DB can participate in a distributed transaction, as the only one-phase commit resource, if the Transaction log file environment property includes the keyword NORRS. See "Transactions" in the "Configuring a Binding Environment" section.

  • Page 119: 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 by Oracle Studio in the Metadata tab of the Design perspective.

  • Page 120: General Tab

    Metadata for the IMS/DB Data Source General Tab Use the General tab to maintain information about the whole table, such as the table name and the way the table is organized. 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...

  • Page 121: Columns Tab

    Metadata for the IMS/DB Data Source Table A–1 (Cont.) General Tab Components Field Description Organization Select how the record represented by the table is organized. The options that are displayed depend on the record. The following options are available: Index ■...

  • Page 122: Column Definition Section

    Metadata for the IMS/DB Data Source Figure A–2 The Columns tab Column Definition Section The top section of this tab lets you define the columns in the source data. You can click in any row (which represents a column in the data base table) to edit the information. The following table describes this section.

  • Page 123: Column Properties

    Metadata for the IMS/DB Data Source Table A–2 (Cont.) Metadata Column Tab Definitions Field name Description Fixed offset This column lets you determine whether to calculate the offset. There are two options: Calc offset: If you clear this check box, the absolute offset for ■...
  • Page 124 Metadata for the IMS/DB Data Source Table A–4 Metadata Properties Property Description Alias A name used to replace the default virtual table name for an array. Virtual table names are created by adding the array name to the record name. When an array includes another array the name of the nested array is the name of the record and the parent array and the nested array.

  • Page 125: Indexes Tab

    Metadata for the IMS/DB Data Source Indexes Tab Use the Indexes tab to specify metadata describing the indexes of a table. The Indexes tab contains information only if the Note: Organization field in the Table tab is set to Index. The Indexes tab is shown in the following figure: Figure A–3 The Indexes tab This tab has two sections.

  • Page 126: Properties

    Metadata for the IMS/DB Data Source Table A–5 Indexes Tab Components Field Description Name The names of existing indexes for the current table. Order The ordering of the rows retrieved by the index. DB Command IMS/DB-specific commands for the index. The information displayed is generated automatically when the metadata is generated and should not be modified.
  • Page 127 Metadata for the IMS/DB Data Source Figure A–4 The Statistics tab The Statistics tab comprises fields as listed in the following tables: Table A–7 Statistics tab Components Field Description No. of rows The approximate number of rows in the table. If the value is -1, then the number of rows in the table is unknown (a value was not supplied and the update statistics utility was not run to update the value).

  • Page 128: Generating Statistics

    Metadata for the IMS/DB Data Source Table A–8 (Cont.) Columns group Components Field Description Cardinality The number of distinct values for the column. If the value is -1, then the number of distinct values for the column is unknown (a value was not supplied and the update statistics utility was not run to update the value).

  • Page 129: Advanced Tab

    Metadata for the IMS/DB Data Source Table A–10 Type group Components Field Description Estimated An estimation of the amount of statistical information returned. Estimated with rows An estimation of the amount of statistical information returned. The estimate includes an estimation of the number of rows in the table.
  • Page 130 Metadata for the IMS/DB Data Source Figure A–6 Data Source Metadata Advanced Tab Enter the following information in this tab: Generate sequential view: Select this to map non-relational files to a single table. ■ Generate virtual views: Select this to have individual tables created for each array ■...

  • Page 131: Adapter Metadata

    Adapter Metadata – default: Select default to use the default data source behavior for this parameter. Adapter Metadata Use Oracle Studio to maintain the metadata for your database adapter. From the Start menu, select Programs, Oracle, and then select Studio. Expand the Machines folder, then expand the machine you are working with.
  • Page 132 Adapter Metadata Figure A–7 Adapter Metadata General Properties The General properties are listed in the following table: Table A–12 General tab Components Field Description Description Specifies an identifying description of the adapter. Authentication mechanism Specifies the authentication to access the adapter. The available mechanisms are: kerbv5 ■...

  • Page 133: Adapter Metadata Interactions

    Adapter Metadata Adapter Metadata Interactions The Adapter Metedata Interactions editor defines an interaction and its input and output definitions. The following describes how to open the Adapter Metadata editor. In Oracle Studio Design perspective, Metadata view, expand the Adapters folder. Expand the adapter with the interaction that you want to edit.

  • Page 134: Interaction Advanced Tab

    Adapter Metadata Table A–13 (Cont.) Interaction General Editor Components Field Description Mode Determines the interaction mode. The following interaction modes are available: sync-send-receive: The interaction sends a request and ■ expects to receive a response. sync-send: The interaction sends a request and does ■...
  • Page 135 Adapter Metadata Figure A–9 Interaction Advanced Tab This tab has three sections. The SQL Statement section lets you build any valid SQL statement. Use the tabs to select the tables and statement types and build a statement. When you select Enable manual query editing, you can manually enter a valid SQL statement at the bottom of the screen.

  • Page 136: Adapter Metadata Schema Records

    Adapter Metadata – hex: Select this for hexadecimal encoding The Parameters section lets you create parameters to use for the interaction. To create a parameter, click Add. Enter a name in the dialog box and click OK. The parameter is entered in the list.
  • Page 137 Adapter Metadata Figure A–10 Adapter Metadata Schema Records The Adapter Metadata Schema Records properties are listed in the following tables: Table A–14 Schema Record Tab Field Description Fields list Defines the single data item within a record. This section has a table with the following three columns: Name: The name of the field ■...

  • Page 138: Adapter Metadata Xml

    Adapter Metadata Table A–15 (Cont.) Valid Data Types Binary Boolean Byte Numeric[(p[,s])] Short String Time Timestamp Adapter Metadata XML You can also edit the adapter metadata by viewing its XML schema. The following describes how to open the adapter metadata XML editor: In Oracle Studio Design perspective, Metadata view, expand the Adapters folder.

  • Page 139: Back-End Adapter Data Type Support

    Back-end Adapter Data Type Support OracleAS Adapters for IMS/DB 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. The mapping of data types between OracleAS Adapters for Note: IMS/DB and Oracle Application Server is performed internally by Oracle Connect.
  • Page 140 Data Type Mapping Table 8–7 (Cont.) Data Type Mapping: COBOL and Oracle Connect Back-end Adapter COBOL Data Type Oracle Connect Data Type NATIVE-4 NATIVE-8 string PACKED-DECIMAL string POINTER [SIGN [IS]] TRAILING string [SIGN [IS]] TRAILING SEPARATE string [CHARACTER] B-2 Oracle Application Server Adapters for IMS/DB User's Guide...

  • Page 141: 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: Control ■ Logging ■ Security ■ Workspaces ■ Control Using the Control tab for the daemon, 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 142 Control Figure 8–3 The Control tab The following table shows the paremters that can be set in the Control tab: Table 8–8 Daemon Control Tab Components Field Description Daemon IP Address Enter the IP address of the machine(s) where the daemon is listening.

  • Page 143: Logging

    Logging Table 8–8 (Cont.) Daemon Control Tab Components Field Description Call timeout The timeout period for short calls for all daemons. The definition of a short call is a call that should be completed in a few seconds. For example, most calls to a database such as DESCRIBE should be completed in a few seconds as opposed to call like a GETROWS call, which can take a long time.
  • Page 144 Logging 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 only implemented after the configuration is reloaded using the Reload Configuration option in the Runtime Manager perspective.

  • Page 145: Security

    Security Table 8–9 (Cont.) Daemon Logging Tab Components Field Description Tracing and debug options Daemon RPC function calls Select this to log all daemon RPC function calls. Log ACX Select this if you want to log requests and processes. Extended RPC trace Generates a verbose message in the server log file for each low-level RPC function called.
  • Page 146 Security Determine access to the computer. ■ The following shows how to open the Daemon Security tab: From the Start menu, select Programs, Oracle, and then select Studio. From the Design perspective Configuration view expand the Machines folder. Right-click the computer and select Open Runtime Perspective. Right-click the daemon in the Runtime Explorer and select Edit Daemon Configuration.

  • Page 147: Workspaces

    Workspaces Table 8–10 Daemon Security Tab Components Field Description Administrators Identifies the users (accounts) allowed to perform privileges administrative tasks (tasks that require administrative login). Enables all users to access the daemon and change the All users settings. Identifies the names of users (accounts) and groups that Selected users only can be administrators.
  • Page 148 Workspaces Right-click a computer and select Open Runtime Perspective. 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.
  • Page 149 Workspaces Table 8–11 (Cont.) General Tab Components Field Description Workspace name The name used to identify the workspace. Note: The default configuration includes the default Navigator workspace. This workspace is automatically used if a workspace is not specified as part of the connection settings.
  • Page 150 Workspaces Table 8–11 (Cont.) General 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 151: Server Mode

    Workspaces Server Mode The Server Mode tab lets you configure 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 152 Workspaces Figure 8–7 The Server Mode tab The Server Mode tab has the following fields: C-12 Oracle Application Server Adapters for IMS/DB User's Guide...
  • Page 153 Workspaces Table 8–12 Server Mode 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 154 Workspaces Table 8–12 (Cont.) Server Mode Tab Components Field Description Server availability 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 155 Workspaces Table 8–12 (Cont.) Server Mode Tab Components Field Description If Limit server reuse is selected, in the field next to the check box, enter the maximum number of times a server can be reused. Select the maximum of clients accepted in a server process.

  • Page 156: Security

    Workspaces Table 8–12 (Cont.) Server Mode Tab Components Field Description Number of spare The minimum number of server processes in the servers prestarted pool before the daemon resumes creating new server processes (to the value specified in the Initial number of servers field). If this field is set to a value higher than the Initial number of servers field, the daemon uses the value specified in the Initial number of servers field.
  • Page 157 Workspaces Notes: You can also change daemon settings using the 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 ■...
  • Page 158 Workspaces Table 8–13 Security Tab Field Description Server Account This section defines the users (accounts) allowed to access the workspace, firewall access ports, workspace account, and anonymous login permissions. Use specific workspace Select this if you want to define the operating system account used account for the workspace.

  • Page 159: Supported Sql Syntax And Sql Enhancements

    Supported SQL Syntax and SQL Enhancements OracleAS Adapter for IMS/DB provides basic support for standard ANSI '92 SQL along with a number of enhancements, all of which can be used when specifying adapter interactions. This appendix contains the following sections: Supported SQL Statements ■...

  • Page 160: Supported Functions

    Supported Functions Table D–2 (Cont.) Comparison Operators Operator > < >= <= <>, !=, ^= IS NOT NULL IS NULL Supported Functions OracleAS Adapter for IMS/DB enables the use of the following functions in SQL statements: String Functions ■ Group Functions ■...

  • Page 161: Sql Enhancements

    SQL Enhancements Table D–4 (Cont.) Group Functions Oracle Oracle Connect Function Function Usage Comment Max(exp) Returns the maximum value of the expression exp Min(exp) Returns the minimum value of the expression exp Sum(exp) Returns the summation of the expression exp Table D–5 Mathematical Functions Oracle...

  • Page 162: Accessing Hierarchical Data Using Sql

    SQL Enhancements Accessing Hierarchical Data Using SQL Data stored hierarchically in a IMS/DB data source can be referenced by using a hyphen followed by a right arrow (->) to denote the parent child relationship in the source: FROM … parent_name->child1->child2… [alias] Or, using an alias for the parent table: FROM …...

  • Page 163: Defining The Language And Codepage

    Globalization Settings The OracleAS CDC Adapter for IMS/DB provides the globalization support for the following languages: Arabic ■ English (the default) ■ French ■ German ■ Greek ■ Hebrew ■ Italian ■ Japanese ■ Korean ■ Portuguses ■ Simple Chinese ■...
  • Page 164 Defining the Language and Codepage From the Language list, select the NLS supported language to use in this ■ binding. Valid values are are listed in the Language Name column of Language Codes table. From the Codepage list, select the codepage that you want to use with this ■...
  • Page 165 Defining the Language and Codepage Table 8–14 (Cont.) NLS Language Codes Alternative Codepages (EBCDIC ASCII EBCDIC based unless Language Language Windows Platforms Platforms noted Name Code Default (Default) (Default) otherwise) French Windows-125 ISO-8859-15 IBM1147 IBM297, IBM037, IBM500, IBM1140, IBM1148, IBM1047, ISO-8859-1 (ASCII based) Latin...
  • Page 166 Defining the Language and Codepage Table 8–14 (Cont.) NLS Language Codes Alternative Codepages (EBCDIC ASCII EBCDIC based unless Language Language Windows Platforms Platforms noted Name Code Default (Default) (Default) otherwise) Windows-125 ISO-8859-9 IBM1155 IBM1026 Turkish Hebrew Windows-125 ISO-8859-8 IBM424 IBM 862 Arabic Windows-125 ISO-8859-6...
  • Page 167 Index disk space requirements IBMmainframe, 2-2 ACX trace parameter, 8-7 add timestamp to traced events parameter, 8-7 arithmetic operators, D-1 environment parameters ACX trace, 8-7 add timestamp to traced events, 8-7 binary XML log level parameter, 8-7 cache buffer size, 8-8 code page, 8-9 COM maximum XML size, 8-10 COM maximum XML size in memory, 8-10...
  • Page 168 year 2000 policy, 8-8 error log, binary XML log level parameter, 8-7 memory requirements error log, log file parameter, 8-7 IBM mainframe, 2-2 metadata atomic data types, B-1 miscellaneous parameters flattening hierarchical data, D-4 environment, 8-8 functions group, D-2 string, D-2 nav utility editor parameter, 8-8 nav utility editor, text editor, 8-8 NLS string parameter, 8-9...
  • Page 169 year 2000 policy parameter, 8-8 See system managed storage software requirements Oracle Application Server, 2-2 UNIX operating system, 2-2 SQL, flattening hierarchical data, D-4 string functions, D-2 system managed storage, 2-4 temporary directory parameter, 8-8 temporary files, 8-8 time limit parameter, 8-10 timeout client idle, 7-6 daemon, 7-6...
  • Page 170 Index-iv...

This manual is also suitable for:

Application server 10g

Table of Contents