TIBCO ActiveMatrix® Adapter for JD Edwards EnterpriseOne · PDF fileTIBCO...

Two-Second Adv

TIBCO ActiveMatrix® Adapter for JD Edwards EnterpriseOne

Configuration and DeploymentSoftware Release 6.0August 2013

antage®

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.TIBCO, Two-Second Advantage, TIBCO ActiveMatrix BusinessWorks, TIBCO Designer, TIBCO Runtime Agent, TIBCO Administrator, TIBCO Rendezvous, TIBCO Hawk, TIBCO Enterprise Message Service, and TIBCO ActiveMatrix Adapter for JD Edwards EnterpriseOne are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform Enterprise Edition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle Corporation in the U.S. and other countriesAll other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.Copyright © 1999-2013 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

| iii

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiTIBCO ActiveMatrix Adapter for JD Edwards EnterpriseOne Documentation . . . . . . . . . . . . . . . . . . . . . . . . xiiOther TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiThird-Party Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiii

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiHow to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiHow to Access TIBCO Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiHow to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Chapter 1 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Preparing JD Edwards EnterpriseOne. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Configuring the INI File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 2 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Configuring an Adapter Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Creating and Configuring Adapter Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Starting the Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Starting the Adapter with the Adapter Tester . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Starting the Adapter from the Command line with a Repository File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 3 Adapter Instance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Configuration Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Design-time Connection Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Runtime Connection Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Multithreading Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Logging Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

TIBCO ActiveMatrix Adapter for JD Edwards EnterpriseOne Configuration and Deployment

iv | Contents

Startup Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Monitoring Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Chapter 4 Adapter Service Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Publication Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Configuration Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Transport Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Real-time Event Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Schema Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Subscription Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Configuration Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Transport Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Business Functions Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Schema Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Request-Response Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Configuration Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Transport Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Business Functions Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Schema Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Chapter 5 Deploying and Starting an Adapter Using TIBCO Administrator . . . . . . . . . . . . . . . 51

Creating an EAR File in TIBCO Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Deploying the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Starting or Stopping the Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Monitoring the Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Chapter 6 Monitoring the Adapter Using TIBCO Hawk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Overview of TIBCO Hawk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Starting TIBCO Hawk Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

The Auto-Discovery Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Invoking Microagent Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Available Microagents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64activateTraceRole() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67deactivateTraceRole() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68getAdapterServiceInformation(). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69getComponents() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70getConfig() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71getConfigProperties(). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72getHostInformation() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73getRvConfig(). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74getRvQueueInfo() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75


Contents | v

getPerformanceMetrics() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76getServerLatency() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77getStatus() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78getTraceSinks(). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79getVersion() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80_onUnsolictedMsg() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81preRegisterListener() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82reviewLedger() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83setTraceSinks() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85stopApplicationInstance() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86unRegisterListener() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Chapter 7 Advanced Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

Using the Adapter with a Revision Control System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Defining a TIBCO Hawk Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Using Global Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Changing Global Variable Values at Runtime. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Predefined Global Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Managing Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Saving Connection Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Refreshing Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Setting Encoding Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Setting Up Debug Log Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

JDE Test Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Appendix A Trace Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Trace Message Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Status Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Appendix B Data Type Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127


vi | Contents


Figures | vii

Figures

Figure 1 JDE Adapter Configuration Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Figure 2 Microagents, Methods and Argument Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Figure 3 Displaying a Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Figure 4 Invocation Results Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Figure 5 Monitoring Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Figure 6 Default Hawk Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Figure 7 Defined Hawk Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Figure 8 Connection Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Figure 9 JDE Test Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104


viii | Figures


Tables | ix

Tables

Table 1 General Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Table 2 Syntax Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Table 3 Adapter Instance: Configuration Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Table 4 Adapter Instance: Design-time Configuration Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Table 5 Adapter Instance: Runtime Connection Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Table 6 Adapter Instance: General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Table 7 Adapter Instance: Multithreading Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Table 8 Adapter Instance: Logging Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Table 9 Adapter Instance: Startup Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Table 10 Adapter Instance: Monitoring Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Table 11 Publication Service: Configuration Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Table 12 Publication Service: Transport Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Table 13 Publication Service: Real-time Event Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Table 14 Publication Service: Schema Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Table 15 Subscription Service: Configuration Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Table 16 Subscription Service: Transport Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Table 17 Subscription Service: Business Function Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Table 18 Subscription Service: Schema Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Table 19 Request-Response Service: Configuration Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Table 20 Request-Response Service: Transport Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Table 21 Request-Response Service: Business Function Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Table 22 Request-Response Service: Schema Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Table 23 Microagent Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Table 24 Predefined Global Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Table 25 Connection Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Table 26 Supported Test Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Table 27 Tracing Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Table 28 Data Type Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125


x | Tables


| xi

Preface

TIBCO ActiveMatrix Adapter for JD Edwards EnterpriseOne allows one-way (publish or subscribe) or two-way (request-response) message exchange between TIBCO applications and the JD Edwards EnterpriseOne enterprise resource planning (ERP) system.

This document describes how to configure and deploy a TIBCO ActiveMatrix adapter for JDE.

Topics

• Related Documentation, page xii

• Typographical Conventions, page xiv

• Connecting with TIBCO Resources, page xvii

In this document, TIBCO ActiveMatrix Adapter for JD Edwards EnterpriseOne is referenced as TIBCO ActiveMatrix Adapter for JDE, and JD Edwards EnterpriseOne is referenced as JDE.


xii | Related Documentation

Related Documentation

This section lists documentation resources you may find useful.

TIBCO ActiveMatrix Adapter for JD Edwards EnterpriseOne DocumentationThe following documents form the TIBCO ActiveMatrix Adapter for JD Edwards EnterpriseOne documentation set:

• TIBCO ActiveMatrix Adapter for JD Edwards EnterpriseOne Concepts Read this manual to gain an understanding of the product that you can apply to the various tasks you may undertake.

• TIBCO ActiveMatrix Adapter for JD Edwards EnterpriseOne Installation Read this manual for instructions on site preparation and installation.

• TIBCO ActiveMatrix Adapter for JD Edwards EnterpriseOne Configuration and Deployment Read this manual for instructions on how to create, configure, and deploy adapter projects.

• TIBCO ActiveMatrix Adapter for JD Edwards EnterpriseOne Examples Read this manual to work through the examples provided with the adapter.

• TIBCO ActiveMatrix Adapter for JD Edwards EnterpriseOne Release Notes Read the release notes for a list of new and changed features. This document also contains lists of known issues and closed issues for this release.

Other TIBCO Product DocumentationYou may find it useful to read the documentation for the following TIBCO products:

• TIBCO ActiveMatrix BusinessWorks™

• TIBCO Adapter® SDK

• TIBCO Administrator™

• TIBCO Designer™

• TIBCO Enterprise Message Service™

• TIBCO Hawk®

• TIBCO Rendezvous®

• TIBCO Runtime Agent™


Preface | xiii

Third-Party DocumentationYou may also find it useful to read the JDE documentation on the following web site:

• http://www.oracle.com/technetwork/documentation/jdedent-098169.html


http://www.oracle.com/technetwork/documentation/jdedent-098169.html

xiv | Typographical Conventions

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

ENV_NAME

TIBCO_HOME

TIBCO products are installed into an installation environment. A product installed into an installation environment does not access components in other installation environments. Incompatible products and multiple instances of the same product must be installed into different installation environments.

An installation environment consists of the following properties:

• Name Identifies the installation environment. This name is referenced in documentation as ENV_NAME. On Microsoft Windows, the name is appended to the name of Windows services created by the installer and is a component of the path to the product shortcut in the Windows Start > All Programs menu.

• Path The folder into which the product is installed. This folder is referenced in documentation as TIBCO_HOME.

ADJDEXE_HOME TIBCO ActiveMatrix Adapter for JD Edwards EnterpriseOne installs into a directory within a TIBCO_HOME. This directory is referenced in documentation as ADJDEXE_HOME. The default value of ADJDEXE_HOME depends on the operating system. For example, on Windows systems, the default value is C:\tibco\adapter\adjdexe\6.0.

code font Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example:

Use MyCommand to start the foo process.

bold code font Bold code font is used in the following ways:

• In procedures, to indicate what a user types. For example: Type admin.

• In large code samples, to indicate the parts of the sample that are of particular interest.

• In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled: MyCommand [enable | disable]


Preface | xv

italic font Italic font is used in the following ways:

• To indicate a document title. For example: See TIBCO ActiveMatrix BusinessWorks Concepts.

• To introduce new terms For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal.

• To indicate a variable in a command or code syntax that you must replace. For example: MyCommand PathName

Key combinations

Key name separated by a plus sign indicate keys pressed simultaneously. For example: Ctrl+C.

Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q.

The note icon indicates information that is of special interest or importance, for example, an additional action required only in certain circumstances.

The tip icon indicates an idea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result.

The warning icon indicates the potential for a damaging situation, for example, data loss or corruption if certain steps are taken or not taken.

Table 1 General Typographical Conventions (Cont’d)

Convention Use

Table 2 Syntax Typographical Conventions

Convention Use

[ ] An optional item in a command or code syntax.

For example:

MyCommand [optional_parameter] required_parameter

| A logical OR that separates multiple items of which only one may be chosen.

For example, you can select only one of the following parameters:

MyCommand param1 | param2 | param3


xvi | Typographical Conventions

{ } A logical group of items in a command. Other syntax notations may appear within each logical group.

For example, the following command requires two parameters, which can be either the pair param1 and param2, or the pair param3 and param4.

MyCommand {param1 param2} | {param3 param4}

In the next example, the command requires two parameters. The first parameter can be either param1 or param2 and the second can be either param3 or param4:

MyCommand {param1 | param2} {param3 | param4}

In the next example, the command can accept either two or three parameters. The first parameter must be param1. You can optionally include param2 as the second parameter. And the last parameter is either param3 or param4.

MyCommand param1 [param2] {param3 | param4}

Table 2 Syntax Typographical Conventions (Cont’d)

Convention Use


Preface | xvii

Connecting with TIBCO Resources

How to Join TIBCOmmunityTIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts. It is a place to share and access the collective experience of the TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety of resources. To register, go to http://www.tibcommunity.com.

How to Access TIBCO DocumentationYou can access TIBCO documentation here:

http://docs.tibco.com

How to Contact TIBCO SupportFor comments or problems with this manual or the software it addresses, contact TIBCO Support as follows:

• For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site:

http://www.tibco.com/services/support

• If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

Entry to this site requires a user name and password. If you do not have a user name, you can request one.


http://www.tibcommunity.com

http://docs.tibco.com

http://www.tibco.com/services/support

https://support.tibco.com

xviii | Connecting with TIBCO Resources


| 1

Chapter 1 Prerequisites

This chapter explains the prerequisites needed to configure and run the adapter.

Topics

• Preparing JD Edwards EnterpriseOne, page 2

• Configuring the INI File, page 3


2 | Chapter 1 Prerequisites

Preparing JD Edwards EnterpriseOne

JD Edwards EnterpriseOne is an integrated application suite of comprehensive enterprise resource planning software, which combines business value, standards-based technology, and deep industry experience into a business solution.

Before configuring an adapter instance for JDE, ensure that the JD Edwards EnterpriseOne enterprise server has been installed and configured.

To use the adapter with the JD Edwards EnterpriseOne, you must use the JD Edwards EnterpriseOne thin or fat client and connect to the JD Edwards EnterpriseOne enterprise server.

You can use the JDE Test Tool to test the connection and JDE data before running the adapter services. See JDE Test Tool on page 103 for more details.

If you want to use the Publication Service to publish the real-time events, the real-time events must be initialized. To successfully retrieve all the real-time events defined in the JD Edwards EnterpriseOne applications, the Transport Type for the Event Subscriber specified in the JD Edwards EnterpriseOne application must be JAVACONN.


Configuring the INI File | 3

Configuring the INI File

Before configuring the adapter, the jdeinterop.ini file that contains the connection parameters must be configured.

Complete the following steps to configure the jdeinterop.ini file:

1. Copy the jdeinterop.ini.templ file in the system\classes\samples\ConnectorSamples.zip\config directory from the JDE enterprise server to the adapter machine, and then change the file name to jdeinterop.ini.

2. Copy the jdbj.ini file in the system\classes\samples\ConnectorSamples.zip\config directory from the JDE enterprise server to the adapter machine.

3. Copy the database configuration file that is used to connect to the database from the JDE enterprise server to the adapter machine. The configuration file varies depending on the JDBC database used. For example, if an Oracle database is used, the configuration file is tnsnames.ora residing in the <database-home>\dbhome_1\network\admin directory.

4. Copy the content in the jdbj.ini file to the jdeinterop.ini file.

5. Configure the jdeinterop.ini file according to the JD Edwards EnterpriseOne system that the adapter connects to.

6. Save the file.


4 | Chapter 1 Prerequisites


| 5

Chapter 2 Getting Started

This chapter describes the basic steps required to configure and run an adapter. It also introduces how to use TIBCO ActiveMatrix BusinessWorks. Details for each of the steps described here are provided later in the manual.

Topics

• Configuring an Adapter Instance, page 6

• Creating and Configuring Adapter Services, page 8

• Starting the Adapter, page 9


6 | Chapter 2 Getting Started

Configuring an Adapter Instance

Before starting the configuration exercise, ensure that all the preparations described in the Prerequisites chapter are in place.

Each project contains one or more instances of the adapter configuration. This configuration is accessed whenever an adapter application is started.

Task A Configure the jdeinterop INI File

The jdeinterop.ini file must be configured prior to configuring an adapter instance. See Configuring the INI File on page 3 for more details about configuring the INI file.

Task B Create a Project

The TIBCO Designer GUI is used to configure adapter instances. When starting Designer, you must create or select a project. A project contains the configuration files that define options used by a runtime adapter.

To create a project:

1. Start TIBCO Designer by executing one of the following platform-specific commands:

— On Microsoft Windows:

