Oracle® Application Server Adapters for IMS/DB User’s Guide 10g Release 3 (10.1.3.
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.
Contents Preface ................................................................................................................................................................. xi Audience....................................................................................................................................................... xi Documentation Accessibility .....................................................................................................................
Securing Access to Oracle Connect .............................................................................................. Setting Password Access to Oracle Studio ........................................................................... Specifying Users with Administrative Rights ..................................................................... Setting Up Run-Time User Access to the IBM z/OS Platform..........................................
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 .................................. Requirements ...................................................................................................................................... Adding the IMS/DB Hospital Data Source ......
Tuning............................................................................................................................................... XML................................................................................................................................................... Migration Considerations.................................................................................................................... Security Considerations ..............................................
Flattening Hierarchical Data Using SQL ....................................................................................... D-4 Using an Alias ............................................................................................................................ D-4 E Globalization Settings Defining the Language and Codepage................................................................................................
x
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.
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.
1 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.
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. Oracle Connect: Oracle Connect runs on the legacy system and handles requests from the J2CA 1.
2 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. Note: In addition to the installation procedures described in this section, the J2CA 1.5 IMS/DB adapter must be installed with Oracle Application Server. Installing the J2CA 1.5 IMS/DB adapter is described in Oracle Application Server Adapter Installation Guide.
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. The actual memory requirement depends on such things as the size of the database and the number of databases accessed. Disk Space (3380 and 3390 disks) 150 cylinders.
Installing Oracle Connect on an IBM z/OS Series Platform If you have an Oracle Connect back-end adapter already 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.
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 500 tracks (3390), format=FB, record length=80, block size=3120 FTP files to z/OS FTP using binary mode. RECEIVE INDSNAME('{HLQ}.
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: 1. 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. 2. Allocate datasets with the following space for each of these files: ■ OCL10134.TRANSMIT.KIT = 130 tracks (3380 and 3390 disks) ■ OCL10134.TRANSMIT.
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. ENTER THE STORCLASS FOR INSTALLATION This prompt is displayed only if SMS is used to manage the TEMP DATASETS [ ] : installation (you answered Y to the first prompt). Enter the storage class.
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 STORAGE FOR THIS INSTALLATION Y/N [N] : If you want to manage the storage using SMS, then answer Y, otherwise answer N. THE SOFTWARE WILL BE INSTALLED UNDER THE HIGH LEVEL QUALIFIER THAT YOU WILL CHOOSE. The high-level qualifier for the installation (referred to as INSTROOT throughout this guide).
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 Enter the IMS PROC Library name for IMS on your system ENTER PGM LIBRARY NAME Enter the IMS PGM Library name f
Installing Oracle Connect on an IBM z/OS Series Platform To define a DSN as APF-authorized, in the SDSF screen enter the command: Note: "/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. If the site uses SMS, then when defining APF-authorization in the SDSF screen, enter the following command: "/setprog apf,add,dsn=INSTROOT.
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 environment information. This PS is read at startup and the correct software version is used, based on the details provided in the startup task.
Updating an Existing Oracle Connect Installation with IMS/DB If you intend on using impersonation, so that you can run in a security context that is different than the context of the process that owns the server, then do the following: Note: ■ ■ Place the INSTROOT.LOAD(ATYSVCW) member in an APF-authorized library outside the LPA.
Installing Oracle Studio Follow the instructions in the Response column in for each entry in the Screen column.
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 Installing Oracle Studio on Windows Oracle Studio is installed with a standard install wizard. Do the following to install Oracle Studio. ■ Run the installation file, either using the Run option in the Windows Start menu or through Windows Explorer.
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 the IBM z/OS platform and that the Oracle Connect daemon is running on this computer. Note: Check with the system administrator to ensure these requirements are fulfilled. Setting Up the IBM z/OS Platform in Oracle Studio Using Oracle Studio, perform the following steps to configure the IBM z/OS platform: 1.
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.
Configuring Oracle Connect Figure 2–3 The Change Master Password Screen 5. Leave the Enter Current Master Password field blank and type a new master password. 6. Confirm the password. 7. 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.
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. Designers: Designers can view all the definitions for the computer in Oracle Studio and can modify any of the definitions under the Bindings and Users nodes for the selected computer.
Configuring Oracle Connect 4. 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 5. 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 6. Select Remote Machine from the Resource Type list. 7. Enter the name of the IBM z/OS computer defined in Oracle Studio. 8.
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.
Modeling Interactions for OracleAS Adapter for IMS/DB Figure 2–7 The New Data Source screen 9. Click Next. The Data Source Connect String screen for the selected data source type is displayed. 10.
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). The default value is ATYCLIEN.
Modeling Interactions for OracleAS Adapter for IMS/DB 2. 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.
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. xcflmsMember: This parameter specifies the Cross System Coupling Facility group member.
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.
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. Importing Metadata for the IMS/DB Data Source Oracle Connect requires metadata describing the IMS/DB data source records and the fields in these records.
Modeling Interactions for OracleAS Adapter for IMS/DB 10. 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 11. Click Finish. The Metadata Import wizard opens. 12. Click Add in the Import Wizard to add DBD files.
Modeling Interactions for OracleAS Adapter for IMS/DB 14. 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. 15. 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. 16.
Modeling Interactions for OracleAS Adapter for IMS/DB Perform the following steps to apply filters. 1. 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 COMP-6’1’ to treat COMP-6 as a COMP data type or COMP-6’2’ to treat COMP-6 as a COMP-3 data type. Compiler source: The compiler vendor.
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: 2. ■ Ignore after column 72: Ignore columns 73 to 80 in the COBOL copybooks. ■ Ignore first 6 columns: Ignore the first six columns in the COBOL copybooks. Click Next to go to the Selecting Tables step.
Modeling Interactions for OracleAS Adapter for IMS/DB Figure 2–15 Match DBD to COBOL Screen 1. 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. 2. Click Next (the Import Manipulation screen opens) to continue to the Import Manipulation step. Import Manipulation This section describes the operations available for manipulating the imported records (tables).
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.
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.
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. The following table describes the tasks that are done in this screen. If a toolbar button is available for a task, it is pictured in the table.
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. When you select this option, the following screen opens with an SQL statement based on the table or column entered at the bottom of the screen.
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. Hide/Reveal field Select a row from the Field manipulation screen and select Hide field to hide the selected field from that row.
Modeling Interactions for OracleAS Adapter for IMS/DB Table 2–14 (Cont.) Field Manipulation Screen Commands Command Description Add 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. Select Add Field or Add Child to open the following screen: Enter the name of the field or child, and click OK to add the field or child to the table.
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.
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. Replace variant Select Replace variant to replace a variant’s selector field.
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.
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). Perform the following steps to transfer the metadata. 1.
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.
Modeling Interactions for OracleAS Adapter for IMS/DB 9. Select Events. 10. Click Finish. The back-end adapter is added to the Configuration view and the Configuration properties open in the Editor. Note: Other adapters that are displayed in the Type list are not supported with the version of Oracle Connect installed at the site. 11. You can change any of the properties for the adapter, as required.
Modeling Interactions for OracleAS Adapter for IMS/DB Use the Metadata Import wizard in Oracle Studio to generate interaction metadata, as follows: 1. From the Start menu, select, Programs, Oracle, and then select Studio. 2. In the Design perspective, Configuration view expand the Machines folder. 3. In the Configuration view, expand the computer defined in "Setting Up the IBM z/OS Platform in Oracle Studio" on page 2-14. 4. Expand the Bindings folder.
Modeling Interactions for OracleAS Adapter for IMS/DB The option to use a previously saved query is not applicable. Note: c. 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 Define Interaction screen is displayed, enabling you to build a SELECT statement only, as indicated in the Query type field.
Modeling Interactions for OracleAS Adapter for IMS/DB Table 2–17 (Cont.) Interaction Parameters Parameter Description Nullable The nullable value (true or false). Default The default value for the parameter. Context Field This field is not applicable. Bind to Sqls This field is not applicable. f. Click Finish to generate the interaction, including the record schema required to support the interaction input and output.
Modeling Interactions for OracleAS Adapter for IMS/DB 3. 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. Any changes that need making to the record structures in the schema part of the metadata are done automatically.
3 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 ■ Configuring the J2CA 1.
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.
Using the CCI API to Develop Applications Table 3–1 (Cont.) OC4J Connection Properties Property Description serverName Sets the TCP/IP address or host name where the Oracle 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" on page 2-14. workspace Specifies to the name of a Oracle Connect server workspace to use. The default workspace is Navigator. See Also: "Workspaces" on page C-7 for details about workspaces.
Configuring Multiple Adapters 3. 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 Description name Specifies the interaction name.
4 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.
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: 1. Open the Oracle BPEL Admin window. 2.
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: PAGE 68Configuring Oracle BPEL Process Manager
Configuring Oracle BPEL Process Manager PAGE 70Configuring Oracle BPEL Process Manager 4-6 Oracle Application Server Adapters for IMS/DB User's Guide
5 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 one GB of RAM.
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. To configure a process with the BPEL process manager, you use JDeveloper. This section describes how to create a BPEL outbound process for IMS/DB reource adapters using JDeveloper.
Deploy a BPEL Outbound Process See Configuring an OracleAS Adapter for IMS/DB for Outbound Interactions for 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. The processes use the Web service called FINDDOCTOR. This service finds a list of doctors from IMS data. The following are the steps required to create the outbound process.
Deploy a BPEL Outbound Process 5. 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. Do the following to create the database adapter. 1. Drag a PartnerLink into a service lane of the visual editor.
Deploy a BPEL Outbound Process d. 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. e. Step 5, File Filtering: Includes Files with Name Pattern: Enter *xml f. Step 6, File Polling: Polling Frequency: enter 1 then select seconds from the list. g. Step 7, Messages: Schema File URL: Enter findDoctor.
Deploy a BPEL Outbound Process Figure 5–4 Outbound Receive Properties 3. 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 Variable field, then click OK in the Create Variable dialog box that is displayed. ■ Make sure that the Create Instance check box is selected. ■ Click OK to close the dialog box and accept the information.
Deploy a BPEL Outbound Process 3. 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. The Partner Link Type field displays the Partner Link defined in the WSDL file. 4.
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. 1. Double-click the Assign_1 activity to edit it. The Assign dialog box is displayed. Figure 5–7 Assign Dialog Box 2. Click the Create list and select Copy Operation. The Create Copy Operation dialog box is displayed. Figure 5–8 Create Copy 3.
Deploy a BPEL Outbound Process 5. 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. Do the following to test the outbound process. 1. Create a file and call it FindDoctor.xml as shown in the following example:
Deploy a BPEL Outbound Process 5-10 Oracle Application Server Adapters for IMS/DB User's Guide
6 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. For information on how to create an endpoint, see BPEL Process Manager Examples.
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. Enter the following information in the Add machine dialog box: ■ ■ ■ ■ ■ ■ Host name/IP address: Enter the name or IP address for the Mainframe computer whith the Hospital database.
Adding the IMS/DB Hospital Data Source 4. 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. The following figure shows the Add data source dialog box with the correct information: Figure 6–2 Add Data Source Dialog Box Import the Metadata You now import the metadata from the IMS/DB data into the data source.
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. For more information on using JDeveloper to create an endpoint, see BPEL Process Manager Examples. Do the following to create the interactions.
Create the findDoctor and findPatient Interactions 1. Expand the computer you just added and then expand the NAV binding. 2. Right-click the adapter you are using and select Show in Metadata. 3. Right-click Interactions and select New. 4. Enter the following information for in the wizard, then click Finish. ■ Name: findDoctor ■ Type: Database ■ Select Create event queue for the adapter. ■ In Creation Mode: select Manual, and Database query. ■ Interaction Name: findDoctor.
Create the findDoctor and findPatient Interactions 6-6 Oracle Application Server Adapters for IMS/DB User's Guide
7 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.
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. See Also: "Starting the Daemon" on page 2-10 for details about the ATTDAEMN JCL Shutting Down the Daemon To shut down the daemon use Oracle Studio, as follows: 1.
Troubleshooting the Daemon Table 7–1 (Cont.) Daemon Options Option Description View Log Displays the daemon log. For details see "Daemon Logs" on 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. Recycle servers Closes all unused servers and prepares all active servers to close when the client disconnects.
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 Option Description Status Checks the status of the server.
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. You can change the level of logging by clicking Properties.
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.
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. Cause: This message is informational only. The daemon successfully shut down. Action: No action required. C00A: Application %s not found.
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. 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.
Resolving Specific Errors To set impersonation: APF authorize all the steplibs in the server 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. In the Security tab of the Navigator workspace, under the daemon node in the Configuration Explorer, check Use specific workspace account and clear the Workspace account field of all values.
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. C021: Required variable %s not found Cause: An environment variable required by the Oracle Connect server was not defined when the server started up.
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. Action: Check whether you have sufficient system privileges.
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. Action: Contact Oracle Support Services. C034: An invalid super-server module ID was specified, %d Cause: Internal error.
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. Either increase the quota or lower the Clients per server limit field value in the WS Info. section of the daemon configuration. See Also: "General" on page C-7.
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. 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.
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. See Also: Daemon "Security" on page C-5 or "Security" on page C-16.
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.
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. Action: Change the value used in the operation to a valid value.
Resolving Specific Errors 7-18 Oracle Application Server Adapters for IMS/DB User's Guide
8 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.
Configuring the Daemon for High Availability 5. Right-click IRPCD and select New Workspace. The New Daemon Workspace screen is displayed. 6. Specify a name for the new workspace and optionally, provide a description. 7. Specify whether you want it to have default settings or copy the properties of an existing workspace. To copy the properties of an existing workspace, click Ellipsis and select the workspace from which you want to copy the properties. 8. Click Next.
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).
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.
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.
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 the adapters defined in the binding. Application adapters on the current computer.
Configuring a Binding Environment ■ Modeling ■ ODBC ■ OLEDB ■ Optimizer ■ Query Processor ■ Parallel Processing ■ Transactions ■ Tuning ■ XML Debug The following table lists the parameters that define debugging and logging operations: Table 8–2 Debug Parameters Parameter Description ACX trace Select this for the the input xml sent to the back-end adapter and the output xml returned by the back-end adapter to be written to the log.
Configuring a Binding Environment Table 8–2 (Cont.) Debug Parameters Parameter Description Transaction extended logging Select this for the transaction manager to write additional 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 Parameter Description NAV_UTIL editor This parameter is not applicable for use with OracleAS Adapter for IMS/DB.
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". Code Page For use with globalization support to identify the codepage for the workspace. See also: Appendix E, "Globalization Settings". NLS String Specifies the codepage used by a field whose data type is defined as nlsString.
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. User commit confirm table This parameter is not applicable for use with OracleAS Adapter for IMS/DB.
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 characters Select this to replace invalid XML characters with a ’?’. This property is used for diagnostic and troubleshooting purposes.
Security Considerations ■ ■ ■ 1. 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). 2. The server generates a random 128-bit RC4 session key which is returned encrypted to the client, using the shared key.
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 on page C-11. Access to the legacy platform through a firewall using the NAT protocol is specified when the computer is added to Oracle Studio.
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. Note: If a log file is not specified, then the format for the logFile parameter when RRS is not running is ,NORRS.
A 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.
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 General Tab Components Field Description Description An optional description of the table. Table Properties Data file location The name of the file that contains the table.
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 ■ Sequential ■ Relative: Used with RRDS files. Access to a specific record number of a relative file is performed by using a pseudo column to specify the record position. The hash symbol (#) is used to specify a pseudo column.
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. Table A–2 Metadata Column Tab Definitions Field name Description Name The name of the column Data type The data type of the column.
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 each of the columns is calculated. Fixed offset: When you select this check box, you will have a fixed offset.
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. When the default generated virtual table name is too long, use an Alias to replace the long name.
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 Organization field in the Table tab is set to Index. Note: The Indexes tab is shown in the following figure: Figure A–3 The Indexes tab This tab has two sections. The first section lets you define the index keys for the columns in the table. The bottom of the tab lists the properties for each of the columns at the top.
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. The buttons on the right side of the tab are used to manipulate the data in this section of the tab.
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). A value of 0 indicates that this table is empty. No.
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). A value of 0 indicates that there are no distinct values for the column.
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. Specify the number in the text box.
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 in the non-relational file. 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.
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. 1. From the Start menu, select Programs, Oracle, and then select Studio. 2. Expand the Machines folder, then expand the machine you are working with. 3. Expand the Bindings folder. 4. Expand the NAV binding. 5. Expand the Adapters folder to display the adapters list. 6.
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 ■ none ■ basic password Max request size Specifies the maximum size in bytes for an XML request or reply.
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. 1. In Oracle Studio Design perspective, Metadata view, expand the Adapters folder. 2. Expand the adapter with the interaction that you want to edit. 3. Expand the Adapter folder. 4. Right-click the adapter you want to edit and select Open.
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 not expect to receive a response. sync-receive: The interaction expects to receive a response. Input record Identifies an input record.
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. The Interaction Properties section lets you select any of the following: ■ ■ ■ ■ Pass Through: Select this to pass a query directly to the IMS/DB data.
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. You can edit the following properties for each parameter you create. Click in the corresponding cell to edit the properties. ■ ■ ■ ■ Name: The name of the parameter. This is automatically entered when you create a new parameter.
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: ■ ■ ■ Specifications Name: The name of the field Type: The data type of the field. See the Valid Data Types table for a list of the valid data types.
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: 1. In Oracle Studio Design perspective, Metadata view, expand the Adapters folder. 2. Right-click the adapter that you want to edit, and select Open as XML. The adapter XML editor is displayed in the Design view.
B 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 IMS/DB and Oracle Application Server is performed internally by Oracle Connect. Note: Data Type Mapping The COBOL data type COMP, in the table is an abbreviation for, and synonymous with, COMPUTATIONAL.
Data Type Mapping Table 8–7 (Cont.
C 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: 1. From the Start menu, select Programs, Oracle, and then select Studio. 2. From the Design perspective Configuration view expand the Machines folder. 3.
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. If no IP address is entered, the daemon will listen on all available IP addresses. Daemon port Enter the port where the daemon is listening. If no port is entered, the daemon listens on all available ports.
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.
Logging 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. Note: Changes made to the daemon configuration are only implemented after the configuration is reloaded using the Reload Configuration option in the Runtime Manager perspective. 7. Right-click the daemon and select Recycle Servers.
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. This is useful for troubleshooting the server. System trace Generates system-specific tracing of various operations.
Security ■ Determine access to the computer. The following shows how to open the Daemon Security tab: 1. From the Start menu, select Programs, Oracle, and then select Studio. 2. From the Design perspective Configuration view expand the Machines folder. 3. Right-click the computer and select Open Runtime Perspective. 4. Right-click the daemon in the Runtime Explorer and select Edit Daemon Configuration. 5. Click the Security tab. 6.
Workspaces Table 8–10 Daemon Security Tab Components Field Description Administrators privileges Identifies the users (accounts) allowed to perform administrative tasks (tasks that require administrative login). All users Enables all users to access the daemon and change the settings. Selected users only Identifies the names of users (accounts) and groups that can be administrators.1 If a user is not specified, the account from which the daemon was started is considered the administrator.
Workspaces 3. Right-click a computer and select Open Runtime Perspective. 4. Expand the Daemons node to display the workspaces in the Runtime Explorer. 5. Right-click the workspace and select Edit Workspace Configuration. The WS Info. tab opens. 6. After making changes to the workspace, right-click the daemon and select Reload Configuration. You can also change daemon settings using the Configuration Explorer, by selecting a computer and scrolling the list to the required daemon.
Workspaces Table 8–11 (Cont.) General Tab Components Field Workspace name Description 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. Description A description of the workspace. Startup script The full path name of the script that starts the workspace server processes.
Workspaces Table 8–11 (Cont.) General Tab Components Field Description Specific log file format Defines the name and location of the server log file if you 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.
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. Do the following to open the Server Mode tab: 1. From the Start menu, select Programs, Oracle, and then select Studio. 2.
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
Workspaces Table 8–12 Server Mode Tab Components Field Description Workspace server mode Specifies the type of new server processes that the daemon 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.
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: ■ ■ ■ ■ Port range Initial number of servers: The number of server processes that are prestarted for this workspace when the daemon starts up.
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. 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.
Workspaces Table 8–12 (Cont.) Server Mode Tab Components Field Description Number of spare servers The minimum number of server processes in the 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. The default for this field is 0.
Workspaces Notes: ■ ■ 8. 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 implemented. They are only implemented after the configuration is reloaded using the Reload Configuration option in the Runtime Manager. Right-click the daemon and select Recycle Servers.
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 account Select this if you want to define the operating system account used for the workspace. If selected, enter the name of the workspace account in the workspace account field. If not selected, the account name that was provided by the client is used.
D 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 ■ Supported Operators ■ Supported Functions ■ SQL Enhancements Supported SQL Statements OracleAS Adapter for IMS/DB supports SELECT, DELETE, INSERT, and UPDATE statements, when specified in interactions.
Supported Functions Table D–2 (Cont.
SQL Enhancements Table D–4 (Cont.
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 … parent_alias->child1->child2… [alias] Flattening Hierarchical Data Using SQL You can produce a flattened view of hierarchical data by embedding a SELECT statement inside the list of columns
E 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 ■ Spanish ■ Traditional Chinese ■ Turkish This appendix describes how to define the language support.
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 NLS Language Codes table. From the Codepage list, select the codepage that you want to use with this language. The code pages available are determined by the Language that is selected. If you have additional code pages available, you can manually enter them in this field.
Defining the Language and Codepage Table 8–14 (Cont.
Defining the Language and Codepage Table 8–14 (Cont.
Index A ACX trace parameter, 8-7 add timestamp to traced events parameter, 8-7 arithmetic operators, D-1 B binary XML log level parameter, 8-7 C cache buffer size parameter, 8-8 code page parameter, 8-9 COM maximum XML size in memory parameter, 8-10 COM maximum XML size parameter, 8-10 COM XML transport buffer parameter, 8-10 commit on destroy, 8-10 comparison operators, D-1 D daemon logging, C-3 security, C-5 server modes, 8-2 shutting down, 7-2 starting, 7-1 timeout, 7-6 data types atomic metadata, B-
year 2000 policy, 8-8 error log, binary XML log level parameter, 8-7 error log, log file parameter, 8-7 F flattening hierarchical data, D-4 functions group, D-2 string, D-2 M memory requirements IBM mainframe, 2-2 metadata atomic data types, B-1 miscellaneous parameters environment, 8-8 N nav utility editor parameter, 8-8 nav utility editor, text editor, 8-8 NLS string parameter, 8-9 G GDB trace parameter, 8-7 general parameters cache buffer size, 8-8 nav utility editor, 8-8 temporary directory, 8-8 yea
SMS 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 year 2000 policy parameter, 8-8 T temporary directory parameter, 8-8 temporary files, 8-8 time limit parameter, 8-10 timeout client idle, 7-6 daemon, 7-6 trace directory parameter, 8-7 trace information, logging, 8-7 transaction conversions parameters, 8-10 transaction extended logging, 8-9 Transaction extend
Index-iv
