Sun Microsystems TCP - Manual

Page 3 - Contents

Contents Sun Adapter for TCP/IP HL7 User's Guide .......................................................................................... 7 Sun Adapter for TCP/IP HL7 Overview ..............................................................................................8 About Sun Adapter for TCP/...

Page 8 - About Sun Adapter for TCP/IP HL7; Macro functionality, providing ease of use and productivity.

These links provide additional information that is useful to know when working with theTCP/IP HL7 Adapter: ■ “TCP/IP HL7 V2 Adapter Inbound Connectivity Map Properties” on page 30 ■ “TCP/IP HL7 V2 Adapter Outbound Connectivity Map Properties” on page 49 ■ “TCP/IP HL7 V3 Adapter Inbound Connectivity ...

Page 9 - Note –; TCP/IP HL7 Adapter Components

Note – Throughout this document the term “JMS queue” is used in the generic sense and actually denotes JMS queues or topics. TCP/IP HL7 Features The TCP/IP HL7 Adapter includes the following features: ■ Bidirectional processing, including client or server mode in either direction (to or from SunJava...

Page 10 - About HL7; Level Seven; information between computer applications.; The TCP/IP HL7 Adapter Architecture; TCP/IP HL7 Resource Adapter; HL7 Collaborations

The Message Library handles all of the lower-layer protocol. The Message Library’s behavior iscustomized using the Adapter configuration properties. These Adapter properties are used bythe resource adapter, but are also accessed and used by the prebuilt Collaborations. About HL7 HL7 is a standard fo...

Page 11 - Error Queues

If a system does not conform to the HL7 specification, the Collaborations can be modified forthat transaction by changing the Java code using the Collaboration Editor. The CollaborationsJava code is designed to be available and “transparent” so you can easily reference thepredefined Java code to see...

Page 12 - Using Enterprise Manager Management Application in; Modes and Roles; Standard Mode

■ Monitoring The Enterprise Manager provides a real-time picture of the Adapter's state and status. Themonitoring facilities display the following information: ■ Adapter up or down ■ Connected to external ■ Current sequence number ■ Date and time of the last transaction ■ Adapter properties ■ Alerts...

Page 13 - ESB Sender Role; The following steps convey the steps taken in this scenario.

HL7 Adapter Sender Role The outbound Collaboration is the implementation of the Sender and the RA is configured foran outbound data flow. A Java CAPS Service forwards the data to the Adapter, which in turnforwards the data to the accepting HL7 external system. The External System responds with anACK...

Page 14 - Sends App Ack; Forward External Acks to eGate; true; Inbound Functionality; Inbound Adapter Data Flow

2. The Receiver sends the message to the Forwarder. 3. The Forwarder sends the message to the receiving External System. 4. The receiving External System sends an ACK to the Forwarder. 5. The Forwarder receives the ACK from the External and forwards it on to the Receiver. 6. The Receiver then forwar...

Page 15 - Sends App Acks

Standard Inbound Message Mode Data Flow and Architecture The following steps describe the flow of data for an inbound Adapter: 1. The external system sends the HL7 message to the Adapter. 2. The Collaboration receives the HL7 message. 3. The Collaboration validates the message (if validate is enable...

Page 16 - Adapter Generates HL7 Acknowledgment; “Inbound Receiver Message Mode” on page 15; Canned HL7 NAK; Recourse Actions; “Recourse Actions” on page 21

Message Verification Message verification begins with reading the message from the external system. The message isexpected to match the MLLP envelope, since both HLLP and MLLP envelopes have the Start ofBlock (SOB), End of Data (EOD), and a Carriage Return (CR) in common. If a message fails the read...

Page 17 - Outbound Functionality; Outbound Adapter Data Flow; Recourse action on NAK received.; Outbound Standard Messaging Mode; accept the HL7 messages.

■ No response is received after a message is sent the maximum number of times. Outbound Functionality The outbound TCP/IP HL7 Adapter Project, prjHL7Outbound, can be implemented instandard outbound mode or in two forward message modes: outbound delayed ACK oroutbound forwarder. Outbound Adapter Data...

Page 18 - Outbound Adapter Roles for Delayed ACK Scenarios; Outbound Delayed ACK Role; message from JMS, and sends the message to the External System.; Outbound Forwarder Role; Data is received by the Collaboration, from the JMS queue.

5. The Collaboration receives and validates the ACK, and then journals the ACK and the HL7 message (if journaling is enabled). If the Collaboration receives a NAK, the NAK and theHL7 message are sent to the error queue. 6. Finally, the Collaboration commits the JMS receive. Outbound Adapter Roles fo...

Page 19 - Message Verification; “Delayed ACK Mode” on page 13; For more information on the available recourse actions, see

Note – For Delayed ACK, the Receiver and Forwarder must be on the same integration server. Message Verification The only verification that the outbound Adapter does is to ensure that the message parses intothe generic Event Message Library, and that the MSH uses the correct fields. The acknowledge i...

Page 20 - General Functionality; “HL7 Sequence Numbering Protocol” on page 20; HL7 Sequence Numbering Protocol

Note – The TCP/IP HL7 Adapter includes internal counters that keep track of all error conditions. General Functionality This section explains the Adapter’s general functions and features. It includes the followingtopics: ■ “Non-blocking I/O” on page 20 ■ “HL7 Sequence Numbering Protocol” on page 20 ...

Page 21 - Failed Message Handling; Error: the actual error message or NAK; Stopping the Collaboration with a Fatal Alert

The minimum HL7 sequence number is 1. The maximum HL7 sequence number is 2 billion. Asequence number of “0“ is used to start a session. If the sequence numbers between the Adapterand the external cannot be reconciled during start or when exchanging messages, the Adaptershuts down and wait for human ...

Page 22 - The; TCP/IP HL7 Adapter Operation; Direction; Connected as a TCP/IP HL7 Client

The argument error message is the user-configured alert message. The argument HL7 is the source component (this must be “HL7”). Note – The alerter.fatal( " error msg " , " HL7 " ) method is only applicable to the packaged TCP/IP HL7 Collaborations. The Exit recourse action should be ...

Page 23 - Lower Layer Protocol; “Lower Layer Protocol — TCP/IP HL7 V2 Inbound Adapter” on page 40; MLLP; HL7 Acknowledgment Level

Lower Layer Protocol This section describes the two supported envelope types used in the HL7 protocol: ■ HLLP (Hybrid Lower Layer Protocol) ■ MLLP (Minimal Lower Layer Protocol) Both envelope types use the following configuration parameters. For more information onthese parameters, see “Lower Layer ...

Page 24 - “Outbound Adapter Roles for Delayed ACK; Monitoring the HL7 Adapter; Using Enterprise Manager

It is expected that, when enabled, the journal queue has one or more subscribers that process thecontents of the queue so that it remains manageable. For example, the Batch Adapter or adatabase Adapter could periodically consume the messages by writing them to a file or adatabase. Error Queues The A...

Page 25 - Schematron Support in the HL7 Adapter

<web-app> ... ...  <context-param> <param-name>monitorperiod</param-name> <param-value>2000</param-value> </context-param> ... </web-app> Schematron Support in th...

Page 26 - Schematron Configuration in HL7 Adapter; Schematron Validation; enables schematron validation. You then need to; Schematron Files; API for Schematron Validation; API is an XSL file called metastylesheet (

In the HL7 Adapter, this schematron is useful for validating an HL7 V3 document againstpredefined schematron schemas that you write. You can also obtain schemas fromorganizations such as NHS and HL7.org. For example, NHS provides schemas for CDAdocuments. Schematron Configuration in HL7 Adapter You ...

Page 27 - Using the Schematron API; Obtaining the Factory Object; Performing the Validation

Using the Schematron API Perform the following to invoke the schematron API from a Java Collaboration: ■ Obtaining the Factory Object ■ Obtaining the Validator Object ■ Performing the Validation Obtaining the Factory Object Below is a sample call to the getSchematronValidatorFactory method. com.stc....

Page 28 - Connectivity Map; : These properties most commonly apply to a specific component; Environment Explorer; : These properties are commonly global, applying to all Adapters of; Collaboration; To Add a TCP/IP HL7 External Application; Select HL7 External Application from the menu.; The TCP/IP HL7 Adapter appears on the link.

You can configure the TCP/IP HL7 Adapter properties in the following locations: ■ Connectivity Map : These properties most commonly apply to a specific component Adapter, and may vary from other Adapters of the same type in the Project. ■ Environment Explorer : These properties are commonly global, ...

Page 29 - “Configuring; Tip –

Modify the Adapter properties, as described in “Modifying the TCP/IP HL7 Adapter Properties in the Connectivity Map” on page 29 . Modifying the TCP/IP HL7 Adapter Properties in theConnectivity Map You can modify an Adapter's properties after it is created in the Connectivity Map. Theproperties you m...

Page 30 - Modifying Adapter Properties in the Connectivity Map; This information is saved for future reference.; When you are done configuring the properties, click OK.; “General Inbound Settings – TCP/IP HL7 V2 Inbound Adapter” on page 31

▼ Modifying Adapter Properties in the Connectivity Map From the Connectivity Map, double-click the Adapter icon located in the link between theTCP/IP HL7 External Application and the Service. The Adapter Properties Editor appears, and displays either inbound or outbound propertiesdepending on the li...

Page 37 - – Available for Java EE, this scheduler is configured using the; Work Manager; using the

■ Timer Service – Available for Java EE, this scheduler is configured using the At Fixed Rate , Delay , and Period properties. ■ Work Manager – Available for Java EE (JCA 1.5 and above), this scheduler is configured using the Delay and Period properties. TABLE 7 Connectivity Map - TCPIP Inbound Sche...

Page 41 - HL7 MSH Segment — TCP/IP HL7 V2 Inbound Adapter

TABLE 10 Connectivity Map - Lower Layer Protocol (Continued) Name Description End Data Character The second to the last envelope marker character in the HL7 envelope, as adecimal ASCII number. Enter a number from 1 to 127. Unless there is a conflict,the value should be ASCII FS (decimal 28). End Blo...

Page 44 - HL7 SFT Segment — TCP/IP HL7 V2 Inbound Adapter; The SFT segment is available starting with HL7 version 2.5.

TABLE 12 Connectivity Map - HL7 MSH Segment (Continued) Name Description Validate MSH An indicator of whether to validate the MSH segment of the data message (forinbound) and the MSH segment of the ACK (for outbound). Select true if you want the Collaboration to validate the MSH segment; otherwise s...

Page 59 - HL7 SFT Segment — TCP/IP HL7 V2 Outbound Adapter

TABLE 23 Connectivity Map - HL7 MSH Segment (Continued) Name Description Conformance StatementID A unique identifier that applies to a query’s conformance statement. It can also beused as a Message Profile Identifier to assert constancy with a message profile(grammar, syntax, usage, and so on). This...

Page 91 - To Configure the Environment Properties; Right-click the External System and select Properties.; The Environment Configuration Properties window appears.; Click on any property field to modify it.

Configuring Sun Adapter for TCP/IP HL7 EnvironmentProperties The adapter environment configuration properties define how the adapter connects to andinteracts with other Java CAPS components within the environment. The environmentproperties are accessed from the NetBeans IDE Services window. The foll...

Page 92 - TCP/IP HL7 Inbound Adapter Environment Properties; “HL7 Inbound Adapter - TCPIP Inbound Settings” on page 92; HL7 Inbound Adapter - TCPIP Inbound Settings; HL7 Inbound Adapter - MDB Pool Settings

TCP/IP HL7 Inbound Adapter Environment Properties The TCP/IP HL7 Adapter configuration parameters accessed from the Environment tree applyto both the inbound and outbound Adapters, and are the same for HL7 v2 and HL7 v3Adapters. The inbound TCP/IP HL7 Adapter’s Environment properties are divided int...

Page 93 - HL7 Inbound Adapter - Sequence Number Protocol

TABLE 52 Environment - HL7 Inbound Adapter - TCPIP Inbound Settings Name Description Steady Pool Size An integer indicating the minimum number of message–driven beans tomaintain. When the value is set to a number greater than 0 (zero), the containerpre-populates the MDB pool with the specified numbe...

Page 94 - HL7 Inbound Adapter - Database Settings; “HL7 Outbound Adapter - TCPIP Outbound Settings” on page 95

TABLE 53 Environment - HL7 Inbound Adapter - Sequence Number Protocol Name Description Sequence Number FileLocation The location of the sequence number file (a local directory). This is required whenthe Sequence Number Protocol is enabled. The sequence number folder is anonvolatile directory that st...

Page 95 - HL7 Outbound Adapter - TCPIP Outbound Settings; HL7 Outbound Adapter - Connection Pool Settings

HL7 Outbound Adapter - TCPIP Outbound Settings The following table lists and describes the properties that appear on the MDB Pool Setting pageof the Properties Editor accessed from the Environment. These properties configure the Javasocket and server socket options. For more information, see the Jav...

Page 96 - HL7 Outbound Adapter - Sequence Number Protocol

TABLE 56 Environment - HL7 Outbound Adapter - Connection Pool Settings Name Description Steady Pool Size An integer indicating the minimum number of resource adapter connections tobe maintained. When the value is set to a number greater than 0 (zero), thecontainer pre-populates the RA connection poo...

Page 97 - Prerequisites for the HL7 V3 Sample Projects

TABLE 57 Environment - HL7 Outbound Adapter - Sequence Number Protocol Name Description Sequence Number FileLocation The location of the sequence number file (a local directory). This is required whenthe Sequence Number Protocol is enabled. The sequence number folder is anonvolatile directory that s...

Page 98 - Creating a Copy of an HL7 Sample Project; To Create a Copy of a Project; Start the CAPS Repository.; The Connect to CAPS Repository dialog box appears.; Enter the connection information and click Connect.; When connected the icon in the status bar turns from red to green.

Collaborations. Therefore, it is important to maintain the original predefinedjcdHL7V3Inbound and jcdHL7V3Outbound Collaborations in their initial form for future use. Before working with the HL7 V3 sample Projects, be sure that the required HL7 V3 SAR filesare uploaded to the repository. The requir...

Page 99 - Export the Project you want to copy:; The Export Manager dialog box appears.; b. Select the Projects and Environments to export.

Export the Project you want to copy: a. On the Projects window, right-click the Project to copy, click Export, and then click Project. The Export Manager dialog box appears. b. Select the Projects and Environments to export. The selected Project appears in the Selected Projects: pane of the Export M...

Page 100 - pane to the left pane.; Rename the original Project in the NetBeans IDE.

Tip – Click the left-arrow button , if you want to move the selected projects from the right pane to the left pane. d. Click Browse and select an appropriate directory to save the exported Project. e. Click Export. The Project is compressed and saved to the specified directory and file name. Rename ...

Page 101 - must perform this step before importing the Project back in.; Import the Project back in to the Repository.; The Import Manager appears.

Note – The NetBeans IDE will not import identically named Projects to the same root, so you must perform this step before importing the Project back in. On the NetBeans IDE, click Save All. Import the Project back in to the Repository. a. On the NetBeans menu bar, select Tools, point to CAPS Reposit...

Page 102 - Customizing Predefined Collaborations for HL7; “Creating Copies of HL7 Collaborations” on page 102; Creating Copies of HL7 Collaborations; To Create Copies of HL7 Collaborations; Right-click the Collaboration you want to copy, and select Copy.

d. Click Import. It may take a few seconds to import the project. When the project is imported, the ImportStatus dialog box appears. e. Click OK on the dialog box. The CAPS Repository is refreshed, and you now have two copies of the same Project in theRepository. Customizing Predefined Collaboration...

Page 103 - Repeat this step for additional copies of the Collaboration.

Repeat this step for additional copies of the Collaboration. To add each new Collaboration to a Project's Connectivity Map, drag and drop the Collaborationfrom the Projects Explorer tree to the Connectivity Map Editor. The new Collaborations can now be associated with the Project's components. FIGUR...

Page 104 - you are working with.; To Add HL7 Message Library to an Existing Collaboration; Select Properties from the drop-down menu.

Adding an HL7 Message Library to an ExistingCollaboration In some cases, a specific HL7 message or messages might need to be added to the Collaboration.Perform the following to add a HL7 Message Library to an existing Collaboration. Note – Make sure you are using the correct version of the Message L...

Page 105 - Click Add to select the object type definition.

Click Add to select the object type definition. A dialog box appears where you can select the Message Library to add. FIGURE 6 Collaboration Definition (Java) Properties 4 Using the TCP/IP HL7 Predefined Templates Sun Adapter for TCP/IP HL7 User's Guide 105

Page 106 - Select the Message Library and then click Select.; The Message Library is added to the list.

In the Look In field, navigate to the location of the Message Library. The HL7 Message Libraries are located in CAPS Components Library > Message Library > HL7. Select the Message Library and then click Select. The Message Library is added to the list. FIGURE 7 Select Object Type Definition 5 ...

Page 107 - On the Collaboration Definition Properties dialog box, click OK.

Tip – You can also modify an existing HL7 V2 Message Library by clicking the Message Library to change, clicking the ellipsis that appears, and selecting the appropriate Message Library. On the Collaboration Definition Properties dialog box, click OK. About TCP/IP HL7 V2 Collaborations This section ...

Page 108 - TCP/IP HL7 V2 Adapter Projects Overview; HL7 Adapter Inbound Collaboration Projects; TCP/IP HL7 V2 Adapter Collaborations

The following topics provide information about the sample V2 Collaborations and provideinstructions for copying and customizing them: ■ “TCP/IP HL7 V2 Adapter Projects Overview” on page 108 ■ “TCP/IP HL7 V2 Adapter Collaborations” on page 108 ■ “Inbound HL7 V2 Collaboration Overview” on page 109 ■ “...

Page 109 - JMS using the; Inbound HL7 V2 Collaboration Overview; “Inbound HL7 V2 Collaboration - Part 1” on page 109; Inbound HL7 V2 Collaboration - Part 1

At the end of each action, the state is set for the next execution of the Collaboration. There arethree main states: ■ To Establish: A new or reset connection needs to have an HL7 session established. If sequence numbering is used, the sequence numbers need to be negotiated. ■ Messaging: This is whe...

Page 110 - The above text has been wrapped to fit the page.

otdHL7_GENERIC_EVT_1, com.stc.SeeBeyond.OTD_Library.HL7.Generic.HL7_ACK.AC K otdHL7_ACK_1,com.stc.connectors.jms.JMS otdJMS_JOURNAL, com.stc.connectors.jms.JMS otdJMS_ERROR) throws Throwable Note – The above text has been wrapped to fit the page. Once the message is received, the Collaboration deter...

Page 112 - Inbound HL7 V2 Collaboration - Part 2

Inbound HL7 V2 Collaboration - Part 2 The Collaboration receives the HL7 V2 message from the external using receiveHL7message() . If an exception occurs due to incomplete data and the adapter fails to read the data within the configured number of retries, the associated recourse action is taken. Ift...

Page 114 - If sequence numbering is enabled, the; Outbound HL7 V2 Collaboration Overview

Inbound HL7 V2 Collaboration - Part 3 After the ACK is sent, the HL7 V2 message and the ACK are journaled to the JMS queue Journaldestination. If the message fails to journal, the associated recourse action is taken. If sequence numbering is enabled, the processAckNakSequenceNumbering method calcula...

Page 115 - Outbound HL7 V2 Collaboration - Part 1; receive

The following topics describe the business logic defined in the jcdHL7Outbound Collaboration: ■ “Outbound HL7 V2 Collaboration - Part 1” on page 115 ■ “Outbound HL7 V2 Collaboration - Part 2” on page 117 ■ “Outbound HL7 V2 Collaboration - Part 3” on page 119 ■ “HL7 V2 Outbound Test Collaboration” on...

Page 117 - Outbound HL7 V2 Collaboration - Part 2; validateAckNak

Outbound HL7 V2 Collaboration - Part 2 The Collaboration receives the HL7 ACK or NAK from the external system using receiveHL7AckNak() . If an exception occurs due to incomplete data and the adapter fails to read the data within the configured number of retries, the associated recourse action is tak...

Page 119 - HL7 V2 Outbound Test Collaboration

Outbound HL7 V2 Collaboration - Part 3 If the ACK message passes validation, the HL7 V2 message and ACK message are sent to theJMS journal destination. If the message fails to journal, the associated recourse action is taken. If sequence numbering is enabled, the processAckNakSequenceNumbering metho...

Page 120 - “TCP/IP HL7 V3 Adapter Projects Overview” on page 121

About TCP/IP HL7 V3 Collaborations The following topics provide a brief overview of HL7 V3, and describe the HL7 V3Collaborations and provide instructions on copying and customizing the Collaborations: ■ “About HL7 V3” on page 120 ■ “TCP/IP HL7 V3 Adapter Projects Overview” on page 121 ■ “TCP/IP HL7...

Page 121 - TCP/IP HL7 V3 Adapter Projects Overview

The V3 standard also includes interactions, such as Create Patient Billing Account. There are three modes of Acknowledgement process in HL7 V3: ■ Immediate Mode ■ Deferred Mode ■ Queued Mode TCP/IP HL7 V3 Adapter Projects Overview Several HL7 V3 sample Projects are provided with the TCP/IP HL7 Adapt...

Page 122 - Inbound HL7 V3 Immediate Collaboration Overview; Process) — Part 1” on page 122

1. Inbound HL7 V3 Immediate Collaboration2. Inbound HL7 V3 Deferred Collaboration3. Inbound HL7 V3 Queue Manager4. Inbound HL7 V3 Message Publisher Inbound HL7 V3 Immediate Collaboration Overview The Inbound HL7 V3 Collaboration, jcdHL7V3Inbound, contains Message Libraries for theHL7 V3 Resource Ada...

Page 127 - Inbound HL7 V3 Deferred Collaboration Overview

Inbound HL7 V3 Deferred Collaboration Overview The Inbound HL7 V3 Collaboration, jcdHL7V3DeferredInbound, contains Message Librariesfor the HL7 V3 Resource Adapter, JMS Data, JMS Journal, JMS Error, and JMS APP ACK aswell as the HL7 V3 Patient Administration Domain Interaction Event (PRPA_IN403001UV...

Page 128 - The above text is wrapped to fit the page.

otdHL7_ACK_1,com.stc.connectors.jms.JMS otdJMS_JOURNAL, com.stc.connectors.jms.JMS otdJMS_ERROR) throws Throwable. Note – The above text is wrapped to fit the page. Once the message is received, the Collaboration determines whether the message needs to bevalidated. The HL7 V3 message is then validat...

Page 133 - Outbound HL7 V3 Collaboration Overview

Outbound HL7 V3 Collaboration Overview The Outbound HL7 V3 Collaboration, jcdHL7V3Outbound, contains Message Libraries for theHL7 V3 Resource Adapter, JMS Data, JMS Journal, and JMS Error, as well as the HL7 V3Patient Administration Domain Interaction Event (PRPA_IN403001UV01) and the HL7 V3 Message...

Page 139 - HL7 V3 Outbound Test Collaboration; “HL7 V2 Outbound Test Collaboration” on page 119

HL7 V3 Outbound Test Collaboration For information, see “HL7 V2 Outbound Test Collaboration” on page 119 . Ack Message passed validation? journalMessage() Sends HL7 and Ack mesaages to JMS Journal Destination Nak Message Journal HL7 message processAckNakSequenceNumbering() Calculates the next sequen...

Page 140 - Creating and Configuring the MLLP V2.0 Database; Oracle; To Create and Connect to the Database; The Create Java DB Database dialog box appears.

MLLP V2 and the Sample Projects Minimal Lower Layer Protocol Release 2 (MLLP V2.0) is a message transport protocol, and isrequired for all message transport protocols used to transport HL7 Version 3 content. Thisprotocol wraps the HL7 message to indicate the beginning and end of each message. The fo...

Page 141 - The New JDBC Driver dialog box appears.; c. Click Add, and then brows to and select the database driver file.; The New Database Connection dialog box appears.

d. Click OK. The database appears in the list of databases on the Services window. Make sure your database instance is running. For Oracle, DB2, SQL Server, and Sybase databases, do the following: a. Copy the database driver file to JavaCAPS_Home /appserver/lib . b. Under Databases on the NetBeans S...

Page 142 - A broken icon represents that the database is not connected.; To Run the MLLP V2.0 Database Scripts; On the NetBeans IDE, click the Projects tab.

Note – A broken icon represents that the database is not connected. ▼ To Run the MLLP V2.0 Database Scripts You can either run the MLLP database scripts from NetBeans or from a SQL editor. Thefollowing steps take you through running the scripts from NetBeans. On the NetBeans IDE, click the Projects ...

Page 143 - This opens the SQL Editor window along with the SQL Statement.

This opens the SQL Editor window along with the SQL Statement. CREATE TABLE HL7MESSAGELOG (MESSAGEID VARCHAR(250), APPLICATIONID VARCHAR(250) , REQUESTMESSAGE CLOB, RESPONSEMESSAGE CLOB, STATUS SMALLINT, CREATEDTIME TIMESTAMP, LASTUPDATEDTIME TIMESTAMP) In the SQL Editor toolbar, click in the Connec...

Page 144 - To Create the Connection Pool and JDBC Resource; “Creating a JDBC; Sun GlassFish Enterprise Server 2.1 Administration Guide; Associating the MLLP Database With the Adapter; The Properties Editor appears.; “To Create the Connection Pool and JDBC Resource” on page 144; MLLP V2 Content Exchange Model

To view the new tables, return to the Services window, right-click the database connection, andthen click Refresh. Expand the database connection and then Tables to view the database. ▼ To Create the Connection Pool and JDBC Resource In order to connect to the database, you need to define a JDBC con...

Sun Microsystems TCP - Manual

Table of Contents:

Summary

Other Sun Microsystems Models