select Start > All Programs > TIBCO > TIBCO Designer version_number > TIBCO Designer

— On Unix:

from a command window change the directory to TIBCO_HOME/designer/version_number/bin and type ./designer

2. In the TIBCO Designer startup panel, click New empty project.

3. From the Project menu, select the Save button.

4. In the Project Directory field, browse to select the directory where you want to save the project and specify a name for the project. Click OK.

Task C Create an Adapter Instance

After creating the project, to create and configure the adapter, complete the following steps:

1. Open the project created in the preceding task in the Project Explorer.


Configuring an Adapter Instance | 7

2. Expand the JDE Adapter palette in the Palettes panel.

3. Drag the JD Edwards EnterpriseOne Adapter Configuration icon to the Design panel on the right. The JDE Adapter Configuration panel is displayed, as shown in Figure 1.

Figure 1 JDE Adapter Configuration Panel

4. Specify a name for this adapter instance in the Configuration tab. The default name is JDEAdapterConfiguration. Check the Show All Tabs checkbox to show the advanced configurations.

5. Set up the connection options in the Design-time Connection tab and the Runtime Connection tab. See Design-time Connection Tab on page 14 and Runtime Connection Tab on page 16 for more details.

6. Save your project.

If the JDE Adapter palette does not appear in the Palettes panel, select Palettes > Adapters > JDE Adapter from the menu.



Creating and Configuring Adapter Services

After configuring the adapter instance, you need to add and configure adapter services that perform the data passing operations for the adapter. You can add more than one service to an adapter service. The available services for the adapter are as follows:

• Publication Service, page 28

• Subscription Service, page 34

• Request-Response Service, page 42

Take the Publication Service as an example. To add and configure a Publication Service, complete the following steps:

1. Expand the adapter instance folder in the Project panel, and then select the Adapter Services folder.

2. Specify a name for this adapter service in the Configuration tab in Adapter Services panel.

3. Drag the Publication Service icon from the JDE Adapter palette to the Design panel. See Publication Service on page 28 for details about configuring the service.

4. Save your project.


Starting the Adapter | 9

Starting the Adapter

After configuring the adapter with corresponding services, you can start the adapter in the following two ways:

• Starting the Adapter with the Adapter Tester, page 9

• Starting the Adapter from the Command line with a Repository File, page 9

Starting the Adapter with the Adapter TesterTo start the adapter with the Adapter Tester, the adapter and TIBCO Designer must be installed on the same machine.

1. Start TIBCO Designer.

2. Select Tools > Show Adapter Tester on the Menu.

3. In the left pane, select the adapter instance that you want to start.

4. Click the Run Settings tab. In the Working Directory field, enter a directory to place running files.

5. In the Adapter Executable field, select the executable.

6. Click the Apply button.

7. Click the Start button. To view the output messages, click the Console tab.

Starting the Adapter from the Command line with a Repository FileTo start the adapter from the command line with a repository file, the project must be run as a local repository and saved in DAT (repository) format. See the TIBCO Designer documentation for more information about repository files.

Task A Convert the Project to a Repository File

To export the project to a local repository:

1. Start TIBCO Designer.

2. Select Project > Export Full Project... on the Menu. The Export Project dialog appears.

3. Click the Local Repository tab and enter the project name and the output directory in the Export Project dialog. Click the OK button.

4. In the Create Project dialog, select File Type and TIBCO Messaging Encoding. Click the Yes button.



Task B Start the Adapter

The adapter can be run by specifying the path of the DAT file in the repo URL, in the properties file or TIBCO Runtime Agent.

1. At the command prompt, go to the ADJDEXE_HOME\bin directory, which hosts the adapter executable.

2. Enter the following command to start the adapter:

adjdexe.exe -system:repourl repository_file_url -system:configurl configuration_url


| 11

Chapter 3 Adapter Instance Options

This chapter explains how to design an adapter instance in TIBCO Designer. For detailed information about creating an adapter instance, see Create an Adapter Instance on page 6.

Topics

• Configuration Tab, page 12

• Design-time Connection Tab, page 14

• Runtime Connection Tab, page 16

• General Tab, page 18

• Multithreading Tab, page 19

• Logging Tab, page 20

• Startup Tab, page 23

• Monitoring Tab, page 24

The jdeinterop INI file must be configured on the adapter machine prior to using the adapter. See Configuring the INI File on page 3 for more details.


12 | Chapter 3 Adapter Instance Options

Configuration Tab

The Configuration tab contains the fields shown in Table 3.

Guidelines for Choosing an Instance Name

• An instance name must use alphanumeric characters. An underscore (_) character can be used. The entire instance name must be less than 80 characters. The space character cannot be used in an instance name.

• An instance name cannot use global variables.

• An instance name must be unique with respect to other adapter instances for the same adapter in the project. The same instance name can be used to name an adapter instance for a different adapter in the same project. For example, a JDE adapter instance named TEST and a Siebel adapter instance named TEST can coexist in the same project.

Table 3 Adapter Instance: Configuration Tab

Field Description

Instance Name The name of the adapter instance. Use the default name or replace it with a name of your choice.

See Guidelines for Choosing an Instance Name, page 12 for more information.

Description (Optional) A short description of the adapter instance.

Version The version string indicates the ActiveEnterprise (AE) format in which the adapter instance is saved. When a new adapter instance is created in TIBCO Designer 5.x, the version string is set to AE Version 5.1. When a 4.x adapter instance is opened in Designer 5.x, the Version field is set to AE Version 4.0.

To change versions, click the Change Version... button. An adapter instance can be saved in AE 4.0 or AE 5.1 format.

Message Filter Specify a message filter, if you have configured a message filter resource for use with the adapter. The filter allows you to manipulate incoming and outgoing data before sending it on the network or handing it to the target application. Filters can be written using the TIBCO Adapter SDK. See TIBCO Adapter SDK Programmer’s Guide for information about writing a message filter.

Show All Tabs Select this checkbox to display the Multithreading tab and General tab for advanced configurations.


Configuration Tab | 13

• Each instance name must be unique per adapter within a project even if each instance is defined in a different folder. That is, configuring same-named adapter instances in different folders will not make their names unique.

When you create an adapter instance, the palette automatically creates several resources for it. The names of these resources derive from the name of the instance they belong to. Changing the adapter instance name results in an automatic regeneration of the resources names. If you manually modify any resource name, that particular name will not be automatically regenerated next time your rename the adapter instance.



Design-time Connection Tab

Many of the following fields, listed in Table 4, make use of global variables. Click the Global Variables tab in the Project panel to enter value for a global variable.

When specifying connection parameters for the adapter, ensure that the adapter connects to the JD Edwards EnterpriseOne enterprise server and NOT the deployment server.

Table 4 Adapter Instance: Design-time Configuration Tab

Field Description

Server Name The host name or the IP address of the machine that hosts the JDE application server to which the adapter instance is connecting.

Port Number The port number that is used for connection between JD Edwards EnterpriseOne and TIBCO Adapter for JDE.

Environment The environment name in JD Edwards EnterpriseOne that is used by the adapter instance.

Note: The environment name must start with letter J, such as JDV900.

Username The username that is used by the adapter to connect to the JD Edwards EnterpriseOne.

Password The password for account used by the adapter to connect to JD Edwards EnterpriseOne.

Remember Password

If not checked (by default), the password must be entered each time the project is opened.

If checked, the password will be stored in the project repository.

Configuration File The INI file that is used to connect to the specified JDE enterprise server.

See Configuring the INI File on page 3 for more details about configuring the INI file.

Use Design-time Connection for Runtime

If checked (by default), this connection will be used at runtime.

If not checked, you need to specify runtime connection parameters in the Runtime Connection tab.


Design-time Connection Tab | 15

After configuring the design-time connection parameters, click the Test Connection... button to test whether the specified configuration fields result in a valid connection to JD Edwards EnterpriseOne enterprise server.



Runtime Connection Tab

If the Use Design-time Connection for Runtime checkbox is checked in the Design-time Connection tab, some of the options in the Runtime Connection tab inherit values set in the Design-time Connection tab and cannot be changed in the Runtime Connection tab.

The fields that are specific to the Runtime Connection tab are displayed in Table 5.

Table 5 Adapter Instance: Runtime Connection Tab

Field Description

Initial Number of Connections The number of connections that should be made to the adapter when the adapter starts up.

Maximum Number of Connections The maximum number of connection that can be made to the adapter.

Connection Idle Time (milliseconds)

The time defined in milliseconds for which a connection is allowed to be idle.

Maximum Number of Reconnect Attempts

The total number of reconnection attempts to make before the runtime adapter or adapter service is stopped.

A value of -1 means reconnection attempts will continue indefinitely.

Number of Reconnect Attempts Before Suspending Impacted Services

The number of reconnection attempts to make before suspending a runtime adapter or an adapter service. The value of Adapter Termination Criteria field determines whether the adapter or the adapter service is stopped.

Interval Between Reconnect Attempts (milliseconds)

The time interval, in milliseconds, to elapse between each connection attempt.


Runtime Connection Tab | 17

Adapter Termination Criteria (after max number of reconnect attempts)

If your adapter supports only a single connection to a vendor application or database, either choice results in the same behavior. The adapter stops if the service loses its connection.

If your adapter supports multiple connections, select from the drop-down list:

• When Any Service is Suspended stops the adapter if any one service has been unable to re-establish connection after the specified reconnection attempts.

• When All Services Are Suspended stops the adapter only when all services have been suspended. That is, only the adapter service that cannot reconnect is stopped. Other adapter services that are connected continue to function normally.

Table 5 Adapter Instance: Runtime Connection Tab (Cont’d)

Field Description



General Tab

The General tab is available only when the Show All Tabs checkbox is checked in the Configuration tab.

The General tab contains the fields shown in Table 6.

Table 6 Adapter Instance: General Tab

Field Description

Termination Subject or Topic

A message sent on the termination subject (if Rendezvous is the transport) or topic (if JMS is the transport) stops the adapter. In most cases, you should use the default value.

See TIBCO Rendezvous Concepts for information about specifying subject names. See TIBCO Enterprise Message Service User’s Guide for information about publishing on a topic.

Transport Type Specifies a transport for the subject sent. Two options are available: JMS and Rendezvous.


Multithreading Tab | 19

Multithreading Tab

The Multithreading tab is available only when the Show All Tabs checkbox is checked in the Configuration tab.

The Multithreading tab contains the field shown in Table 7.

Table 7 Adapter Instance: Multithreading Tab

Field Description

Inbound Thread Count The JDEInboundThreadCount global variable is used to specify the number of inbound threads that the application has at runtime. Refer to Using Global Variables on page 94 for more information.

If no inbound services are configured, that is, no Subscription Service or Request-Response Service is configured; the value of this field is ignored.



Logging Tab

The Logging tab specifies the output destination (sinks) for the trace messages and sets the tracing level for the roles selected.

Table 8 Adapter Instance: Logging Tab

Field Description

Use Advanced Logging

If the checkbox is not checked (by default), you can set two standard output destinations (sinks) for trace messages and set the tracing level for the roles selected.

If the checkbox is checked, you have complete control on selecting the destinations and associating desired roles with each of the destinations.

To create and configure sinks, refer to Guideline for Creating and Configuring the Sinks on page 21.

Log to Standard I/O (STDIO Sink) If the checkbox is checked, trace messages are displayed in the command prompt window where the adapter is started. If the checkbox is not checked, trace messages do not display in the window.

Log File Specify the name of the log file (log sink) to which trace messages are written. Global variables can be used to specify the location of the log file. Refer to Using Global Variables on page 94 for more information.

The roles available are Info, Debug, Warning, and Error messages. The trace message generated depends on the roles selected. Turning on the roles can affect the performance of the adapter. Therefore, it is recommended that you turn on the required roles only.


Logging Tab | 21

Guideline for Creating and Configuring the Sinks

To create and configure the sinks, follow these steps:

1. Check the Use Advanced Logging checkbox in the Logging Tab.

2. Expand ProjectName > JDEAdapterConfiguration > Advanced > Log Sinks in the Project Panel.

3. Drag the Generic Log Sink icon from the Palettes panel to the Design panel, and then select a Sink Type in the Configuration tab. Click the Apply button. For detailed information about Sink Types, refer to Sink Types.

4. For all the sinks, optionally the name and description can be provided.

5. Select a sink displayed in the Design Panel and configure it in the Configuration Panel. There are two predefined sinks in the adapter instance, fileSink and stdioSink.

Sink Types

Four sink types available: File, Hawk, Network, and STDIO. Each of them has certain configuration options:

• For the File sink, the file limit, file count, and the option to append or overwrite can be specified. When created by default, this is set to 30000 bytes, 3 and append mode respectively.

Log Info Messages The roles available are Info, Debug, Warning, and Error messages. The trace message generated depends on the roles selected. Turning on the roles can affect the performance of the adapter. Therefore, it is recommended that you turn on the required roles only.

Trace messages of the selected level(s) will be collected in the named log sink. You can configure what levels of trace messages you want logged, and where trace messages are sent. There are three types of logs (log sinks) that you can configure to hold trace messages, corresponding to three levels (roles) of trace messages, Information, Warning and Error. A fourth level of trace messages, Debug, is reserved and should not be enabled unless requested by the TIBCO Product Support Group. This option writes a lot of information to the log file and significantly reduces the speed of the adapter.

Users can set up log levels for the debug messages, see Setting Up Debug Log Level on page 102 for more details.

Log Debug Messages

Log Warning Messages

Log Error Messages

Table 8 Adapter Instance: Logging Tab (Cont’d)

Field Description



• For the STDIO sink, the option to write to stdout or stderr can be selected. When created by default, stdout is selected.

• The Hawk sink uses the hawk session, created and used by the adapter for monitoring purposes, to send tracing messages to the TIBCO Hawk monitor or Display.

For details on Hawk sessions, refer to Using Global Variables on page 94 The configuration for the Hawk sink involves specifying the MicroAgent Name that must be specified in the configuration panel.

• The Network sink is used to publish tracing message on TIBCO Rendezvous. The configuration for the network sink involves specifying the session, and the subject on which the trace messages needs to be published.


Startup Tab | 23

Startup Tab

The Startup tab contains the fields shown in Table 9.

Table 9 Adapter Instance: Startup Tab

Field Description

Show Startup Banner

If the checkbox is checked (by default), the startup banner displays the runtime adapter version, the infrastructure version on which the adapter is built, and copyright information in the console window when the adapter is started.

The content of the start banner is predefined and cannot be changed.



Monitoring Tab

The settings available in the Monitoring tab do not need to be configured unless TIBCO Hawk is installed.

You can use microagents to supplement the monitoring information provided by the standard logging capability. Examples of supplemental information that you can obtain with microagents include the repository URL and the command line arguments used to start the adapter.

Many of the fields, listed in Table 10, make use of global variables. Click the Global Variables tab in the project panel to enter a value for a global variable.

For a list of all supported microagents, refer to Available Microagents on page 64.

Table 10 Adapter Instance: Monitoring Tab

Field Description

Enable Standard MicroAgent

Allows you to turn on or off the standard TIBCO Hawk MicroAgent.

Clicking the icon changes the checkbox to a text field. This allows you to specify a global variable. When this is a text field, turn the MicroAgent on and off by entering true or false.

Standard MicroAgent Name

This is the name for the standard MicroAgent that will be registered with the TIBCO Hawk system. In most cases the default value is used, COM.TIBCO.ADAPTER.adjdexe.%%deployment%%.%%InstanceId%%.

The value for the %%deployment%% global variable is the name of the project where the adapter instance is defined. It is set automatically and cannot be modified.

The %%InstanceId%% variable does not need to be set because it is automatically set at run time by the runtime adapter.

Standard MicroAgent Timeout (ms)

Specifies the amount of time that TIBCO Hawk Agent should wait for HMA method invocations to complete before timing them out. The default value is 10000 milliseconds. Normally no need to change this value, however, on machines under extreme stress where method invocations are timing out, this option allows the timeout value to be increased.

Enable Class MicroAgent

Allows you to turn on or off the instance-specific or class-specific standard TIBCO Hawk.

Clicking the icon changes the checkbox to a text field. This allows you to specify a global variable. When this is a text field, turn the MicroAgent on and off by entering true or false.


Monitoring Tab | 25

Class Microagent Name

This is the name for the standard MicroAgent that will be registered with the TIBCO Hawk system. In most cases the default value is used, COM.TIBCO.adjdexe.%%deployment%%.%%InstanceId%%.

The value for the %%deployment%% global variable is the name of the project where the adapter instance is defined. It is set automatically and cannot be modified.

The %%InstanceId%% variable does not need to be set because it is automatically set at run time by the runtime adapter.

Class MicroAgent Timeout (ms)

Specifies the amount of time that TIBCO Hawk Agent should wait for HMA method invocations to complete before timing them out. The default value is 10000 milliseconds. Normally no need to change this value, however, on machines under extreme stress where method invocations are timing out, this option allows the timeout value to be increased.

Default MicroAgent Session

Specify the name of the TIBCO Rendezvous session that will be used by the standard, class, and custom MicroAgents.

The session name and the corresponding session are automatically generated by TIBCO Designer. Do not change the session name or the session. However, you can modify the session parameters if required. Navigate to the Sessions folder under the Advanced folder to modify the session parameters.

Make sure you have set the correct parameter value for the global variables that correspond to the TIBCO Hawk configuration. If the session parameters are not set properly, the microagents will not display in TIBCO Hawk Display.

Table 10 Adapter Instance: Monitoring Tab (Cont’d)

Field Description




| 27

Chapter 4 Adapter Service Options

This chapter explains configuration options of each adapter service. All the configuration tasks are performed in TIBCO Designer and the information is stored in a project that is later used by the runtime adapter.

For detailed information about adding an adapter service, see Creating and Configuring Adapter Services on page 8.

Topics

• Publication Service, page 28

• Subscription Service, page 34

• Request-Response Service, page 42


28 | Chapter 4 Adapter Service Options

Publication Service

When running as a Publication Service, the adapter publishes the real-time events generated by the JD Edwards EnterpriseOne applications to TIBCO ActiveEnterprise applications.

You can configure the parameters for the Publication Service using the following tabs:

• Configuration Tab on page 28

• Transport Tab on page 29

• Real-time Event Tab, page 32

• Schema Tab on page 33

Configuration TabThe Configuration tab contains the fields shown in Table 11.

Table 11 Publication Service: Configuration Tab

Field Description

Name The name of the service.

You can use the default name or replace it with a name of your choice.

• A service name must use alphanumeric characters. An underscore (_) character can be used. The entire instance name must be less than 80 characters. The space character cannot be used in an instance name.

• A service name cannot use global variables.

Description A short description for the Publication Service.


Publication Service | 29

Transport TabThe Transport tab contains the fields shown in Table 12.

Transport Type Select the transport to be used by the runtime adapter, JMS or Rendezvous. After selecting the transport, the transport-specific configuration fields display.

The transport can be configured to use a trusted store and identity resource for use in SSL (Secure Sockets Layer) configurations. TIBCO Rendezvous sessions and JMS topics have an SSL configuration field which uses a dialog to perform SSL configuration.

To enable and configure SSL, in the Project panel, expand the Advanced folder, then expand the Sessions folder. Select the TIBCO Rendezvous session or JMS topic and click Use SSL?. The SSL configuration options are explained in the online help associated with the session dialog. Click the question mark to display the online help.

Table 11 Publication Service: Configuration Tab (Cont’d)

Field Description

Table 12 Publication Service: Transport Tab (Sheet 1 of 3)

Fields Description

The following fields are available when the Rendezvous transport type is selected under the Configuration tab.

Message Subject By default, a service uses a message subject that is generated using the Domain and Deployment global variables, the adapter system, the adapter instance name, and the service name. To use this default subject, ensure that the values for Domain and Deployment are configured.

You can type a TIBCO Rendezvous subject name different from the default in this field. See TIBCO Rendezvous Concepts for more details about specifying subject names.

Quality of Service Two options are available, see Quality of Service Options on page 31 for more details.

Wire Format Three options are available when the Rendezvous transport type is used, see Wire Format Options on page 32.

Note: services must use the same wire format to exchange data.



Session Reference Every adapter instance can have one or more sessions configured for it. Sessions encapsulate stateful connections to TIBCO Rendezvous and other messaging sources. The session object shown in this field is initially supplied by the adapter, depending on the Quality of the Service selected.

Click the button to change the session.

Endpoint Reference You can drag a different endpoint, browse for another endpoint resource, go to the referenced endpoint to edit its properties or delete the endpoint. Endpoint reference objects are explained in TIBCO Designer Palette Reference.

The following fields are available when the JMS transport type is selected under the Configuration tab.

Destination By default, a service uses a dynamic destination that is generated using the Domain and Deployment global variables, the adapter acronym, the adapter instance name, and the service name. If you use the default dynamic destination, ensure that the Domain and Deployment global variables are configured.

You can override the default dynamic destination by specifying the static destination in this field. The static destination must be defined on the JMS server before it can be used by the runtime adapter.

Reply Destination The subject that receives a response from TIBCO ActiveEnterprise Message Service.

Wire Format The XML message wire format conforms to specifically constructed and fully compliant XML Schema (XSD) based on the existing definition of the ActiveEnterprise schema.


Fields Description



Quality of Service Options

when Rendezvous transport type is selected under the Configuration tab, two options are available for the Quality of Service:

• Certified Guarantees that every certified message reaches its intended recipient in the order sent. The message can be sent across network boundaries, and if a network fails, delivery attempts continue until the delivery succeeds or until the limit time of the message expires. This is often called certified message delivery.

If certified message delivery is used, data is stored in a ledger file. The size of the ledger depends on several factors, the most important of which is the retention rate of stored data. That is, the ledger grows fastest in response to the cumulative length of undeliverable messages. Ensure that sufficient disk space is available for the expected size of the ledger.

• Reliable Ensure that each multicast or broadcast message is received as long as the physical network and packet recipients are working, and that the loss of a message is detected. This choice can compensate for brief network failures because it can retransmit a message on request if the first attempt failed. This choice is appropriate when message delivery is expected but some loss can be tolerated.

Connection Factory Type Two options are available:

• Topic A message published to a topic is broadcast to one or more Subscription Services. All messages published to the topic are received by all services that have subscribed to the topic. This messaging model is known as publish-subscribe.

• Queue A message sent to a queue is consumed by one and only one receiver. Each message has only one receiver through multiple receivers may connect to the queue. The first receiver to access the queue gets the message. The other receivers do not. This message is known as point-to-point.

Delivery Mode Two options are available:

• Persistent In general, a message marked persistent will be available to a JMS client even if the JMS server goes down.

• Non Persistent A message marked non persistent will not be available to a JMS client if the JMS server goes down.


Fields Description



Wire Format Options

when Rendezvous transport type is selected under the Configuration tab, three options are available:

• Rendezvous Message Control information for validation is not sent in the message. If you use this format, the adapter is compatible with adapters not developed with TIBCO Adapter SDK.

• XML Message The XML message wire format conforms to specifically constructed and fully compliant XML Schema (XSD) based on the existing definition of the ActiveEnterprise schema.

• ActiveEnterprise Message Control information for validation is sent in the message. If no control information is included, an exception is returned to the Subscription Service. ActiveEnterprise standard wire format provides class information and packing rules for the TIBCO Adapter SDK set of data types. This format allows ActiveEnterprise components to perform extra validation on messages sent or received.

See the TIBCO Adapter SDK Programer’s Guide for details about control information generated and sent with ActiveEnterprise messages.

Real-time Event TabThe Real-time Event Tab allows you to specify which real-time events to be published by the adapter. The real-time events are retrieved from the JD Edwards EnterpriseOne system.

Click the button to select one or more real-time events from the drop-down list and click the button to delete the selected real-time event.

A real-time event can be configured as described in Table 13.

Table 13 Publication Service: Real-time Event Tab

Columns Description

Event, Data Structure and Attributes

Displays the name of the real-time event.

Each real-time event has one or more data structures associated with it. The data structure defines and groups attributes for the event. You can expand the real-time event to view the data structure.



Schema TabThe Schema tab contains the fields shown in Table 14.

Use Looping? Check the Use Looping? checkbox to indicate that the data structure occurs multiple times in a real-time event.

A data structure may have multiple occurrences when the business transaction is published in real-time events. For example, in a sales order real-time event, the data structure for sales order lines will occur as long as a sales order is added. In such cases, the Use Looping? checkbox should be checked for the sales order lines data structure.

Use Attribute? Indicates whether the attribute in a data structure is used as an output attribute.

If the Use Attribute? checkbox is checked, the attribute will be the output in the ActiveEnterprise message published by the adapter.

Attribute Wanted

Displays the name of the attribute if the Use Attribute? checkbox is checked. If the Use Attribute? checkbox is not selected for an attribute, the value in this column will be blank for that attribute.

Table 13 Publication Service: Real-time Event Tab (Cont’d)

Columns Description

Table 14 Publication Service: Schema Tab

Field Description

Class Reference The class reference for a service is set automatically.

Before a schema is applied to the service, select Project > Validate Project For Deployment... from the menu bar to validate your configurations.

Once the schema has been specified for a service, you can view its attributes by selecting the AESchemas folder in the Project panel. For more detailed information about schema, see the TIBCO Designer User’s Guide.



Subscription Service

When running as a Subscription Service, the adapter gets the message from the TIBCO environment and sends it to the JD Edwards EnterpriseOne application by invoking a Business Function. No response is returned by a Subscription Service.

You can configure the parameters for the Subscription Service using the following tabs:


• Transport Tab, page 35

• Business Functions Tab, page 38

• Schema Tab, page 41


Table 15 Subscription Service: Configuration Tab

Field Description





Description A short description for the Subscription Service.


Subscription Service | 35





Table 15 Subscription Service: Configuration Tab (Cont’d)

Field Description

Table 16 Subscription Service: Transport Tab (Sheet 1 of 3)

Fields Description

The following fields are available when the Rendezvous transport type is selected in the Configuration tab.

Message Subject By default, a service uses a message subject that is generated using the Domain and Deployment global variables, the adapter system, the adapter instance name, and the service name. To use this default subject, ensure that the values for Domain and Deployment are not empty.


Quality of Service Three options are available. See Quality of Service Options on page 37 for more details.

Wire Format Three options are available. See Wire Format Options on page 38 for more details.

Note: Services must use the same wire format to exchange data.






The following fields are available when the JMS transport type is selected in the Configuration tab.






• Queue A message sent to a queue is consumed by one and only one receiver. Each message has only one receiver through multiple receivers may connect to the queue. The first receiver to access the queue gets the message. The other receivers do not. This message is known as point-to-point

Table 16 Subscription Service: Transport Tab (Cont’d) (Sheet 2 of 3)

Fields Description




when Rendezvous transport type is selected under the Configuration tab, three options are available for the Quality of Service:



• Reliable Ensure that each multicast or broadcast message is received as long as the physical network and packet recipients are working, and that the loss of a message is detected. This choice can compensate for brief network failures because it can retransmit a message on request if the first attempt failed. This choice is appropriate when message delivery is expected but some loss can be tolerated.

• Distributed Queue Distributed queue includes a group of cooperating transport objects, each in a separate process. Each transport object is called member. To balance the transmission load among servers, the adapter can use distributed queues for one-of-n delivery messages to a group of servers. Each member of a distributed queue listens for the same object using the TIBCO Rendezvous Distributed Queue listener objects. Even though many members listen for each inbound message (or task), only one member processes the message. For details on distributed queues, see TIBCO Rendezvous Concepts.

Load balancing for the processing of TIBCO Rendezvous certified messages is supported by using distributed queuing. The messages from TIBCO


• Non-Durable If a Subscription Service is marked non-durable, it indicates that messages will not be resent on the configured topic or queue if the JMS server goes down.

• Durable If a Subscription Service is marked durable, it indicates that messages need to be resent on the configured topic or queue if the JMS server goes down.

Table 16 Subscription Service: Transport Tab (Cont’d) (Sheet 3 of 3)

Fields Description



Rendezvous are distributed equally among all instances that belong to the same group. This distributes load over several adapter instances. However, the order in which messages are sent to the application is not guaranteed.

Wire Format Options

when Rendezvous transport type is selected under the Configuration tab, three options are available:

• Rendezvous Message Control information for validation is not sent in the message. If you use this format, the adapter is compatible with adapters not developed with TIBCO Adapter SDK.

• XML Message The XML message wire format conforms to specifically constructed and fully compliant XML Schema (XSD) based on the existing definition of the ActiveEnterprise schema.

• ActiveEnterprise Message Control information for validation is sent in the message. If no control information is included, an exception is returned to the Subscription Service. ActiveEnterprise standard wire format provides class information and packing rules for the TIBCO Adapter SDK set of data types. This format allows ActiveEnterprise components to perform extra validation on messages sent or received.

See the TIBCO Adapter SDK Programer’s Guide for details about control information generated and sent with ActiveEnterprise messages.

Business Functions TabThe adapter can invoke a business function or a business function group when running as the Subscription Service to handle the incoming request.

Select a category for the service from the drop-down list in the Business Function tab. Two options available for the Subscription Service:

• Business Function Business functions are executable functions that can be used in any application in the JD Edwards EnterpriseOne system.

If the BusinessFunction option is selected, click the button to add one or more business functions from the Select a Business Function dialog displayed. The available business functions are retrieved from all the business functions

By default, the XMLCallObject method is used to execute business functions.

See Disabling XMLCallObject to disable the CallXMLObject method if you want to execute the business functions one by one.



deployed on the JD Edwards EnterpriseOne server, which are displayed in alphabetical order.

• Business Function Group A business function group is a group of business functions that are executed together, which is created in the Business Functions tab. See Invoking a Business Function Group on page 40 for more details.

Configure a business function as described in Table 17.

Table 17 Subscription Service: Business Function Tab

Columns Description

Business Functions

Displays the name of the business function or business function group to be invoked.

Each business function has a data structure associated with it. Each data structure defines the input or the output attributes for the business function. You can expand each business function to view the data structure.

Use Attribute? Indicates whether the attribute in a data structure is used as an input attribute.

If the checkbox Use Attribute? is checked, the attribute will be used as an input parameter for the business function and will be available in the ActiveEnterprise message schema used by the adapter.

Attribute Wanted

Displays the name of the attribute if the Use Attribute? checkbox is selected. If the Use Attribute? checkbox is not selected for an attribute, the value in this column will be blank for that attribute.

The following columns are available only when the BusinessFunctionGroup option is selected as the category.

Use Looping? Check the Use Looping? checkbox to indicate that the business function is called multiple times in a business function group.

A business function can be invoked multiple times in a business function group. For example, in a sales order creation function, the business function for creating sales order lines will be called as long as a sales order is created. In such cases, the Use Looping? checkbox should be checked for creating sales order lines business function.

Use Bind? The adapter supports passing values of output parameters of any business function to subsequent business functions as the input.

Checking the Use Bind? checkbox to indicate that the value of the output parameter in that business function will be used as the input parameter of the subsequent business functions.



Invoking a Business Function Group

To invoke a business function group, complete the following steps:

1. Select the BusinessFunctionGroup option from the drop-down list in the Business Functions tab.

2. Enter a name in the Group Name field for the business function group.

3. Click the button next to the Group Name field to add business functions to the group. The Select a Business Function dialog is displayed.

4. Select one or more business functions, and then click the OK button to add the selected business functions. The business functions are displayed in alphabetical order. Enter a letter in the Filter field to search desired business functions.

5. Refer to Table 17 to configure the business functions added in the group. Use the button and the button to arrange the order of each business function in the group.

Disabling XMLCallObject

To disable the CallXMLObject method, complete the following steps:

1. Navigate to the ADJDEXE_HOME\bin directory and locate the adjdexe.tra file.

2. Open the adjdexe.tra file.

3. Find the UseCallXMLObject parameter, and then set the value of this parameter to false.

4. Save the file.

Bind Identifier If a parameter in a business function inherits the value from a parameter in a preceding business function, specify the value of which Bind parameter is used from the drop-down list.

All the parameters with the Use Bind? checkbox checked in a preceding business function are displayed in the drop-down list.

Table 17 Subscription Service: Business Function Tab (Cont’d)

Columns Description



Schema Tab The Schema tab contains the fields shown in Table 18.

Table 18 Subscription Service: Schema Tab

Field Description






Request-Response Service

When running as a Request-Response Service, the adapter receives request messages from TIBCO ActiveEnterprise clients and converts the messages to make a Business Function invocation or an XML Query List invocation in the JD Edwards EnterpriseOne system. The results of invocation will be returned.

You can configure the parameters for the Request-Response Service using the following tabs:


• Transport Tab, page 43

• Business Functions Tab, page 46

• Schema Tab, page 49


Table 19 Request-Response Service: Configuration Tab

Field Description





Description A short description for the Request-Response Service.


Request-Response Service | 43





Table 19 Request-Response Service: Configuration Tab (Cont’d)

Field Description

Table 20 Request-Response Service: Transport Tab (Sheet 1 of 3)

Fields Description

The following fields are available when the Rendezvous transport type is selected in the Configuration tab.

Message Subject By default, a service uses a message subject that is generated using the Domain and Deployment global variables, the adapter system, the adapter instance name, and the service name. To use this default subject, ensure that the values for Domain and Deployment are not empty.


Quality of Service Three options are available. See Quality of Service Options on page 45 for more details.



Wire Format The control information for validation is sent in the message when The ActiveEnterpriseMessage wire format is used. If no control information is included, an exception is returned to the Subscription Service. ActiveEnterprise standard wire format provides class information and packing rules for the TIBCO Adapter SDK set of data types. This format allows ActiveEnterprise components to perform extra validation on messages sent or received.

See the TIBCO Adapter SDK Programer’s Guide for details about control information generated and sent with ActiveEnterprise messages




The following fields are available when the JMS transport type is selected in the Configuration tab.




Table 20 Request-Response Service: Transport Tab (Cont’d) (Sheet 2 of 3)

Fields Description




when Rendezvous transport type is selected under the Configuration tab, three options are available for the Quality of Service:



• Reliable Ensure that each multicast or broadcast message is received as long as the physical network and packet recipients are working, and that the loss of a message is detected. This choice can compensate for brief network failures because it can retransmit a message on request if the first attempt failed. This



• Queue A message sent to a queue is consumed by one and only one receiver. Each message has only one receiver through multiple receivers may connect to the queue. The first receiver to access the queue gets the message. The other receivers do not. This message is known as point-to-point


• Non-Durable If a Subscription Service is marked non-durable, it indicates that messages will not be resent on the configured topic or queue if the JMS server goes down.

• Durable If a Subscription Service is marked durable, it indicates that messages need to be resent on the configured topic or queue if the JMS server goes down.

Table 20 Request-Response Service: Transport Tab (Cont’d) (Sheet 3 of 3)

Fields Description



choice is appropriate when message delivery is expected but some loss can be tolerated.

• Distributed Queue Distributed queue includes a group of cooperating transport objects, each in a separate process. Each transport object is called member. To balance the transmission load among servers, the adapter can use distributed queues for one-of-n delivery messages to a group of servers. Each member of a distributed queue listens for the same object using the TIBCO Rendezvous Distributed Queue listener objects. Even though many members listen for each inbound message (or task), only one member processes the message. For details on distributed queues, see TIBCO Rendezvous Concepts.

Load balancing for the processing of TIBCO Rendezvous certified messages is supported by using distributed queuing. The messages from TIBCO Rendezvous are distributed equally among all instances that belong to the same group. This distributes load over several adapter instances. However, the order in which messages are sent to the application is not guaranteed.

Business Functions TabThe adapter can invoke a business function, a business function group, or an XML query list when running as the Request-Response Service.

Select a category from the drop-down list in the Business Function tab. Three are options available for the Request-Response Service:

• Business Function Business functions are executable functions that can be used in any application in the JD Edwards EnterpriseOne system.

If the BusinessFunction option is selected, click the button to add one or more business functions from the Select a Business Function dialog displayed. The available business functions are retrieved from all the business functions deployed on the JD Edwards EnterpriseOne server, which are displayed in alphabetical order.

• Business Function Group A business function group is a group of business functions that are executed together, which can be created under the Business Functions tab.

If the BusinessFunctionGroup option is selected, see Invoking a Business Function Group on page 48 for more details.

By default, the XMLCallObject method is used to execute business functions.

See Disabling XMLCallObject to disable the CallXMLObject method if you want to execute the business functions one by one.



• XML Query List The XML tables that exist in the JD Edwards EnterpriseOne system can be queried by the adapter. The data in the XML tables may or may not correspond to a given business function.

If the XMLQueryList option is selected, see Invoking XML Query List on page 49 for more details.

Configure a business function or the XML table as described in Table 21.

Table 21 Request-Response Service: Business Function Tab

Columns Description

Business Function

Displays the name of a business function, a business function group, or an XML table to be invoked.

Each business function or XML table as a data structures associated with it. Each data structure defines the input or the output attributes for the business function. You can expand each business function to view the data structure.

Use Attribute? Indicates whether the attribute in a data structure is used as an input attribute.

If the checkbox Use Attribute? is checked, the attribute will be used as an input parameter for the business function and will be available in the ActiveEnterprise message schema used by the adapter.

Attribute Wanted

Displays the name of the attribute if the Use Attribute? checkbox is selected. If the Use Attribute? checkbox is not selected for an attribute, the value in this column will be blank for that attribute.

The following columns are available only when the BusinessFunctionGroup option is selected as the category.

Use Looping? Check the Use Looping? checkbox to indicate that a business function is called multiple times in a business function group.

A business function can be invoked multiple times in a business function group. For example, in a sales order creation function, the business function for creating sales order lines will be called as long as a sales order is created. In such cases, the Use Looping? checkbox should be checked for creating sales order lines business function.

Use Bind? The adapter supports passing values of output parameters of any business function to subsequent business functions as the input.

Checking the Use Bind? checkbox to indicate that the value of the output parameter in that business function will be used as the input parameter of the subsequent business functions.



Invoking a Business Function Group

To invoke a business function group, complete the following steps:

1. Select the BusinessFunctionGroup option from the drop-down list in the Business Functions tab.

2. Enter a name in the Group Name field for the business function group.

3. Click the button next to the Group Name field to add business functions to the group. The Select a Business Function dialog is displayed.

4. Select one or more business functions, and then click the OK button to add the selected business functions. The business functions are displayed in the alphabetical order. Enter a letter in the Filter field to search desired business functions.

5. Refer to Table 21 to configure the business functions added in the group. Use the button and the button to arrange the order of each business function in the group.

Disabling XMLCallObject

To disable the CallXMLObject method, complete the following steps:



3. Find the UseCallXMLObject parameter, and then set the value of this parameter to false.

4. Save the file.

Bind Identifier If a parameter in a business function inherits the value from a parameter in a preceding business function, specify the value of which Bind parameter is used from the drop-down list.

All the parameters with the Use Bind? checkbox checked in a preceding business function are displayed in the drop-down list.

Table 21 Request-Response Service: Business Function Tab (Cont’d)

Columns Description



Invoking XML Query List

To invoke an XML query list, complete the following steps:

1. Select the XMLQueryList item from the drop-down list in the Business Functions tab.

2. Select a Query Type from the drop-down list. Three operations are available:

— ListCreate—Creates a list in the specified table, view or TC.

— ListRetrieve—Gets a list from the specified table, view or TC.

— ListDelete—Deletes a list from the specified table, view or TC.

3. Specify where the selected operation will be performed by clicking the corresponding radio button. Three options are available: Table, View or TC.

4. Click the button to select a table or a view from the Select a Table or View dialog displayed.

5. Refer to Table 21 to configure the attributes for the XML list.

Schema TabThe Schema tab contains the fields shown in Table 22.

Table 22 Request-Response Service: Schema Tab

Field Description







| 51

Chapter 5 Deploying and Starting an Adapter Using TIBCO Administrator

This chapter provides an overview about deploying, starting, stopping, and monitoring adapter services using the TIBCO Administrator web interface.

Topics

• Creating an EAR File in TIBCO Designer, page 52

• Deploying the Project, page 53

• Starting or Stopping the Adapter, page 54

• Monitoring the Adapter, page 55


52 | Chapter 5 Deploying and Starting an Adapter Using TIBCO Administrator

Creating an EAR File in TIBCO Designer

Generate an Enterprise Archive file (EAR) that contains information about the adapter services to deploy.

The EAR file contains information on what you wish to deploy. This could be one or more adapter services, one or more TIBCO BusinessWorks process engines, or both.

In TIBCO Designer, follow these steps to create an EAR:

1. Configure the adapter services.

2. Select the adapter project in the Project panel.

3. Drag the Enterprise Archive resource from the Palettes panel to the Design panel and then specify a name and a location for the Enterprise Archive file in the Configuration panel.

4. Select the Enterprise Archive project you have created in the Project panel.

5. Drag the Adapter Archive resource from the Palettes panel to the Design panel and then configure the Adapter Archive in the Configuration panel.

6. Select the Enterprise Archive project in the project panel and then click the Build Archive button in the Configuration panel.

See Also

See TIBCO Designer User’s Guide for more information about this procedure. The guide is available from the Designer Help menu.

Building an archive creates the EAR file, which you can then deploy from TIBCO Administrator. If you make changes to the business processes or adapter services included in the archive, you need to rebuild the archive. Saving the project does not affect the archive.


Deploying the Project | 53

Deploying the Project

Before deploying a project, the machine on which the adapter is installed must be part of a TIBCO administration domain. After you have installed the TIBCO Administration Server, any machine on which you install TIBCO Runtime Agent (required by an adapter) can be added to the administration domain. The TIBCO software installed on the machine is then visible and accessible via the TIBCO Administrator GUI.

When you deploy a project, startup scripts and other information about the different components are sent to the machines to which the components were assigned. The project data store and TIBCO Administration Server are updated with the deployed components.

To deploy a project:

1. Import the EAR file into TIBCO Administrator.

2. Assign adapter archives in the EAR file to adapters installed in the administration domain and likewise assign process archives to process engines.

3. Specify startup options for each adapter service.

See Also

See TIBCO Administrator User’s Guide for an introduction to the TIBCO administration domain and detailed information about the above steps.

See TIBCO Administrator Server Configuration Guide for fault tolerance information.



Starting or Stopping the Adapter

The TIBCO Administrator Application Management module allows you to start, and stop deployed applications.

To start an adapter service from the module:

1. In the Administrator GUI left pane, expand Application Management > Application-Name > Service Instances.

2. In the Service Instance panel, select the checkbox next to the adapter service.

3. Click the Start Selected button.

The status changes from Stopped to Starting up to Started.

4. To stop the adapter service, click the Stop Selected button.

See Also

See TIBCO Administrator User’s Guide for more information.


Monitoring the Adapter | 55

Monitoring the Adapter

TIBCO Administrator offers a number of monitoring options:

• Specify alerts and TIBCO Hawk rulebases for each machine in the domain.

• Specify alerts and Hawk rulebases for each adapter service.

• View the log for each adapter service.

See Also

See TIBCO Administrator User’s Guide for information about configuring the above monitoring options.




| 57

Chapter 6 Monitoring the Adapter Using TIBCO Hawk

This chapter explains how to use TIBCO Hawk microagents to monitor and manage the adapter.

Topics

• Monitoring the Adapter, page 55

• Overview of TIBCO Hawk, page 58

• Starting TIBCO Hawk Software, page 59

• The Auto-Discovery Process, page 60

• Invoking Microagent Methods, page 61

• Available Microagents, page 64


58 | Chapter 6 Monitoring the Adapter Using TIBCO Hawk

Overview of TIBCO Hawk

TIBCO Hawk is a sophisticated tool for enterprise-wide monitoring and managing of all distributed applications and systems. System administrators can use it to monitor adapters in a wide area network of any size. TIBCO Hawk can be configured to monitor system and adapter parameters and to take actions when predefined conditions occur. These actions include: sending alarms that are graphically displayed in the TIBCO Hawk display, sending email, paging, running executables, or modifying the behavior of a managed adapter.

Unlike other monitoring applications, TIBCO Hawk relies on a purely distributed intelligent agent architecture using publish or subscribe to distribute alerts. TIBCO Hawk uses TIBCO Rendezvous for all messaging and thus gains the benefits and scalability from the TIBCO Rendezvous features of publish/subscribe, subject name addressing, interest-based routing, and reliable multicast.

TIBCO Hawk is a purely event-based system that uses alerts. The agents are configured with rules that instruct them on everything from what and how to monitor to what actions to take when problems are discovered. Thus the workload is fully distributed throughout the enterprise. Every agent is autonomous in that it does not depend on other components to perform its functions.

The TIBCO Hawk Enterprise Monitor consists of these components:

• Display—GUI front end that displays alarms and provides editors to create rule bases, create tests, view messages, and invoke microagents to request information or initiate an action.

• Agents—Intelligent processes that perform monitoring and take actions as defined in rules.

• Rulebases—Rules that are loaded by agents to determine agent behavior.

• Application Management Interface (AMI)—Manages network applications via TIBCO Rendezvous and supports communication between a network application and monitoring TIBCO Hawk agents, including the ability to examine application variables, invoke methods, and monitor system performance.

• Microagents—Feed information back to TIBCO Hawk and expose action methods to rulebases.

For more information, see the TIBCO Hawk documentation.


Starting TIBCO Hawk Software | 59

Starting TIBCO Hawk Software

The TIBCO Hawk agent can be configured to start automatically during the system boot cycle. See the TIBCO Hawk Installation and Configuration guide for information about starting TIBCO Hawk.

The TIBCO Hawk Administrator’s Guide explains how to start the TIBCO Hawk Display.

The guides are included in your TIBCO Hawk software installation area.



The Auto-Discovery Process

After you start an instance of TIBCO Hawk Display, it continually discovers machines running TIBCO Hawk Agents on your network. Container icons are created for each agent, and arranged hierarchically in clusters. By default, agent icons are clustered according to subnets.

At first, the Agents container is empty. Its counter displays a value of zero and, on the right, the Discovered counter is also at zero. Both icons are initially green in color to show that no alerts, or warning messages, are in effect. As agents are discovered, the counters increment to reflect the current number of discovered agents:

Monitored network nodes are arranged in a hierarchical tree of containers. Clicking a container in the left panel displays nested items on the right.

Icon colors change to reflect the highest level of alert found on discovered agents. For explanations of icon elements and characteristics, see your TIBCO Hawk Administrator’s Guide.


Invoking Microagent Methods | 61

Invoking Microagent Methods

A set of default microagents is loaded when a TIBCO Hawk Agent is started. When you install and start the adapter, its microagents are dynamically added to the local agent.

To invoke a microagent method:

1. Start TIBCO Hawk Display, then right-click on the agent icon and select Get Microagents.

If TIBCO Hawk security is implemented on your system and you do not have access to microagents on this agent, an error dialog displays. Select another agent, or contact your system administrator to obtain access.

The Microagents, Methods and Arguments dialog displays. The panel on the upper left lists microagents you can access on the current agent.

Figure 2 Microagents, Methods and Argument Dialog

This dialog has two modes, Invoke and Subscribe. Invoking a method immediately returns a single set of current results. Subscribing provides updates of current results at regular intervals. Radio buttons at the bottom of the dialog control these modes.

2. Click a microagent name, such as Self, to display a list of associated methods and text descriptions in the panels below.



3. Click the name of the method to invoke, such as getComponentInfo.

Figure 3 Displaying a Method

If the method accepts arguments, fields for each argument display in the upper right panel. Detailed help text displays in the lower panel.

4. Specify any arguments for the method invocation.

5. Verify that the Invoke radio button is selected.

6. Click the Invoke button to invoke the selected method.

The Invocation Results dialog displays the results returned by the method.


Invoking Microagent Methods | 63

Figure 4 Invocation Results Dialog

7. Click Done to close the dialog.

These steps describe how to interactively invoke a microagent method and receive a single set of results in TIBCO Hawk Display. You can also use a microagent method as the data source of a TIBCO Hawk rule. Rules automatically receive method results, apply tests to evaluate them, then take action if necessary. For more information on building TIBCO Hawk rules and rule bases, see your TIBCO Hawk Administrator’s Guide.



Available Microagents

Each adapter has two microagents, a standard TIBCO Hawk microagent named COM.TIBCO.ADAPTER.xyz where xyz is the adapter configuration name and a custom microagent. The microagents provide:

• Business level statistics—statistics that report the progress of the adapter as it interacts with the vendor application. For example, in a database adapter such statistics might indicate whether objects were successfully or unsuccessfully inserted, updated, or deleted in the database.

• Queries that return information about the state of the adapter. This can be an important tool for seeing the internals of an adapter and debugging it if something appears wrong. For example, methods can return information about threads, internal queues, or connections to the target system. Using these methods, one might be able to identify certain bottlenecks or gauge how successfully an adapter is scaling with respect to the current environment.

• Updates of the adapter runtime parameters. This includes retrieving the current runtime parameters and setting new runtime parameters without restarting the adapter. An example of this is getting and setting the polling interval. Updating a runtime parameter through the Hawk microagent only affects the setting of the instance that is running. It does not make a permanent change of the setting in either the repository or the .tra file.

By default both the standard and custom microagents are available at runtime. You can disallow adding custom methods to the standard microagent when deploying the adapter by changing the addCustomHawkMethodstoStdMAgent property value in the adapter’s property file.

Table 23 lists each method available for the adapter and page on which the method is explained.

Table 23 Microagent Methods (Sheet 1 of 3)

Method Description

activateTraceRole() Activates a mapping of a role to a sink at runtime.

deactivateTraceRole() Deactivates a mapping of a roles to sinks at runtime.

getAdapterServiceInformation()

Returns information about the services implemented by this adapter.


Available Microagents | 65

getComponents() Returns information about the publisher, subscriber and IODescriptor.

getConfig() Returns basic configuration information. More specific information is accessed by the more specific methods.

getConfigProperties() Returns all attributes and elements for the given repository object.

getHostInformation() Returns standard and extended application information.

getRvConfig() Returns information about all TIBCO Rendezvous sessions defined.

getRvQueueInfo() Gets information about the event queue defined in the Rendezvous session.

getPerformanceMetrics()

Gets throughput performance metrics on endpoints.

getServerLatency() Gets the server latency performance metrics of the MRpcServer.

getStatus() Retrieves basic status information about the adapter.

getTraceSinks() Returns information about sinks to which traces currently go.

getVersion() Returns the configuration ID, application name, version, and date for this adapter instance.

_onUnsolictedMsg() Displays alert messages sent to the current adapter.

preRegisterListener() Preregisters an anticipated listener.

reviewLedger() Returns information retrieved from the ledger file of a certified messaging session for a publisher adapter.


Method (Cont’d) Description (Cont’d)



setTraceSinks() Adds a role or changes the file limit of a previously specified sink.

stopApplicationInstance()

Stops the running adapter instance.

unRegisterListener() Unregisters a currently preregistered listener.


Method (Cont’d) Description (Cont’d)


activateTraceRole() | 67

activateTraceRole()

Activates a mapping of a role to a sink at runtime. This replaces the now-deprecated setTraceSink() TIBCO Hawk method.

Input Parameters Type Description

Role Name string Name of the role to activate.

Sink Name string Name of the sink for which to activate the role.



deactivateTraceRole()

Deactivates a mapping of a roles to sinks at runtime.


Role Name string Name of the role to activate.

Sink Name string Name of the sink for which to activate the role.


getAdapterServiceInformation() | 69

getAdapterServiceInformation()

Returns information about the services implemented by this adapter.

Input Parameter Type Description

Service Name string Name of the service from which to get information. Default is ALL.

Returns Type Description

Line integer Sequential row number.

Service Name string Name of the service as defined at design-time.

Endpoint Name string Name of the endpoint used for this service.

Type string Type of the endpoint, for example, publisher or subscriber.

Quality of Service

string Quality of service for the endpoint. For example RVCM or JMS Persistent.

Subject string Subject defined for this endpoint.

Class string Class associated with the endpoint.

Number of Messages

integer Number of messages processed for this endpoint.



getComponents()

Returns information about the currently active TIBCO Hawk components such as publishers, subscribers, or timers.


Component Name string Name of the component. If no value is enter, all components display.

Component Type string Any of Publisher, Subscriber, Timer, or IODescriptor. The default value is All.


Instance ID string Name of this adapter instance as defined at design-time.

Adapter Name string Name of the adapter.

Component Name string Name of the component.

Component Type string The name of the TIBCO Adapter SDK class for this component, such as Publisher, Subscriber, or IODescriptorSource. For more information about the class, see your TIBCO Adapter SDK documentation.

Session Name string Name of the session.

Description string Information about this component, for example, time interval, signal type, and validating the publisher or subscriber.


getConfig() | 71

getConfig()

Retrieves generic configuration information. More specific configuration information is accessed through separate methods.


Instance ID string Configuration ID of this adapter.


Repository Connection

string URL of the repository used for adapter instance.

Configuration URL

string Location of the adapter project; either a file name or configuration URL.

Command string Command line arguments used to start the adapter.



getConfigProperties()

Returns all attributes and elements for the given repository object.


Property string Name of the property for which elements (tags) and attributes are desired. For example, agentone/startup.

If no value is given, all properties are returned.


Element Name string Repository directory for the property.

Attribute Name string Name of the repository object attribute.

Attribute Value string Value of the repository object attribute.

Line integer Line number in which this property is defined in the project file.


getHostInformation() | 73

getHostInformation()

Return standard and extended application information set. It returns the following information.


Name string Name of the property.

Value string Value of the property.



getRvConfig()

Returns information about the Rendezvous session defined by this adapter. Information about all currently defined sessions is returned if no sessionName is provided.


Session Name string Name of the Rendezvous session for which configuration is required. If not given, information about all sessions is returned. The default is all.


Instance ID string Configuration ID of this adapter.



Service string Service parameter for this session.

Daemon string Daemon parameter for this session.

Network string Network parameter for this session.

Synchronous? boolean Returns 1 if this is a synchronous session, 0 otherwise.

Session Type string Type of session; one of M_RV, M_RVCM, or M_RVCMQ.

Certified Name string Name of this certified session.

Ledger File string Ledger file for this certified messaging session. Returns the empty string for sessions that are not certified messaging sessions.

CM Timeout string Timeout for this certified messaging session. Returns the empty string for sessions that are not certified messaging sessions.


getRvQueueInfo() | 75

getRvQueueInfo()

Gets information about the event queue defined in the Rendezvous session. Information about all currently defined sessions is returned if no sessionName is provided.


Session Name string Name of the Rendezvous session for which configuration is required. If not given, information about all sessions is returned. The default is all.



Session Type string Type of session; one of RV, RVCM, RVCMQ,or RVA.

Queue Size integer The current number of events in the queue.

Queue Priority integer The priority of the Rendezvous sessions in the queue.



getPerformanceMetrics()

Gets throughput performance metrics on endpoints.


Endpoint Name

string Name of the endpoint for which the configuration is required. If not given, information about all endpoints is returned. The default is all.

Reset string Specifies whether to get the performance metrics of the endpoint. The default is true.


Activity Name string Name of the activity.

Messages Count string The number of messages calculated by this measurement.

Average Messages per Sec

string The average number of messages sent per second.

Average Bytes per Sec string Average bytes sent per second.

Average Bytes per Message

string Average bytes per message sent.

Max Bytes per Message string The maximum bytes per message sent.

Measurement Interval in Sec

string The measurement interval in millisecond.


getServerLatency() | 77

getServerLatency()

Gets the server latency performance metrics of the MRpcServer.


Server Name string Name of the server for which configuration is required. If not given, information about all servers is returned. The default is all.


Server Name string Name of the server.

Number of Requests integer The number of requests calculated by this measurement.

Average Seconds per Request

double The average time (in seconds) per request sent.

Max Seconds per Request

double The maximum time (in seconds) per request sent.



getStatus()

Retrieves basic status information about the adapter.

This information is fairly limited; for more detail, additional methods are provided (getConfig() on page 71 and getRvConfig() on page 74).


Instance ID string Configuration ID for this adapter instance.


Uptime integer Number of seconds since startup.

Messages Received integer Number of Rendezvous messages received.

Messages Sent integer Number of Rendezvous messages published.

New Errors integer Number of errors since the last call to this method.

Total Errors integer Total number of errors since startup.

Process ID integer Process ID of the application.

Host string Name of host machine on which this adapter is running.


getTraceSinks() | 79

getTraceSinks()

Returns information about sinks to which traces currently go.


Sink Name string Name of the sink for which you need information. If no name is specified, information about all sinks is returned. Default is all.

Role Name string Name of the role for which you need information for the specified sink or sinks. Default is all.


Instance ID string Name of this adapter instance as a string.

Adapter Name string Name of the application for this sink.

Sink Name string Name of the sink

Sink Type string Type of this sink. One of fileSink, rvSink, hawkSink, stderrSink.

Roles string Roles this sink supports, as a string. For example warning, error, debug.



getVersion()

Retrieves version information for the current application. Two lines may be returned, one for the TIBCO Adapter SDK, one for the adapter.

Returns Description

Instance ID Configuration ID as a string, for example SDK.

Adapter Name Name of the adapter as a string, for example agentone.

Version Version number as a string, for example 5.2.


_onUnsolictedMsg() | 81

_onUnsolictedMsg()

Displays all alert messages sent from the adapter or an error if not successful.



preRegisterListener()

Preregister an anticipated subscription service. Some sending applications can anticipate requests for certified delivery even before the listening applications start running. In such situations, the publication service can preregister subscription services, so TIBCO Rendezvous software begins storing outbound messages in the publication service ledger. If the listening correspondent requires old messages, it receives the backlogged messages when it requests certified deliver.

Returns OK if the subscription service was preregistered successfully, false otherwise.


Session Name string Name of the session that anticipates the listener.

Publisher Name string Name of the component for which the listener should be preregistered.

Listener Session Name

string Name of the subscription service to preregister.


reviewLedger() | 83

reviewLedger()

Returns information retrieved from the ledger file of a Rendezvous certified messaging session.

Before invoking this method, ensure that the certified messaging publisher adapter has established a certified delivery agreement with its subscriber agents.


Session Name string Name of the Rendezvous session for which ledger information is desired (default is all).

Subject string Name of the subject for which ledger information is desired.


Session Name string Name of the Rendezvous CM session to which this information applies.

Subject string Subject name for this session.

Last Sent Message integer Sequence number of the most recently sent message with this subject name.

Total Messages string Total number of pending messages with this subject name.

Total Size integer Total storage (in bytes) occupied by all pending messages with this subject name.

If the ledger contains ten messages with this subject name, then this field sums the storage space over all of them.


string Within each listener submessage, the Listener Session Name field contains the name of the delivery-tracking listener session.

Last Confirmed string Within each listener submessage, the Last Confirmed field contains the sequence number of the last message for which this listener session confirmed delivery.



Line integer Row number in ledger file.

UnacknowledgedMessages

integer Number of RVCM messages pending for this listener. The value is computed by subtracting the last sent sequence number from the last acknowledged sequence number.

Returns (Cont’d) Type Description


setTraceSinks() | 85

setTraceSinks()

Adds a role or changes the file limit of a previously specified sink.

Returns OK if successful or an error if not successful.


Sink Name string Name of the sink for which you want to add a role or change the file limit.

Role Name string Name of the role you want to add to this sink (warning, error, debug, or user defined). Default is all.

File Size integer Maximum file size for this sink.

This parameter is ignored if the sink specified by sinkName is not a file sink.



stopApplicationInstance()

Stops the specified adapter by calling the internal stop() method. This method returns OK if successful or an error if not successful.


unRegisterListener() | 87

unRegisterListener()

Unregister a currently preregistered subscription service.

This method returns true if the subscription service was unregistered successfully, false otherwise.


Session Name string Name of the session that anticipates the subscription service.

Publisher Name string Name of the publication service to which the subscription service is preregistered.


string Name of the subscription service to unregister.




| 89

Chapter 7 Advanced Topics

This chapter explains advanced topics for the TIBCO ActiveMatrix Adapter for JD Edwards EnterpriseOne.

Topics

• Using the Adapter with a Revision Control System, page 90

• Defining a TIBCO Hawk Session, page 92

• Using Global Variables, page 94

• Managing Connections, page 99

• Setting Encoding Options, page 101

• Setting Up Debug Log Level, page 102

• JDE Test Tool, page 103


90 | Chapter 7 Advanced Topics

Using the Adapter with a Revision Control System

TIBCO Designer supports revision control systems such as Microsoft Visual SourceSafe and Perforce. If you are using a revision control system, you must manually add some configured resources to the revision control system and check in the resources when completing the instance configuration.

As part of service configuration, the adapter creates schema files in root/AESchemas/ae/jdexe. For example, if you configure a service in an adapter configuration Instance1, the following files and folders are created:

Project_root/AESchemas/ae/jdexe/Instance/jdexe/BSFNSequences.aeschema

Project_root/AESchemas/ae/jdexe/Instance/jdexe/BusinessFunctions

When the project is saved and a revision control system has been specified, the adapter displays a warning that additional files were created and should be added to the revision control system. This warning appears only when the files are created for the first time. The warning displays a Go To Resource button that helps in navigating to the resource. You should use the Multi-User>Add Resources to RCS menu command to add these files to the revision control system.

For information about how to use the Multi-User feature in TIBCO Designer, refer to the TIBCO Designer User’s Guide.

Copy, Cut, Paste and Move Operations

To successfully copy and paste a service from adapter Instance1 to Instance2, the adapter configuration and schema files for the Instance2 must be checked out.

To successfully cut and paste a service from adapter Instance1 to Instance2, the adapter configuration and schema files for both Instance1 and Instance2 must be checked out.

To successfully move a service from adapter Instance1 to Instance2, the adapter configuration and schema files for both Instance1 and Instance2 must be checked out.

Regeneration When Moving, Copying and Pasting

• Default subjects are not regenerated to reflect the new instance name when a service is moved.

• Manually changed certified messaging and certified messaging queue ledger file names are regenerated to defaults when a service is moved, or copied and pasted to a new instance.


Using the Adapter with a Revision Control System | 91

• If a service associated with a custom session is moved, or copied and pasted, the custom session is not moved, or copied and pasted. The session is regenerated as a default session.



Defining a TIBCO Hawk Session

To use TIBCO Hawk to monitor the adapter you must first define a TIBCO Rendezvous session. Use the following steps to create the session.

1. In the project tree panel, click the JDEA Adapter Configuration icon defined for your adapter instance.

2. Select the Show All Tabs checkbox, then click the Monitoring tab.

3. Use default setting for all the fields, as shown in Figure 5.

Figure 5 Monitoring Tab

4. Expand JDE Adapter Configuration > Advanced > Sessions and select the DefaultHawkSession option in the Project panel. The Configuration panel appears, as shown in Figure 6.

Figure 6 Default Hawk Session

5. Configure the hawk session in the Configuration panel as follows:

a. In the Service field, type 7474 (the default used by TIBCO Hawk) or modify the global variable by clicking the Global Variables tab.

b. In the Daemon field, type tcp:7474 (the default used by TIBCO Hawk) or modify the global variable by clicking the Global Variables tab.

c. Click Apply and save the project.


Defining a TIBCO Hawk Session | 93

Figure 7 Defined Hawk Session



Using Global Variables

The variable substitution mechanism can override global variables predefined in the project in a restricted manner. Predefined variables can be viewed and set in TIBCO Designer. Variables are specified as %%VARNAME%% and cannot contain any white space.

Variable substitution allows you to accomplish the following.

• Substitute string variables specified in the project at startup time.

• Locally define the value for a variable for a specific project. The local value takes precedence over any global value.

• Specify the value for a variable in a properties file. This overrides the project repository and values set in code, but not variables set on the command line.

• Enforce the pre-defined variables listed in Predefined Global Variables on page 96.

Variables can be used anywhere in the configuration and will be replaced by the locally-defined adapter instance.

Specifying Variables Using TIBCO Designer

Global variables provide an easy way to set defaults for use throughout your project. There are several ways in which they can be used:

• Define a variable using TIBCO Designer, then override the value for individual applications at deployment time using TIBCO Administrator. You can also override values for predefined variables, unless the GUI does not allow you to set them later.

• Predefine a variable using TIBCO Designer, then override the value for individual services (for example, publication service or TIBCO BusinessWorks process) at deployment time using TIBCO Administrator. The values you specify are then used at runtime. You can also override values for predefined variables, unless the GUI does not allow you to set them later.

For example, you could assign the value 7474 to the predefined global variable RvDaemon. You can then use the variable in different sessions in your adapter. If you wish to change the TIBCO Rendezvous daemon for your adapter, you can globally set it to a different value or override it from the command line.

To use global variables in your project, follow these steps:

1. In the Project panel, select the Global Variables tab. All the currently defined variables are displayed.


Using Global Variables | 95

2. Click the button. The Global Variables dialog appears.

You now have these choices:

— To assign or change a variable value, select that region and triple-click the variable. The variable expands so you can change either the variable name or the variable value. Press the Enter key when you are done.

— To add a new global variable group, click . Specify the name of the group, then press the Enter key. With the group icon selected, you can click

to add variables to the group.

— To add a global variable, click . A new global variable item is added to the bottom of the list. Supply the variable name and, optionally, the value. Press the Enter key when you’re done.

The global variable is now displayed in the global variables list.

3. When you want to use the global variable in the fields of a resource, enter the variable name surrounded by %% on both sides.

When the project is deployed and the configured components are run, all occurrences of the global variable name are replaced with the global variable value (unless it was overridden in a way that had higher precedence).

A number of global variables are predefined. See Predefined Global Variables on page 96 for information. You may add definitions of any variables you need to the predefined variables.

Changing Global Variable Values at RuntimeYou can change the value of a global variable when you deploy your project in TIBCO Administrator. See the section on modifying runtime variables in the TIBCO Administrator User’s Guide for more information on using TIBCO Administrator.

You can also specify values for global variables when starting a process engine on the command line. To do this, specify the following as a command line argument when starting the process engine:

-tibco.clientVar.<variablePathAndName> <value>

where variablePathAndName is the name of the variable you wish to set, including the path to the variable if it is contained in a folder. value is the value you wish to set the variable to. For example, if you have a global variable named item1 contained in a folder named myGroup and you wish to set its value to 500, add the following argument to the command line when starting the process engine:

-tibco.clientVar.myGroup/item1 500



Predefined Global VariablesThe next table lists and explains the predefined global variables. Some global variables are automatically used within the system when an adapter instance is configured. For example, the RV Session shown above uses the value defined for the RvService, RvNetwork and RvDaemon global variables

For further information on the connection variables, see Managing Connections on page 99.

Table 24 Predefined Global Variables (Sheet 1 of 3)

Variable Description

Deployment Defaults to the TIBCO Designer project name. This global variable is used by the system to partially define the subject name defined for a service.

DirLedger Specifies the path name of the TIBCO Rendezvous certified messaging ledger file. The default is the root installation directory.

DirTrace Specifies the path name for log file used by the adapter. The default is the root installation directory.

Domain The default value for file-based local projects is MyDomain. The value for server-based projects is the domain to which the project was saved.

HawkEnabled Indicates whether TIBCO Hawk is used to monitor the adapter. True indicates that a Hawk microagent is defined for the adapter. False indicates the microagent is not to be used.

JDEInboundThreadCount Specifies the number of inbound threads that the application has at runtime. The default value is 5.

If no inbound services are configured, that is, no Subscription Service or Request-Response Service is configured; the value of this field is ignored.


Using Global Variables | 97

JDEXEInvocationTimeout Specifies the maximum time spent on retrieving business function lists and real-time events from the JDE applications.

JmsSslProviderUrl Specifies where the JMS SSL daemon is located.

JmsProviderUrl Specifies where the JMS server is located. Setting this value mostly makes sense in early stages of a project, when only one JMS server is used.

RemoteRvDaemon TIBCO Rendezvous routing daemon (rvrd) to be used. See TIBCO Administrator Server Configuration Guide for details about setting up a domain using rvrd.

RvDaemon TIBCO Rendezvous daemon. Sessions use this daemon to establish communication. The default value is 7500.

RvNetwork TIBCO Rendezvous network. This variable need only be set on computers with more than one network interface. If specified, the TIBCO Rendezvous daemon uses that network for all outbound messages.

In most cases, you can leave the default.

RvService TIBCO Rendezvous service. The Rendezvous daemon divides the network into logical partitions. Each transport communicates on a single service. A transport can communicate only on the same service with other transports.

Unless you are using a non-default TIBCO Rendezvous configuration, you should leave the default (7500).





RvaHost Computer on which the TIBCO Rendezvous agent runs. This variable is only relevant if you are using the TIBCO Rendezvous Agent (rva) instead of the TIBCO Rendezvous daemon, and if you have configured a non-default setup. See TIBCO Rendezvous Administration for details about specifying the rva parameters.

RvaPort TCP port where the TIBCO Rendezvous agent (rva) listens for client connection requests. See TIBCO Rendezvous Administration for details about specifying the rva parameters. Defaults to 7501.

TIBHawkDaemon TIBCO Rendezvous daemon used in the TIBCO Hawk session. See the TIBCO Hawk Installation and Configuration manual for details about this parameter.

TIBHawkNetwork TIBCO Rendezvous network used by the TIBCO Hawk session. See the TIBCO Hawk Installation and Configuration manual for details about this parameter.

TIBHawkService TIBCO Rendezvous service used by the TIBCO Hawk session. See the TIBCO Hawk Installation and Configuration manual for details about this parameter.




Managing Connections | 99

Managing Connections

This section explains how to save your connection settings for reuse and how to refresh connections to improve performance:

• Saving Connection Settings, page 99

• Refreshing Connection, page 100

Saving Connection SettingsYou can save the connection settings, and then reuse them when creating another adapter instance.

Complete the following steps to manage the connection settings:

1. Select an adapter configuration instance in the project panel. Upon clicking, the JD Edwards option is displayed in the menu, as shown in Figure 8.

Figure 8 Connection Settings

2. Click the JD Edwards option and select the operation that you want to perform from the displayed menu. You have the following choices:

— Save Connection Settings

After filling the information in the Configuration panel, use this choice to save the adapter configuration.

— Delete Connection Setting

Use to delete a saved adapter configuration.

— User Connections

Choose a stored connection setting for use for the current adapter instance.



Refreshing ConnectionWhen intensively using the adapter, users may encounter a situation where the adapter performance lowers gradually. If users restart the adapter, and then the adapter performance becomes normal. To keep the adapter performance stable and normal, also to avoid data loss, users can set up a threshold for the adapter connections. When the connection reaches the defined threshold, the connection will be automatically refreshed.

If the connection is busy when it reaches the defined threshold, the adapter will wait until the connection is idle. Upon becoming idle, the connection will be cut off, and then re-connected.

To set up a threshold for refreshing connections, do the following:



3. Find the jde.connection.limit.time parameter, which defines the time interval (in seconds) that the connections are refreshed, and then set up a value for this parameter. The default value is 3600.

4. Save the file.


Setting Encoding Options | 101

Setting Encoding Options

See TIBCO ActiveMatrix Adapter for JD Edwards EnterpriseOne Concepts for an introduction to Internationalization topics such as Unicode and how adapters handle it.

The wire format encoding used for communication between adapters and TIBCO applications is determined by the encoding property set in the project. Configure inter-communication encoding prior to running the adapter so it can handle files in different encoding.

The adapter configuration can be saved in a local or repository server-based project.

• If the adapter configuration is saved in a repository server-based project, inter-communication encoding is determined by the repo.encoding property in the server’s config file. Each adapter or TIBCO application that uses the repository server for storing and retrieving configuration data from a project users this encoding setting when communicating. This assures that all components (including adapters and other TIBCO applications) that use the same repository also use the same encoding value to communicate. The value of the repo.encoding property can either be ISO8859-1 (by default) or UTF-8. If English or other Latin-1 languages data is transmitted between adapters, ISO8859-1 should be used. Otherwise use UTF-8.

• If an adapter configuration is saved in a local project, the inter-communication encoding is determined by the encoding property of the local project file. To communicate with each other adapters using the same the encoding, all adapters and applications must set their local project file encoding property identical. Use the Repository Finder in TIBCO Designer to set the encoding property for a local project. The default encoding is Latin-1.

When a local project is later promoted to a repository server-based project, the encoding property set in the project file is superseded by the server’s encoding property.

The encoding property discussed here is the encoding used by the communication between adapters and applications, not the encoding used for the persistent storage of the project files. Project files are always saved using UTF-8.



Setting Up Debug Log Level

The adapter allows users to set up a log level for the debug messages. The default debug level is 2. The level can be set to 0, 1, 2, or 3. The higher the debug level is, the more detailed the messages are. However, the adapter performance becomes lower when the debug level is higher.

For more details about log settings, see Logging Tab on page 20.

To set up debug log level, do the following:



3. Find the jde.debug parameter and specify a debug level. The valid value is 0, 1, 2, or 3.

4. Save the file.


JDE Test Tool | 103

JDE Test Tool

TIBCO ActiveMatrix Adapter for JD Edwards EnterpriseOne provides a tool to validate connections between the adapter and the JDE enterprise server, and also to test whether the JDE data, such as business functions and real-time events, are accessible.

To run the JDE test tool, complete the following tasks:

• Task A, Specify the Connection

• Task B, Run the JDE Test Tool

Task A Specify the Connection

The configuration file, used to specify the adapter connection to test, must be configured before running the tool. To specify an adapter connection, do the following:

1. Navigate to the ADJDEXE_HOME\util directory.

2. Open the config.properties file and configure the connection parameters according to the information listed in Table 25.

3. Save the file.

Table 25 Connection Parameters

Parameters Description

Username The username used to connect to the JD Edwards EnterpriseOne.

Password The password for the account used to connect to the JD Edwards EnterpriseOne.

Environment The environment name in JD Edwards EnterpriseOne that is used by the adapter instance.

Port Number The port number that is used for connection between JD Edwards EnterpriseOne and TIBCO ActiveMatrix Adapter for JDE.

Server Name The host name or the IP address of the machine that hosts the JDE application server to which the adapter instance is connecting.

INI File Path The absolute path of the jdeinterop.ini file that is detailed to the file name.

JDE Connectors The absolute path of the JDE connector that the adapter uses.

JAVAHOME The absolute path of Java. The value of this parameter is TIBCO_HOME/tibcojre/version_number.



Task B Run the JDE Test Tool

After configuring the config.properties file, do the following to run the tool:

1. Double-click the platform-specific executable residing in the ADJDEXE_HOME\util directory to start the tool.

On Microsoft Windows—double-click the JDETEST.bat file.

On Unix—double-click the JDETEST.sh file.

2. Press any key to continue in the displayed command-line interface. A short description of the tool is displayed.

3. Press any key to continue in the displayed command-line interface. The tests that can be done are displayed.

4. Press any key to continue, and then enter an integer to do the corresponding test. See Table 26 for more details about each test.

Figure 9 JDE Test Tool

5. Press any key to start testing and provide the specific information according to the test that you perform if necessary. The test result is displayed in the command-line interface when the test is finished.

6. Enter q to exit the tool.

Table 26 Supported Test Actions

Integer Action

1 Test the connection between the adapter and the JDE enterprise server. The connection to test is specified in the config.properties file.

2 Test whether the real-time events used for the Publication Service are available.


JDE Test Tool | 105

3 Test whether the business functions deployed on the specified enterprise server are available.

4 Test the CallXMLObject method. The AddressBook Master Business Function is used.

Note: You need to provide an address book number that you want to call when you perform this test.

5 Test calling a business function. The AddressBook Master Business Function is used.

Note: You need to provide an address book number that you want to call when you perform this test.

Table 26 Supported Test Actions (Cont’d)

Integer Action




| 107

Appendix A Trace Messages

This appendix explains the error messages that are logged to the location specified when the adapter was configured.

Topics

• Overview, page 108

• Trace Message Fields, page 110

• Status Messages, page 112


108 | Appendix A Trace Messages

Overview

Trace messages provide information about adapter activities. The messages are logged to the console where the runtime adapter was started and to a log file. Trace messages can also be redirected to the TIBCO Hawk Display application, or sent to other applications using the TIBCO Rendezvous transport.

Each trace message can include the following fields:

<Timestamp> <Adapter Identifier> <Role> <Category> <Status Code> <Tracking Identifier>

The above fields are explained in Trace Message Fields on page 110. The following diagram shows an example trace message and calls out the fields.

Example Trace Messages

The following trace messages were written during a session where TIBCO Adapter for JD Edwards EnterpriseOne received a request for creating a sales order, then processed the object.

The first message indicates that TIBCO Adapter for JD Edwards EnterpriseOne has started. The timestamp indicates when the adapter started, and the role indicates that the trace message is informational, which means the activity is normal for the adapter. The category is identified, and the corresponding status code is displayed. The status code indicates that the adapter started successfully.

2004 Feb 04 17:10:28:328 GMT -8 JDEAdapterConfiguration Info [Adapter] TIS-00001 "Adapter JDEAdapter started successfully"

The next set of trace messages indicates the adapter received a request for creating a sales order. The tracking identifier #jFGRltnZUneFOE7gGHzzw8PEzzw# included in the trace message uniquely identifies the message. The process (TIBCO BusinessWorks process) from which the message originated provided the identifier.

JDEAdapterConfiguration

Timestamp

Adapter Identifier Role Category

Status Code

Tracking Identifier

2004 Feb 04 17:11:32:625 GMT -8

[JDEOneWorldBSFNExecuteOperation] Info

TJDE-0182 Completed processing business function request: CreateSalesOrder

tracking=#jFGRltnZUneFOE7gGHzzw8PEzzw#


Overview | 109

2004 Feb 04 17:11:17:968 GMT -8 JDEAdapterConfiguration Info [Adapter] TIS-30028 "Obtained connection from pool"

2004 Feb 04 17:11:32:625 GMT -8 JDEAdapterConfiguration Info [JDEOneWorldBSFNExecuteOperation] TJDE-0182 Completed processing business function request: CreateSalesOrder tracking=#jFGRltnZUneFOE7gGHzzw8PEzzw#

The final trace message indicates that the request for creating a sales order in JD Edwards EnterpriseOne was completed successfully.



Trace Message Fields

Each trace message includes the following fields:

Table 27 Tracing Fields

Field Name Description

Timestamp Timestamp of occurrence. For example, 2003 Feb 22 20:14:51:718 GMT -8.

Adapter Identifier

Name of the adapter that wrote the trace message. This is a combination of the adapter acronym and adapter configuration name. For example, the application identifier, ADB.publisher1 identifies a TIBCO Adapter for ActiveDatabase service named publisher1.

Role A role can be:

• Info. Indicates normal adapter operation. No action is necessary. A tracing message tagged with Info indicates that a significant processing step was reached and has been logged for tracking or auditing purposes. Only info messages preceding a tracking identifier are considered significant steps.

• Warn. An abnormal condition was found. Processing will continue, but special attention from an administrator is recommended.

• Error. An unrecoverable error occurred. Depending on the error severity, the adapter may continue with the next operation or may stop altogether.

• Debug. A developer-defined tracing message. In normal operating conditions, debug messages should not display.

When configuring the adapter you define what roles should or should not be logged. For example, you may decide not to log Info roles to increase performance. See Setting Up Debug Log Level on page 102 for more details.

Category Name of the adapter java class that is printing this message.

Status Code Unique code for the message and description. Status codes are identified by a unique number and description. If a trace message includes an error or warn role, the status code documentation includes a resolution. See Status Messages on page 112 for details.


Trace Message Fields | 111

Tracking Identifier

A unique identifier that is "stamped" on each message by the originating adapter. The tracking identifier remains in effect from a message’s beginning to its completion as it is exchanged by TIBCO applications. If the adapter is the termination point of the message, the tracking identifier is not displayed in the trace message.

You cannot modify the tracking identifier format or configure what information is displayed.

Application Information

Application-specific information added to the tracking info to trace the message back to its source. Set initially by the originating adapter and carried forward. It is augmented by each intermediate component.

Table 27 Tracing Fields

Field Name Description



Status Messages

Status Code Role Category Description Resolution

TJDE-100001 Error Occurred while creating JDE Connection

errorRole JDEAdapterConnection

Error occurred when creating the JDE connection.

Please check the JDE debug log for more information about this error. Also check whether the connection parameters are correct.

TJDE-100004 Error occurred when retrieving J.D. Edwards EnterpriseOne Connection parameters.\nResolution: Please make sure that connection parameters are defined in Repository.


Error occurred when retrieving the parameters of the JDE connection.

Please make sure that the connection parameters are defined in Repository.

TJDE-100008 Error occurred while create connection pool, some parameter request environment=%1, serverName=%2, portNo=%3.


Error occurred when creating the connection pool.

Please make sure that the input parameters are correct, and then restart the adapter.

TJDE-100012 JDE dynamic connection close error


Error occurred when closing the JDE dynamic connection.

None.

TJDE-100013 Error occurred while create the timer to record the connection's wait time


Error occurred when creating the timer.

Please restart the JDE adapter.


Status Messages | 113

TJDE-100014 Error occurred while deactivate the connection timer


Error occurred when deactivating the connection timer.

None.

TJDE-100016 Error occurred while read the connection deactivate value from the .tra file , cause by %1.


Error occurred when reading the deactivated value of the adapter connection from the TRA file.

Please check your adapter connections.

TJDE-200003 Error occurred while processing real-time Event

errorRole Publication Service

Error occurred when processing the real-time event.

Please check the configurations of the real-time event on the JDE server.

TJDE-200004 Error occurred while subscribing to real-time event


Error occurred when subscribing to the real-time event.

Please check the JDE debug log for more information about this error.

TJDE-200006 here is an exception for %1 publication service when run the real-time event


Error occurred when processing the real-time event.

Please check the configurations of the real-time event on the JDE server.

TJDE-200008 Error occurred while create dispatcher


Error occurred when creating the dispatcher.

Please restart the JDE adapter.




TJDE-200009 Error occurred while execute JDE event method of JDEEventListener class


Error occurred when executing the JDE event method of the JDEEventListner class.

Please check error log for additional information.

TJDE-200010 Error occurred while convert the data to JDEdata type


Error occurred when converting the data type.

None.

TJDE-300002 Error while parsing incoming data for Business Function Execute Subscriber

errorRole Subscription Service

Error occurred when parsing the incoming data.

Please check the input data of the business function.

TJDE-300003 Error in Business Function Execute operation implementation for request

errorRole Subscription Service

Error occurred when executing the request from the subscriber.

None.

TJDE-400002 Business function request contains no data.\nResolution: Please specify a correct business function request schema. Then try the request again.

errorRole RPCBusinessFunction

No data is contained in the business function request.

Please specify a correct request schema for the business function and try again.




TJDE-400006 Error in Business Function Execute operation implementation for request : %1\nResolution: Please check previously listed error messages for business functions to resolve the errors. Error message numbers for business function messages are TJDE-400002 through TJDE-410003.


Error occurred when executing the business function request.

Please check previously listed error messages from TJDE-400002 to TJDE-410003.

TJDE-400007 There is an error and an exception is thrown to run RPC Server.


No response is sent from the JDE server.

None.

TJDE-410001 Error in setting parameter {%1} value in business function {%2}.\nResolution: Please check the type definition for the field in business function request schema.


Error occurred when setting values for the parameter in the business function.

Please check the type definition for the field defined in request schema in the business function.

TJDE-410002 Error in instantiating {%1} business function.\nResolution: Please make sure that the GenJava JAR file for business function exists and the business function class name is correct. Please check the error log for additional information.


Error occurred when instantiating the business function.

Please make sure that the business function class name is correct. Also check the error log for additional information.




TJDE-410003 Error in instantiating {%1} business function and {%2} data structure.\nResolution: Please make sure that the GenJava JAR file for business function exists and the business function class name is correct. Please check the error log for additional information.


Error occurred when instantiating the business function and data structure.

Please make sure that the JAR files for business function class name is correct. Also check the error log for additional information.

TJDE-410004 Error occurred when calling business function {%1}. Error: {%2}\nResolution: Please check the errors returned by J. D. Edwards EnterpriseOne server. Correct the business function data accordingly and try the request again.


Error occurred when calling the business function.

Please check errors returned by the JDE server. Correct the business function data accordingly and try again.

TJDE-420005 Error(s) occurred when executing business function!


Error occurred when executing the business function.


TJDE-420006 Error occurred in getting reply from J. D. Edwards EnterpriseOne server.\n{%1}\nResolution: Please check the errors returned by J. D. Edwards EnterpriseOne server. Correct the business function data accordingly and try the request again


Error occurred when getting reply from the JDE server.

Please check the errors returned by the JDE server. Correct the business function data accordingly and try again.




TJDE-510001 Error occurred when creating list for request: Table=%1, Type= %2, Data Selection=%3, Data Sequence = %4\nResolution: Please check the debug log for additional information.

errorRole RPCXMLQueryListCreate

Error occurred when creating the XMLQueryList.

Please check the debug log for additional information.

TJDE-510002 Table Name and Table Type must be defined in the server request %1.\nResolution: Please specify a table name and its type in the Query List request schema and try the request again.


No table name or table type is defined in the request.

Please specify the name and the type of the table in the request schema of the XMLQueryList and try again.

TJDE-510003 Query {%1} is not defined for the adapter.\nResolution: Please define the J. D. Edwards EnterpriseOne table or view using Services GUI and try the request again.


The XMLQueryList is not defined for the JDE adapter.

Please define the JDE table or view using Services GUI and try again.

TJDE-510004 Error in converting input parameters into XML Call List Request {%1}.


Error occurred when converting the input parameters to XML Call List Request.

Please correct the input parameters in the request schema defined for the Query List and try again.

TJDE-510005 Error executing J. D. Edwards EnterpriseOne Request. {%1}\nResolution: Please check the J. D. Edwards EnterpriseOne server logs for additional information.


Error occurred when executing the request from the JDE server.

Please check the JDE server log for additional information.




TJDE-510006 J. D. Edwards EnterpriseOne returned Error Code: {%1}. Error Description: {%2}.\nResolution: Please correct the Query List request schema and try the request again.


Error occurred when executing XMLQueryList request.

Please correct the request schema of the XMLQueryList and try again.

TJDE-510007 Error while parsing J. D. Edwards EnterpriseOne response XML {%1}.\nResolution: Please check the debug log for additional information.


Error occurred when parsing the response data from the JDE server to XML.


TJDE-520001 Error occurred when processing list retrieve request for: Table=%1, Handle=%2, From Value=%3, To Value=%4\n{%6}\nResolution: Please check error returned by the service to determine the problem.


Error occurred when processing the ListRetrieve request.

Please check error returned by the service to determine the problem.

TJDE-520002 XML List Handle required for retrieving list{%1}.\nResolution: Please specify a correct list handle value in the Query List Retrieve schema and try the request again.


Error occurred when executing the ListRetrieve request.

Please check the data schema for the ListRetrieve query and try again.



Error occurred when executing the JDE request.





TJDE-520004 J. D. Edwards EnterpriseOne returned Error Code: {%1}. Error Description: {%2}\nResolution: Please correct the Query List request schema and try the request again.


Error occurred when executing the XMLQueryList request.


TJDE-520005 Error while parsing J. D. Edwards EnterpriseOne Response XML {%1}\nResolution: Please check the debug log for additional information.




TJDE-530001 XML List Handle required for deleting list.{%1}\nResolution: Please specify a correct list handle value in the Query List Delete schema and try the request again.


Error occurred when executing the ListDelete request.

Please check the data schema for the ListDelete query and try again.



Error occurred when executing the JDE request.


TJDE-530003 J. D. Edwards EnterpriseOne returned Error Code: {%1}. Error Description: {%2}\nResolution: Please correct the Query List request schema and try the request again..


Error occurred when executing the XMLQueryList request.





TJDE-530004 Error while parsing J. D. Edwards EnterpriseOne Response XML {%1}\nResolution: Please check the debug log for additional information.




TJDE-530005 Error executing J. D. Edwards EnterpriseOne ListDeleteOperation : %1.\nResolution: Please check the J. D. Edwards EnterpriseOne server logs for additional information.


Error occurred when executing the JDE ListDelete request.


TJDE-700001 Error occurred when calling business function {%1}. Error: {%2}\nResolution: Please check the errors returned by J. D. Edwards EnterpriseOne server. Correct the business function data accordingly and try the request again.

errorRole BusinessFunction

Error occurred when calling the business function.


TJDE-700002 Adding error in the ErrorList from GroupCall. . {%1}



Please check previously listed error messages and JDE debug log for more additional information about the error.

TJDE-700003 Error in setting parameter {%1) value in business function {%2}.\nResolution: Please check the type definition for the field in business function request schema.


Error occurred when setting values for the parameter in the business function.

Please check the type definition for the field defined for the request schema in the business function.




TJDE-700004 Adding error in the ErrorList. {%1}.



Please check previously listed error messages and JDE debug log for more additional information about the error.

TJDE-700007 Error in creating XML request for business function {%1}.\nResolution: Please check the error log for additional information.\nThe exception message is : %2


Error occurred when creating the XML request for the business function.

Please check the error log for additional information.

TJDE-700008 Error in creating XML request for {%1} business function from list of business functions.\nResolution: Please check the error log for additional information.\nThe exception message is : %2


Error occurred when creating the XML request for the business function.

Please check the error log for additional information.

TJDE-900001 Field type must be JDEDate for Date field {%1} in {%2} function.\nResolution: Please check the type definition for the field in request/reply schema.

errorRole JDEDataType The field type for the Date field in the business function is incorrect.

Please check the type definition for the field in the request/reply schema.




TJDE-900002 Field type must be JDEMathNumeric for short field {%1} in {%2} function.\nResolution: Please check the type definition for the field in request/reply schema.

errorRole JDEDataType The field type for the Short field in the business function is incorrect.

Please check the type definition for the field in the request/reply schema.

TJDE-900003 Field type must be JDEMathNumeric for int field {%1} in {%2} function.\nResolution: Please check the type definition for the field in request/reply schema.

errorRole JDEDataType The field type for the Int field in the business function is incorrect.

Please check the type definition for the field in request/reply schema.

TJDE-900004 Field type must be JDEMathNumeric for long field {%1} in {%2} function.\nResolution: Please check the type definition for the field in request/reply schema.

errorRole JDEDataType The field type for the Long field in the business function is incorrect.


TJDE-900005 Field type must be JDEMathNumeric for float field {%1} in {%2} function.\nResolution: Please check the type definition for the field in request/reply schema.

errorRole JDEDataType The field type for the Float field in the business function is incorrect.





TJDE-900006 Field type must be JDEMathNumeric for double field {%1} in {%2} function.\nResolution: Please check the type definition for the field in request/reply schema.

errorRole JDEDataType The field type for the Double field in the business function is incorrect.


TJDE-900007 Field type must be char for a char field {%1} in {%2} function.\nResolution: Please check the type definition for the field in request/reply schema.

errorRole JDEDataType The field type for the Char field in the business function is incorrect.


TJDE-900008 Field type must be Date for JDEDate field {%1} in data structure {%2}.\nResolution: Please check the type definition for the field in business function request schema.

errorRole JDEDataType The field type for the JDEDate field in the business function is incorrect.

Please check the type definition for the field in request schema.

TJDE-900009 Field type must be short, int, long, float or double for a JDEMathNumeric field {%1} in data structure {%2}.\nResolution: Please check the type definition for the field in business function request schema.

errorRole JDEDataType The field type for the JDEMath Numeric field in the business function is incorrect.





TJDE-900010 Field type must be short, int, long, float or double for a Double field {%1} in data structure {%2}.\nResolution: Please check the type definition for the field in business function request schema.

errorRole JDEDataType The field type for the Double field in the business function is incorrect.


TJDE-900011 Error while setting JDEdwards DS element {%1} in data structure {%2}.\nResolution: Please check the type definition for the field in business function request schema.

errorRole JDEDataType Error occurred when setting values for the JDE DS element in the data structure.

Please check the type definition for the field defined in the request schema in the business function.

TJDE-900014 The value is %1 when the attrName is %2.The error message is %3.

errorRole JDEDataType An error occurred in the data type of the business function.

Please check the type definition.



| 125

Appendix B Data Type Mapping

Table 28 describes the mapping between JD Edwards EnterpriseOne data types, TIBCO ActiveEnterprise data types, and Java data types.

Table 28 Data Type Mapping

JD Edwards EnterpriseOne Data Type

Java Data Type TIBCO ActiveEnterprise Data Type

Character Char char

JDEDate java.util.Date date

JDEMathNumeric double r8

String java.lang.String string

All other data types java.lang.String string


126 | Appendix B Data Type Mapping


| 127

Index

Symbols

_onUnsolictedMsg() 81

A

activateTraceRole() 67adapter instance

configuration tab 12general tab 18logging tab 20multithreading tab 19

adapter instance, configuration 6adapter instance, creation 6adapter services, creation 8adapter tester, starting 9adapter, command line, starting 9agents 58alerts 58

C

choosing an instance name 12class microagent name field, adapter 25class microAgent timeout field, adapter 25command line arguments 71converting project to repository file 9creating and configuring the sinks 21customer support xvii

D

deactivateTraceRole() 68

E

ENV_NAME xiv

G

getAdapterServiceInformation() 69getComponents() 70getConfigProperties() 72getHostInformation() 73getPerformanceMetrics() 76getRvConfig() 74getRvQueueInfo() 75getServerLatency() 77getStatus() 78getting started 3getTraceSinks() 79getVersion() 80global variables 94

setting for monitoring 24, 25

I

instance name 12

J

JDE test tool 103JDE connectors 103test options 104


128 | Index

L

load balancing 53logging, log debug messages 21logging, log error messages 21logging, log file 20logging, log info messages 21logging, log to standard I/O 20logging, log warning messages 21logging, use advanced logging 20

M

message filter 12microagent methods supported 64Microagent Session field, adapter 25

N

nRegisterListener() 87

P

preRegisterListener() 82project, creation 6

R

refresh connection 100repository file 9Request-Response Service 42reviewLedger() 83

S

setTraceSinks() 85show all tabs 12show startup banner 23standard MicroAgent name field, adapter 24standard MicroAgent timout field, adapter 24stopApplicationInstance() 86Subscription service 34substitution 94support, contacting xvii

T

technical support xviitermination subject or topic 18TIBCO Hawk

background information 58enterprise monitor components 58

TIBCO Hawk methods 64_onUnsolictedMsg() 81activateTraceRole() 67deactivateTraceRole() 68getAdapterServiceInformation() 69getComponents() 70getConfig() 71getConfigProperties() 72getHostInformation() 73getPerformanceMetrics() 76getRvConfig() 74getRvQueueInfo() 75getServerLatency() 77getStatus() 78getTraceSinks() 79getVersion() 80preRegisterListener() 82reviewLedger() 83setTraceSinks() 85stopApplicationInstance() 86unRegisterListener() 87

TIBCO_HOME xivTracing Levels and Fields 110


Index | 129

V

variable substitution 94variables 94version 12


Date post:	16-Mar-2018
Category:	Documents
Upload:	duongdien
View:	222 times
Download:	2 times

TIBCO ActiveMatrix® Adapter for JD Edwards EnterpriseOne · PDF fileTIBCO...

Documents