®
JD Edwards EnterpriseOne: The Complete Reference
About the Authors
Allen Jacot is a leading industry expert on En...
411 downloads
4044 Views
29MB Size
Report
This content was uploaded by our users and we assume good faith they have the permission to share this book. If you own the copyright to this book and it is wrongfully on our website, we offer a simple DMCA procedure to remove your content from our site. Start by pressing the button below!
Report copyright / DMCA form
®
JD Edwards EnterpriseOne: The Complete Reference
About the Authors
Allen Jacot is a leading industry expert on EnterpriseOne with over 11 years of experience with the product. He frequently makes presentations at both Oracle Open World and Quest Collaborate. He is also a widely published author, having written two other books on the EnterpriseOne product. Allen started working with the EnterpriseOne product in 1996 when he worked on the beta release of the product for JD Edwards. Currently Allen is the director of the CNC JD Edwards National Practice for Fujitsu Consulting. He lives in Denver, Colorado, with his wife, Kimberly, and his two daughters, Samantha and Alexandra. Joseph Miller is a Vice President in DHL Express US working as the head of the Marketing, Sales, and Services domain concentrating on IT systems and business solutions. Joe started work with the EnterpriseOne application suite in 1996 and has worked in a technical and project-consulting capacity with over 60 different implementations globally. Joe currently works and lives in Plantation, Florida, with his wife and two kids. Michael Jacot is a seasoned ERP consultant with 10 years of technical experience. During the course of his career Michael has had the opportunity to manage many different types of EnterpriseOne implementations, where he has been responsible for providing technical project leadership, advanced practice methodologies, and performance and tuning efforts, as well as lowlevel technical solutions. These project efforts have ranged from complex phased upgrades to the design and implementation of advanced technical architectures. Michael’s tenure has provided him the opportunity to work with accounts around the world. This experience has afforded him a view into how ERP implementations operate domestically as well as globally. The combination of these experiences allows Michael to truly enjoy the opportunity to assist clients in effectively applying technology to their business requirements. Michael Jacot is currently a Senior Principal Consultant for Oracle. John Stern is a highly accomplished senior-level IT executive currently serving as Chief Information Officer for a Fortune 1000 company with manufacturing, distribution, and retail operations. John is widely recognized as an industry leader in technology integration and has a track record of delivering impressive contributions to top- and bottom-line growth in a global market and a reputation for creating corporate value through the integration of IS&T, business processes, and people. Central to his 3-Core strategy is a focus on ERP.
About the Contributing Authors Sandra Holmes has 15 years of enterprise resource planning software experience, and 12 of these years are with JD Edwards software. She is a recognized industry expert with CNC. Sandra holds an electrical engineering degree from LSU. Jay Burtt is a certified Project Management Professional through PMI with over 15 years of JD Edwards implementation experience. His current responsibilities as Director of Project Delivery for Fujitsu Consulting include oversight of all consultants responsible for financials, HR/payroll, offshore development, and offshore CNC technology, as well as all project managers on every JD Edwards project in North America. Jay resides in Lake Kiowa, Texas, with his wife, Tracy, of 22 years and his two children. Alex Jorna is a Senior Sales Engineer at MicroStrategy and formerly worked at Fujitsu Consulting as Practice Director for the JDE BI practice, installing, maintaining, and enhancing BI solutions for customers running on JDE ERP. Alex was an integral part of the JDE BI concept, from its inception in 1999 thru 2005 while at Oracle as a development manager and technical lead for the BI solution that was developed and made available to JDE customers. Alex is originally from South Africa and has about 19 years of industry and BI experience reaching across country lines, database platforms, ETL, and analytical reporting toolsets.
About the Technical Editor Scott Watson has over 6 years of technical CNC experience for EnterpriseOne. During this time Scott has been involved with a variety of projects including installations, upgrades, and general support for a number of clients in a variety of industries. To complement his experience, Scott has a Masters in Computer Information Systems from the University of Denver and a B.S. in Financial Accounting from Colorado State University. Scott is currently a senior consultant for Fujitsu Consulting. He resides in Denver, Colorado, with his wife, Cheyenne, and their dog Bear.
This page intentionally left blank
®
JD Edwards EnterpriseOne: The Complete Reference Allen Jacot Joseph E. Miller Michael Jacot John A. Stern
New York Chicago San Francisco Lisbon London Madrid Mexico City Milan New Delhi San Juan Seoul Singapore Sydney
Toronto
Copyright © 2009 by The McGraw-Hill Companies. All rights reserved. Except as permitted under the United States Copyright Act of 1976, no part of this publication may be reproduced or distributed in any form or by any means, or stored in a database or retrieval system, without the prior written permission of the publisher. ISBN: 978-0-07-159874-3 MHID: 0-07-159874-X The material in this eBook also appears in the print version of this title: ISBN: 978-0-07-159873-6, MHID: 0-07-159873-1. All trademarks are trademarks of their respective owners. Rather than put a trademark symbol after every occurrence of a trademarked name, we use names in an editorial fashion only, and to the benefit of the trademark owner, with no intention of infringement of the trademark. Where such designations appear in this book, they have been printed with initial caps. McGraw-Hill eBooks are available at special quantity discounts to use as premiums and sales promotions, or for use in corporate training programs. To contact a representative please visit the Contact Us page at www.mhprofessional.com. Information has been obtained by McGraw-Hill from sources believed to be reliable. However, because of the possibility of human or mechanical error by our sources, McGraw-Hill, or others, McGraw-Hill does not guarantee the accuracy, adequacy, or completeness of any information and is not responsible for any errors or omissions or the results obtained from the use of such information. TERMS OF USE This is a copyrighted work and The McGraw-Hill Companies, Inc. (“McGraw-Hill”) and its licensors reserve all rights in and to the work. Use of this work is subject to these terms. Except as permitted under the Copyright Act of 1976 and the right to store and retrieve one copy of the work, you may not decompile, disassemble, reverse engineer, reproduce, modify, create derivative works based upon, transmit, distribute, disseminate, sell, publish or sublicense the work or any part of it without McGrawHill’s prior consent. You may use the work for your own noncommercial and personal use; any other use of the work is strictly prohibited. Your right to use the work may be terminated if you fail to comply with these terms. THE WORK IS PROVIDED “AS IS.” McGRAW-HILL AND ITS LICENSORS MAKE NO GUARANTEES OR WARRANTIES AS TO THE ACCURACY, ADEQUACY OR COMPLETENESS OF OR RESULTS TO BE OBTAINED FROM USING THE WORK, INCLUDING ANY INFORMATION THAT CAN BE ACCESSED THROUGH THE WORK VIA HYPERLINK OR OTHERWISE, AND EXPRESSLY DISCLAIM ANY WARRANTY, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. McGraw-Hill and its licensors do not warrant or guarantee that the functions contained in the work will meet your requirements or that its operation will be uninterrupted or error free. Neither McGraw-Hill nor its licensors shall be liable to you or anyone else for any inaccuracy, error or omission, regardless of cause, in the work or for any damages resulting therefrom. McGraw-Hill has no responsibility for the content of any information accessed through the work. Under no circumstances shall McGraw-Hill and/or its licensors be liable for any indirect, incidental, special, punitive, consequential or similar damages that result from the use of or inability to use the work, even if any of them has been advised of the possibility of such damages. This limitation of liability shall apply to any claim or cause whatsoever whether such claim or cause arises in contract, tort or otherwise.
This book is dedicated to our families, who provided the support and patience needed to complete this journey.
This page intentionally left blank
Contents at a Glance PART I
EnterpriseOne Explained—Inside and Out 1
The Future of EnterpriseOne and Fusion
...........................
3
2
EnterpriseOne Building Blocks
..................................
29
3
Solution Explorer
.............................................
93
4
EnterpriseOne Servers
5
Data Warehouse and Business Intelligence
. . . . . . . . . . . . . . . . . . . . . . . . . 181
6
Interactive and Batch Applications Defined
. . . . . . . . . . . . . . . . . . . . . . . . . 221
7
Packages and Their Delivery
8
Foundation Code
9
EnterpriseOne Kernel Architecture
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
PART II
System Administration and Troubleshooting 10
EnterpriseOne Specialty Applications
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
11
EnterpriseOne Security
12
EnterpriseOne Administrative Tasks
13
Printing in EnterpriseOne
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
14
Web Servers and Portals
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
ix
x
JD Edwards EnterpriseOne: The Complete Reference
15
Upgrade Tools and Rules
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
16
Optimizing EnterpriseOne for Your Business
17
Troubleshooting EnterpriseOne
. . . . . . . . . . . . . . . . . . . . . 725
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753
A
The EnterpriseOne Implementation
B
Offshore, Near Shore, and Remote Development Index
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783 . . . . . . . . . . . . . . . . . . 857
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 881
Contents FOREWORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii ACKNOWLEDGMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii PART I
EnterpriseOne Explained—Inside and Out 1
The Future of EnterpriseOne and Fusion . . . . . . . . . . . . . . . . . . . . . . . . . . . Definition and Difference Between Fusion Middleware and Applications . . . Fusion Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade Path to Fusion Applications ........................ Service-Oriented Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Integration Architecture .............................. Fusion Middleware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fusion Middleware Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 4 6 8 9 10 11 11 28
2
EnterpriseOne Building Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Some Information Necessary to Understand Data Sources ........ What Is a Data Source? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What Information Is Contained in a Data Source? . . . . . . . . . . . . . . . How Many Data Sources Do I Need? . . . . . . . . . . . . . . . . . . . . . . . . Data Sources and Their Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Now Back to the Question . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How Do You Set Up and Configure Data Sources? . . . . . . . . . . . . . . Architecture of the Data Source Revisions Window ............. Special Uses for Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Path Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Path Codes: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definition of a Path Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29 30 30 32 33 37 37 41 41 43 46 50 50 51
xi
xii
JD Edwards EnterpriseOne: The Complete Reference
Which Tables Are Used .................................. Adding a Path Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying the F9861 Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a Path Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definition of an Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tables Used for Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding an Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copying an Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting an Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . When to Create a Custom Environment . . . . . . . . . . . . . . . . . . . . . . . Object Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definition of the Object Configuration Manager . . . . . . . . . . . . . . . . Tables That Are Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What Really Happens When a Workstation Requests Data or Logic . What Happens When a Workstation Runs a UBE . . . . . . . . . . . . . . . How to Add OCM Mappings .............................. How to Copy OCM Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting an OCM Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Difference Between System and Server Map . . . . . . . . . . . . . . . . Changing the Mappings for Object Librarian Tables . . . . . . . . . . . . . Changing Oracle Parameters that EnterpriseOne Uses . . . . . . . . . . . . Revise Table and Data Source Overrides Screen . . . . . . . . . . . . . . . . Advanced Object Configuration Manager Operations . . . . . . . . . . . . Oracle EnterpriseOne Middleware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Middleware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . JDENET_N, JDENET_K, and JDEQUEUE . . . . . . . . . . . . . . . . . . . . . . JDEBase Middleware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Synchronous Versus Asynchronous Processing . . . . . . . . . . . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
51 52 63 66 66 67 67 68 70 70 70 71 71 72 72 74 76 80 80 80 80 82 84 86 86 86 87 88 89 90
Solution Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Basic EnterpriseOne Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Solution Explorer: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 HTML: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Main View: Left Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Main View: Right Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Task View Structure Explained – Solution Explorer . . . . . . . . . . . . . . . . . . . . 104 File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Tools Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Applications Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Contents
xiii
Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 How Task Views Interact with EnterpriseOne . . . . . . . . . . . . . . . . . . 119 Customizing an Existing Task View . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Adding a Custom Task View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Inserting an Existing Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Deleting a Task View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Modifying an Existing Task View . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Copying a Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Applying Roles to a Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Adding a Task Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Copying an Existing Task and Its Relationships to a New Task View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Deleting a Task Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Task Where Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Deleting Relationships When Multilevel Relationships Exist . . . . . . . 135 Delete a Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Task Translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Filtering Task Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Understanding Task View Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Changing a Role View of Task View . . . . . . . . . . . . . . . . . . . . . . . . . 140 Change Control and Task Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 4
EnterpriseOne Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Does the Platform Matter? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 The EnterpriseOne Deployment Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Deployment Server Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Does the Deployment Server Have to Do All That? . . . . . . . . . . . . . . 146 Rolling the Deployment Server into a Configuration . . . . . . . . . . . . . 148 Data Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Data Servers Defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Why You Would Implement a Data Server . . . . . . . . . . . . . . . . . . . . 152 How to Implement the Data Server Solution . . . . . . . . . . . . . . . . . . . 155 Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 App Servers Defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Uses for App Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 App Servers Pros and Cons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Application Server Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Making the Application Server Work for You . . . . . . . . . . . . . . . . . . 163 Enterprise Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Definition of an Enterprise Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Types of Enterprise Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 How to Add an Enterprise Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 When to Add an Enterprise Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
xiv
JD Edwards EnterpriseOne: The Complete Reference
Web Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Definition of a Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Setting Up a Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Special Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Collaboration Portal Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 The Windows Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 5
Data Warehouse and Business Intelligence . . . . . . . . . . . . . . . . . . . . . . . . . 181 The Business Case for Business Intelligence . . . . . . . . . . . . . . . . . . . . . . . . . 183 The Connection Between Data Warehousing and Business Intelligence . . . . 184 Data Warehouse Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Why Not Obtain the Necessary Data Directly? . . . . . . . . . . . . . . . . . . . . . . 185 Making Use of the Data Warehouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Options for Creating a Data Warehouse Solution . . . . . . . . . . . . . . . . . . . . . 188 Advantages of Starting Now . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Using the Right Data Warehousing Architecture . . . . . . . . . . . . . . . . . . . . . 191 Phase 1: Implement Initial Architected Data Mart . . . . . . . . . . . . . . . 192 Phase 2: Implement Additional Architected Data Marts . . . . . . . . . . . 193 Phase 3: Expand to Enterprise Architecture . . . . . . . . . . . . . . . . . . . . 194 Steps in the Development of a Data Warehouse . . . . . . . . . . . . . . . . 195 Best Practices for Next-Generation Data Warehouses . . . . . . . . . . . . 196 Using the Oracle Business Intelligence Suite of Products . . . . . . . . . . . . . . . 197 Oracle BI Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Oracle BI Presentation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Oracle BI Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Oracle BI Interactive Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Oracle BI Publisher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Oracle BI Briefing Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Oracle BI Delivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Oracle BI Office Plug-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Oracle BI Disconnected Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Oracle BI Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
6
Interactive and Batch Applications Defined . . . . . . . . . . . . . . . . . . . . . . . . . 221 Applications Defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Logic Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Application Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Taking a Peek Inside Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Interactive Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Forms: An Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Contents
Batch Application Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Walkthrough of Report Design Aid (RDA) . . . . . . . . . . . . . . . . . . . . . 235 Report Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Report Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Data Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Data Sequencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Processing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Batch Versions Versus Interactive Versions . . . . . . . . . . . . . . . . . . . . 240 Commonalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 7
Packages and Their Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 EnterpriseOne Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Centralized Versus Decentralized Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Standard Central Objects and Check-in Location . . . . . . . . . . . . . . . 246 Decentralized Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Workstation Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 Full Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Update Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Overview of Package Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Defining a Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 What Happens During a Package Build . . . . . . . . . . . . . . . . . . . . . . 261 Tables Used During a Package Build Definition and Build Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 Server Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 Full Server Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Update Server Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 Package Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 Deploying Client Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 Deploying Server Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 Troubleshooting Package Builds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 Troubleshooting Client Package Builds . . . . . . . . . . . . . . . . . . . . . . . 286 Troubleshooting Server Package Builds . . . . . . . . . . . . . . . . . . . . . . . 287 Package Build History Application . . . . . . . . . . . . . . . . . . . . . . . . . . 289 Troubleshooting Client Package Deployment . . . . . . . . . . . . . . . . . . 290 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
8
Foundation Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 Definition: What Is a Tools Release? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 When to Apply a Tools Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 Why to Apply a Tools Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
xv
xvi
JD Edwards EnterpriseOne: The Complete Reference
How to Apply the Tools Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 Backing Up Your Old Tools Release . . . . . . . . . . . . . . . . . . . . . . . . . 297 Apply the New Tools Release to the Deployment Server . . . . . . . . . . 298 Apply Tools Release 8.97 and Newer Using Server Manager . . . . . . 299 Upload the Tools Release into Server Manager . . . . . . . . . . . . . . . . . 299 Distribute the Tools Release to the Appropriate Server . . . . . . . . . . . 299 Have the Server Manager Install/Upgrade the Tools Release . . . . . . . 301 Tools Release 8.96 and Older . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 Building and Deploying an Update Package to Your Client Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 How to Test and Remove a Tools Release . . . . . . . . . . . . . . . . . . . . . 310 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 9
EnterpriseOne Kernel Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 What Is a Kernel? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 Overview of Kernel Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 A Closer Look at the JDENET_n Processes . . . . . . . . . . . . . . . . . . . . . 318 JDENET_k Kernel Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 How to Configure These Kernels . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 Strategies for Configuring Your Servers . . . . . . . . . . . . . . . . . . . . . . . 331 Monitoring EnterpriseOne Kernel Processes . . . . . . . . . . . . . . . . . . . 332 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 PART II
System Administration and Troubleshooting 10
EnterpriseOne Specialty Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339 Object Management Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340 Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342 Owners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 Allowed Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 Tokens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345 The Object Management Workbench Form . . . . . . . . . . . . . . . . . . . 347 Basic Search in OMW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 Behind the Scenes of OMW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 Data Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 Data Dictionary Defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 The Data Dictionary and Development . . . . . . . . . . . . . . . . . . . . . . . 357 Working with the Data Dictionary Application . . . . . . . . . . . . . . . . . 358 Data Dictionary Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 Wrapping Up the Data Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Contents
xvii
Media Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 Media Objects Defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 Imaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 Setting Up Media Objects in EnterpriseOne . . . . . . . . . . . . . . . . . . . 365 System Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369 Server Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 Server Map Defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 Tools Associated with Server Maps . . . . . . . . . . . . . . . . . . . . . . . . . . 371 Data Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 Control Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 Control Tables Defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 Next Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 User-Defined Codes (UDCs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 Data Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382 Job Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 11
EnterpriseOne Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387 Users and Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388 Defining Users and Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389 The Real Story on Users and Roles . . . . . . . . . . . . . . . . . . . . . . . . . . 397 Sign-on Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404 Sign-on Security Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404 Other Application Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412 Enterprise Server INI Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 Client Workstation INI Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416 Security Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416 Inclusive/Exclusive Row Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419 Application Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420 Action Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423 Row and Column Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425 Processing Option Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429 Tab Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433 Hyper Exit Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 Exclusive Application Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436 External Calls Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438 Solution Explorer Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440 Miscellaneous Security Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 Data Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 Push Button Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 Link Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444 Image Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444 Media Object Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
xviii
JD Edwards EnterpriseOne: The Complete Reference
Text Block Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446 Chart Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446 Publish BSSV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 Business Unit Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 UDC Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 Business Unit Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449 Transaction Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 Menu Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451 LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452 EnterpriseOne User Profiles in an LDAP-Enabled Environment . . . . . 452 Under the Hood of LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452 Single Sign-on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453 Third-Party Security Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 12
EnterpriseOne Administrative Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455 Server Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456 Server Manager Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457 Installing Server Manager Console . . . . . . . . . . . . . . . . . . . . . . . . . . 458 Configuring Server Manager for Your System . . . . . . . . . . . . . . . . . . 460 Server Manager Console Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487 Oracle Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494 Administering Different Servers with Server Manager . . . . . . . . . . . . 497 How EnterpriseOne Server Code Really Works . . . . . . . . . . . . . . . . . . . . . . 515 JDENet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517 Kernel Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519 User Overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521 Types of User Overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522 How User Overrides Are Created . . . . . . . . . . . . . . . . . . . . . . . . . . . 522 User Override Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526 The EnterpriseOne Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529 F91300, the Schedule Job Master Table . . . . . . . . . . . . . . . . . . . . . . 530 Setting Up the Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530 Scheduling Batch Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534 Adding a Job Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535 Trouble Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
13
Printing in EnterpriseOne . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545 The EnterpriseOne Printing Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547 A Quick History Lesson . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547 P98616 – EnterpriseOne Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548 Settings for Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567 Printing to a Comma-Delimited File . . . . . . . . . . . . . . . . . . . . . . . . . 569
Contents
xix
Importing and Exporting from EnterpriseOne Grid Forms . . . . . . . . . . . . . . . 571 Exporting from Grid—Ad Hoc Reporting . . . . . . . . . . . . . . . . . . . . . . 571 Importing to Grid—A EnterpriseOne Powerhouse . . . . . . . . . . . . . . . 574 Other Printing Options in EnterpriseOne . . . . . . . . . . . . . . . . . . . . . . . . . . . 579 Troubleshooting Printing in EnterpriseOne . . . . . . . . . . . . . . . . . . . . . . . . . . 580 Printer Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580 Printing with Third-Party Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582 XML Publishing – 8.97 – The New Frontier . . . . . . . . . . . . . . . . . . . . . . . . . 583 XML Publishing – An overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584 XML Publishing – A Deeper Look . . . . . . . . . . . . . . . . . . . . . . . . . . . 585 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601 14
Web Servers and Portals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603 E1 HTML Server, Formerly Java Application Server (JAS) . . . . . . . . . . . . . . . 604 Server Manager Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605 Architecture Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605 Installing EnterpriseOne HTML Code Using Server Manager . . . . . . . 605 WebSphere vs. Oracle Application Server . . . . . . . . . . . . . . . . . . . . . 608 Definition of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609 Oracle Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610 Installation of EnterpriseOne using OAS . . . . . . . . . . . . . . . . . . . . . . 610 WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625 Portal Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635 Oracle Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637 IBM Collaborative Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
15
Upgrade Tools and Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655 Differences Between Upgrades and Updates . . . . . . . . . . . . . . . . . . . . . . . . 656 JD Edwards Methodology for Updates and Upgrades . . . . . . . . . . . . 657 Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658 Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660 Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663 Basic Parts of an Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663 EnterpriseOne Minimum Technical Requirements for Windows NT Enterprise Servers . . . . . . . . . . . . . . . . . . . . . . . . 665 Backup Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669 When to Roll Back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672 Impact on Your End Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675 Nuts and Bolts of an Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675 Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715 Table Conversions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715 Control Table Merges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716
xx
JD Edwards EnterpriseOne: The Complete Reference
Environment Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716 Specification Merge Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716 Electronic Software Updates (ESUs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718 Retrofitting Modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719 Running in Parallel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719 Running Two Separate Releases of EnterpriseOne in Parallel . . . . . . 720 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723 16
Optimizing EnterpriseOne for Your Business . . . . . . . . . . . . . . . . . . . . . . . 725 When to Optimize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726 Understanding the Jigsaw Puzzle . . . . . . . . . . . . . . . . . . . . . . . . . . . 726 The Five-Step Optimization Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . 728 Step 1: Optimize the OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 728 Step 2: Optimize the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730 Step 3: Optimize the Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732 Step 4: Apply Process Redesign . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733 Step 5: Apply CNC Concepts Where Available . . . . . . . . . . . . . . . . . 736 Summarizing the Five-Step Optimization Process . . . . . . . . . . . . . . . 738 Creating Multiple Queues on a Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738 Multiple Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739 Why Add Queues? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740 The Required Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740 Tuning the JDE.INI Kernels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744 Multithreaded Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745 Optimizing the Kernels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745 Tuning the Web Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746 The Apache Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747 The Web Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747 The EnterpriseOne JAS Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
17
Troubleshooting EnterpriseOne . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753 Performance Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754 Setting Up to Use the Performance Workbench . . . . . . . . . . . . . . . . 754 Analyzing Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755 Performance Workbench Do’s and Don’ts . . . . . . . . . . . . . . . . . . . . 760 Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761 Server Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761 Server Debug Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764 UBEDEBUG.LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766 Platform-Specific Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768 AS/400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769 UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777 Intel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782
Contents
A
xxi
The EnterpriseOne Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783 The Software Selection Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784 Preparing to Make the Move of a Lifetime . . . . . . . . . . . . . . . . . . . . . 785 Do You Understand Your System Requirements? . . . . . . . . . . . . . . . 786 Are There Any Existing Products That Already Fit the Bill? . . . . . . . . . 786 Create the Request for Proposal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787 Reviewing the RFP Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787 What Are Your Current Technology Skill Sets? . . . . . . . . . . . . . . . . . 788 Can You Afford the Move at This Time or Can You Afford Not To? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 788 Things to Know About the Contract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789 It’s a License—You Didn’t Purchase It . . . . . . . . . . . . . . . . . . . . . . . . 789 Hiring Consultants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789 System Audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 791 Phases of the Technology Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . 791 Events Associated with a Technology Implementation . . . . . . . . . . . . 791 Phase 4: EnterpriseOne Architecture Modeling . . . . . . . . . . . . . . . . . 797 Phase 5: Pre-Go-Live Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799 Phase 6: Go-Live Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800 Phase 7: Continuing Technology Support . . . . . . . . . . . . . . . . . . . . . 800 The EnterpriseOne Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801 Before You Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801 Sizing Your Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803 Purchasing the Hardware and Software . . . . . . . . . . . . . . . . . . . . . . . 804 Preinstallation Audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804 The Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805 The Postinstallation Audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805 Wrapping Up the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806 Modeling Your Solution (Phases of the Application Implementation) . . . . . . 806 From the Application Point of View . . . . . . . . . . . . . . . . . . . . . . . . . 807 From the Technologist’s Point of View . . . . . . . . . . . . . . . . . . . . . . . 809 Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811 Core Implementation Team Training . . . . . . . . . . . . . . . . . . . . . . . . . 811 End-User Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812 Continued Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814 Development and Version Control Methodology . . . . . . . . . . . . . . . . . . . . . 814 How to Use This Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814 Can You Separate Development and Version Control? . . . . . . . . . . . 815 Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815 Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821 Go-Live Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829 Application and Technical Audits . . . . . . . . . . . . . . . . . . . . . . . . . . . 830 Final User Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
xxii
JD Edwards EnterpriseOne: The Complete Reference
Software Package Builds and Deployments . . . . . . . . . . . . . . . . . . . . 832 Final Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833 Real-Time Data Conversions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833 Flipping the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834 What Now? (Maintaining the Value of Your System) . . . . . . . . . . . . . . . . . . 834 Globalization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834 Single or Multiple Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835 Unicode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835 EnterpriseOne Languages at Tier Levels 1–3 . . . . . . . . . . . . . . . . . . . 836 Global Development Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 839 Localizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840 Application and Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . 843 Interoperability and EnterpriseOne . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844 Electronic Data Interchange (EDI) . . . . . . . . . . . . . . . . . . . . . . . . . . . 844 Interfaces and Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 852 e-Opportunities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855 In Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855 B
Offshore, Near Shore, and Remote Development . . . . . . . . . . . . . . . . . . . . 857 Are Managed Services Right for You? The Question of Outsourcing . . . . . . . 858 The Basics of Managed Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 858 Ten Simple Rules of Managed Services . . . . . . . . . . . . . . . . . . . . . . . 859 Quick Case Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865 Managed Services Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866 Managed Services – Development Activities . . . . . . . . . . . . . . . . . . . 866 Managed Services – Technology Activities . . . . . . . . . . . . . . . . . . . . 867 Managed Services – Hosting of Your System . . . . . . . . . . . . . . . . . . . 869 Managed Services – Maintenance Contracts . . . . . . . . . . . . . . . . . . . 870 Pros of Managed Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871 Cons of Managed Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871 The Resources Available via a Managed Services Offering . . . . . . . . . . . . . . 872 Offshore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872 Near-shore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873 Onshore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 874 Remote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875 Onsite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876 A Quick Example of Costs for Onshore Resources . . . . . . . . . . . . . . . 876 Assessing Risk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876 Understanding Risk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876 An Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 878 Risk Mitigation Strategy Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 878 Wrapping IT Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 879
Index
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 881
Foreword Working for an organization that has utilized JD Edwards’ software for 20 years has allowed me to better appreciate the evolutionary process that has resulted in EnterpriseOne Version 8.12. TETRA Technologies, Inc. implemented its first instance of JD Edwards’ software in 1988 and, subsequently, maintained and upgraded it with successive versions, culminating in an implementation of World 8.1 that did a good job of supporting much of the Company’s business well into 2007. This longevity was possible, because, as TETRA grew from a small product manufacturing company into a much larger diversified products and services company, its JD Edwards software could be readily configured to address new lines of business. In 2004, when TETRA acquired a Scandinavian operating unit, international business activities grew exponentially. With this acquisition, it was determined that the best option was to continue down the JD Edwards evolutionary path and implement EnterpriseOne 8.9. This implementation was accomplished in 90 days! The flexibility of JD Edwards EnterpriseOne, coupled with a working knowledge of JD Edwards World 8.1 which was applicable to an understanding of EnterpriseOne, in no small way helped to make this very rapid deployment possible. The most significant challenge associated with this implementation was not that of configuring it to address specific business needs, but rather that of making a client-server application perform adequately on an international network. In 2006, further acquisitions and organic growth led to TETRA’s decision to upgrade from dual World 8.1/EnterpriseOne 8.9 instances to a single instance of EnterpriseOne. Given the success achieved over the years following the JD Edwards evolutionary trail, the decision was made to deploy EnterpriseOne version 8.12. Throughout this project, knowledge of World 8.1 and EnterpriseOne 8.9 was valuable and applicable to configuring EnterpriseOne 8.12—further evidence of the resilience of the underlying system design and JD Edwards’ adherence to an evolutionary path. This path also encompasses the underlying technologies used in conjunction with JD Edwards’ software. Version 8.12 is now HTML web-enabled, allowing our users to securely access TETRA’s EnterpriseOne implementation from anywhere they can get Internet connectivity.
xxiii
xxiv
JD Edwards EnterpriseOne: The Complete Reference
JD Edwards is known for its loyal customer base—a loyalty that has been earned over time by virtue of delivering a solid product that can be configured to address a multitude of business requirements before incurring the need to customize. These qualities allow JD Edwards’ customers to more easily address business requirements, while maintaining a current implementation of the software, thus receiving the benefits of improved vendor support, system functionality, and technology advances without the attendant burdens of customization and/or less than optimal business solutions. A point that is often made about Enterprise Requirements Planning (ERP) Systems, in general, is that they are monolithic and, thus, very hard to implement and maintain. JD Edwards has significantly mitigated this issue by developing their software utilizing a modular, Services Oriented Architecture. This quality allows a new JD Edwards customer to implement the software and functionality they need today with the knowledge that they can add modules and functionality as they are needed. This feature is a significant value proposition for a company that anticipates the need to grow and scale over time. When one looks across today’s packaged ERP market landscape, the first thing that becomes apparent is the limited number of vendors who offer true Enterprise capability. Although there are several vendors who claim to provide ERP systems, not all do. A true Enterprise Requirements Planning system must not only support basic financial activities, but also enable a broad range of underlying business processes (e.g., Planning, Manufacturing, and Job Costing), while capturing and reporting key metrics needed to effectively manage business. Today, there are very few ERP packages that can deliver such; and when you add the requirement of being highly configurable “out of the box,” the list gets very short, but most certainly includes JD Edwards EnterpriseOne. Regarding the future of ERP systems, there is some amount of discussion around the development of the Business Process Execution Language (BPEL). With a BPELenabled ERP system, a business process defined in BPEL format would “autoconfigure” the ERP implementation to enable support of the business process. When, not if, this technology is made available, JD Edwards’ evolutionary history serves to point out that if EnterpriseOne 8.12 is not BPEL-enabled, its descendent will be. For all the above reasons, whether you are considering the acquisition of a new ERP system or desire to maximize your existing JD Edwards investment, you should gain as much information about JD Edwards EnterpriseOne’s functional and technical capabilities as you can. I know of no better way to do so than to read JD Edwards EnterpriseOne: The Complete Reference. —Michael B. Lobin V.P., Information Technology TETRA Technologies, Inc.
Acknowledgments We would like to thank the following people: ■ This book would not have been possible without the support of Nancy Littlejohn and Kevin Sullivan. Nancy, thank you for working with us on schedules, deadlines, and always being a sounding board. ■ A special thanks to Clayton Seeley for providing excellent technical insight and ensuring we were really explaining the web and portal. Clayton’s attention to detail was critical in ensuring specific items were thoroughly explained. ■ Brett Mcgarity for his insights and suggestions in explaining the underpinnings of the EnterpriseOne Kernel processess. Brett was a constant source of information and an invaluable sounding board for this process. ■ Michael Guerra for his excellent suggestions, ideas and all around ability to look at things from all sides. Michael’s views helped shape the type of information we wanted to deliver to our readers. ■ The team at McGraw-Hill (Lisa McClain, Patty Mon, Vastavikta Sharma, Margaret Berson, Paul Tyler, Jack Lewis, Mandy Canales, Jennifer Housh, and many more) who worked tirelessly to ensure this project was a success. ■ Sheila Cepero for all her help with contracts and tracking down information for our chapters. Thank you so much for your patience and dedication to this project. ■ We would also like to thank Ed Abbo, Lenley Hensarling, Steven Reeter, and Steve Schaffer for helping us involve some outstanding resources from Oracle. Without the use of the extremely talented individuals, we would not have been able to deliver some of the great information that our readers expect. Thank you for your support of this project. ■ Finally a special thank you to Scott Watson who provided great insight as the technical editor of this book, but also ensured he got all his edits in even though he had his wedding in the middle of the project. Thank you Scott for your dedication and many thanks to your wife Cheyenne for her patience and understanding.
xxv
This page intentionally left blank
Introduction
Greetings, fellow travelers along the quest we call enterprise resource planning. It is a pleasure to see that you are on this journey, are contemplating this journey, or are just plain bored and thought this book would interest you. This book was almost a year in the making, and we hope our efforts have produced a book that will interest you, entertain you, and provide you with deeper insight into Oracle’s JD Edwards EnterpriseOne ERP suite of products. It has been a pleasure for us to bring it to you. The combined experience of the authors includes over 30 years of EnterpriseOne technology and implementation experience. We have pushed ourselves to show both the good and the bad, and though we have occasionally disagreed on specific content, we are all in agreement that this book will benefit every organization that is in the process, has completed this process, or is contemplating the process of implementing EnterpriseOne. One of our specific goals has been to ensure that the novice and experienced practitioner alike can read, understand, and get something out of these pages. We have it on good authority (and yes, we did test it) that it will benefit you and your organization. One of the key goals of this book is to provide not just the “how” associated with various setups within EnterpriseOne, but the “what” as well. After all, in this age of the Internet, information is readily available. But information is not knowledge, and knowledge is what we, the authors, sought to impart.
How to Use This Book This section was difficult for the authors to agree on because there are simply a huge number of ways to use this book. In the simplest of terms, the book can act as a reference where you look for specific answers or information. By using the appendix or the glossary, you can quickly zero in on the information you need right now. Additionally, the book can be read from cover to cover, providing a general framework of information. The authors specifically laid out the book to provide building blocks of EnterpriseOne knowledge and then grow based on those blocks.
xxvii
xxviii
JD Edwards EnterpriseOne: The Complete Reference
Sections Within a Chapter We’ve added several unique sections into the layout of each chapter. All chapters start with an introduction (some are humorous and some simply attempt it). At the end of the introduction, you will see a list of the topics covered in the chapter. We won’t list every topic, just the main threads of discussion. Notes, Definitions, and Tables You will see a variety of notes, definitions, tables, and other special sections where we pull information from different sources to add to your overall understanding of the topics we are presenting. Additionally, we have added as many screen shots from the actual product and different supported platforms as we can. These screen shots have been picked not necessarily as duplicates of the examples provided (that is, the same information), but rather to assist you in understanding how the applications look and feel within the product. Parts of the Book The chapters in the book can be broken into two primary parts: an in-depth section with very technical concepts illustrating how the product works (especially under the GUI), and a section on administering, configuring, and manipulating the system to your company’s requirements. How you read the book is up to you, but we think that all of it is both informative and useful. Writing Style This book is written with an interactive style. Often, you will feel as if the authors are talking directly to you (or at least that is the feel we’ve been shooting for). We have tried to anticipate your questions. Many times, we actually write what we think you will be asking yourself while reading it. If we miss our mark, we hope our questions will address something you didn’t think to ask but wish you had.
The Authors’ Notes As mentioned, this book is the best compilation of the combined experiences of the authors’ 30 years of working with EnterpriseOne technology. We have tried to provide real examples wherever possible to help with your learning curve. We have changed or omitted the names of companies and other pertinent information, but the vast majority of the work comes from our personal experiences working with and implementing the EnterpriseOne product at real client sites. And again, we hope that you will find it both useful and educational. Going forward, we thought that it would help if you understood some of the background of the company bringing you the EnterpriseOne product and the history of that product itself. Take a couple of minutes and read through these pages to gain a better understanding of who they are and where they came from.
Introduction
A Little Company on the Prairie
xxix
If you have worked with JD Edwards for any amount of time, you will probably hear them referred to as “the little software company on the prairie.” This company really did start out as a little software company. Three people with a vision came together to create JD Edwards: Jack Thompson, Dan Gregory, and Ed McVaney. Each of these founders lent a small part of their names to create JD Edwards. When the company was first started, it designed custom business software for small and medium-sized companies. Eventually, JD Edwards focused on the IBM System/38 and began creating business application suites. It was this focus that allowed JD Edwards to create their CASE software development and design tool. This design tool gave the company consistency across the range of their integrated applications. As the company rolled through the 1980s, they really began to grow. This is when JD Edwards started to open branch offices around the country. In the late 1980s, the decision was made to start concentrating on international expansion. To kick off this international growth, the company opened a European headquarters in Belgium (the European headquarters was later moved to the United Kingdom) and soon followed with a series of offices around the world to now encompass North America, South America, Europe, and Asia. It soon became apparent from the company’s incredible growth that they would either need to remain a small software company on the prairie servicing customers on an individual basis or they would need to break out as an industry leader, providing a software package that would meet the needs of many different companies. This is how the WorldSoftware suite was born. This software helped JD Edwards become recognized as an industry-leading supplier of applications software for the IBM AS/400. JD Edwards has enjoyed great success with the WorldSoftware suite. However, this is a company that is used to being an industry leader. So as the industry started to move to client/server solutions, JD Edwards responded. In August 1996, OneWorld (the original public name of the EnterpriseOne software) was brought to the market. This software again allowed the company to achieve a technological breakthrough. JD Edwards was not interested in just meeting industry standards; they wanted to go beyond them and remain an industry leader in the enterprise software market. EnterpriseOne has allowed the company to do this. This software is highly configurable and runs on a variety of different platforms. It also has an integrated toolset that gives Oracle’s JD Edwards customers the ability to modify the software to meet their business needs. As customers’ business needs change, the EnterpriseOne software is flexible enough to change with them. After all, this is what Oracle does best: meet their clients’ business needs. Ed McVaney, one of the company’s founders and a driving force for the EnterpriseOne software, has been quoted as saying, “We believe our first job is to solve your business problems. Nothing else counts if we don’t solve your business problems.”
xxx
JD Edwards EnterpriseOne: The Complete Reference
As a company in 2003, JD Edwards knew it needed to consolidate with another organization if it was going to continue its fast pace of growth and provide an everincreasing array of business solutions to the market. Major ERP competitors had come and gone due to their leadership’s lack of foresight. When Ed McVaney returned as CEO of JD Edwards in 2000 replacing then CEO Doug Massingill, he knew he would have to be willing to lead the industry to ensure the success not only of the product, but also of his customers. In 2003, JD Edwards was acquired by PeopleSoft in a move that shook the industry. Weeks after the announcement that PeopleSoft and JD Edwards would merge, Oracle tendered a bid on PeopleSoft itself. Though this was fought in court, the industry was ripe for consolidation and Oracle began an impressive run of software company acquisitions. As you can see, the little company on the prairie has become part of the industry leader. They have moved from providing enterprise resource planning software to providing e-business solutions. They continue to search for new ways to provide highly configurable solutions to their customers that will enable them to realize their own dreams.
PART
I
EnterpriseOne Explained— Inside and Out
This page intentionally left blank
CHAPTER
1
The Future of EnterpriseOne and Fusion 3
4
JD Edwards EnterpriseOne: The Complete Reference
W
e peer deeply into the EnterpriseOne magic crystal ball. We are looking into the future. Now if we really had a true, working magic crystal ball, we would be playing the lottery. Seriously though, there is an outstanding question in many people’s minds about where the industry is going. This is a fair question. Oracle has told the world that they will be releasing the Fusion Applications set in mid-2009. The tech stack on which Fusion Applications is being built is already available; you will hear this referred to as Fusion Middleware. This new product, Fusion Applications, is going to have some of the best functionality from the different products that Oracle has acquired. However, many customers have invested a lot of time, sweat, and money into their existing EnterpriseOne systems. These customers do not want to see their investment wasted. When Oracle first bought PeopleSoft, there was a lot of fear in the industry that EnterpriseOne was going to disappear. This caused the number of upgrades and new implementations to come almost entirely to a stop, at least temporarily. Oracle quickly realized not only how much customer loyalty there is in the EnterpriseOne space, but the amount of money that could be made by marketing this solution. So to put the customers at ease, Oracle introduced their lifetime support policy (Applications Unlimited Program). With this program, Oracle has committed to supporting certain EnterpriseOne releases without a stop date. Bug fixes and tax updates will stop after a certain number of years, but you will still be able to get support for these releases, providing you pay your maintenance contract! This bold move, which the authors applaud, has put the industry at ease, and more and more customers are moving to the newer releases of EnterpriseOne. However, what will Fusion Applications offer? What is it really? Can I use some of it with my EnterpriseOne system? These are the new questions that are on the minds of EnterpriseOne customers. In this section we are going to try to answer some of these questions. Now we do not have a crystal ball and also are not sitting in on Oracle’s board meetings. We are going to simply walk through what we see happening and the wonderful opportunities that EnterpriseOne customers can take advantage of in the next several years.
Definition and Difference Between Fusion Middleware and Applications
Let’s start out by clearing up some confusion that seems to be out there on Fusion. You see, there are two different prongs to the Fusion story. These are the Fusion Applications and Fusion Middleware. Often people hear “Fusion” and immediately think of the Fusion Applications that are scheduled to be released in 2009. However, that is only part of the story. There is a powerful set of tools called Fusion Middleware.
Chapter 1:
The Future of EnterpriseOne and Fusion
What is really the difference? The Fusion Applications will be an enterprise resource planning (ERP) software package. This software package will cover a variety of functionality for customers. This new application set is designed to be Service-Oriented Architecture–compliant. This means that it is standards based: Customers will be able to fill roles to support this product more easily as industrystandard skills will be required instead of just skills on proprietary tools. This also means that it will be easier to integrate with the Fusion Applications. This will allow customers to create a best-of-breed solution for their business requirements. Fusion Middleware is already out and available. This software allows for the integration of systems. It is basically the plumbing that you can put into place to have systems talk to each other. This middleware uses industry-standard technology. Some of this is Simple Object Access Protocol (SOAP), Business Process Execution Language (BPEL), and Web Services. Oracle has supplied hooks for Fusion into EnterpriseOne. This allows EnterpriseOne customers to “Fusionize” their solutions. You do not have to go to Fusion Applications to take advantage of some of the new Service-Oriented Architecture (SOA) functionality. We will discuss this in more detail in the “Fusion Middleware” section of this chapter. Prior to moving on to discuss the Fusion Applications, we need to stop for a moment and define some terms that you will hear throughout this chapter again and again. Understanding these terms is a requirement for being able to have a conversation about Fusion Applications and Fusion Middleware. Term
Definition
Service-Oriented Architecture (SOA)
A business-centric architectural approach that supports integrating business processes. This is a standards-based approach to architecture for integrating loosely coupled interactive services.
Business Process Execution Language (BPEL)
A programming language that allows you to extend your solution by hooking systems together through business processes. This language enables you to distribute your business process across multiple systems. This is also one of the standards that Oracle uses with its Fusion Middleware Suite.
Simple Object Access Protocol (SOAP)
A protocol that is used to move information in and out of web services. It is XML based and is also another industry standard that Oracle uses in its Fusion Middleware solution.
Extensible Markup Language (XML)
A language that allows developers to share information between applications. It is especially tailored for web applications. XML has been available in the industry for quite a while.
5
6
JD Edwards EnterpriseOne: The Complete Reference
Term
Definition
Web Service
An integration that uses standards, such as XML and SOAP, to integrate systems. An example of a web service might be a bank web page performing a loan credit check. The bank can subscribe to a web service, using these standards, and receive the information back into its system. Thus to the consumer it looks as if they never left the original system.
Web Service Definition Language (WSDL)
A language that is used to communicate what each web service can do. This can be thought of as a contract by the web service saying this is what I can do and what information I require.
Application Integration Architecture (AIA)
An integration platform developed by Oracle for integrating business processes that span application silos. AIA is a methodology as well as a product. Using the AIA methodology, businesses can build cross-application business processes that leverage the AIA toolset. AIA itself is built on the Fusion Middleware technology stack.
Process Integration Pack (PIP)
Industry-specific best-practice flows that have been prepackaged by Oracle and built on the AIA framework. Example: Order to cash flow spanning Oracle EBS and Siebel.
Middleware
Middleware can be thought of as the plumbing to get information from one system to another. Some examples of common middleware packages are BizTalk, TIBCO, and WebMethods.
Fusion Applications
The authors spent a lot of time and thought before including this section in the chapter. We felt we had to address this on some level. The only issue is that at the time of publication there is not a lot of information on exactly what the Fusion Applications will look like. Even at the large user-group event Collaborate of 08, there was not a lot of new information. This is really a timing issue. Oracle cannot discuss functionality until the quarter in which they are going to release the software, or they could get into a revenue recognition issue. This leaves the customers yearning for more information. In this section we are going to share everything that we can about the Fusion Applications. However, we encourage you to regularly visit Oracle’s web site to look for more information to be posted. To start, let’s cover what we know today. The Fusion Applications are a new product line, meaning a new ERP product that Oracle has stated will be released in 2009. This new product is based on
Chapter 1:
The Future of EnterpriseOne and Fusion
Service-Oriented Architecture and uses the middleware solution. You can see the “Fusion Middleware” section of this chapter for more information. This middleware solution exists today and can be used right now. The Fusion Applications will sit on top of this already-proven middleware solution. Although they have been holding information fairly close to the vest, Oracle has stated that Fusion Applications will contain a customer relationship management (CRM) solution. This solution will be based on Siebel’s CRM, which Oracle acquired recently. This is a good move on Oracle’s part as Siebel had a very strong CRM solution that they can now leverage. Since this is based on Fusion Middleware as well, customers can plug in different systems if they have the requirement. What else does Oracle have cooking on the stove for Fusion Applications? They have stated that they are reviewing all of the functionality from their current product lines. They plan to take the best of this functionality and place it into Fusion Applications. Oracle is also trying to bring the look and feel of their product lines closer together. They know that as people move toward Fusion or simply use Fusion Middleware to hook multiple systems together, they will want the end users to have a consistent experience across the system. This is a very exciting time in the industry, and to see Oracle so committed to a standards-based approach should appeal to a lot of their customer base. This standards-based approach will help to reduce the implementation costs and total cost of ownership for Oracle customers. With this in mind, many people ask what they can do today to prepare for the new Fusion Applications. To prepare, you can start to work with the Fusion Middleware product. The Fusion Applications will be sitting on top of this middleware product, so you will have a skill set that can be directly applied to Fusion Applications when you are finally ready to move to them. To do this you should be on a current release. As of 8.12 with foundation code 8.97, there is a lot of functionality coupled with the EnterpriseOne software. Some of this is business services, which are the way that EnterpriseOne publishes web services. These also are hooked directly into the Object Management Workbench, so that makes for easy promotion, deployment, and monitoring of the code line. Getting back to the point of the discussion about preparing for Fusion Applications, you also need to start evaluating your modifications and especially your integration points. See if there is an area where you can start to use business services instead of a point-to-point integration. This will help you to start down the road to fusion. If you have Fusion Middleware in-house, this is even better, as you can start to become familiar with BPEL Process Manager, Enterprise Service Bus, Oracle Web Services Manager, and Business Activity Monitor. These are all pieces of the Oracle Fusion Middleware. You can also consider using the prebuilt SOA pieces from Oracle. This is offered through their Application Integration Architecture (AIA). These Process Integration Packs (PIP) can help you to start the process into Fusion and the overall SOA approach to resolving your business requirements. AIA can be used stand-alone or in conjunction with a PIP, depending upon your needs.
7
8
JD Edwards EnterpriseOne: The Complete Reference
Your head might be swimming with the alphabet soup that you see when discussing an SOA product, such as Fusion Applications and Fusion Middleware. This is when you need to think of the old saying that you eat an elephant one bite at a time. Oracle has a vast offering to address many different business requirements. You should not try to jump into this all at once. Since it is standards based, you can pick and choose pieces to dip your toes into the Fusion pool and develop the skill sets in-house that you will need to implement the full set of Fusion Applications. This will help to reduce your implementation costs, risk, and overall level of discomfort during your move to Fusion Applications.
Upgrade Path to Fusion Applications Some of you out there are early adopters and cannot wait to get to the new Fusion Applications, or you may be thinking long term and you want to be sure you have a choice of staying on a newer release of EnterpriseOne software or moving to Fusion Applications. Well, you are in luck—Oracle is thinking about you with the product strategy. Oracle has identified releases in not only EnterpriseOne, but also in World software that will provide you a direct upgrade path to Fusion Applications. This does not mean that you have to move to Fusion Applications. It just gives you the option. Table 1-1 shows the upgrade path for EnterpriseOne. You will notice that there is a gap between OneWorld Xe and EnterpriseOne 8.11 where there is not an upgrade path to Fusion Applications. Now some folks are probably wondering why would Oracle go back and support OneWorld Xe for an upgrade path, but not 8.0, 8.9, and 8.10 which are newer releases? Well, there is definitely a method to the madness. You see, a significant part of the EnterpriseOne customer base is on OneWorld Xe or was on the Xe release when the decision for the upgrade path was made. However, this is not the only reason; Oracle was not going to leave their World software customers behind, so they went back and
Release
Upgrade Path to Fusion Applications
OneWorld Xe
Y
EnterpriseOne 8.0
N
EnterpriseOne 8.9
N
EnterpriseOne 8.10
N
EnterpriseOne 8.11
Y
EnterpriseOne 8.12
Y
EnterpriseOne 9.0
Y
TABLE 1-1.
Upgrade Path for EnterpriseOne Software to Fusion Applications
Chapter 1:
World Software Release
The Future of EnterpriseOne and Fusion
Fusion Applications Upgrade Path
A6.3 and earlier
N
A7.3
Y
A8.1
Y
A9.1
Y
TABLE 1-2.
World Software Fusion Applications Upgrade Path
created an upgrade path for World A7.3 release. Now those of you who have been working with OneWorld/EnterpriseOne for a while probably have already figured out where we are going. The data model for OneWorld Xe is the same as the data model for World A7.3. This is how coexistence was possible. The data model was officially first broken between OneWorld and World software with the ERP 8.0 release, although in reality 8.0 had very few changes in its data model. The first large data model change was ERP 8.9. This is why it was easy for Oracle to allow for an upgrade path for OneWorld Xe to Fusion Applications. They already had to do almost all of the work anyway for the upgrade path from World A7.3. This, combined with the number of customers on OneWorld Xe, made it an easy decision for Oracle. Since we brought it up, let’s briefly cover the upgrade path for the World software. Table 1-2 shows the releases that have an upgrade path to Fusion Applications.
Service-Oriented Architecture
Up to this point we have briefly touched upon Service-Oriented Architecture. This is the architecture that Oracle and other ERP software vendors are using in the industry. In this section we will take a little bit of time to step back and look at SOA not just from an EnterpriseOne point of view, but how it is affecting the industry. This will help to round out the discussion and provide you with better insight when diving deeper into the Fusion Middleware layer. Let’s start this discussion by stating that SOA is not specific to any one company. The concept of SOA is to have a world of services that can be subscribed to and used through different applications. This is really to get businesses to an information- and process-driven enterprise. This means that all of the information required for business processes is readily available. When a business gets to this point, it will not matter what system the information is in. You will no longer have isolated silos of data. A real-world example of this would be if you purchased multiple companies, that is, you are growing through acquisitions. You might inherit lots of different systems that you need to string together. With SOA you can grab all this data as you need it. You can also configure
9
10
JD Edwards EnterpriseOne: The Complete Reference
your systems to show this data through a single portal-type interface for your users. Although this sounds like a utopia, it is close to being achieved.
Application Integration Architecture
You cannot go to any Oracle user group meeting without hearing something about Oracle application integration architecture. The market does not sit still and thus the demands on the information technology departments also do not stand still. Very few companies get to start out with a blank slate. They inherit systems or acquire them when other companies are purchased. Most of the time, companies have point-to-point integrations with these systems. These point-to-point integrations are basically “poured in concrete.” This means that they are difficult to change and fairly inflexible. This adds risk to customers’ architectures and makes changes, such as upgrading one system, very difficult. Oracle believes they have a solution to resolve this type of issue. They want their customers to be able to show value to the business through very flexible and adaptable integration of systems. Their solution to this is AIA. This solution helps to reduce the complexity for your infrastructure to support your different integrations. How does it handle this? This is handled through standards-based code. This allows you to automate your business processes. Application Integration Architecture has three key components: These are industry reference models, Process Integration Packs, and prebuilt Service-Oriented Architecture with Fusion Middleware. The reference models are industry best practices that have been documented for your use. These models will help you to quickly move forward on your integrations. You don’t need to learn the hard way about what works and what doesn’t. Some of these hard-learned lessons have already been found for you. This will help you to reduce your time and effort when working with AIA. Application Integration Architecture also has what are called Process Integration Packs. These packs have been created for you by Oracle to integrate different Oracle products. You can then take a best-of-breed approach with different Oracle products. This means that you can use a preconfigured pack to map a business process across different systems, that is, Siebel to E-business, for example. With these integration packs your modifications are greatly reduced as are your implementation times. Most of the time you will still need to do some configuration to tweak these packs to your specific business requirements. You will need to contact Oracle to see what packs are available for your different requirements. It is important to check the versions of the Oracle product that are supported by a PIP. PIPs tend to be product- and version-specific. Finally, you can also leverage prebuilt SOA integrations levering Fusion Middleware. This allows you to reduce your implementation time by using these standards-based pieces of code. This makes them not only extendable, but highly reusable. Another reason that these prebuilt SOAs are important is that they reduce the number of mappings that you need to configure when setting up your
Chapter 1:
The Future of EnterpriseOne and Fusion
integration points. The less mapping you need to do, the less cost and also less risk since you have less custom code.
Fusion Middleware
Now that we have talked about the Fusion Applications and the upgrade path to move to them, let’s talk about the Fusion Middleware. This functionality is available now to EnterpriseOne customers. In this section we are going to talk about what Fusion Middleware really is, why you would care, and how you can leverage it to expand your EnterpriseOne solution. Let’s start with what Fusion Middleware is. It is exactly what it sounds like, a middleware solution, and much more. Middleware is software that allows you to integrate systems and move data from one point to another. The Fusion Middleware is based on SOA. This means that it is a standards-based solution. You will also hear Oracle refer to this technology as Oracle Fusion Middleware – SOA Suite. This is because there are different pieces of the Fusion Middleware that you can use. We will cover these in detail in the “Fusion Middleware Architecture” section. However, briefly, these parts are ■
Monitoring optimization
■
Internet/access
■
Orchestration
■
Gateway
■
EnterpriseOne Tools–Business Services
Fusion Middleware Architecture Let’s talk about the actual architecture that makes up Fusion Middleware. To do this we are going to break things down into smaller chunks. These groupings or chunks will make things much easier to understand. We are going to talk about the Oracle Fusion Middleware – SOA Suite, presentation layer (HTML or Portal), and finally the tools in JD Edwards EnterpriseOne.
Oracle Fusion SOA Suite The Oracle Fusion Middleware – SOA Suite consists of several layers. You do not need to use all of these layers in your solution. This means that you can select the layers that your company needs. It also means that Oracle is not locking you into using their total solution. You can use other middleware and still take advantage of Fusion functionality in EnterpriseOne. We will explain this in greater detail when we talk about Business Services for EnterpriseOne.
11
12
JD Edwards EnterpriseOne: The Complete Reference
Right now let’s say you have a web service that you are publishing. If that is the case, you will need software to function as the gateway. This gateway will provide event routing, security, logging, and failover capabilities. The Oracle solution for this gateway is the Enterprise Service Bus and Web Services Manager software. This software allows you to configure message routing between different systems. You can also set up the system to have guaranteed message delivery. With guaranteed message delivery, the messages are stored on a server so that if something fails they can be retransmitted. This is also where you can configure how many systems you want to send certain messages to. Let’s talk about a real-world problem. Let’s say you are a company that has grown through acquisition. You have five different distribution centers all currently running five different warehousing programs, but you want the clerks taking your orders through the EnterpriseOne sales order application to be able to see, reserve, and relieve inventory from any of these distribution centers. You also want this to be in real time, as customers are on the phone, and the message has to get through, so you would want guaranteed delivery. To do this you can use a web service out of EnterpriseOne. This service can be called from the HTML sales order screen during an order entry activity. You would then use your Web Services Manager and Enterprise Service Bus to configure which distribution sites “subscribe” to this type of web service. There may be conditions where only three of the distribution centers would subscribe to a specific web service, for example, a specific type of configured order that only three distribution centers out of the five could handle. Continuing with our real-world example, you need something to orchestrate your business process. It is not always as simple as data in and data out. Decisions may need to be made. For example, do you allow items to be backordered? Does another system need to be used in the process as well? This can be handled through the BPEL Process Manager. This software lets you map out the entire business process, pulling in web services as required. When you look at this software the business process looks like a flowchart. This makes the programming fairly simple as well as standards based. Also in the orchestration layer you can handle data mapping if required. In our example we have multiple warehouse systems, which may have different field lengths for things like order number. Suppose in one system the order number is split across two fields and in another it is in a single field. You can set up rules to handle this through your orchestration layer. Thus you do not have to go in and change the data model for your systems. The ability to “float” above the system data model like this is very powerful and can help to keep development costs down. So in our example we now have a process that goes out and validates item availability from different distribution centers and sends the data back to EnterpriseOne in real time with guaranteed delivery. There is really nothing else out there to look at, right? Wrong. Once you have a system, you are going to want to know how it is performing and also to monitor it for issues. In Oracle’s solution this
Chapter 1:
The Future of EnterpriseOne and Fusion
is their Business Activity Monitoring (BAM) software. This allows you to monitor your business events. In this section we have covered a lot of ground. We have talked about gateway, orchestration, monitoring, and other key concepts. Figure 1-1 shows you a visual representation of the different pieces of the Oracle Fusion Middleware – SOA Suite. This will help to show how the different pieces fit together.
Enterprise Service Bus and Web Services Manager The first question many people have is, what is an enterprise service bus? This is software that can move data from multiple endpoints. These points do not need to be within the enterprise. The software can not only move data, but also provide orchestration, meaning that it can transform and route data as well. If you look at the high-level architecture of the enterprise service bus, you will see that you will have an Enterprise Server Bus (ESB) server, console, metadata server, and of course the hook into JDeveloper. Let’s start by talking about the
Monitoring & Optimization
Business Activity Monitoring
Client Presentation Layer
This layer is where you can call the business process
Portal
Orchestration
Process Flow Logic is handled here
BPEL PM
Gateway
Event Routing
Security and Logging
Failover
Enterprise Service Bus
E1 Tools
Oracle Fusion Middleware – SOA Suite
WSDL
Business Services
XML
SOAP
HTML Application
FIGURE 1-1. Oracle Fusion Middleware – SOA Suite architecture diagram
13
14
JD Edwards EnterpriseOne: The Complete Reference
Enterprise Service Bus. This server lets you interpret Web Services Definition Language (WSDL). It can also handle SOAP and HTTP. Under the hood of this server you have built-in integration services. This is very powerful as it can handle routing information as well as transformation. Although you won’t really see the underpinnings of ESB as a user, you hook directly into it using JDeveloper. The next piece of the architecture to the Enterprise Service Bus is the ESB metadata server. This server holds your metadata information. This type of information handles your transformations and routing rules. This is how the ESB server knows where to send specific messages.
BPEL Process Manager We have been spending a lot of time in this chapter talking about standards. The BPEL Process Manager is another extension of the Oracle offering so that their customers can leverage industry standards. BPEL stands for Business Process Execution Language (BPEL). The Oracle BPEL Process Manager is a Fusion Middleware product that allows customers to easily model, publish, and manage BPEL processes. This allows customers to configure their business processes using this tool. Since the authors are not full-time developers, they will be the first to tell you there are always some tricks of the trade that developers use. However, Oracle actually allowed us to get our hands dirty with the BPEL Process Manager. This tool has a very easy-to-use interface. You can map processes, which will show up like a flowchart in the tool. Even for us folks who have not coded for more years than we care to admit, it was fairly easy to open up and start working with the tool. The thing to keep in mind is that you are automating a process with this tool, which is why you can see the process flow in the tool. You can have an exception to handle. On the Oracle web page Oracle gives a great example of a load application as a BPEL process being worked on with a BPEL Process Manager. In the process flow they invoke a credit rating check; this would be another web service they are subscribing to. They then obtain quotes from multiple sources. These allow for the lowest rate to be shown. This is a simple example, but a very good one. The authors highly recommend you review this example in Oracle’s BPEL 101 Tutorial on their web site. It gives you a nice high-level feel for what you can accomplish with this tool. NOTE The BPEL Process Manager is loaded into the JDeveloper software. So you can call this right from JDeveloper.
Chapter 1:
The Future of EnterpriseOne and Fusion
So what are some of the cool features of this software that all the developers will love? Well, very quickly this software allows you several key items, such as: ■
Direct integration into JDeveloper
■
Native BPEL support
■
Debugging for BPEL
■
Incorporated integration services
■
Oracle BPEL Server
■
Capability of synchronous and asynchronous messaging
■
Side-by-side versioning
■
Capability of handling large XML documents
■
And as they say on TV, much, much more
Business Activity Monitor When you have your integration configured and set up, you still need the ability to see what is happening. It is also great if this can be real-time information in a dashboard type of view. The Oracle genie says “wish granted,” in a loud booming voice. This is where Business Activity Monitor (BAM) comes into play. This software is a part of the Fusion Middleware solution offered by Oracle. This means that you can use this software with different ERP products; you are not simply tied into EnterpriseOne. So let’s talk about some of the real-world requirements again. Let’s say you are a manufacturing firm with one ERP solution for distribution and a different one for manufacturing and advanced warehouse. The theme nowadays is that we have to be more nimble and do more with less. So how can you improve your inventory accuracy for your warehouse? How much do you need to manufacture for next month or even next week? This is where BAM really shines. This tool is very new to the EnterpriseOne customers. However, it is not new to the Oracle software arsenal. This solution has been available and used with other Oracle products throughout the world. This is very good news for EnterpriseOne customers. This means that the software has been through real paces with real customers in the industry. Oracle has simply extended this functionality, through Fusion Middleware, to EnterpriseOne customers.
15
16
JD Edwards EnterpriseOne: The Complete Reference
Business Activity Monitor Components This software solution is built of different components or layers. It is these components that work together to provide users with real-time analytical information for decision making. These components are ■
Data integration
■
Data caching
■
Analytics
■
Monitoring
■
Alerting
■
Reporting
In this section we are going to talk at a high level about each of these components. With this understanding, you will be able to better understand how you can use this software to monitor your business processes and alert you to changes so that your business can react to them. TIP You will need to refer to the Oracle web site to obtain current release and minimum requirements information. Let’s start the discussion with data integration. This is exactly what it sounds like, a data integration engine. This engine allows you to capture data and feed it into the data cache. This component or piece of BAM will also be referred to as EnterpriseLink. With this integration engine you can pull data from a multitude of locations. You can use web services, message queues, XML sources, and even relational database queries from data warehouses. As you grab the data you can move it and even transform it as required. Since not only real-time data, but historical data, can be looked at, this gives the software the ability to generate alerts, since real-time data can be compared to historical data. This is very powerful as it allows you to quickly identify and respond to trends in your business processes. Active data cache is another component of BAM. This is actually a system that is designed to support monitoring and active data. What does that mean? What this means in plain English is that the data is put into a form for the end user, after being extracted from the system being monitored. This data is then kept in sync with those systems so that the data does not get stale.
Chapter 1:
The Future of EnterpriseOne and Fusion
Let’s take a look at another real-world example. Suppose your company is a manufacturing firm that has multiple systems, such as distribution, manufacturing, and advanced warehousing systems. With the active data cache you can keep all of the data you need from these systems in sync and organize the data in a form that works for your business. So let’s say you are manufacturing and some of your materials are perishable or lose potency over time. You can actually use a solution like this to see how much of this material you have on hand and when it will drop in its potency. So this is presented to your users in a manner they understand and that works with your business process; thus you can make good decisions and avoid losing money on material going to waste. Any time you are monitoring data, analytics become very important. So you will hear the term event engine used with BAM. Basically this component allows the system to see complex data streams and make “decisions” based on rules. Then a specific action can be taken such as a work flow message or perhaps even more complex actions. It is important to do some careful analysis of your business processes when defining the rules for the software. Finally, let’s touch upon monitoring, reporting, and alerting. We have already discussed some of the monitoring and alerting in this section. Based on rules you define, you can configure alerts to be sent to your users. So let’s talk about reporting. In BAM you have what is called the active report engine. These reports can be generated in a variety of different types. Some common types of reports are on key performance indicators. These reports tell you how key pieces of your business are performing, such as your warehouse accuracy. This is also extremely current data as the engine obtains a shot of the data, then can display to the client requesting the data. This allows for up-to-date reporting through BAM. Prior to closing this section, let’s briefly talk about the different client types you can use. After all, we just went through all of the components, that is, the under-thehood pieces, so let’s take a second to talk about the clients that the users would see. You have two options with BAM, a thick client and a thin client. On the thin client you can use the active viewer to display reports. If you are a power user you can use the Active Studio on the thin client. This allows you to actually create and edit reports. The user can also publish reports out to users or set them up to run at specific times. Another tool for a thin client user is the BAM Administrator. This is used by the system administrator to administer and configure the system. This includes setting up security and users. The final tool we will talk about is the BAM Architect. This is another feature that can be used by a thin client. It is used to define data objects for the active data cache so the reports can be used against this data. This is the tool that allows you to define how your data flows into the system and to configure the rules for how to work with that data, such as performing a data transformation.
17
18
JD Edwards EnterpriseOne: The Complete Reference
Monitoring a Business Process Now that we have talked about the details of the different components of BAM, let’s move back up to a higher-level discussion. This is about monitoring business processes, a key function of BAM. The first question is, what are you going to monitor? This will need to be determined as you configure and architect your system, although most businesses will admit that they would like to monitor and orchestrate processes checking for performance indicators. However, very few are actually performing this type of process monitoring today. The reasons for this disparity in monitoring will not really be surprising to you. Most companies have different business processes across divisions and have inherited a lot of different systems along the way. This makes it difficult to monitor business processes across the enterprise. This is the problem that BAM attempts to address. This software allows users to monitor both structured and unstructured processes. This allows businesses to monitor key performance indicators (KPIs) for their business. This makes the data usable for the business and also in a format that makes sense to the business. If the data is hard to sift through and understand, you will not get a lot of users using the data to make decisions. That is why it is so important that the data be up to date and in a format that the users understand. It is not good enough to just identify an issue; there must be a correlation to what is causing the issue. Users need the ability to see what is causing problems, not just that orders are delayed. For example, suppose you are not receiving shipments on time from one of your transportation vendors. The decision makers in your organization need to see that this is the reason items are on back order, not just the fact that items are on back order. This allows for real business decisions to take place.
EnterpriseOne Tools Once you get outside the walls of the EnterpriseOne application, there are a lot of things that you can do. You are probably asking yourself: Is it hard to punch a process out of EnterpriseOne and take advantage of all this cool web services and SOA technology? If you have worked with the software for a while you are probably cringing, thinking you will need to use APIs. Well, take heart—Oracle has put Fusion Middleware technology right into the foundation code for EnterpriseOne. Things really started happening with the foundation code release of 8.95, which can be run on all 8.9 and higher releases of EnterpriseOne. In this foundation code EnterpriseOne was certified with Oracle BPEL Process Manager. They also introduced the web services gateway. Things kept moving with the foundation code release of 8.96. Oracle put out over 70 prebuilt integration points. These are features that you can use right away out of the box. They did not stop there. With the release of foundation code 8.97, you got the concept of business services. These are native web services in EnterpriseOne. They also certified the software with Oracle ESB. During the time this publication was being written, the latest foundation code release was 8.97. So we will be concentrating our discussion on this foundation code release.
Chapter 1:
The Future of EnterpriseOne and Fusion
Business Services Business Services are the native web services inside EnterpriseOne. In this section we are going to break down how business services can be leveraged by EnterpriseOne customers. The first thing to understand is that business services are directly embedded into the EnterpriseOne toolset. There is no additional licensing required to leverage business services. However, you will need to download a copy of JDeveloper, which is required for business services development. This is a free piece of software and can be obtained from the Oracle web site. Business Services Architecture The first thing to understand about business services is that you have both internal and external business services, as shown in Figure 1-2. This is a very important concept to understand. When Oracle came up with the concept of business services, they set this up so that certain functions were
Call to Business Services through WSDL
External Business Services
External Business Services calls will be validated through security.
Internal Business Services
The internal business services are what actually do the work. So when a call for inventory to be relieved is executed, it will be an internal business service that does the actual work and then passes the information back to the external service. These services cannot be called externally.
FIGURE 1-2. Internal and external business services diagram
19
20
JD Edwards EnterpriseOne: The Complete Reference
internal facing. This makes the system more secure as well as giving the developers an easier time of designing their business service. When a developer is creating an external business service, their goal is to ultimately create a WSDL for another system to subscribe to. This is referred to as EnterpriseOne being a publisher of a service. This WSDL is a contract with the other system on what is required to subscribe to the service. When we set up a third-party system to subscribe to a business service, it will use the WSDL to figure out how to call into EnterpriseOne. To make the call into the EnterpriseOne software, middleware software will be used. This could be Fusion Middleware, but does not have to be. All of the major middleware products can handle using Web Services Definition Language. This middleware software will be used to move the data over to the EnterpriseOne System. Some orchestration could also possibly be done here. What this could entail is the mapping of fields from one format to another. The middleware, say Fusion Middleware for simplicity’s sake, gets the message to EnterpriseOne that it will use the business services server. This is where the actual business service has been built and deployed. We will discuss exactly how to do this later in this chapter. When the business service is called, it will check with the security server to ensure that the provided user or role can indeed execute this service. If they are in fact allowed to run the service, then this external business service will call internal business services to accomplish some work. NOTE Oracle has built-in security on the business services– type objects. You can configure the business services to be allowed or restricted to run on the user or role level from the security workbench, P00950. Let’s say the task is to enter an address book record. The external business service would call the specific functions to add the parent record. These are what is referred to as internal business services. A lot of these functions are also master business functions, so for those who started out in the early days, you may recognize some of the functions, but you will be very pleased with how easy it is to call them through business services. This internal business service will perform the work and then, if necessary, you can pass information back to the other system. An example would be if you are using guaranteed events or upon entry you want to send the EnterpriseOne address book number back to the calling system so that it can be referenced in that system. Figure 1-3 shows an example of what it looks like when EnterpriseOne business services are acting as a publisher. Now that we have talked about EnterpriseOne being a publisher of a business service, let’s talk about going the reverse direction. What if we want the system to
Chapter 1:
The Future of EnterpriseOne and Fusion
Web Service
External Business Services
Internal Business Services
EnterpriseOne Kernels Security Server Kernel
EnterpriseOne Database
EnterpriseOne Enterprise Server UBE
HTML Client Call to Business Service
FIGURE 1-3. EnterpriseOne Business Services as a publisher subscribe to a web service? How would that look at an architectural layer? We are glad you asked! In this case EnterpriseOne is consuming some form of web service. So let’s talk about a real-life situation. Many customers have EnterpriseOne running their order entry and financial applications, but have their warehousing systems with another software product. So a user goes into the sales order entry screen and starts to enter an order. They type in an item number. This is where you will have had to put a call in your code to call the web service you are subscribing to. So you will make a call out to check inventory from the third-party system. To do this, the business logic or business function call will be made from the EnterpriseOne HTML server to your EnterpriseOne application server. This server type runs the EnterpriseOne reports and business logic. This will be recognized as a call for a web service, so it will reference the business services server.
21
22
JD Edwards EnterpriseOne: The Complete Reference
At this point the business services server will retrieve information on this particular service from the database. This information is most often stored in the system tables. Some examples would be what user and environment to use. Once this information is obtained, then the middleware solution will be invoked. This can be Fusion Middleware or any other major middleware product such as BizTalk or TIBCO. This is why being standards based is so important. It does not paint the EnterpriseOne customers into a corner where they must use only the Fusion Middleware. The middleware product will then take the information, such as the item number, amount, date of order, and other things in the payload to transfer to the other system. During this process the middleware solution can be configured to perform some orchestration, such as changing the item number to be longer or shorter based on rules. If you are using Fusion Middleware, you can also use BEPL Process Manager to set up a process flow with rules and actions. Let’s say we get into the other system and find that what we want to order is out of stock. Do you allow the system to place a back order? Do you perform product substitution? Perhaps you automatically search several other distribution centers and do an inventory transfer or relieve that inventory for this order. This can all be done through the process manager as you lay out your business process. The third-party inventory system would then show the inventory relieved for this order. So we now have this reserved and send this back to EnterpriseOne so that we can see we can order the item. In this case you would want to use guaranteed delivery and you would also need to architect the system to ensure this integration was very quick. After all, you have one of your customers on the phone. As long as you architect your system correctly, you can get very good throughput and performance out of these integration points. Also if you configure guaranteed delivery, even if you lose communication with the other system, your order will go through as soon as the system comes back on line, meaning you lose nothing in the old bit bucket. This would be an example of EnterpriseOne as a consumer of a web service, which is shown in Figure 1-4. Developing a Business Service So how does all of this work? You now have a new object type on the Object Management Workbench (OMW) for business services. You also have a new server type for business services. What this means is that the development and use of web services will go through the same standard process of develop, build, and deploy as any other object type in EnterpriseOne. This means that it is automatically hooked into your software development life cycle (SDLC). Those of you who did some of the early coding with Extended Business Processes (XPI) are cheering right now. Back then you had to manually promote the code through web methods as well as through EnterpriseOne. There was no direct tie. What this meant was that sometimes you would get one thing promoted, but not
Chapter 1:
The Future of EnterpriseOne and Fusion
Web Service
Business Services
EnterpriseOne Kernels
EnterpriseOne Database
EnterpriseOne Enterprise Server UBE
HTML Client Call to Business Service
FIGURE 1-4. EnterpriseOne as a consumer of a web service something else and then all heck would break loose. This made the job of administering the system difficult at times. With business services we can now create and promote the business service, which is an EnterpriseOne web service directly in the Object Management Workbench. This helps to solve so many of those annoying snags that always seem to come at the worst possible time, such as one little piece of code not being promoted to the next environment. If a developer is going to create a business service, they would log into EnterpriseOne and go to the Object Management Workbench. Once there, they can search on different existing business services or they can add their own if they like. Oracle has over 70 different integrations with business services that are shipped with the EnterpriseOne 8.12 software. Developers should not reinvent the wheel, but should look to copy some of Oracle’s code so they don’t have to create everything from scratch. Figure 1-5 shows what the new business services look like in the Object Management Workbench. If you look closely at Figure 1-5, you will notice that there are two different types of components that affect business services listed. These are the actual business services, which are a Business Service Security Revisions (BSSV) business
23
24
JD Edwards EnterpriseOne: The Complete Reference
FIGURE 1-5. Business Services in Object Management Workbench function type. We will come back to this object. However, you also have the object type of business service property. This object type can almost be thought of as the processing options of the business services. It contains information on the business service itself. Now when you go into the design on the actual business services and select Design Tools, you will see a window with several options, as shown in Figure 1-6. These are Invoke JDeveloper, View Checked In Artifacts, and JDeveloper Install Path. JDeveloper is really your development tool for business services. You can and must download this software from Oracle’s web page in order to modify business services. If this is the first time you have used the business services design tools, you will need to tell the system about your path to JDeveloper. To do this you simply click the JDeveloper Install Path button and browse to the folder where you installed JDeveloper. After doing this, you will be able to click the Invoke JDeveloper button to actually see the code for the business service, as shown in Figure 1-7.
Chapter 1:
The Future of EnterpriseOne and Fusion
FIGURE 1-6. Business Services design tools Now we are actually in the code for the business service. As many developers will note, this code is Java-based. If you have developers who know the JD Edwards business function code, they will pick JDeveloper up fairly quickly. Oracle has a lot of examples to work from and you can easily recognize some of the functions that you can call in JDeveloper. As you use JDeveloper, you will see where you can call internal functions for your business service. This allows you to execute specific functions, such as adding a parent address book record. So if you are creating a new business service, you can copy an existing one and use that code as an example. You would then need to build the business services through JDeveloper. You can then check the business service in. Some other key features in JDeveloper can be accessed through the Event Rule development window, in the Object Management Workbench. There are also many built-in features in JDeveloper itself, which extend the developer’s ability by using icons and more visual buttons to integrate repetitive processes, such as invoking a function. Within JDeveloper there is an easy way to view and modify the actual
25
26
JD Edwards EnterpriseOne: The Complete Reference
FIGURE 1-7. Business service code in JDeveloper source code of the business service. This type of development allows more flexibility when compared to the ease of named event rule (NER) development versus the level of control in C Business Function development. JDeveloper allows a developer to bounce easily between visual-based, workflow development and actual Java code when the need arises. Now you have your code checked in and all is good, right? Actually there are some special programs that can help you with your environment. Specifically these are soft coding and the cross-reference programs. Before moving on, we would not be doing this chapter justice without taking some time to discuss these important programs and how you can use them. Let’s start with the soft coding application, shown in Figure 1-8. This application allows you to plug values dynamically into the code without having to modify the actual code itself. This is very handy when you need to change a user or environment variable in the code line. This application also allows you to mask sensitive data, such as passwords. This means that not just anyone can see this type of data.
Chapter 1:
The Future of EnterpriseOne and Fusion
FIGURE 1-8. Soft coding for business services Now why would you really care about soft coding a value or values? You can create templates for common interfaces, so these records are very reusable. Still not enough? OK, let’s talk about a real-world example. In the past, with the use of web methods and solutions, you had to maintain these values in the actual code line. This meant that you had to open the code again and change the value after you promoted it from environment to environment to ensure that the correct user and environment variables were passed. Also these values were not always masked, which caused a security risk and thus could show up on audit reports. Although this was not a lot of effort, it could cause some rather painful issues. Here’s an example: You promote code and run transactions through prior to realizing that the production integration is writing to the prototyping environment. This would be a key example of why you should not only use soft coding, but why it can be so important. Building and Deploying a Business Service You have created your business services and are ready to move on. Now how do you get the code to where you can have it
27
28
JD Edwards EnterpriseOne: The Complete Reference
used and recognized by other systems? Just as with any other object in EnterpriseOne, you must check the object in, build the object, and then deploy the object. The first step is very simple: You use the Object Check-in option in the Object Management Workbench application. This will move the code from the local workstation into the check-in location and central objects. At this point the work generally moves from the developer to the system administrator. We have discussed earlier in this chapter how business services are now another object type in OMW. So now the objects and/or project are given to the system administrator. They can then build these into a full or update package. Once the package is built it will need to be verified and deployed out. When this package is deployed, it will also be deployed to the business services server. This is how the code can then be recognized and called. Your EnterpriseOne system will then be able to publish your business service.
Summary
As you come to the end of this chapter you may be thinking that you have heard more acronyms than you thought ever existed! Yes, there are a lot of new acronyms to learn as it is an exciting new information technology world. In this chapter we have covered a lot of ground. We have talked about what Service-Oriented Architecture (SOA) is and how it is becoming the industry standard. We spoke about how Oracle is going to a standards-based approach to their ERP applications. We spoke about differences between Fusion Middleware and Fusion Applications. In this chapter we covered the different components of Fusion Middleware. You learned about Business Activity Monitor (BAM) and how you can see what is happening in your system. We showed you Enterprise Service Bus (ESB) and how this can route and orchestrate for your integrations. We also spoke about BPEL Process Manager and how this tool can help to lay out business processes into your integrations. We covered Application Integration Architecture (AIA) from Oracle. We spoke about how you can use preconfigured SOA solutions and packaged integration pieces to speed up your implementation. This approach from Oracle allows you to take advantage of SOA technology faster with less total cost of ownership. We then moved on and spoke specifically about the EnterpriseOne toolset. We covered how EnterpriseOne can be the consumer or publisher of a web services. We also spoke about business services, which are a part of the Fusion Middleware incorporated into the EnterpriseOne foundation code. We showed you how you could use Object Management Workbench to create or modify your business services and then how to deploy them using standard tools. This chapter truly has covered a lot of ground with the new Fusion Middleware, SOA, AIA, and Fusion Applications. However, there is so much more happening every day in this area. The authors highly encourage you to visit the Oracle web site on this technology. Attend a podcast, or better yet, an instructor-led training session. Putting some time and effort into learning about Fusion Middleware will pay off and prepare you for Fusion Applications.
CHAPTER
2
EnterpriseOne Building Blocks 29
30
JD Edwards EnterpriseOne: The Complete Reference
H
ow does EnterpriseOne work? This is one of the questions most frequently asked by both the new EnterpriseOne initiate and the seasoned EnterpriseOne professional. Unless you understand the building blocks that make EnterpriseOne function, there seems to be a mystery to the entire product. In this chapter, we will go into enough detail to give you what you need to understand the EnterpriseOne product from the ground up. We will start laying the foundation by reviewing the data source and providing an understanding of how the system finds data and machines that process logic. We will then move on to path codes and how applications are maintained within the EnterpriseOne system. After that, we will talk about how we can define instances of EnterpriseOne by using the building blocks we covered in the previous two sections. We will also discuss the power behind the versatility of the EnterpriseOne system: the Object Configuration Manager. We will then go into detail concerning the EnterpriseOne middleware and review how this software helps you with all EnterpriseOne activity. Finally, we will end with a quick discussion about asynchronous and synchronous processing.
Data Sources
In this section, we will go into detail concerning what data sources are, how many are required for a system, and how to modify and maintain them, as well as why you might add and modify these elusive little devils. The following list details some of the topics in this chapter that will help remove some of the mystery of EnterpriseOne: ■
Database differences
■
Data source definitions
■
Components that make up a data source
■
The number and types of data sources
■
Data source application P986115
■
Special uses for data sources
■
Data source Law of the West actions
Some Information Necessary to Understand Data Sources Before we jump directly into data sources, which we think is one of the most important topics in this book, we need to talk about the relational database management systems (RDBMSs) supported by the EnterpriseOne Enterprise
Chapter 2:
EnterpriseOne Building Blocks
Resource Planning (ERP) product. There are six primary RDBMSs used by EnterpriseOne. Depending on your implementation, you probably use two or three of these systems; however, you could use them all if it made business sense. EnterpriseOne supports Oracle, Microsoft SQL Server, DB2 on the AS/400, DB2 Universal Database (UDB), Microsoft SQL Server Desktop Engine (MSDE), and as of 8.97, SQL Server Express (SSE). Although many people don’t count MSDE or SSE as a part of their business solution, in reality, these are the databases that can be common among all of the EnterpriseOne solutions. We want to spend a couple of minutes going over the RDBMSs supported by the EnterpriseOne solution because these systems will hold the tables you define using the EnterpriseOne data sources. These relational database systems are different, and these differences show up in how you configure your data sources and why. This may seem somewhat ambiguous, so let us get a little more detailed.
Oracle Oracle maintains tables within table spaces. These table spaces can have a specific owner and are maintained on separate data files. Consequently, if you were looking for F0101 (Address Book Master) for production, it would be in a different table space within the same database as F0101 for the Prototype (PY812) environment. Currently, Oracle ships EnterpriseOne on Oracle with a single database defined. Breaking up this master database can yield superior performance, additional configurability, and flexibility to your EnterpriseOne enterprise solution. Oracle uses a custom communication software package called SQL*Net to communicate between the database itself and other machines trying to reach the data within the tables. Your Oracle database administrator (DBA) will define a connect string (in essence, a series of parameters that tell the client machines how to connect with the Oracle database) for the EnterpriseOne database. If you decide to create several different databases, or if you implement a distributed data architecture, you will have several different connect strings. All the connect string data will be contained in a file called TNSNAMES.ORA under the Oracle path on each client machine.
SQL Server In the past, SQL Server could have all the tables within a single data file. The only difference between the tables was the owner of the tables. This is not to say that the data within the tables is identical, but that the tables themselves can be maintained in the same physical file. In the early releases of EnterpriseOne, all the tables necessary to support all instances of EnterpriseOne were maintained in the same database. Many people who worked in the field noticed that this architecture, while easy to maintain, was certainly not the most efficient for speed or performance. Some began experimenting with breaking up the database into multiple databases maintaining fewer tables in smaller, more efficient devices. There was a marked increase in performance, and the B733 version of OneWorld shipped with multiple
31
32
JD Edwards EnterpriseOne: The Complete Reference
databases instead of a single master database. Today, EnterpriseOne also uses multiple SQL Server databases to enhance performance and to make backups easier in the EnterpriseOne system. This combination of multiple databases can be spread over separate disk drives for optimal performance and configuration capabilities.
AS/400 The AS/400 uses its integrated version of DB2 to accommodate EnterpriseOne’s table requirements (tables are referred to as files on the AS/400). These tables are maintained in libraries (the equivalent of directories or databases in UNIX and on NT). The AS/400 does not support table/file owners. Because of this, you can’t have two identically named tables in the same library. What this means to the person installing or maintaining EnterpriseOne is that you will have multiple libraries for your EnterpriseOne solution. This setup is similar to Oracle’s table spaces discussed earlier.
What Is a Data Source? Before we can adequately answer this question, we have to ask what the underlying piece of any ERP software application is: the data. After all, in the end, it all comes back to the data that is stored, manipulated, and ultimately provides organizations with the return on their system’s investment. Rather than have to hard-code a data link to provide users with multisystem functionality, the EnterpriseOne software engineers came up with the idea of a data source. In the simplest terms, a data source is nothing more than a pointer to where data resides or to a machine that will process logic. These pointers are then used by the EnterpriseOne software itself to determine where the data resides and in what format. When we talk about data pointers, we are really talking about a table or sets of tables that can be identified by either a common table owner or a common data location. Data sources always point out whole tables, not rows or sets of rows within a table. The data source is not used as a method of segmenting data within a table; transactional SQL statements will extract actual subsets of data as required by the specific EnterpriseOne application. Because EnterpriseOne uses data sources, a client can use any one of five different databases (Oracle, SQL Server, DB2 [AS400/UDB], MSDE, or SSE) with equal ease and in multiple combinations designed to allow the user a freedom of choice. Even in a base installation, there are usually two different database formats being used, often without the user’s knowledge. Why did Oracle do this, when architecturally it is more difficult to design? Well, the firm foundation of this system is to create a product that answers a business need. EnterpriseOne is designed to be the ultimately configurable system, where the client decides what makes business sense for them. If you have an Oracle DBA at one site and a SQL Server DBA at another, why not use both of them to maximize the use of your personnel? Why spend money retraining any of these people? The EnterpriseOne answer is to use both database
Chapter 2:
EnterpriseOne Building Blocks
types without retraining anyone. The EnterpriseOne system will allow both of these databases to work together in a way that appears seamless to the end user. Again, the data source is the answer.
What Information Is Contained in a Data Source? The data source is a powerful component of the EnterpriseOne system. This key “building block” accomplishes its job by combining a series of information. Figure 2-1 provides a view of the information contained in a datasource: ■
Data Source Name This name can be up to 30 characters in length and will be used whenever you need to reference the tables defined by this data source.
■
Data Source Use This indicates whether you are using the data source to define tables within an RDBMS or a server that is performing EnterpriseOne logic. Accepted values are DB and SVR.
FIGURE 2-1. Data Source Revisions window
33
34
JD Edwards EnterpriseOne: The Complete Reference
■
Data Source Type This will specifiy if the datasource will be SQL, Oracle, DB2 UDB on OS/400, DB2 UBD on UNIX or Windows, Access, MSDE, or SSE. The setting in this field will control the other fields that are displayed to the user (for instance an AS/400 data source will have different fields then a SQL datasource).
■
Data Class This defines the type of data that will be held in the data source being defined. This new field helps provide better data selection for Universal Batch Engines (UBEs) and servers to further identify what kind of data a data source is referencing. The classes of data available are: Business Data, Central Objects, Data Dictionary, Logic, Host Server Map, Local, Object Librarian, Installation Planner, System, Control Tables, and Versions.
■
Platform This field tells the software what type of platform you are running; accepted values are AS400, NTSVR, HP9000, LINUX, LOCAL, RS6000, and SUN.
■
Database Server Name This is the name of the server that holds the database or performs the EnterpriseOne logic. This can be case sensitive, depending on platform; UNIX servers differentiate between “machine” and “MACHINE.”
■
Object Owner ID The object owner ID is only used with Microsoft SQL Server and Oracle. It indicates the database table owner.
NOTE Only two of the four supported RDBMSs support table owners (SQL Server and Oracle). In essence, these databases allow you to have tables with identical names within the same database differentiated by the user who created them. Use of this system allows you to keep multiple copies of some tables (such as F986101 OCM) in the exact same location. This may simplify system maintenance when you have multiple application servers. ■
Database Name (TNS/Alias) This field is used for SQL Server, Oracle, MSDE, and UDB data source. The field captures the name of the SQL database (for example JDE_PRODUCTION), the name of the Oracle instance (for instance JDEPROD), or the alias of the UDB database.
■
Database Instance This field is used for SQL Server ODBC, MSDE, and SQL Server OLEDB data source. It is the name of the server instance.
Chapter 2:
EnterpriseOne Building Blocks
■
Library Name This is for AS/400 data source only; it will contain the actual AS/400 library name where the tables reside.
■
ODBC Data Source Name or Oracle Connect String This is called the database name on the EnterpriseOne form, but it truly needs to be either the ODBC data source name or the Oracle connect string. This field is both case and space sensitive.
NOTE In 8.12 this field should match the name of your database server. This allows all EnterpriseOne (E1) data sources contained on a SQL database to use only one ODBC data source on the workstations/ servers. This minimizes maintenance and complexity ■
JDBNET Data Source check box This field indicates whether the data source uses JDBNet. This allows EnterpriseOne on an AS/400 to communicate with other platforms/databases such as NT/SQL.
In addition to the fields we have already discussed, Data sources also contain a series of flags and supplemental data that help control how the data sources interact with the system. Figure 2-2 displays the options that can be set in the Advanced Set-Up window. ■
Clustered This flag indicates that EnterpriseOne is configured for database clustering.
■
Unicode Indicates whether a database supports Unicode. EnterpriseOne now ships with all data sources in Unicode except for Business Data and Control tables. These data sources can be converted to Unicode on an upgrade.
■
Use Decimal Shift This selection is used for EnterpriseOne tables within data sources. It indicates that the EnterpriseOne data dictionary will determine the number of decimal places displayed. All database formats except Microsoft Access should have this flag checked.
■
Use Julian Dates All RDBMSs supported by EnterpriseOne with the exception of Microsoft Access should have this flag checked.
■
Support for Locking Updates This flag indicates whether the database supports row-level locking. All database formats except Microsoft Access should have this flag checked.
35
36
JD Edwards EnterpriseOne: The Complete Reference
FIGURE 2-2. Advanced Set-Up window
■
OCM Data Source This flag tells the software that these data sources will have, at a minimum, the F98611 and F986101 tables contained in the data source. Examples include the system data source and any server map data sources. When this flag is checked, the data source will appear as an option when the user goes into the Object Configuration Manager (OCM) or data source application.
■
Use Table Owner This flag tells the system to use the object owner ID listed in the data source and should only be used with an RDBMS that supports table owners (Microsoft SQL Server and Oracle).
■
LOB Data Type Support This option indicates whether a data source supports large object (LOB) data types. This option is required for all AS/400 and Oracle data sources.
Chapter 2:
EnterpriseOne Building Blocks
■
AS/400 BLOB Support This option indicates that the data source may contain BLOB (Binary Large Object) tables.
■
XML Formatted Workflow This option is utilized to indicate XML formatted workflow will be used.
There is also software-linked data source information contained in the F986115 table that regulates whether the data source can have automatic table creation and whether data can be copied from the table. (Complete definitions and examples are provided in the section “Object Configuration Manager”.)
How Many Data Sources Do I Need? We wish that we could say the answer to this question was simple. It is really dependent on what type of implementation your company has chosen to perform and whether you have made custom changes that require additional data sources. Let’s first go over the types of data sources, and then we can move on to which ones you may need and why. Finally, we will discuss adding additional data sources to the system to meet your special requirements. There are 12 primary types of data sources that can be configured with EnterpriseOne. Remember, a data source is nothing more than a pointer to tables or logic within the system. These tables are usually identified either by owner or by a specific location and server.
Data Sources and Their Types There are two categories of data sources that can be defined on the EnterpriseOne system. One category points to data within the enterprise. This data source is the one that most people can quickly understand and deal with, and the majority of this section is dedicated to explaining it. This type of data source is identified by DB, in the P986115 data source application and in the OMOCM1 column of the F98611 data source table. The second data source type defines a machine running EnterpriseOne services that can be accessed by other machines in the enterprise. By programmatic default, EnterpriseOne automatically runs all applications and batch programs locally for non-HTML/JAS environments. To offload some of this processing time to a server (either the enterprise server or an application server) instead of taking up valuable workstation processing time, you have to define the server that you want to perform the job. This data source is designated by SVR in the OMOCM1 column of F98611, the data source master table.
Business Data This DB (database) data source points to the EnterpriseOne tables that are specific to business applications. Where it can be, and often is, shared between multiple environments in the EnterpriseOne enterprise, it is a defining characteristic of an
37
38
JD Edwards EnterpriseOne: The Complete Reference
environment. There are more than 4,400 tables within a normal installation of EnterpriseOne (8.12 series) that qualify as business data. Does this mean you need 4,400 data sources? No. Rather, a single data source can point to all these tables provided they have a single owner or are in a single library. There are times when it might make good business sense to separate selected tables to different data sources (for example, if you were implementing HR/payroll and wanted to place database security on these tables in addition to regular security), but this will be discussed in more detail later in the book. Business data tables are most commonly used after you have logged in on a client workstation. The standard naming convention is Business Data – XXX. The XXX is specific to the business data being defined, such as TEST, CRP, PROD, and so on.
Control Tables This DB data source identifies control tables, including user-defined codes (UDCs), task views, and next numbers. These tables go hand in hand with the business data source described above and function strictly as controlling information for the EnterpriseOne product. For more information on what tables are identified by this data source, see the appendix tables within EnterpriseOne. Control tables can be used at any time during an EnterpriseOne application session. The standard naming convention is Control Tables – XXX. The XXX is specific to the control tables being defined, such as TEST, CRP, PROD, and so on. DEFINITION User-defined code (UDC): These are sets of values that display in the EnterpriseOne applications. These values can be modified by the end user so that they display in a way that is meaningful. An example of a UDC would be a search type in your address book, such as searching by vendors, employees, or other values the system administrator adds.
Central Objects This DB data source points to data necessary for running the actual EnterpriseOne applications. These tables contain processing options for applications and UBEs, template data, business view data, and a host of other information required to run the applications (both interactive and batch). Central objects often contain binary large objects (BLOBs) within the tables themselves. Under various RDBMSs, you might see these described as long raw data. The information is in binary format and can range from 1 byte to multiple megabytes. The central object tables, consequently, are very large. Central objects can be hit at any time EnterpriseOne is in use; however, they are most commonly updated during development or when processing options are changed for specific interactive and batch applications. The standard naming
Chapter 2:
EnterpriseOne Building Blocks
convention is Central Objects – XX812. The XX is path code–specific. The name is major release level–specific, such as 812, B733, and so on.
Versions The Versions data source separates the F983051 table from other central object tables. This table maintains information on all the versions, interactive and batch applications for each path code. This data source is database oriented. The standard naming convention is Versions – XX812. The XX is path code–specific. This name is major release–specific, such as 812, B733, and so on.
JDELocal/JDESSELocal This database-oriented data source points to the JDELocal MSDE (or as of 8.97 SSE) database loaded on the local client. It is often referred to as locally replicated data. This is a database format. This database is used when a developer executes any HTML or web application locally. The information is populated to a local copy of the HTML serialized object tables (F989999 and F989998). This enables the developers to examine code prior to checking that code in. This database also serves to contain a copy of the Central Object information on a fat client (as of 8.12 Central Objects moved to an XML format instead of the old TAM format). In this way the fat client uses the copy of Central Objects contained locally to execute the EnterpriseOne code. NOTE Very few applications still execute on the fat client; most everything is now web based. The standard naming convention is OneWorld Local – XX812. The XX represents the path code name. The name represents major release versions such as 812, B733, and so on. This data source does not exist for application/logic servers (only on the development workstations).
System The system data source identifies tables that are common to the entire EnterpriseOne implementation and are not environment- or path code–specific. These shared tables include information such as the data source tables themselves, the Object Configuration Manager, and printers, in addition to a range of other global settings. Many of the tables used in the system data source are cached at run time and changes to them are only realized when the client cache is cleared (this applies to client workstations, application servers, and JAS/HTML servers). A good example of this is the security table (F00950). You can look in the appendix tables in EnterpriseOne for all the tables that are associated with this data source. These tables can be accessed any time during a session of EnterpriseOne; however, they
39
40
JD Edwards EnterpriseOne: The Complete Reference
are most heavily used during the initial logon to EnterpriseOne. The standard naming convention is System – 812. This data source is named according to major release level, such as 812, B733, and so on. It is a DB data source.
Server Map This DB data source provides access to a special subset of the system tables maintained exclusively for use by enterprise and application servers. Because of special requirements of application servers, there may be times when data used by workstations is different. The only way of maintaining these differences is to have an identical set of tables maintained for this purpose. A good example of data that could be different between the server and the workstation is data sources themselves. Some servers use a different set of EnterpriseOne middleware to acquire data. The standard naming convention, for a server map, is machinename – 812 Server Map. The machinename is the name as defined in the logic data source; it is usually the same as the actual machine name on the LAN/WAN. This data source is named according to the major release level, such as 812.
Object Librarian The Object Librarian data source contains five tables (the F986x series) that define every object in the EnterpriseOne system. When we refer to an object in the EnterpriseOne system, this includes applications, business views, UBEs, processing option templates, and so forth. The tables in this data source define every non-data object. These tables are integral in all object modifications. The standard naming convention is Object Librarian – 812. This name is major release level–specific, such as 812, 811, 810, and so on. This data source is a DB data source pointing to data with a relational database. This data source, like the system and server map, is a shared data source, making it environment and path code independent.
Data Dictionary This DB data source describes a set of tables (the F92xx series). These tables provide a series of functions in the EnterpriseOne implementation that includes defining all columns in the system, all error messaging, and how many decimal places are displayed. The master data dictionary tables are maintained in an RDBMS on the enterprise/database server. Workstations and servers use replicated copies of these tables copied to table access management (TAM) files. The standard naming convention is Data Dictionary – 812. This name is major release level–specific, such as 812, 810, and so on. This is one of the few places that TAM format is still utilized in the 8.12 EnterpriseOne product.
Server The server data source usually is annotated as the enterprise server’s name, but is also a required data source for every enterprise, application, or logic server on the system. Depending on the hardware platform, this data source can be case sensitive.
Chapter 2:
EnterpriseOne Building Blocks
This is particularly true with the UNIX platforms. Its primary use is to indicate to EnterpriseOne where it needs to process logic within the enterprise. By installation default, UBEs will process on the enterprise server (this is defined during the installation or upgrade). However, you can use the server data source to override where batch applications or business functions run. You can do this on the fly when launching a UBE or by OCM mappings. The standard naming convention is machinename. This is usually the name the computer is known by on the LAN/WAN. This name is not release-specific.
Server – Logic This data source is a logic data source and will be primarily used to map business functions to run on specific servers. In newer releases Oracle provides logic data sources based on the type of logic being mapped (Business Functions [BSFNs], Real-Time Events [RTE]). The standard naming convention is machinename – Logic. This concept allows customers the ability to split out their batch and BSFNs processes to execute on different servers or tier their implementations. This name is not release-specific.
Local The Local data source defines the machine running EnterpriseOne itself. It is generally used to define a workstation to allow business functions to be run locally or to run batch applications on the local workstation rather than on the enterprise server or an application server. The standard naming convention is LOCAL. This name is not release-specific.
Now Back to the Question How many EnterpriseOne data sources do you need? Well, you could get by with as few as seven (if you are running the EnterpriseOne stand-alone version), or as many as you can define (this depends on how many application servers, batch servers, logic server data sources, and so on you may have). An average EnterpriseOne installation (assuming PD812, DV812, PY812, and PS812 environments) will have around 20 or more data sources.
How Do You Set Up and Configure Data Sources? The following section is essential to understanding and being able to configure data sources. Various guides produced by Oracle contain information related to this topic. We have added more information with the hope of providing a deeper understanding of the application. There are two basic methods used to set up data sources. During an installation, update, or upgrade, there are automated wizards that will set up the standard accepted data sources. For more detailed instructions on how to set these up during the installation process, we recommend that you review the installation manuals for whichever platform you are installing.
41
42
JD Edwards EnterpriseOne: The Complete Reference
During this part of this chapter, however, we do want to take you through a basic setup of a data source from scratch. If you understand how to set up a data source, you will have what you need to troubleshoot data source–related issues. You will also be able to configure EnterpriseOne to best suit your business needs and provide the fastest return on your ERP investment. To understand how to manually set up a data source, you have to understand the architecture of the data source window. The program used is the P986115, and the place most EnterpriseOne administrators will find it is the GH9011 task view. The method for setting up both logic and database data sources is similar. We will start with the database data sources and then look at the differences in setup for the logic data source. When you first select the P986115 (Database Data Sources) application, you will see a form similar to Figure 2-3 (Machine Search & Select). This window is designed to allow you to choose which OCM data sources you want to configure. To change data sources used by workstations (both fat and thin clients), you need to choose the system data source in this window. If you want to work with the data sources for a specific enterprise or application server, choose the machine name–812 server map associated with the server you want to modify. NOTE Earlier in this chapter, we discussed the flag that designates whether a data source is an OCM data source; that is, if it contains the F98611 and F986101 tables. The Machine Search & Select form automatically searches all the data sources in the system F98611 table for this flag and lists them on the form.
FIGURE 2-3. Machine Search & Select
Chapter 2:
EnterpriseOne Building Blocks
Once you select a specific data source to work with on the Machine Search & Select form, the Work With Data Sources window form will automatically launch on your machine. This form will allow you to do the following: ■
Find any or all of the data sources defined for that specific machine
■
Work with the data source database parameters
■
Set up ODBC data sources (associated with EnterpriseOne data sources, this will also add the information into the ODBCDataSource.inf used, which is read to automatically set up ODBC workstations during a client installation)
Architecture of the Data Source Revisions Window The Work With Data Sources window, shown in Figure 2-4, is key to a system administrator, as it allows them to easily change the existing data sources or add new data sources to the system. Remember that a data source is just a pointer to your data. 1. The Data Source Use field indicates whether you are defining tables within a database or a machine that processes EnterpriseOne logic. Accepted values for this field are DB and SVR. When working with a database data source, this field will automatically fill in a DB to indicate the type of data source you are creating. This information, once saved, cannot be revised for a
FIGURE 2-4. Work With Data Sources window
43
44
JD Edwards EnterpriseOne: The Complete Reference
specific data source. If you set up a DB data source and meant to set up a logic (SVR) data source, you will have to delete the DB data source and set up a new data source for the SVR. 2. The Data Source Name field can be any name up to 30 characters in length. It is usually recommended, especially in custom data sources, that you choose a name that will make sense to you and other users on the system. There is a standard naming convention for data sources. Examples of the naming conventions are provided in the descriptions of the data source types in previous sections. 3. The Data Source Type field indicates the type of RDBMS being defined by the data source. This is a required field for this form. If you are defining a logic data source, by convention, you would indicate the same RDBMS as in the logic’s associated server map data source. For example, when defining an NT application server that has its server map in a Microsoft SQL Server database, you would put an S in the Data Source Type field for the server map and the machinename data source. 4. The Data Class field defines the type of data stored in the data source. For example, a business data source would have a data class value of B. This provides greater tracking and definition for data selection on reports. 5. The Platform Type field allows you to specify the server type. Accepted values include LINUX, AS400, HP9000, LOCAL, NTSVR, RS6000, and SUN. 6. The Database Server Name field defines the name of the server that the database resides on. 7. The Object Owner ID field indicates the table owner for that specific data source. You can have multiple data sources with identical table owners, depending on your specific setup. This field is used when EnterpriseOne structures the SQL statements that return data to the EnterpriseOne applications. For example, if you were to perform a find in the Address Book Master for a specific customer with customer number 1234, EnterpriseOne might automatically create the following SQL statement: select * from crpdta.f0101 where aban8='1234'. In this example, crpdta is a table owner and is used to differentiate the F0101 table associated with the CRP data from the production, test, or pristine data. 8. The Library Name field is used for data source tables on the AS/400 only. This field tells EnterpriseOne exactly which library contains the tables defined by the database data source. 9. The Server Name field holds the network name of the server containing the database or the actual name of the logic server. Although its case sensitivity is dependent on the platform being hit, it is safest to assume
Chapter 2:
EnterpriseOne Building Blocks
that all information in the Data Source Revisions form is case and space sensitive. This is much easier than trying to figure out when case sensitivity is important. 10. The Use Table Owner flag is used in conjunction with the Object Owner ID field. It must be checked in order for the information in the Object Owner ID field to be used in the SQL statements generated by EnterpriseOne applications. Filling in that field by itself is not enough. 11. The Use Julian Dates flag indicates whether the database supports Julian dates. This flag should be set for all supported RDBMS types with the exception of Microsoft Access. 12. The Use Decimal Shift flag indicates that the tables within the data sources will use the data dictionary to determine the number of decimals displayed per item type. If this box is checked, EnterpriseOne will automatically shift the information input into the database to account for decimal places and will automatically display the appropriate number of decimals when retrieved. (For example, you can define inventory to have four decimal places, while currency may only have two.) This flag should be used for all supported RDBMS types with the exception of Microsoft Access. 13. The Support For Locking Updates flag determines whether JDEBase should use row-level locking with this data source. It is used on all RDBMS data sources with the exception of Microsoft Access. 14. We’ve already talked about the OCM Data Source flag. It indicates that the data source contains, at the minimum, the F98611 and F986101 tables. The system and all server map data sources use this flag. This flag determines whether the data source is shown in the Machine Search_Select form of the P986115 application. 15. The LOB Data Type Support flag tells the EnterpriseOne application that at least some tables within the data source contain binary large objects (BLOBs) on the AS/400. A good example of a data source that has this flag checked is Versions – 812. The table defined by this data source is the F983051 (Versions List) table, which contains information in a BLOB format. You can also house the central objects’ data sources on the AS/400. If you choose to do this, these data sources would also have the LOB Data Type Support flag checked. NOTE This flag is also required for Oracle database data sources.
45
46
JD Edwards EnterpriseOne: The Complete Reference
16. The Database Prams form hyperlink launches the P9861151 application. This program populates the F986115 table and is discussed in detail in the section “Object Configuration Manager.” 17. The Default Database form hyperlink also launches the P9861151 application and is also discussed in detail in the section “Object Configuration Manager.” Now let’s move on to something a little more fun.
Special Uses for Data Sources You now know what data sources are and how you would configure them, but you might be wondering why you need to know so much about them, especially considering that wizards are going to set up all the basic data sources during the installation of the EnterpriseOne product. There are several times during the life cycle of the EnterpriseOne product where you might set up special data sources to perform legacy data conversions, to download and upload EnterpriseOne tables, or to add additional environments, for example. To accomplish some of the special uses for data sources, you have to understand which data sources are required for what you are trying to achieve. We will go over some of the more common system customizations so you will be able to continue on your own.
Adding an Application Server (from the Data Sources’ Point of View) There are three data sources that should be set up for a new EnterpriseOne application server (that is, a server that performs EnterpriseOne logic: Batch/BSFNs). Of these three, one is required and the other two are optional, based on what you are trying to accomplish with the application server and how you want to configure it. To determine which data sources are required, think back to the 12 types of data sources. Of those data sources, the one you must have is the server data source. This logic data source defines a machine that performs EnterpriseOne logic (in other words, that has the EnterpriseOne application loaded on it). Many people would immediately argue that you have to have a server map. Though we would agree most of the time, this is not a required data source for an application server. If you have another server set up that is of the same machine type, same database type, and performs the same function, you can actually have the servers share server maps. Why would you want to do this, you ask? Well, let’s take the example of the application server used to offload business functions. If you have multiple application servers, you can have a single server map, which makes modifying the data sources and OCM tables much easier. Rather than have to modify each server separately, this would make a single modification universal (this is a two-edged sword; if you make a mistake, you made the mistake to all your servers at the same time).
Chapter 2:
EnterpriseOne Building Blocks
The third data source associated with an application server is the server/logic data source.
What About Custom Environments? Another reason you would add additional data sources centers on adding environments. As you will see in the “Environments” section of this chapter, EnterpriseOne by default comes preconfigured with five environments. Though they meet the needs of most clients, these environments may not meet your specific business needs. When you add new environments, you will often have to define new data sources. Is there a hard rule as to how many? No, it all depends on what you are doing and exactly how you want these environments to interact with each other. To gain a perspective on the possible data sources used by a single environment, let’s assume you want this environment to be completely independent of the preconfigured environments. What this means is that you will configure the data sources necessary for a completely new environment, including business data, a path code, and control tables. For the sake of this set of questions, let’s say you want to create a training environment. We will use the term TRAIN for most of the data sources we add, and we will follow the Oracle standard naming convention for these data sources. How Many and Which Data Sources Do You Need? Would you say 3 new data sources? Or do you think that 4, 5, 6, or even 12 data sources are needed? If you answered 5, you would be correct. So, which data sources should you add? You need all the following data sources before you can add this new environment. Adding any new data source is the first step to adding a new environment or path code. ■
Business Data – TRAIN
■
Control Tables – TRAIN
■
Central Objects – TRAIN812
■
Versions – TRAIN812
■
OneWorld Local – TRAIN812
Would you need to add new data dictionary, object librarian, system, server, server map, local, or logic data sources? No. These data sources are all shared data sources throughout the EnterpriseOne implementation. Because of this, under a normal EnterpriseOne configuration, these data sources contain data that is shared among all the environments.
47
48
JD Edwards EnterpriseOne: The Complete Reference
Are there other reasons for adding data sources? Sure! What about data conversions? There are several different methods of getting legacy data into E1 (EnterpriseOne), and if you are performing conversions from non-E1 tables, you often have to add a data source. Although data sources can be named anything, PROD Conversions – 812 or CRP Conversions – 812 would be a good start. The specific data source setup information for these data sources is dependent on what type of database holds the data you are trying to convert. Do You Want to Be a Cowboy? This is always one of our favorite sections. Oracle EnterpriseOne staff (especially during training) often refer to someone as being a “cowboy.” What is a cowboy? A cowboy is someone who is manipulating EnterpriseOne either directly through a back door (that is, direct database access using the SQL language or a database tool) or who is using the EnterpriseOne applications and tools in a manner not traditionally supported by Oracle’s development and support staff. We will refer to this type of activity throughout this book as the “Law of the West,” since cowboys do need to follow at least frontiertype rules! Is being a cowboy wrong? That really is a matter of opinion. There is a saying within the EnterpriseOne community that it isn’t “cowboy” if you know what you are doing. It is only cowboy when you don’t. To give you a better example of what this means, let’s think about it this way. If you want to directly manipulate information used by EnterpriseOne, you can often type SQL commands directly, affecting the data within the database faster than using the E1 toolset. For example, you could turn hundreds of OCM entries on and off with a single statement. This is faster than starting E1, entering the OCM application, choosing the data source, finding the records to manipulate, and then clicking the Change Status button (after that, of course, you would have to log out of E1 and back in so that you could see the changes you’d just made). Is this cowboy? Yes and no. If you didn’t know what table was being affected, didn’t know all associated tables, didn’t understand exactly which fields to query against and finally modify, yes, this would be cowboy. In this hypothetical example, however, you knew exactly what tables to modify and exactly what fields to query and update to quickly effect the changes you wanted to effect. It comes down to knowing what you are doing and how that affects the EnterpriseOne environment. The best advice concerning the Law of the West is that if you aren’t completely comfortable with what you are doing, don’t do it. Even when the experienced perform maneuvers, they can be surprised, so you should always have a method of getting yourself out of trouble. This might be a recently performed backup or performing the maneuver in a testing environment first. Finally, if you are thinking of manipulating E1 directly through non-EnterpriseOne methods, remember that Oracle may not support your efforts. If there is such potential risk to Law of the West activities, why do it? First, it is much faster for those who are experienced. Second, there are occasions when it is
Chapter 2:
EnterpriseOne Building Blocks
simply the only way to get the work done. These creative workarounds can be invaluable. Because of the potential gains, performing Law of the West activities is worth consideration. Data sources lend themselves to Law of the West operations because they only use a few tables. Here is some information that you will need to perform data source manipulations: ■
The F98611 and F986115 tables contain all the information defining an EnterpriseOne data source.
■
The F986101 OCM table uses data sources for all its work. If you change a data source, be sure it is not going to affect this table.
■
There are multiple sets of F98611 and F986101 tables. There is only one copy of the F986115 table. When you make changes to the F98611 table, be sure you are changing the correct one for the desired effect. Many times, changes to one table need to be replicated to the other tables. For example, if you change the name of a data source in F98611, you must change the data source name in all the corresponding records in the F986101.
■
Data sources are one of the most important definitions in EnterpriseOne. If you are going to manipulate them directly, be sure you know what you are doing.
Using the guidelines in the preceding list, you can quickly make changes to your system. An example of this is when an Oracle DBA changes the connect string’s name for access to the JDE database. You could open every one of the data sources and manually change this information, or you could effect the same change by entering a SQL statement like this one: update sys812.f98611 set omdatb='JDE1' where omdatb='JDE';
This would quickly change every connect string currently defined as JDE to JDE1. The only thing to consider on this particular change is that it did not change the server map F98611 or the actual TNSNAMES.ORA. Your DBA would have to ensure that the TNSNAMES.ORA file was changed on all workstations and servers before they could correctly access EnterpriseOne again. Another quick cowboy maneuver that can help is creating a new F98611 table for an application server. You can copy F98611 from an existing source to the new machine’s server map database and use SQL to modify the differences—for example, copy the F98611 from a UNIX server map to an NT machine (don’t forget to change the platform). If you know what you are doing, this can be done faster than copying the table using a UBE. As with most cowboy operations, it comes down to quickly and efficiently making changes based on specific user requirements.
49
50
JD Edwards EnterpriseOne: The Complete Reference
Path Codes
In this section, we will discuss what EnterpriseOne path codes are, how they fit into the system, and how path codes meet business needs. A path code can be thought of simply as the path to the code. A mathematical representation of a path code might be shown as PATH CODE = RDBMS + C components. In previous releases, specifications for EnterpriseOne objects in a path code (or metadata) were stored in TAM (Table Access Management) format. In the 8.12 release, this metadata is now stored in XML format in an XML schema in the relational database. This change allows all servers to view and match their code up to one central source. This provides a more robust solution than the previous TAM specifications. Some of the topics covered in this section include: ■
Path codes: overview
■
Definition of a path code
■
Which tables are used
■
Adding a path code
■
When to add a custom path code
■
Copying a path code
■
Modifying the F9861 table
■
Deleting a path code
Path Codes: Overview A path code is really EnterpriseOne’s window to the world. This is because a path code contains all the information the system needs to run its objects. Oracle ships several “canned” path codes. These include pristine, prototype, development, and production path codes. The reason Oracle chose to ship these path codes is to allow their clients the ability to have a pristine set of specifications, which they can always use in troubleshooting as a benchmark comparison. The Prototype path code is meant to be a testing ground. This path code allows users of EnterpriseOne to test their changes to shipped Oracle objects or their custom objects before moving them into their production environment. Nothing should go into the production path code before being completely tested. This will help ensure the stability of the objects your production users are using. The development path code is meant for just that, development. This is the area where your developers can modify objects or add custom objects to meet your business needs. The entire purpose of this path code is to have an area where developers can code and ready their objects. It is important to use the path codes in a correct manner. Development should be performed in the development path code, then transferred to the Prototype
Chapter 2:
EnterpriseOne Building Blocks
path code. The objects should then be validated in the Prototype path code, which should point to a copy of the production data. This way you know that your objects are safe to move into the production path code, which is the final step of the process. This process will be discussed more later in the book when we review packages and their delivery.
Definition of a Path Code A path code is how EnterpriseOne finds the specifications necessary to run its applications, business functions, and reports. This is because a path code is also the storage area for these applications, business functions, and reports. When dealing with a path code, you need to ask yourself what part of the path code you are interested in at that time. The directory structure contains C components on clients and enterprise servers. As of 8.12, runtime information for the objects is accessed from XML formatted tables in the RDBMS. EnterpriseOne software runs on an enterprise server by using the XML metadata. Each enterprise server will check the code it is running against the central XML metadata and ensure that the code matches. This allows the system to provide a way to ensure each server is executing the same object code for a particular path code. The fat client machines/web development machines are a little different as they execute their runtime by accessing a local MSDE or SSE database that has XML formatted metadata for the path code. This also allows the web development client to have their own copy of the F989999/F989998 (HTML/JAVA) tables so that they can preview code in HTML format without having to wait for a package. The HTML/JAS servers will reference a central setup for XML specifications, making this server more of a first-class citizen (as objects will automatically generate in 8.12). There are also the central object components of a path code. The central objects of a path code are a series of relational database files that store the specifications for E1 objects. These tables are utilized when package builds are executed and are the source for the creation of the XML formatted tables utilized at run time. Package builds will be discussed later in this book in Chapter 7; for now, just think of a package build as a snapshot in time of the information contained in the central object tables. Finally, a path code tells EnterpriseOne where to find its check-in location. Not all objects can be converted into a relational database format; these are the source and header files of EnterpriseOne. When you check these objects in, E1 looks at the path code to determine where to store them.
Which Tables Are Used In EnterpriseOne, the F00942 table, which is contained in the system data source, is used to store path code information. This table contains several key pieces of information: ■
The name of the path code.
■
The description of the path code.
51
52
JD Edwards EnterpriseOne: The Complete Reference
■
The name of the machine that contains your path code’s source and header files. This is normally your deployment server.
■
Your server share path. This will be explained in more detail later.
■
The status code of the path code.
■
The merge option.
■
The release level of the path code. This is important because you can apply an update to one path code—for example, the development path code—but not others. This means this path code would be at a different level than the other path codes.
■
Deployment data source. This tells EnterpriseOne where to find the central object tables.
■
The Universal Naming Convention (UNC) flag setting of your path code.
■
This table is read every time a client workstation logs on to the system. For a fat client, the system then looks to see if the client machine has the proper directory structure for each path code assigned to an environment. If this structure does not exist, the environment will not be displayed to the end user, even if their user profile has been assigned this environment. This is because there would be no specifications for EnterpriseOne to run its applications on that client workstation as a local MSDE or SSE database holding XML specifications would not exist for that path code. The Double Byte field contains an XML formatted flag that denotes how textual information is stored (this flag indicates that the data source can handle double byte information).
Adding a Path Code If you need to add a path code, an experienced E1 system administrator or someone who has read this book can accomplish this in a relatively short amount of time. NOTE The only time you really need to add a new path code is if you have an environment that needs its own specific set of E1 objects. In the authors’ experience, you should only add a custom path code when it meets a business need; otherwise, all the path code does is add overhead to the system and complicate the administration of the system.
Chapter 2:
EnterpriseOne Building Blocks
There are several steps to adding a path code correctly: ■
The path code information must be added into the F00942 table.
■
The central object tables will need to be created or copied.
■
The check-in location will need to be created and the path code created on the enterprise or application server.
Adding Information to the F00942 Path Code Master Table To add path code information into the F00942 table, log on to a client workstation and go to menu GH9053 Environments. Double-click on the path code master program P980042. You will be presented with the Work With Path Codes window, shown in Figure 2-5. Click the Add button on the toolbar. This will take you to the Path Code Revisions window, shown in Figure 2-6. This window is very important. If the fields in this window are not populated correctly, you will have problems with check-in and check-out of objects, package builds, and package deployments. We list the fields on this window, explaining the use of each one and how they affect the E1 system. ■
Path Code This field denotes the name of the path code you are creating (for instance TR812).
■
Description This field provides a description of the path code (that is, Development, Training, and so on).
FIGURE 2-5. Work With Path Codes window
53
54
JD Edwards EnterpriseOne: The Complete Reference
FIGURE 2-6. Path Code Revisions window ■
Location This field indicates the name of the machine on the network.
■
Server Share Path This field provides the name of the share on the deployment server. This allows the path code to find its check-in location/ file structure on the deployment server.
■
Status Code cycle.
■
Merge Option The option set in this field determines whether the customer’s changes will be merged with the Oracle EnterpriseOne object.
■
Release
■
Deployment Data Source This field provides the location of the Central Objects for the path code (for example, Central Objects – PY812).
■
UNC Flag This field determines whether the software uses the Universal Naming Convention when making the server path.
■
Cumulative Description
■
XML Specifications This field indicates whether the Central Objects defined in the Deployment Data Source are using XML-formatted specs.
This field denotes the status of the code in the development
This field provides the release level of the product (such as E812).
This field is used by Oracle Development.
Chapter 2:
EnterpriseOne Building Blocks
Once you have filled in these fields, click OK. This will write the information to the F00942 table.
Central Objects The next step in adding a path code is to either create or copy the central object tables. We will go over the procedure of creating these tables first. You will need to execute the platform pack to install the central objects or modify the scripts that the platform pack uses. Unlike in previous releases, the scripts to create the databases are no longer stored on the deployment server but instead are delivered with the platform pack. However, the setup process also cleans these scripts up after the install completes. For this reason, to capture the scripts you need to stop the process at the third CD. This will leave the scripts on the hard drive for you to modify. These scripts can then be modified to reflect the new path code name. This will allow the platform pack to load the central objects for you. (When you install the platform pack, select only the EnterpriseOne DB components you are concerned with. See Figure 2-7.)
Courtesy of Clayton Seeley
FIGURE 2-7. Platform Pack – Feature Selection
55
56
JD Edwards EnterpriseOne: The Complete Reference
NOTE The user you specify will need to already exist in your database with sufficient privileges to create tables, or this procedure will fail. If you are using Oracle, you will also have to ensure that the table spaces exist. In previous releases, this can be done by modifying and running the CRTABSP script. In 8.12 this script will be created on the database server automatically by the platform pack. The platform pack will populate almost all of your central object tables. It will create and populate the following tables: ■
F98306
■
F98745
■
F98710
■
F98750
■
F98711
■
F98751
■
F98712
■
F98752
■
F98713
■
F98753
■
F98720
■
F98760
■
F98740
■
F98761
■
F98741
■
F98762
■
F98743
Once this process is finished, you still need to create one more central object table. That table is F983051; this table is normally loaded during the environment workbench. However, since you are only adding a path code, you are not going to execute the environment workbench. To create this table, use the following procedure: 1. Log on to the deployment server in the planner environment. 2. Open the Object Management Workbench application. You can run this application by typing OMW in the Fast Path. 3. Find the F983051 table in the Query By Example line on the Search tab and click Find.
Chapter 2:
EnterpriseOne Building Blocks
4. Select the F983051 table and arrow it over to the default project. 5. Locate the F983051 table in the default project and click on it. 6. Click the Design button. 7. Select the Table Operations tab. 8. Select Copy Table. NOTE This procedure will overlay an existing table. You will need to ensure that your source and target data sources are correct; otherwise, you risk overlaying an existing table and causing yourself some interesting problems. 9. Make sure that OneWorld Local is the source data source. 10. Enter the name of your central object or versions data source for the target data source. Since you are adding a custom path code, you would have to add this data source as described in the section “How Do You Set Up and Configure Data Sources?” 11. Click OK. This will copy the shipped Oracle F983051 table from the Planner local spec database, on your deployment server, to your central objects database. 12. You will now have the shipped F983051 created and populated in your new central objects data source. You must now update this file with a SQL statement to reflect your path code and deployment server’s name. Use the following select and update statements. In the authors’ experience, you should always do a select statement before your update statement to ensure you are actually updating the records you think you are updating. select * from XXXX.F983051 where VRENHV = 'PATH CODE' and VRMKEY = 'SERVER';
The XXXX is the user that you set up to own your central object tables. Now that you know what records you are going to update, you can perform the following update statement: update XXXX.F983051 set VRENVH = 'YOURPATH CODENAME' and VRMKEY = 'DEPLOYMENT SERVER NAME' where VRENVH = 'PATH CODE' and VRMKEY = 'SERVER';
57
58
JD Edwards EnterpriseOne: The Complete Reference
You have now created your custom central object tables. These tables will contain all of the shipped Oracle objects. Now let’s go over how you would copy an existing set of central object tables. You would do this when you want your new path code to match the source path code. EnterpriseOne contains a utility to copy an existing set of central object tables. This utility is UBE R98403, version XJDE0019. You can get to this report by typing BV in the Fast Path or going to menu GH9011 and double-clicking on P98305 Batch Versions. Highlight the XJDE0019 and go to Form Processing Options (see Figure 2-8). These processing options are very important, as R98403 is a utility that will copy tables between different data sources in EnterpriseOne. Yes, that means you can copy a table between different types of databases as well as copying the tables between different owners in the same database. This utility is Oracle’s recommended way of moving large amounts of data.
FIGURE 2-8. R98403 Processing Options dialog box
Chapter 2:
EnterpriseOne Building Blocks
Enter the following processing options, which you will see on the R98403, to copy your source path code into your new custom path code. On the Environment tab, enter the following information: Processing Option
Description of Processing Option Values
1. Enter the environment the database is created for. (If this report is called from another process, the environment will be passed in.)
You can enter the name of the environment to which you are copying the information. When this field is filled in, the report uses OCM mappings to find the target data source. The other process that would call this report is the environment workbench, as Oracle uses this utility to create EnterpriseOne tables during an installation or upgrade.
2. Or enter the data source the database is created for.
Unless you are copying tables that exist in more than one data source, you should use this option in R98403. Place the name of your custom central objects data source in this field. Either processing option 1 or processing option 2 needs to be filled in, not both.
3. Enter a 1 to load production data or a 2 to load demonstration data. The default is to load production data. (If the report is called from another process, this flag will be passed in.)
This setting often confuses users. If you choose 1 to load production data, the report will create all the tables blank, except the ones necessary to run EnterpriseOne. In this instance, you will need to choose 2 so that the contents of your source path code tables will be copied into your target path code.
4. Enter the data source for loading data. (If the report is called from another process, this value will be passed in.)
Fill this field with the name of your central objects data source (for example, Central Objects – PD812).
5. Enter the environment the database is created for. (If this report is called from another process, the environment will be passed in.)
You can enter the name of the environment you are copying the information from. When this field is filled in, the report uses OCM mappings to find the target data source. The other process that would call this report is the environment workbench, as Oracle uses this utility to create E1 tables during an installation or upgrade. Again, 4 and 5 are either/or, not both.
59
60
JD Edwards EnterpriseOne: The Complete Reference
On the Update tab, enter the following values: Processing Option
Description of Processing Option Values
6. Enter 1 for proof or 2 to create the environment database.
If the job is run in proof mode, it will not copy tables; it will just show what it would have done. It is generally a good idea to run the job in proof mode first to verify it is affecting the tables that you want it to hit.
7. Enter an A to re-create existing tables in data sources that allow automatic table creation. The default is not to re-create tables.
For the purposes of copying an existing set of central object tables, this value should be set to A.
Any existing tables will be overwritten, so be sure that your processing options are correct before running this report in update mode. 8. Enter a 1 to copy only tables that exist in the target data source.
When this value is set to 1, the UBE will copy only the tables that exist in the target data source. This value should be blank to copy your path code tables.
9. Enter a Y to add records without clearing the target table. This is used for language tables.
When this option is set to Y, the UBE will append to the table. Leave this field blank for the purposes of creating new central object tables.
Accept the defaults on the Print and Licensing tabs. The default values for these tabs are blank. Click OK to save your processing options. You will now be back at the Work With Batch Versions window. Highlight XJDE0019 and click Select. You will then be presented with the Version Prompting window. Go to Form Advanced; this will take you into the Advanced Version Prompting window (see Figure 2-9). Check the Override Location box and click OK. You will now be back at the Version Prompting window. Click Submit, select the local data source, select the output to be displayed onscreen, and the job will start running. This job will then copy the central object tables from your source path code to your new path code’s central object data source. If you have problems with this report, look at the JDE.LOG file, which will normally be located on the root of your C drive. You can also look for a JDECPY.LOG on the C root of your machine. This log will tell you what tables are copied and how many records succeeded and how many failed. A benefit of running R98403 to copy an existing central object path code is that this tool will copy the F983051 table and update the table with the name of your deployment server and path code name. However, just to be safe, you should confirm that these values are correct after your job completes.
Chapter 2:
EnterpriseOne Building Blocks
FIGURE 2-9. Advanced Version Prompting window NOTE You do not want to use SQL Server or Oracle’s builtin bulk copy functionality to copy these tables, as padding issues have been encountered when this type of copy is used. However, what you can do is export your tables to a dump file and then restore them to a new owner. This is a quick way of copying tables, but when you use this method, you will have to update the F983051 table to reflect your deployment server and path code name. This method should only be used when you have a database administrator or if you possess the database skills necessary to perform this operation.
Creating the Check-in Location The final part of adding a path code is to create the check-in location and create the path code on the enterprise server.
61
62
JD Edwards EnterpriseOne: The Complete Reference
Before we cover the actual process of creating the check-in location, we should go over exactly what a check-in location is, in reference to EnterpriseOne. When you entered the path code information into the path code master application, you entered the name of a server in the Location field. This is how E1 knows where to copy the source and header files when objects are checked in. Some examples of objects that have source and header files are business functions and tables. These files are not stored in a relational database format, so they need to be stored in a directory structure. TIP A common problem for developers checking in objects is receiving the error “Cannot copy file.” This error normally means the user does not have the permissions to copy a source or header file into the check-in location or EnterpriseOne cannot find the check-in location due to an incorrect setup. You can create the check-in location in two ways: by manually copying the directory structure through Windows Explorer or by running a report. To create it manually, open Windows Explorer on your deployment server and create a folder with the same name as your custom path code under EnterpriseOne\E812. Copy the contents of the PS812 directory into this new folder, if you are creating your custom path code from scratch. If you are copying an existing path code, you will need to copy that path code’s directory structure. If your new path code was named TEST812, for example, you would copy the contents of PS812 or another path code into TEST812. This is because you need to move the source and header records that match your central object tables. If you do not want to do this process manually, you can run a report to copy these directory structures. This report is R9800942. To run this report, type BV in the Fast Path. You will now be in the Batch Versions window. Type R9800942 in the Batch Application field. Highlight the XJDE0001 version and click Select to submit the job. Be sure to run the job locally by going to the Form Advanced option on the Version Prompting window and checking Override Location. When you submit the report, you will be prompted to enter some processing options. Processing Options
Description of Processing Option Values
Source Path Code
This is the path code that you are copying—in our example, PS812.
Destination Path Code
This is your target path code. In our example, this would be TEST812.
Chapter 2:
EnterpriseOne Building Blocks
Processing Options
Description of Processing Option Values
Copy Package
Enter a Y if you want to copy the packages that currently exist in your source path code. Normally, you would enter a Y so that you could deploy a package immediately, thus allowing your end users to work, and build a package later to test the new path code. NOTE: In 812 we are not able to copy packages when copying path codes. The reason for this is that specifications are now stored in the XML format in the database. These tables are named to match the name of the package.
Update F9861 Copy Local or Deployment
This setting will determine whether you copy the path code information locally on a workstation or on the deployment server.
Creating the Path Code on the Enterprise Server Unfortunately, the only way to get a path code onto the enterprise server is by manually making a manual copy. When you perform this manual copy operation, be sure the host services are stopped. Then all you have to do is copy the directory structure. So let’s say you are copying the PD812 path code; you would copy the path code information from one directory to the other (for example, PD812 to TEST812) and then update the spec.ini file. This file tells the server where to look for the XML specifications in the RDBMS. You would update the file to include a data source pointing at the central objects of the new path code (Central Objects – TEST812). CAUTION When you do this, be sure your host services are stopped.
Modifying the F9861 Table You now have a path code master definition in the F00942 table, you have your central object tables, and you have your check-in location created. The only thing you have left to do is modify your F9861 object librarian detail table. (This only needs to be done if you did not set the Y parameter when you ran R9800942 before.) This table will need to reflect your deployment server name and your new path code name; this is so that your developers can check out objects and work on them. To update this table, you can use SQL statements or you can run R989861 (Update/ Write F9861). Figure 2-10 provides an example of the R989861 processing options.
63
64
JD Edwards EnterpriseOne: The Complete Reference
FIGURE 2-10. R989861 Processing Options If you are not familiar with SQL statements, you will want to run the R989861 report. To accomplish this, log on to a client workstation. The environment does not matter as all environments use the same object librarian. Type BV in the Fast Path and press ENTER. You will now be on the Work With Batch Versions window. Highlight the XJDE0001 version and click Row Processing Options. Enter the source path code you want to copy records from. If you created your path code from scratch, you will want to copy a pristine path code that does not have custom objects in it. This is because the UBE will place a record in the F9861 object librarian detail table for every entry of the source path code. If you have custom objects in this source path code, but have created your central object tables from scratch, it would appear that this custom object existed in the new path code even though it did not. So when your developers go to check this object out, they would receive an error. EnterpriseOne would not be able to find the object in the central object tables, although the object would appear as if it existed in that path code in the object librarian.
Chapter 2:
EnterpriseOne Building Blocks
If you copied an existing path code’s central object files and check-in location, use that path code as your source path code. The target path code will be the name of your new path code. Click OK to save your processing option changes. You are now back in the Work With Batch Versions window; highlight XJDE0001 and click Select. Go to Form Advanced and check the Override Location box, then click OK. You are now back at the Version Prompting window. Click the Submit button. You will be prompted for your processing options again; just confirm they are correct and click OK. EnterpriseOne will then ask you where you want to run the job. Choose LOCAL; this will cause the job to run on your local workstation. This job cannot be run on the enterprise server. The job will then enter your new path code into the F9861 table. To check the job after its completion, go into the Object Librarian application, click Find, select a shipped Oracle object, and click Select. You should now see your path code in the check-out line in the Design Aid window. The second way to update the F9861 table is by using a SQL statement to create a temporary table. Update this table and copy the records from it into your original F9861 table. Use the following SQL statements. First create the temporary environment: create table temp.f9861 as select * from ol.812.f98761 where SIMKEY = 'DEPLOYMENTSERVERNAME' and SIPATHCD = 'PRODB733';
NOTE If you are using Oracle, remember to perform a commit statement: select count(*) from temp.f9861; select count(*) from f9861 where SIMKEY = 'DEPLOYMENTSERVERNAME' and SIPATHCD = 'PRODB733';
You now will need to update your F9861 temporary table so that it contains the correct information and then copy the contents back into your original F9861 table: update temp.f9861 set SIPATHCD = 'TEST812';
NOTE If you are using Oracle, be sure to run a commit statement: commit; insert into ol812.f9861 select * from tempF9861;
Once you confirm that your new path code is in the F9861 table, you can drop this table by using the following statement: drop table temp.f9861;
65
66
JD Edwards EnterpriseOne: The Complete Reference
Deleting a Path Code To delete a path code, you must perform several steps: 1. Remove the path code record from the F00942 table. 2. Delete the central object tables. 3. Manually delete the check-in location and path code directory on the deployment and enterprise servers. To delete the path code record from the F00942 table, from the client workstation, or on the deployment server in the deployment environment, go to menu GH9053 and double-click on the Path Code Master P980042. You will now be in the Work With Path Codes application. Click Find, highlight the desired path code, and press DELETE. This will remove the path code record from F00942. This does not delete the central object tables or remove the path code’s directory structure from the deployment or enterprise server. Have your database administrator drop the appropriate central object tables; he or she can do this by searching for the owner of these tables and then dropping all tables that are owned by that owner. Next you will need to delete the data sources associated with this path code. This can be done through the database data source application on menu GH9611. Finally, from Windows Explorer on the deployment server, highlight the path code directory under EnterpriseOne\E812 and press DELETE. You will also have to delete the directory structure for your path code from your enterprise server. This procedure will vary a bit depending on your platform. However, no matter what platform you are on, you will need to ensure that your host services are down when you remove the path code’s directory structure from the enterprise server. Now that you have seen how to find the data and define the applications that are used in EnterpriseOne, let’s look at how you combine the applications with the data to create an instance of the EnterpriseOne product. The tool used to do this is Environment Master.
Environments
This section goes into detail about how EnterpriseOne environments work. It describes what an environment is and how this feature of E1 ties into the entire system. An environment can be described as the framework on which the system rests. This framework is made up of object configuration mappings and a path code. These are what tell EnterpriseOne where to find the data and specification files needed for its applications to run. We have just gone over what a path code is in detail in the last section. In this section, we will cover the following:
Chapter 2:
■
Definition of an environment
■
Tables used for environments
■
Adding an environment
■
Copying an environment
■
Deleting an environment
■
When to create a custom environment
EnterpriseOne Building Blocks
Definition of an Environment An environment is the framework on which your business runs. This framework is how EnterpriseOne finds the company’s business data. It also allows E1 to find other objects, such as a business function; this helps run the system more efficiently. To keep what an EnterpriseOne environment is straight in your mind, just remember that an environment consists of object configuration mappings and a path code. A mathematical representation of this would be Env = OCM + Path Code
Tables Used for Environments EnterpriseOne touches or uses several tables to keep track of environment information. These tables are system files, meaning they are contained in the E1 system data source. ■
F0093 – Library List Control
■
F0094 – Library List Master
■
F00941 – Environment Detail
■
F986101 – Object Configuration Manager
■
F98611 – Data Source Master
■
F00942 – Path Code Master
The F0093 library list control table contains a list of the environments users are authorized to gain access to. This table is read when a user logs on to E1; the software then displays the environments they can log on to. The F0094 library list master file basically contains the header record information for an environment. You can find the environment name and its description in this table. More detailed information is contained in the F00941 environment detail table.
67
68
JD Edwards EnterpriseOne: The Complete Reference
The F00941 environment detail file contains information on the name of an environment, the path code it is associated with, if just-in-time installation is turned on or off for the environment, and the release level of the environment. The F986101 is the Object Configuration Manager table and acts like the traffic cop of EnterpriseOne. This table contains mappings, which tell the system what data source the data is stored in. The F98611 is the data source master table. Once the system finds a mapping, in the F986101, it then has a data source name. It needs to read that data source in order to determine what type of database the business data is contained in, what machine these tables reside on, and how to connect to that database. All of this information is contained in the data source master table. The F00942 path code master file contains information on the path code an environment is associated with. A path code tells EnterpriseOne where to find the specifications it needs to run its applications and where the check-in location is located on the system.
Adding an Environment Adding an environment is actually a simple process. If you are in E1, you can add an environment from the Environment Master program (P0094), located on the Environments menu (GH9053). When you double-click on this program, you will be taken to the Work With Environments window (see Figure 2-11).
FIGURE 2-11. Work With Environments window
Chapter 2:
EnterpriseOne Building Blocks
On this window you will see the Display Only JD Edwards Environments check box (this will limit the environments displayed). You can add an environment by clicking the Add button to bring up the Environments Revisions window. The Work With Environments window has several important fields: ■
Environment Name example, JTR812.
■
Description Enter a description of the environment, such as “Atlanta’s production environment.”
■
Path Code This is the path code associated with the environment. The path code is the way E1 finds the specifications it needs to run its applications. These are contained in the central object tables or XML files, depending on what area of E1 you are trying to use.
■
Release
■
Just In Time Installation This field can be used to enable or disable just-intime installation of applications to workstations in the environment. If you set this to N, your clients with partial packages will not be able to pull down applications. This is why you should use caution when setting this feature of EnterpriseOne.
■
Developer
■
WAN Configured Environment This check box is used to tell EnterpriseOne if the environment is going to be used for a WAN. If this box is checked, it will affect the object configuration mappings.
Place the name of your environment in this field—for
This is the release level of software you are on.
This is a future use field.
NOTE You must ensure that your environment is associated with a path code. If it is not, the software will not be able to find your check-in location or your central object tables. This means that you will have problems with package builds and the check-in/ check-out process. TIP It is important to realize that when you add an environment, you will have to manually add all your object configuration mappings. This is why, in the authors’ experience, you will almost never want to add an environment from scratch. It is much simpler to copy a shipped Oracle environment and modify it to suit your needs.
69
70
JD Edwards EnterpriseOne: The Complete Reference
Copying an Environment The feature that allows you to copy an environment is one you will use more than anything else in the Environment Master program. When you copy an environment, you can copy the mappings of the environment as well. This is useful, as many of the mappings in the Object Configuration Manager are the same for all environments. These shared mappings are to data dictionary, object librarian, and system tables. If you add an environment, you must manually add all the mappings to certain tables, such as system tables, that are necessary for the EnterpriseOne software to run. To copy an environment, click the Row Copy Environments button from the Work With Environments window. You will be presented with the Copy Environment window. Enter the desired name of your new environment in the New Environment field. Be sure to note the check box labeled Copy *Public Records Only. When this box is checked, you will only copy the Object Configuration Manager mappings for *PUBLIC. This means that mappings for individual users would not be copied. In most circumstances, you will want this box checked. When you click OK, EnterpriseOne will write to the F0094, F00941, and F986101 tables. What about the path code? When you copy an environment, the new environment is associated with the copied environment’s path code. One path code can have many environments assigned to it, but each environment can only be assigned to one path code. What this really means is that EnterpriseOne environments can share the specifications for applications. So you can have two environments that have the same application functionality but point to different business data. This is useful when you have a company with different departments that need the same functionality, but also need their own business data.
Deleting an Environment When you are in the Environment Master program, P0094, highlight an environment and click the Delete button on the toolbar. This will remove the records for the environment from F0093, F0094, F00941, and F986101. NOTE When you delete an environment, you are not automatically deleting the data sources and business data associated with that environment. This will need to be done as a separate step.
When to Create a Custom Environment When do you need a custom environment and when is it just extra overhead? This is a question that faces a lot of EnterpriseOne system administrators. Each custom environment should have a business purpose. One good example would be two
Chapter 2:
EnterpriseOne Building Blocks
departments that both need to use the same custom applications, but also need to have their own business data, menus, or user-defined codes. We cannot stress enough that the system is only there to meet the business’s needs, so any environment that does not address a business need is extra overhead and should not be in the system.
Object Configuration Manager
In this section, we will discuss one of the nerve centers of an EnterpriseOne system, the Object Configuration Manager (OCM). The OCM program is truly the nerve center of EnterpriseOne, the application that tells the system in what data source data resides. If there are incorrect entries in this program, E1 will not function correctly. To avoid this, we will go over several areas of the Object Configuration Manager, including: ■
The definition of the Object Configuration Manager
■
Tables that are used
■
What really happens when a workstation requests data or logic
■
What happens when a workstation runs a UBE
■
How to add OCM mappings
■
How to copy OCM mappings
■
How to delete OCM mappings
■
The difference between system and server map
■
Changing the mappings for object librarian tables
■
Changing Oracle parameters that E1 uses
■
Advanced Object Configuration Manager operations
Definition of the Object Configuration Manager The Object Configuration Manager is key to an EnterpriseOne system. It allows separate environments to access data on a variety of machines and databases. Think of this program as the nerve center of EnterpriseOne where you can configure and guide the system. The program allows you to configure E1 in almost unlimited ways. Using this program, you can tell the system on what machines and databases business data resides, where to run reports, and where to run business functions.
71
72
JD Edwards EnterpriseOne: The Complete Reference
You will always have two types of OCM mappings. These are system mappings and server map mappings. The system mappings are used to direct client workstations to business data tables and business functions, and to tell them where to run UBEs. Once a mapping is found, EnterpriseOne determines what data source is to be used from the mapping and passes the information in that data source to JDEBase. JDEBase is the kernel software of EnterpriseOne that will make the call to the database; it can determine how to construct the SQL statements based on the platform and the type of database being used. The server map mappings, or OCM, are used once a UBE is run on an enterprise server. The report then looks at the server map OCM tables to find the necessary tables to run. Since this application is so powerful, we recommend that only system administrators have access to this program. You can restrict the use of this program through EnterpriseOne security.
Tables That Are Used The Object Configuration Manager mainly uses the F986101 object configuration master table. This table contains the environment names, user, objects, object type, object status, and primary data source value (see Figure 2-12). This information makes up an OCM mapping. The environment value is just an environment name. The user can be a specific user such as JDE, a user role, or *PUBLIC. The object type provides the ability to define DEFAULT mappings based on the type of object (TBLE or Tables). The primary data source value contains a data source; this data source is what gives the system the final information on where the relational database tables, which the software is looking for, reside. There can be many copies of this table on an EnterpriseOne system. The workstations will use one copy, in the system data source, to find their data. The enterprise and logic servers have their own copy of this table, which is used when a report is run on an enterprise or logic server. The F986101 table really only consists of what is called OCM mappings. These mappings tell the system what data source the table resides in, where to run its business functions, and how to process its reports.
What Really Happens When a Workstation Requests Data or Logic When a workstation requests data or logic, it must use the F986101 object configuration master table as a guide. The workstation will poll this table looking for certain information. It will look for the environment that is needed, the user who is logged on, and the object that has been requested. How this works will become clear after we go through an example of a workstation’s request for data. When a workstation requests data, it will read F986101 in a particular manner. The system
Chapter 2:
EnterpriseOne Building Blocks
FIGURE 2-12. OCM Mapping will pass select statements using F986101’s primary keys. It will look for the environment, an object name, a user, and a primary data source. The system will also only look for mappings that have a status of AV, for active. Figure 2-12 is an example of an OCM mapping. This mapping is what is going to tell EnterpriseOne in what data source the table that the system is looking for resides. We will discuss each individual part of this mapping later in this section; for now, let’s take a look at how E1 reads mappings. The system reads the F986101 using the following logic: 1. The system knows you are logged in to the PD812 environment and you are looking for an object of type TBLE, since that is what the application you are running tells the system.
73
74
JD Edwards EnterpriseOne: The Complete Reference
2. The system will then poll F986101 for an environment—in this case PD812—a status of AV, a type of TBLE, the object name, and the user who is logged on to the system. 3. If these are not found, EnterpriseOne will look to see if there is a record for the environment, a status of AV, a type of TBLE, the object name, and a role that the user logged on to the system belongs to. NOTE In 8.12 a single user can belong to multiple roles. For this reason, the OCM application will search through all of the roles associated with the user ID. 4. Next, it will look for a record for the environment, a status of AV, a type of TBLE, the object name, and the user *PUBLIC. 5. If EnterpriseOne still does not find the mapping, it will poll F986101 for a record with the environment, a status of AV, a type of TBLE, an object name of DEFAULT, and the user who is signed in to EnterpriseOne. This object name of DEFAULT is used so that the F986101 does not need a record for every object. This helps improve performance. 6. If this does not return a mapping, the system will then look for a record with the environment, a status of AV, a type of TBLE, an object name of DEFAULT, and a role. 7. Finally, EnterpriseOne will poll F986101 for a record with the environment, a status of AV, a type of TBLE, an object name of DEFAULT, and the user *PUBLIC. Once E1 has found the mapping, it uses the data source contained in that mapping to determine what type of database to connect to, what machine, and what owner or library. It passes this information to JDEBase, which knows how to construct calls to these databases and platforms. This same process occurs for both workstations and HTML clients (although HTML utilizes Java Database Connectivity [JDBC] for its connections).
What Happens When a Workstation Runs a UBE When a workstation attempts to run a UBE, the logic that EnterpriseOne follows to determine where this report should be run is similar to how the system polls F986101 for data. The process is also the same for business functions. Let’s step through the logic one more time, this time for a report being run from a client workstation.
Chapter 2:
EnterpriseOne Building Blocks
1. The system knows you are logged on to the PD812 environment and you are looking for an object of type UBE, since that is what the report you are running tells the system. 2. The system will then poll F986101 for an environment—in this case PD812—a status of AV, a type of UBE, the object name, and the user who is logged on to the system. 3. If this is not found, EnterpriseOne will look to see if there is a record for the environment, a status of AV, a type of UBE, the object name, and a role that the user logged on to the system belongs to. 4. Next, it will look for a record for the environment, a status of AV, a type of UBE, the object name, and the user *PUBLIC. 5. If EnterpriseOne still does not find the mapping, it will poll F986101 for a record with the environment, a status of AV, a type of UBE, an object name of DEFAULT, and the user who is logged in to E1. This object name of DEFAULT is used so that F986101 does not need a record for every object. This helps improve the performance of the system. 6. If this does not return a mapping, the system will then look for a record with the environment, a status of AV, a type of UBE, the object name of DEFAULT, and role. 7. Next, EnterpriseOne will poll F986101 for a record with the environment, a status of AV, a type of UBE, an object name of DEFAULT, and the user *PUBLIC. If a record is found, E1 sends JDENET the proper information. JDENET is the area of EnterpriseOne that handles sending messages between servers and clients. These messages are not database calls. This is how the enterprise server knows what report, version, and data selection to run, because the information is passed to it from JDENET. Once the enterprise or logic server receives the request, it responds by processing the UBE. NOTE The only call to F986101 in this example was to find out where to process the logic. Once the server starts to process the report, it will read F986101 in the server map data source to find the data required by the UBE. The logic behind this process is the same as the one described in the section “What Happens When a Workstation Runs a UBE.”
75
76
JD Edwards EnterpriseOne: The Complete Reference
Some people ask, why have multiple OCMs at all? Why not just read one and be done with it? Well, there are several reasons for having a server map F986101. A primary reason is performance and configurability. By having multiple copies of the OCM table you can provide yourself with a greater level of control on what runs where in your implementation. Your enterprise server also might be located across a WAN and you do not want to have it make calls across the WAN to find its data, as this could slow your system down.
How to Add OCM Mappings You will only need to add a new OCM mapping when you need a specific user, role, or environment to look for its data, business functions, or where to process its UBEs in a different spot. Say you have 20 people in accounting, but only one runs your payroll checks. You want all this person’s reports to run on one specific machine, and you want this person to look for their tables in a certain database. You can handle all this by adding OCM mappings for type UBE for this user’s reports and of type TBLE for the tables that he needs to find in a different location than other users. These OCM mappings allow you to configure the system to run in a way that supports your business operations. To add an OCM mapping, log on to a client machine. The reason you are logging on to a client machine is that it will update the system F986101. When you log on to the deployment server in the planner environment, it will change the F986101 contained in the planner MSDE or SSE database. Since this is not the database accessed by your end users for mappings, you normally do not want to change your mappings in this database. Once you have logged on to the client machine, type OCM in the Fast Path or go to menu GH9611 (Advanced Operations) and double-click on P986110, Object Configuration Manager. You will then be prompted with the Object Configuration Manager Machine Search & Select window. This window allows you to modify either a server map F986101 table or the system F986101 table. Normally you will choose a system to change a mapping for your client workstations. However, when you change these mappings, you should always ask yourself, does this mapping need to be changed in the server map F986101 as well? If you change the mappings for your users in the system data source, but not the server map data source, you may see different results when running reports locally compared to reports run on the server. You will now be on the Object Configuration Manage Work With Object Mappings window. Click the Add button located on the toolbar. This will take you into the Object Mapping Revisions window, shown in Figure 2-13. The Object Mapping Revisions window contains the following fields: ■
Environment Name Enter the name of the environment that you want OCM mapping to affect.
Chapter 2:
EnterpriseOne Building Blocks
FIGURE 2-13. Object Mapping Revisions window ■
Object Name Enter the name of the object the mapping is for. If you want the mapping to affect all non-mapped object names of a certain object type, enter DEFAULT.
■
Primary Data Source This is the data source in which E1 will look for your object. If you are mapping a business function or a UBE, the data source must be a logical data source. If you are mapping a table, the data source must be a database data source.
■
System Role Enter the user or role you want this mapping to affect. You can enter a specific user, such as JDE, a specific role, or *PUBLIC.
■
Object Type This is the type of object you are mapping. This field is grayed out and will default based on the Object Name field. However, if the object name is DEFAULT, you will be allowed to choose your object type. E1 allows you to map UBEs, tables, generic text (object type of GT), and business functions (object type of BSFN).
77
78
JD Edwards EnterpriseOne: The Complete Reference
■
Data Source Mode This indicates whether EnterpriseOne should use the data source specified in the primary data source field or the secondary data source field. The valid values for this field are P for primary and S for secondary. You will almost never use S.
■
Secondary Data Source EnterpriseOne uses this data source if the object cannot be found in the primary data source.
■
Allow QBE This flag is used to turn on and off row-level record locking. The acceptable values for this field are: ■
All QBE allowed
■
No QBE allowed
■
Indexed fields QBE allowed (this is recommended)
EnterpriseOne will look at this field to determine if JDEBase uses row-level record locking. Oracle recommends that this functionality be turned on to prevent data integrity issues. Once you have filled in these fields, click OK to commit the record. EnterpriseOne will write the record to the F986101 table. It will then blank out the Environment Name field, Object Name, and Primary Data Source, and return the System Role to *PUBLIC. If you do not want to add any more mappings, click Cancel, which will take you back to the Work With Object Mappings window (see Figure 2-14). NOTE You may receive a warning on this window if the table does not exist in the data source your mapping points to. This warns you that you are creating a mapping that points to a location where the table does not reside. You can set a processing option for the Object Configuration Manager to have this appear as an error or a warning. Go to menu GH9011, System Administration Tools, and rightclick on the Object Configuration Manager program. Choose Prompt For Values. You will be allowed to enter a 1 to have the Object Configuration Manager produce a hard error when a mapping points to a location where the table does not exist. The other option is to leave this value blank and only a warning will be issued. EnterpriseOne is shipped with this value set so that you will only be presented with a warning and not a hard error.
Chapter 2:
EnterpriseOne Building Blocks
FIGURE 2-14. Work With Object Mappings window Now that we have added a new mapping, we must activate it. When a mapping is added to EnterpriseOne, the status is set to NA (not active). E1 will ignore the mapping until the status is set to AV (active). To set your mapping to AV, enter the object name in the QBE line and click Find. Highlight your mapping and go to Row Change Status. This will change the status of the mapping from NA to AV. TIP You may want to click Find to refresh your screen and ensure that the status of your mapping has changed. NOTE The F986101 table is cached upon logon, so your client machines will have to log out and back into EnterpriseOne to use the mapping change. The HTML instance would need to be stopped and restarted or the cache cleared through SAW/Server Manager in 8.97 to ensure that change has been read into memory.
79
80
JD Edwards EnterpriseOne: The Complete Reference
How to Copy OCM Mappings You will often need to set up a mapping for the same object in several environments. Copying an OCM mapping can save you some time and typing. To copy an Object Configuration Manager mapping, from the Work With Object Mappings window, highlight the mapping you want to copy and click the Copy button on the toolbar. You will now be on the Object Mapping Revisions window, like when you added a mapping. However, this time all the fields will be filled in for you, with the information from the mapping that you are copying. You can now modify the mapping as necessary. This feature saves time when you are mapping several objects to the same data source. Remember that once you click OK to commit the record to F986101, you will also have to activate the mapping.
Deleting an OCM Mapping Deleting an OCM mapping is a simple process. When you are on the Work With Object Mappings window, highlight the desired OCM record and click the Delete button on the toolbar. This will remove this record from the F986101 table. Remember that if you remove a mapping from the system data source, your client machines will need to log out and back into E1 before they will be able to see the change. If you change a server map F986101 entry, you will need to stop and start your host services to ensure that the mapping takes effect. You will also need to clear the cache for the HTML clients via SAW/Server Manager (8.97) or by stopping and restarting the Web Services (WebSphere orOAS). NOTE All *PUBLIC mappings will have to be deactivated prior to being deleted.
The Difference Between System and Server Map We have skirted the differences between the system and server map OCM mappings throughout this section. However, we will now address them head-on. The Object Configuration Manager is truly the nerve center of EnterpriseOne. The system F986101 table tells client workstations where they need to look for their data, process their UBEs, and run their business functions. So any changes to this table will directly affect the client workstations. The server map F986101 table is used once a UBE starts to run on the enterprise or logic server. The UBE will read this table to determine where it needs to find its data and business functions.
Changing the Mappings for Object Librarian Tables This procedure will go through changing the OCM mappings for object librarian tables. Before you even think about attempting this procedure, you need to understand what changing the mappings for the object librarian tables truly means. It means your EnterpriseOne system will have multiple object librarian data sources.
Chapter 2:
EnterpriseOne Building Blocks
The object librarian is how E1 keeps track of the objects in the system. This is what ensures that you do not have more than one object with the same name. However, if you add another mapping for the object librarian tables, you will have two object librarians. That means you could have two objects named the same in the E1 system. So if you performed an object transfer between the two path codes with which the environments are associated, you would overlay one of the objects. The other thing to keep in mind is that in all the authors’ experience, we have not set up a system in this manner. This process should only be attempted by someone with advanced Configurable Network Computing (CNC) knowledge, as the possibility of introducing problems into the system exists. DEFINITION Configurable Network Computing (CNC): This is a term used by Oracle to describe their software’s ability to be easily configured to meet business needs. This describes the ability of the software to run on multiple platforms against different types of databases. To remap the object librarian tables to a new object librarian data source, you need to do the following: 1. Log on to a client workstation and go to the Object Configuration Manager program. You can find this program on the GH9611 menu or by typing OCM in the Fast Path. 2. You will be prompted to select either the system or server map on the Machine Search & Select window. Select your system data source. 3. You will now be on the Work With Object Mappings window. 4. Go to Form Revise OL Data Source. 5. You will then be prompted for the path code and OL data source. The reason you are being prompted for a path code and not an environment is that the object librarian is used to keep track of objects in path codes, and each environment is associated with a path code. So when you enter a path code on this window, EnterpriseOne will remap the object librarian tables for all the environments associated with this path code. 6. After you have entered the path code and your new object librarian data source, which must contain all the object librarian tables, click OK. 7. You will now be back on the Work With Object Mappings window. Your client workstations will need to log out and back in to see this change.
81
82
JD Edwards EnterpriseOne: The Complete Reference
CAUTION Although this procedure is documented and any package builds should find the new object librarian mappings, the support line will probably caution you against using this functionality, due to the added complexity of system maintenance with two object librarians and the opportunity for introducing errors into the system.
Changing Oracle Parameters That EnterpriseOne Uses If you are using Oracle with EnterpriseOne, you will need to pay attention to the Oracle parameter values that can be set within the system. If you use the standard Oracle shipped environments and data sources, you will not need to worry about these settings. However, if you add a custom data source or do not follow the standard Oracle naming conventions, you will want to look at these settings. You can use these settings to control certain things within E1, such as what Oracle table space and index space your data sources use. You can also control certain Oracle settings on specific tables within EnterpriseOne for Oracle parameters. The system stores all the values we are about to discuss in the F986115 table (Table and Data Source Sizing). This table is a system table, meaning it is located in the E1 system data source. To set the Oracle parameters, go to menu GH9011 and double-click on Object Configuration Manager or type OCM in the Fast Path. Select the system data source when prompted on the Machine Search & Select form. You will now be on the Work With Object Mappings window. From this window, go to Row Oracle Prams. You will now be on the Oracle Database Object Sizing window (shown in Figure 2-15). Depending on the database you are using, this window will allow you to configure the system for table and data source sizing. Enter an asterisk (*) in the Data Source field, enter DEFAULT in the Object Name field, and click Find. This will show you the DEFAULT records for all your data sources. (Another way to access this window is from the DB Data Source window.)
Chapter 2:
EnterpriseOne Building Blocks
FIGURE 2-15. Oracle Database Object Sizing window Select one of these records; you will now be on the Revise Table and Data Source Sizing window. This window has a couple of important fields. You can define the Oracle table space and index space you want EnterpriseOne to use when the system tries to find an object in this data source. In Figure 2-16, the system would attempt to use the crpdtat table space and crpdtai index space when it tries to locate a table using this data source. If you add a custom data source, you will need to use this window to tell EnterpriseOne what table space and index space to use in Oracle. EnterpriseOne also gives you the ability to affect Oracle parameters on individual tables within a table space. EnterpriseOne is shipped with only the Oracle table space and index space defined for EnterpriseOne standard data sources. EnterpriseOne does not ship Oracle settings for specific tables. If you want to use this feature, click the Add button in the Work with Table and Data Sizing window. You will then be prompted with a new form to revise the table and data source sizing, labeled Oracle Database Object Sizing.
83
84
JD Edwards EnterpriseOne: The Complete Reference
FIGURE 2-16. Oracle Database Object Sizing window This window allows you to set some specific table and index information for Oracle on individual tables. You can also leave the Data Source field blank, which asks EnterpriseOne to use the specified settings for this table in all data sources, or you can specify a specific table and data source. You can also only specify a data source and ask Oracle to use the parameters on all tables within that data source. That being said, let’s take a look at what Oracle settings you can specify from within EnterpriseOne. On the lower half of this window, you can specify table and index information. The system will allow you to specify the following Oracle parameters: ■
Table/Index Initial Storage
■
Table/Index Next Storage
■
Table/Index Percent Increase Storage
■
Table/Index Minimum Extent
■
Table/Index Maximum Extent
Your Oracle database administrator should be the person who sets this screen up. You may also want to run with these settings only defined in Oracle and not E1. That is an option, as setting the table information and index information in
Chapter 2:
EnterpriseOne Building Blocks
EnterpriseOne is not a mandatory procedure. Setting up the table space and index space that a custom E1 data source will use (as described earlier), however, is a mandatory procedure.
Revise Table and Data Source Overrides Screen There is one final setting that can be changed from the Work with Table and Data Source Sizing window. This setting applies to all types of databases, not just Oracle. If you highlight a data source in the grid and go to Row Overrides, you will be taken to the Revise Table and Data Source Overrides window (see Figure 2-17). This window will default in the Release, Data Source, and Object Name fields (if applicable). The only two fields you are allowed to modify on this window are Copy Data and Create Tables. It is very important that these fields be set correctly for your data sources, as these values are used by R98403 to determine whether tables should be created and whether data should be copied. ■
Copy Data Currently this field is not used. However, if you add a custom data source, set this value to Y.
FIGURE 2-17. Revise Table and Data Source Overrides window
85
86
JD Edwards EnterpriseOne: The Complete Reference
■
Create Tables This setting will accept either a 0 or a 1 as a valid value. If the field is blank, EnterpriseOne considers it to be a 0 value. When this field is set to 1, E1 will automatically create the tables in this data source during the environment workbench, so any tables mapped to this data source will be created. If this field is set to 0 or is blank, the environment workbench and R98403 will not create tables in this data source. This means you would have to create them by hand. If you add a custom data source, set this value to a 1.
Advanced Object Configuration Manager Operations There are several reports that are useful when administering mappings on an EnterpriseOne system. These reports can be found on the GH9012 menu, Advanced Operations. You can also get there by choosing the Advanced Operations folder on the GH9011 menu, System Administration Tools. These reports give you the ability to administer and add to your OCM mappings. Since the processing options of these reports may change from release to release, we only want to call your attention to the reports. If you want detailed instructions on how to use these reports, please refer to a current Oracle EnterpriseOne CNC Implementation manual.
Oracle EnterpriseOne Middleware
Any chapter on EnterpriseOne building blocks would not be complete without a section on the Oracle EnterpriseOne middleware. In this section, we will discuss the following: ■
The definition of middleware
■
Functions of JDEBase and JDENet middleware
■
EnterpriseOne middleware processes
■
Synchronous versus asynchronous processing
So, what is middleware? Is it hardware or software? Or maybe, as one of our clients thought, it is a mysterious black box that is required as part of the EnterpriseOne solution? This client just wanted to know how much this black box was going to cost and what location would be the best place for it. First, let’s dispel this myth. Middleware is not a black box. Nor is it that mysterious. It doesn’t cost extra, and you don’t need special hardware to run it. As for its location, it is on every machine that runs the EnterpriseOne product. Is it a requirement? Yes! Middleware is software designed to perform two primary functions. As such, it comes in two distinctly different types: database middleware and communication
Chapter 2:
EnterpriseOne Building Blocks
middleware. They are also often referred to as JDEBase and JDENet, and they are the glue that keeps the EnterpriseOne product working. They facilitate all computerto-computer communications as well as structure each and every SQL statement generated by the system.
Types of Middleware EnterpriseOne has two different types of middleware that help perform all the work between machines (servers and workstations) and databases. JDENet is a network communication middleware that performs network communications workstation-toserver and server-to-server. It also ensures messaging for distributed requests (for example, when a two-phase commit is required between two different databases on two different servers). You might hear JDENet referred to as a “peer-to-peer, message-based, socket-based, multiprocess communication middleware solution.” What does that mean, you may ask? Well, you might think that a marketing person had one too many drinks with a technical person and wrote this in a slightly blurry evening of deep discussions. But in reality, the phrase speaks volumes about the EnterpriseOne product. This is because JDENet handles an immense amount of communication between the EnterpriseOne servers and workstations. A server is a machine that responds to a request for information or services. A workstation is a machine on the network that initiates a call for information or services. E1 is a message-based system. All communication goes through messages. To improve performance, EnterpriseOne limits the size of the messages coming to your machine. A good example of this is when you click Find on an application within E1. The program comes back with a certain amount of information. As you begin to scroll down the list of returned information, you will occasionally have a brief pause in scrolling (there is a little icon of a policeman blowing a whistle in the lower-right portion of the window telling you to wait). This happens when the EnterpriseOne product is retrieving the next set of rows from the data set as derived from your initial query. EnterpriseOne is socket-based. E1 uses Win-Sockets to ensure data communication between servers and workstations. These sockets provide a duplex communication channel and are specifically set up in the JDE.INI on both the workstation and the servers. Servers and workstations must be set up on the same socket to communicate. The sockets used most frequently on different installations of EnterpriseOne include 6003, 6006, and 6007. However, any socket specified can be used for this purpose (we’ve seen some clients use 10004 and 10005). EnterpriseOne has a process-based design and supports multiple processes. Although a client installation of E1 can only run a single instance at any one time, a server installation can support multiple requests from multiple machines. These service and data requests range from security to UBE to logic. We’ve seen up to 100 EnterpriseOne kernels running on a single server supporting 20,000 business function requests.
87
88
JD Edwards EnterpriseOne: The Complete Reference
JDENET_N, JDENET_K, and JDEQUEUE On a server running the E1 runtime services, you can see a series of EnterpriseOne processes. Let’s take a minute or two to explore these processes to get a better understanding of exactly what role each of them plays in the EnterpriseOne product. First, though, let’s talk about how requests are split up among the available processes. If you have ten JDENET_n processes defined in the JDE.INI, the first one would be the master process and would launch the other nine as needed. As network communication requests come in, each one is given to a separate JDENET_n until all nine are in use. At that time, the eleventh request for network connectivity would be processed by the first JDENET_n. This process continues evenly, splitting the load among the available processes. This is an example of EnterpriseOne load balancing. JDENET_n is a network communication process. Its job is to determine what type of request is being made by the workstation. Once that determination is made, JDENET_n automatically routes the request to the appropriate server process to handle the request. Each type of request has a specified range of values used to determine the type of job being processed. The JDENET_n process offloads logic processing requests to JDENET_k processes. The JDENET_k process ensures that requests for logic processing reach the appropriate server job and that the results are passed back to the JDENET_n job for the return route to the workstation. There are 22 defined kernel processes in EnterpriseOne. They are identified by function and range in the JDE.INI file. JDEQUEUE is a UBE process that is set up to run batch logic requests. The EnterpriseOne administrator can determine the number of JDEQUEUEs on any particular server. Generally, a server is only limited in the number of JDEQUEUEs based on system resources. We have seen in excess of 18 batch queues defined on a specific machine. Up to 18 UBEs could be run on that machine concurrently.
JDEBase Middleware The JDENet middleware deals with communications (in particular, requests for logic services). The JDEBase middleware deals with database connectivity and communication. Its functions include interpreting APIs, converting SQL into the appropriate format for each machine and database, managing optimized fetch algorithms, and database transaction monitoring. Needless to say, you can’t work with EnterpriseOne without using JDEBase. As described earlier, there are four different databases supported in the EnterpriseOne solution and most implementations use at least two of them. Although this provides great flexibility for companies using E1, it creates a certain amount of complexity for the developers of this ERP product. Why? Because each of these database types is different and supports different SQL conventions. Let’s look at one of the simplest SQL statements and see how it differs from one database to the next: ■
SQL Server: SELECT * FROM PRODDTA.F4201 WHERE SHAN8='123456'
Chapter 2:
■
EnterpriseOne Building Blocks
Oracle: SELECT * FROM PRODDTA.F4201 WHERE SHAN8='123456';
■
DB2 on the AS/400: SELECT * FROM PRODDTA/F4201 WHERE SHAN8='123456'
■
MSDE/SSE SELECT * FROM F4201 WHERE SHAN8='123456'
The differences in the preceding code lines are very quick examples of RDBMS requirements in SQL conventions. Note that the Oracle statement has to have a semicolon at the end of it; DB2/400 has to have a slash indicating a different library because it does not support table ownership; and MSDE doesn’t use a table owner at all—it just skips that part, relying on an Open Database Connectivity (ODBC) connection to point it to the correct database. Though these differences seem minor, there are other, more important, differences as well. Does the RDBMS support table owners? SQL Server and Oracle do; DB2/400 and MSDE do not. Does the RDBMS support an explicit or implicit commit? Oracle supports explicit; SQL Server, DB2/400, and Microsoft Access support implicit. How does the RDBMS handle rollbacks—automatically or only when requested? What about indices? There are a slew of differences between each of the RDBMS vendors, each with their own pros and cons. While these differences aren’t great on the larger software scale, they do make a difference and must be reflected in the software. So, the next question you might ask yourself is, how could the architects of E1 handle these differences? Would it be best to code all four statements into the software? If so, how would an application know to use one type of SQL statement over the other? How would you upgrade this type of application to support changes in the database conventions that accompany RDBMS upgrades? These questions and many more like them went through the minds of the original EnterpriseOne architects, and their solution was JDEBase middleware. When you set up a data source, you define to the E1 system the type of RDBMS used by that data source. This information, when combined with the DLL name (also defined in the data source), allows EnterpriseOne to properly handle the differences between RDBMS conventions. The JDEBase middleware is a part of the foundation code of EnterpriseOne and cannot be modified by clients.
Synchronous Versus Asynchronous Processing Though some of the sections of this chapter seem tedious and long, other sections are blissfully short—such as this section. Really, it is little more than a note or an aside, but it contains an important issue to discuss and understand: What is synchronous as opposed to asynchronous processing?
89
90
JD Edwards EnterpriseOne: The Complete Reference
Synchronous processing can be defined as logic processing that requires the application, client, or user to wait until results are tendered (the logic event completed) before continuing to other processing. An example of synchronous processing will help you understand this better. When you click the OK button on a sales order, certain business functions are launched that check inventory, customer credit limits, and so on. Before you can print a pick slip or add a new order, these business functions must run and return without user-defined errors. If the business functions bring back an error (such as the customer being over their credit limit), the application will either automatically initiate a new workflow procedure or it will prompt the user for an action. All this occurs before the user can enter the next sales order. The user waits until the processing completes with results before continuing. This is called synchronous processing. In effect, the user must wait until the logic is processed before continuing to the next step. Some EnterpriseOne applications are designed so that you can turn their processing to synchronous or asynchronous modes. With this in mind, what is asynchronous processing? Asynchronous processing is logic that can be performed while other logic processing occurs. One of the simplest examples of asynchronous processing is a Universal Batch Engine (UBE). This can be a basic report or a complicated posting job. The key is that it can be launched on either a client workstation or an application server, and the user doesn’t have to wait for it to complete its work before continuing with other work. Considering that some of these UBEs can take days to complete, this is probably a good thing. We mentioned that some applications can be set to run in either a synchronous or asynchronous mode. When you decide to use asynchronous mode, you are telling the application to run ahead of itself. This will often speed up data entry, but there could be some issues with this style of processing (memory overwrites and data corruption quickly come to mind as possible pitfalls). The best advice is to research these options before you decide to implement them. Your local EnterpriseOne application consultant can often help you decide which mode of processing will best fit your business needs.
Summary
In this chapter, we have gone over the true building blocks of EnterpriseOne: data sources, path codes, environments, Object Configuration Manager, middleware, and synchronous and asynchronous processing. A user or system administrator needs to understand these concepts to truly understand the E1 system. The data source is a pointer to a set of tables within a database or to a specific machine that is running EnterpriseOne logic. It is housed in two tables (F98611 and F986115) and is the first building block of EnterpriseOne. We have talked about configuring data sources and when you might modify or add additional data sources.
Chapter 2:
EnterpriseOne Building Blocks
We have also discussed at length the data source’s importance to the E1 enterprise system. Another important piece to the EnterpriseOne puzzle is path codes. We have stated that a path code consists of central object tables, a directory structure, and an entry in the F00942 table. We have also discussed how to add a custom path code and delete a path code. It is vital that you understand how a path code affects the E1 system, as these path codes contain all the specifications that EnterpriseOne needs in order to run. Basically these path codes are storage areas for your specifications. To configure an E1 system correctly, you need to have a true understanding of what a path code is. We also went over adding, copying, and deleting environments. The discussion of these important topics not only covered the mechanics of how to maintain EnterpriseOne environments, but also why you would want to add additional environments and the impact this operation could have on your system. The technology is great, but don’t lose sight of your business needs for the sake of the technology. After we discussed EnterpriseOne environments, we moved on to talk about the three most powerful letters in EnterpriseOne, OCM (Object Configuration Manager). E1 uses the Object Configuration Manager to find its data, run logic, and run business functions. We have gone over the difference between the server map F986101 and the system F986101. The reasons why you would add a mapping and how to add OCM mappings were discussed. It is very important that you understand this chapter before moving on, as the Object Configuration Manager truly is one of EnterpriseOne’s building blocks. Finally, in this chapter we covered the EnterpriseOne middleware. The E1 middleware is an important piece of the product and one that greatly enhances the functionality of this ERP package. It is easily the butter on the bread of this software, allowing all database connectivity, machine-to-machine communication, multiple database and hardware independence, ease of use, guaranteed communications, transactional processing, and more. With this knowledge at your fingertips, you are ready to move into the more advanced topics covered later in this book. Always remember that these topics are truly the building blocks to EnterpriseOne and you will need to understand them before you can grasp more advanced topics.
91
This page intentionally left blank
CHAPTER
3
Solution Explorer
93
94
JD Edwards EnterpriseOne: The Complete Reference
T
he EnterpriseOne product provides an easy-to-use interface for enduser navigation. This interface is based on a tree-type hierarchy of task views and associated tasks that is comparable to a Windows Explorer tree-structure interface and allows users to easily find and execute programs. In this chapter, we will examine how users can interact with the EnterpriseOne interface, including: ■
Basic EnterpriseOne navigation
■
The Solution Explorer: Overview
■
What are EnterpriseOne task views and tasks?
■
Task view structure explained ■
Solution Explorer interface
■
Customizing an existing task view
■
Adding a custom task view
■
Inserting an existing task
■
Deleting a task view
■
Modifying an existing task view
■
Copying a task
■
Applying roles to a task
■
Adding a task relationship
■
Copying an existing task and its relationship
■
Deleting a task relationship
■
Tasks where used
■
Deleting tasks
■
Task translations
■
Task view filtering
■
Task view roles
■
Task views and change management
Chapter 3:
Basic EnterpriseOne Navigation
Solution Explorer
We’ll start this chapter by discussing the basics of how to navigate in EnterpriseOne. The EnterpriseOne software currently utilizes the concept of task views and tasks to provide the user with an easy-to-use interface. These task views are organized in a hierarchical tree structure that closely resembles a Windows Explorer directory layout. The task views are represented as logical groupings of tasks (similar to the concept of a directory) where tasks are utilized to call EnterpriseOne applications, external programs/links, or other task view(s) (similar to the concept of files/subdirectories). In this fashion, tasks are the most discrete units in Solution Explorer and form the building blocks on which full task views are built. Figure 3-1 shows the Solution Explorer. Generally, tasks are grouped in specific task views, as they relate to a common business process (such as Finance). By grouping tasks in this way, Oracle provides an interface that helps users easily locate their required functions. When a user accesses an EnterpriseOne session, the first thing the user will see is the EnterpriseOne task view structure. This task view structure provides the user
FIGURE 3-1. Solution Explorer
95
96
JD Edwards EnterpriseOne: The Complete Reference
FIGURE 3-2. HTML task views with a dual-pane display. The left pane displays task views and the right pane displays the programs that are being executed. The EnterpriseOne interface was designed this way so that users would quickly feel comfortable using it. As with most things in the EnterpriseOne product, task views are configurable. For this reason, the layout of the task views will vary from site to site. Figure 3-2 provides an example of the standard HTML task view layout.
Solution Explorer: Overview
Solution Explorer provides a convenient method for creating, maintaining, and managing EnterpriseOne task views for web or Windows-based (fat clients) interfaces. As with a number of things in EnterpriseOne (such as Object Management Workbench), the administration of task views generally occurs on a fat client utilizing the Solution Explorer application. This interface will be a little different than the standard HTML interface that most users will be exposed to.
Chapter 3:
Solution Explorer
Figure 3-3 provides an example of the Solution Explorer. Our primary focus, for this chapter, will be the creation and administration of task views in the EnterpriseOne product utilizing the fat-client Solution Explorer interface. When working with task views in Solution Explorer, the following modes are available: ■
Menu Design mode The Menu Design mode is used to set up tasks, task views, and task view roles.
■
Menu Filtering mode The Menu Filtering mode is utilized to enable or disable access to task views for users in a specific role(s). Figure 3-4 displays the Solution Explorer in Menu Filtering mode. This mode provides the ability to hide or filter task views for users and roles. This provides the ability to have more tasks in a task view than specific users can see. In this manner EnterpriseOne implementations can leverage the structure of the task view while filtering the user’s view of these tasks based on function or role.
FIGURE 3-3. Fat client – Solution Explorer
97
98
JD Edwards EnterpriseOne: The Complete Reference
FIGURE 3-4. Solution Explorer – Menu Filtering mode
■
Task Launching mode Use Task Launching mode to navigate to development and administrative applications in EnterpriseOne using the Fast Path or drilling down in specific task views (for example, executing the Object Management Workbench task). Figure 3-5 shows the Solution Explorer in Task Launching mode.
The Solution Explorer application is the launchpad for the effective configuration and implementation of task views. As with many things in EnterpriseOne, a little planning will go a long way. By laying out a solid implementation strategy (naming conventions, Object Management Workbench promotion paths, identified support resources, logical groupings of business processes, and so on), you can maximize the efficiency of the task views in your implementation and provide a effective
Chapter 3:
Solution Explorer
FIGURE 3-5. Solution Explorer – Task Launching mode interface for your user community. To meet this need, the Solution Explorer interface can be leveraged to 1. Set up task views 2. Set up tasks 3. Set up task view roles Before we dive into using the Solution Explorer to complete these tasks, we want to review a little bit of the overall interface.
HTML: Overview In the EnterpriseOne application, outside of administration programs, the primary user interface will be the HTML client. The creation and administration of task views is performed on a fat client via the Solution Explorer. For this reason, the primary focus of this chapter will be how to effectively utilize these administration applications to develop and deploy task views in your implementation. However, to keep things in perspective, we thought it prudent to provide an overview of the task
99
100
JD Edwards EnterpriseOne: The Complete Reference
view interface as seen by an HTML/web user (as this will be the end result of your task view creation efforts). Much like the fat client interface, task views on the web/ HTML are composed of two panes. The left-hand pane presents the user with the task views they have access to (we will discuss how to filter task views later in the chapter). Users can drill into these task views to access individual tasks that can call EnterpriseOne programs, HTML/web URLs, or other task views. When a program is accessed, it will appear in the right-hand pane. Depending on the HTML/web setting, users will be able to open multiple applications at the same time. Figure 3-6 provides an example of what task views will look like to a standard web-based EnterpriseOne user. NOTE By examining the Open Applications heading on the left-hand side, you can see that this user has several applications open at the same time.
FIGURE 3-6. HTML/web – task view
Chapter 3:
Solution Explorer
101
Main View: Left Pane The task view tree structure has a familiar look and feel for users who have experience with Microsoft’s Windows Explorer. When you sign on, you are taken to the default task views for your role (different roles can have separate task views). The default view out of the box is shown in Figure 3-7. As you can see, each task view has a plus sign (+) or the arrow next to it (depending on whether you are viewing the task in Solution Explorer or HTML). You can expand a task view by double-clicking on the name or by clicking once on the + or arrow symbol. When you expand the task view, the underlying tasks grouped within that task view appear on the left-hand side of the window. It is important to remember that the left-hand side of your window represents task views (which are logical grouping of tasks) and their associated tasks, not the actual programs to execute. This split-window interface allows you to easily navigate through the EnterpriseOne application.
FIGURE 3-7. Solution Explorer – Menu Design mode
102
JD Edwards EnterpriseOne: The Complete Reference
NOTE By utilizing filtering you can control what task views specific users are able to view and access. We would also strongly recommend disabling the Fast Path functionality so users cannot call task views directly. Disabling the Fast Path will be discussed later in the book. As you navigate through the shipped EnterpriseOne Menu task view, you will notice that each of the main task views represents an Oracle functional application suite. For example, if you expand the Financials directory, you will find task views containing the programs for the financial suite. This allows you to easily navigate to the programs that you might use on a daily basis. This easy-to-use interface should help to reduce training costs for any users familiar with Windows applications. It is also important to note that this task view layout is configurable, so the look of the task views may differ a little from site to site. This means that the users can customize the appearance of the task views. How to do this is covered in the section “Task View Structure Explained – Solution Explorer.”
Main View: Right Pane Now let’s take a closer look at the right-hand side of the user interface. In the HTML interface this “pane” will initially display welcome information (see Figure 3-8). Once a specific task is executed, this pane will be used to display the actual program(s) called by individual task(s). The right-hand pane allows users to access EnterpriseOne interactive programs, and call batch applications or links to thirdparty applications that can be “hooked” into EnterpriseOne. NOTE When the system is initially set up, there is no security restricting users from accessing applications, so users can go anywhere and run any application they please. How to secure the system is covered later in this publication. Once security is added, there are entire applications that will not appear on users’ task views if they are secured out of the application. It is also important to note that the initial task view that a user sees may be different from system to system. This is because the system administrator can filter the task views that a specific role will see or even specify a custom task view.
Chapter 3:
Solution Explorer
103
FIGURE 3-8. HTML interface – right pane Although it’s similar, the pane layout for the fat client is just a little bit different. The fat/Solution Explorer client does not have the welcome information on the first screen. When logging in to the Solution Explorer, you will initially only see one pane and are generally presented with the EnterpriseOne Life Cycle Tools task view (this can be adjusted and modified). If you drill down into the parent-child relationships. you can execute administration programs on the fat client that will appear in their own windows (outside of administration programs, most EnterpriseOne processes are now entirely web-based). The only time you will see the right-hand pane on the Solution Explorer client is if you Fast Path to a task view. This will then show the task view where you were in the left-hand pane and the task view you Fast Pathed to in the right-hand pane. Again, while most EnterpriseOne users will not see the Solution Explorer client view, we will be focusing on it quite a bit in this chapter to draw out how best to utilize the task view administration applications.
104
JD Edwards EnterpriseOne: The Complete Reference
Task View Structure Explained – Solution Explorer
When you log in to the Solution Explorer and access the initial task views, you will notice that there is a menu bar across the top of the interface, as shown in Figure 3-9. We wanted to take a moment to review some aspects of this part of the Solution Explorer client interface before diving into how to utilize the administration tools for task views in the EnterpriseOne product. This menu bar gives the user several options: ■
File
■
Tools
■
Edit
■
Applications
■
View
■
Help
We will go though the selections on this menu bar one by one, from left to right.
FIGURE 3-9. Solution Explorer – menu bar
Chapter 3:
Solution Explorer
File Menu The options on the File menu (see Figure 3-10) are ■
Run
■
Print This option prints out the task view currently displayed in the lefthand pane.
■
Print Setup This option simply allows you to select your prints and print characteristics (for example, Portrait or Landscape).
■
Save Settings on Exit This setting automatically saves any local settings made during the session when the user exits.
■
Exit
This option executes the task that is currently selected.
This option quits the Solution Explorer application.
FIGURE 3-10. Solution Explorer – File menu
105
106
JD Edwards EnterpriseOne: The Complete Reference
Edit Menu The options on the Edit menu, as shown in Figure 3-11, are ■
Prompt For: ■
Values
■
Version
■
Data Selection
■
Data Selection And Values
FIGURE 3-11. Solution Explorer - Edit menu
Chapter 3:
Solution Explorer
107
The Prompt For Values option allows you to review and edit the processing option values for reports and interactive applications. All you need to do is highlight the report or application you are interested in and go to Edit | Prompt For Values. The processing options for that report or application are then displayed (Figure 3-12 provides an example of the processing options for the Work with Servers application). Processing options enable you to take advantage of different functionalities offered by a report or application so that, for example, you can specify whether or not to give a user a hard error or a warning when a certain action is taken. Processing options can also tell a report to run in proof mode instead of update mode, which allows users to check their work before committing records to the system. This option will be grayed out if the report or application does not have any processing options.
FIGURE 3-12. Processing Options dialog box
108
JD Edwards EnterpriseOne: The Complete Reference
CAUTION Processing options are an important part of configuring your EnterpriseOne system. Once these are set up, you will want to lock your users out of these processing options for certain applications and reports. Failure to do so could cause problems with the system later. For example, if a user changes the processing options on your financial reports and/or applications, you may get unexpected results. The next selection is Prompt For Versions. This option allows you to choose the version of a report or interactive application that you want to run (see Figure 3-13). Users can set up different versions for reports and applications that allow them to specify, for example, different processing options or data selection. Instead of having to set the data selection up again and again, they can simply select a version with the desired data selection or processing options. This means that your users
FIGURE 3-13. Work With Versions window
Chapter 3:
Solution Explorer
can easily run a version that suits their needs and then just as easily change to another version. However, it is important to note that not all applications or reports will have a version associated with them. The next selection is Prompt For Data Selection, which brings up the Version Prompting window, as shown in Figure 3-14. This option will enable the user to view the default data selection for a report. NOTE If a task calling a report is not highlighted, this option will be grayed out. Data selection is stored at the spec level in EnterpriseOne. This means that while users can override the data selection configured on the report, it will return to the default on the next run. To change the default data selection, users need to update it at the spec level using the development tools.
FIGURE 3-14. Version Prompting window – Prompt For Data Selection
109
110
JD Edwards EnterpriseOne: The Complete Reference
The last option on the Edit menu is Prompt For Data Selection And Values. This option will prompt the user with the data selection for a UBE as well as the Processing Options. This is simply a slight variation on the options already discussed. Because the prompts for some of these options are not something you would want all of your users accessing, EnterpriseOne allows you to secure prompting for versions, values, and data selection.
View Menu The next item on the menu bar is View. The options on the View menu, as shown in Figure 3-15, are ■
Task Views
■
Show ■
Task Properties
FIGURE 3-15. Solution Explorer – View menu
Chapter 3:
■
■
Task Documentation
■
Fast Path
■
Toolbar
■
Toolbar Text
■
Status Bar
Solution Explorer
111
User Options
The Task Views option will display the major parent task view, like the EnterpriseOne Life Cycle Tools task view. This option will be grayed out until you go into Menu Design mode and start editing task views. This allows you to go from task view to task view via the View option. The Show option on the View menu can be used to determine whether a Solution Explorer user will see the Task Properties. This window, shown in Figure 3-16, will provide the user with information on the task that they have highlighted. When enabled, it generally appears to the far right-hand side of the Solution Explorer client. There will be three tabs on the Task View Properties pane: Basic, Intermediate and Advanced: The Basic tab provides the following options: ■
Task Name
■
Product Code
■
Product Code/Reporting
The Intermediate tab provides the following options: ■
Version
■
Task Type ■
Folder, Interactive, Program or UBE
■
Object Name
■
Form Name
■
URL Referenced
■
Option Code ■
Blind Execution, Prompt for Values
112
JD Edwards EnterpriseOne: The Complete Reference
FIGURE 3-16. Solution Explorer – Task Properties window ■
Form Mode
■
UDC Product Code
■
UDC Code Type
■
Icon Identifier
■
Country Code
■
Application Type
■
PO Option ID
■
Task View ID
Chapter 3:
■
Presentation Sequence
■
Parent Child Relationship
■
From Mode Override
Solution Explorer
The Advanced tab provides the following options: Task Properties ■
Task ID
■
Parent Task ID
■
Internal Task ID
■
Child Task ID
■
User ID
Relationship Properties
■
Program ID
■
User ID
■
Work Station ID
■
Program ID
■
Date – Updated
■
Work Station ID
■
Time – Last Updated
■
Data – Updated
■
Client Platforms
■
Time – Last Updated
The next suboption under the Show option on the View menu, Task Documentation, provides the ability to display task documentation. The EnterpriseOne application provides the ability to document information about the individual tasks. Another suboption under the Show option on the View menu, Fast Path, provides the ability to display or to hide the Fast Path. Fast Path is a powerful tool that allows a user to call applications or task views directly. We would strongly recommend limiting who has access to Fast Path in your implementation. NOTE A common practice is to provide developers and application resources with access to the Fast Path in the non-production/development environment but not in the production environment(s). One way to accomplish this is to provide the developer or application resource with two separate EnterpriseOne user IDs. The Toolbar option under Show on the View menu is used to show or hide the Menu toolbar. This toolbar provides access to the Menu Design and Menu Filtering modes.
113
114
JD Edwards EnterpriseOne: The Complete Reference
The Toolbar Text option under Show will hide the text for the toolbar buttons. This can be used to make the icons for the Menu Design and Menu Filtering modes smaller. The last suboption available under Show is the Status Bar setting. This setting provides the ability to hide or show the status bar on the lower right-hand side of the Solution Explorer interface. This status bar displays ■
The user currently logged in (for example, Demo)
■
The environment the user is logged into (such as DV812, PY812 and so on)
■
The role the user is logged in under (for example, All My Roles)
NOTE Information displayed will depend on the type of task highlighted. The User Options selection provides the user access to different programs for general user tasks, such as changing their password. When the user selects this option, the User Default Revisions dialog box (see Figure 3-17) will provide the following links: ■
User Profile Revisions This application allows you to add, copy, and revise users and groups. If a user selects this option, information on their user profile will be displayed.
■
Change Password If you set up EnterpriseOne sign-on security, each EnterpriseOne user will be required to have an individual password. This option allows users to change their own passwords. However, this option will not allow the users to change the passwords of other users or give themselves more authority on the system.
■
Submitted Reports This option allows you to view reports that have been run on your enterprise/application servers.
■
Default Printer EnterpriseOne allows you to set up printers so that users can print reports on a printer that is physically near them. However, users may move around the building, so EnterpriseOne gives you the ability to easily change the default printer for your users. The user can also manually change printers when running or printing a report.
■
View Local Output When a report or UBE is run on a fat client, it can be run on the server or locally on the workstation. When the report is run on the workstation, the output of the report is saved in the E812/printqueue directory on the local workstation. This option will allow you to browse/ view these jobs via the EnterpriseOne application.
Chapter 3:
Solution Explorer
FIGURE 3-17. Solution Explorer – User Default Revisions dialog box
Tools Menu The next option on the menu bar is the Tools option. The selections on the Tools menu, as shown in Figure 3-18, are as follows: ■
Message Management ■
Work Center
■
Internal Mail Messages
■
Add New Task View
■
Work with Tasks
■
Work with Task Relationships
115
116
JD Edwards EnterpriseOne: The Complete Reference
■
Task Where Used
■
EnterpriseOne Menu
■
Object Management Workbench
■
Report Design
■
Report Versions
■
Event Capture
The Message Management suboption on the Tools menu provides access to the Work Center program and Internal Mail Messages. The Work Center program is utilized to verify messages from reports or applications that are executed. This can be used to identify why a program such as the post did not post specific data. The
FIGURE 3-18. Solution Explorer – Tools menu
Chapter 3:
Solution Explorer
117
second program, Internal Mail Messages, can be used to send mail messages within the EnterpriseOne application. The Add New Task View option will be grayed out unless you are in the Menu Design mode. This option calls the P9000 program to allow new tasks to be added. We will review this action in more detail later in this chapter. The Work with Tasks option will be grayed out unless you are in the Menu Design mode. This option will call the P9000 program and will provide a user with the ability to add, delete, and browse tasks. You will find that we will discuss this program in greater detail as this chapter unfolds. The Work with Task Relationships option will be grayed out unless you are in the Menu Design mode. This option allows the user to add new parent-child task relationships or modify existing ones. We will review this process in much greater detail later in the chapter. The Task Where Used option will be grayed out unless you are in the Menu Design mode. This option allows the user to determine where an individual task is utilized in the system. The EnterpriseOne Menu option will load the EnterpriseOne Menu task view via the local Web Development client. If you are working on the web locally on a Web Development machine, this is a quick way to open the HTML/browser access to EnterpriseOne (E1). The Report Design menu option is for developers. The authors recommend that you use EnterpriseOne security to lock everyone but necessary users out of this option. The Report Design Aid program allows you to either customize EnterpriseOne reports or create custom reports that suit the needs of your business. Only trained developers should use this tool, which can also be accessed through the Object Management Workbench application, as the misuse of the application could seriously damage your implementation. The next option on the Tools menu is Report Versions. This option allows you to easily find and run batch applications or reports by taking your user into the Batch Versions program that allows you to find and run Universal Batch Engines (UBEs), which are really reports. DEFINITION Universal Batch Engine (UBE): These are the reports that you can run in EnterpriseOne. An example of this is a report that lists all of your customers. Event Capture is the last option on the Tools menu. This option is only utilized if you are working with the Autopilot tool.
118
JD Edwards EnterpriseOne: The Complete Reference
FIGURE 3-19. Solution Explorer – Applications menu
Applications Menu The next choice on the menu bar is Applications (see Figure 3-19). This option simply shows you the applications that you currently have open in EnterpriseOne and allows you to maximize them when you click on them.
Help Menu The Help option can give you just that, help. This option can lead you to help on specific topics or even information on the system itself, including: ■
Solution Explorer Help
■
Tip of the Day
■
Oracle on the Web
■
■
Oracle Home Page
■
Contact Us
About JD Edwards EnterpriseOne
Chapter 3:
Solution Explorer
119
The Solution Explorer Help option brings up a browser that shows you your online help files. These will only come up if you deployed them to the workstation or set your installation up so that your workstations know where to find these files. The Tip of the Day option shows you the tip of the day and allows you to turn the display of tips on and off. Tips of the day are customizable and held in a relational database table. The Oracle on the Web option can take you to the Oracle home page or to a contact page. The About JD Edwards EnterpriseOne option gives you information on the EnterpriseOne installation installed on the client machine. This option will tell you the release of EnterpriseOne, service pack level, package installed on the client, and environment name.
Toolbar Now that we have discussed the menu bar, let’s talk about the toolbar, the series of buttons across the top of the EnterpriseOne interface. We will start from the left and move to the right.
Menu Design The Menu Design button will place the Solution Explorer in the Menu Design mode to allow the configuration of tasks, task views, and task view roles.
Menu Filtering The Menu Filtering button places the Solution Explorer in Menu Filtering mode, which allows a user to enable and disable tasks that users assigned to a certain role can view or perform.
How Task Views Interact with EnterpriseOne Now that we have reviewed the Solution Explorer interface, let’s take a closer look at task views. Task views are an integral part of the EnterpriseOne product. In previous releases, the product was shipped with the menus mapped to the LocalPath Code. In the latest EnterpriseOne releases, the task views are mapped and read directly out of the Control Tables data source. Task views are contained in the following tables (which are accessed via the control table data source): ■
F9000 Task Master
■
F9001 Task Relationship
■
F9002 Task Alternate Description
120
JD Edwards EnterpriseOne: The Complete Reference
■
F90021 Task Master Language Status
■
F9005 Variant Description
■
F90051 Variant Description Language Status
■
F9006 Variant Detail
■
F90061 Variant Detail Language Status
■
F9005 Variant Description Alternate Description
■
F9006D Variant Detail Alternate Description
As you navigate through EnterpriseOne, you are actually making calls to these task view tables directly out of the database. These tables control what you see as you move through EnterpriseOne. They also control what applications or jobs are associated with each task; in other words, when a user logs on to a session, they see the task views as they do because of the way the data is returned from these task view tables. The content of these task view files can be controlled through the interactive application P9000. This application is the main control point for adding, modifying, and performing general maintenance on task views. Now like most things in EnterpriseOne, task views are objects. For this reason, they should be included in your change management planning. In the current release of EnterpriseOne, task views can be promoted via the Object Management Workbench (OMW) application. Development life cycles will vary from site to site, but the authors recommend that you select a lower-level environment where task views are configured and then promoted via OMW projects. This will provide you with tracking capability for changes to these objects and provide the ability to merge these changes into your normal development life cycle. Along that same vein of thought, it is always a good idea to put a little forethought into how you would like your task views to be configured. Some general concepts to consider: ■
Develop a standard naming convention. You will notice that the standard EnterpriseOne tasks are generally prefixed by JDE followed by a sixdigit number. For example, JDE002478 is the Task ID for the Object Management task view. ■
To ensure that your task views do not conflict with standard task views, we recommend developing a custom prefix for any custom task views (for example, ABC000000). While the numeric part of the Task ID can be
Chapter 3:
Solution Explorer
121
manually overridden, it is a good practice to utilize a next number for this, to ensure a next number will be used to verify the Processing Options of the P9000 application. You will not only be able to set the application to use next numbers, but you can define your own prefix to be used as well.
NOTE Ensure that this Processing Option (PO) change is promoted to all path codes. ■
Verify in the next numbers application (P0002) that a next number is defined for Task ID under system code H90.
■
Configure your custom task views to meet your business requirements with the least amount of maintenance. For example, if you have a number of divisions that use different programs, you can add the programs to a shared task view and use E1 security to prevent each division from accessing the other’s applications. This provides you with a common parent-child relationship while leveraging EnterpriseOne security capabilities.
So how do you really manage task views in EnterpriseOne? As with anything else, it is a good idea to start small and build from there. So we will start by explaining how to customize an existing task view for your own purposes. We will then move on to a review of how to add a custom task view and continue to walk through the major components of task view customization and administration. This discussion should provide you with the base knowledge to start defining your task view strategy.
Customizing an Existing Task View Let’s start with customizing an existing task view. From the Solution Explorer, select the Menu Design button on the toolbar. Open the P9000 application by selecting Work with Tasks from the Tools menu. Once you are on the Work with Tasks window (see Figure 3-20), you can search for the task you want based on the Task ID, Task Name, Product Code, Jargon, Country Code, Application, Form Mode, or application type. For example, if you wanted to find a task view with the Address Book application on it, you could search on the P01012 in the application field. This will show you all of the tasks that call the P01012 application. You can then modify the individual task by selecting the task and editing the information on the Common or Executable tabs on the Task Revisions window. For example, you might adjust the selected task to call a different version of the application or modify the Option Code to prompt for values.
122
JD Edwards EnterpriseOne: The Complete Reference
FIGURE 3-20. Work with Tasks window From the Task Revisions window (see Figure 3-21), you can add an EnterpriseOne Application, Report, URL, Folder/Task view, User Defined Code or EnterpriseOne Workflow to the task you have selected. To change the description and program that is called from a task view selection, first change the Task name in the Task Name field on the Task Revisions window. Then, on the Executable tab, in the Task Type area, click the Interactive or Batch radio button. You can then enter the program that you want to run in the Application field. If you do not know the name of your application, you can use the Visual Assist to help you find it. This will take you into the Search & Select window, where you can search for your application. You can also set the version of the application to be called by filling in the Version field in the Interactive Information section on the Executable tab. In the example, you are going to change the Task Name to Address Book and the application being called to P01012. Clicking OK will update the task and close the P9000 application.
Chapter 3:
Solution Explorer
123
FIGURE 3-21. Task Revisions window
Adding a Custom Task View Now that we have examined modifying an existing task view, we will go over adding a custom task view. Ensure that you are in the Menu Design mode and then select Add New Task View from the Tools menu. This will take you to the Task View Revisions dialog box (see Figure 3-22). In this dialog you can add a new task view. This is where you would define a parent task view to hang your custom tasks and task views on. Most often this will generally be a master name such as the name of the company or the project. Under this top task structure you normally hang task views for each of the functional areas for your implementation. These task views can then be filtered based on the roles for each of the users. When entering a new task view, you define the task view number, the name, and description. You can then select OK. You will notice that you can now see the new task view under the views section.
124
JD Edwards EnterpriseOne: The Complete Reference
FIGURE 3-22. Task View Revisions dialog box Once you have established your primary task view, you can move on to inserting a new task view on an existing task view. To insert a new task view to an existing parent task, ensure you are in Menu Design mode, right-click on the task, and select Insert New Task. This will take you to the Task Revisions dialog box (see Figure 3-23). In this dialog you will see the Task ID field. We would recommend that you allow the application to provide a next number for the new task view (this is set in the Processing Options for the P9000 application). First enter a Task Name and then you can select the values for the Common tab. On this tab, you will notice that you have Parent Task ID (which will be filled in based on the initial task view you right-click on), the Product Code, Jargon, and Country Code. The Product Code should match the type of tasks you are creating (for example, 55 for custom). The Country Code is utilized if you need to set up a task for a specific language (this will be discussed in greater detail later in the chapter). Once you have filled out the fields on the Common tab, you can move to the Executable tab and in the Task Type area, select the radio button for the task type you would like to define (such as Interactive, Batch, URL, Folder, User Defined Code, EnterpriseOne Workflow, or Crystal Enterprise). Enter the application and version and select your option (such as
Chapter 3:
Solution Explorer
125
FIGURE 3-23. Task Revisions dialog box Blind Execution, Prompt for Versions, and so on). Once you click OK on this dialog, you will have added a new task view to an existing parent task view.
Inserting an Existing Task To insert an existing task onto a task view under a parent task view, ensure that you are in Menu Design mode, right-click on the task view, and select Insert Existing Task. This will bring up the Task Relationship Revisions dialog box (see Figure 3-24). This dialog box will show you the Task View (this is the primary task view that you hang other task views on), Parent Task ID, the Child Task IDs, Child Task Names and Presentation Sequence. This application enables you to establish parent-child relationships and create hierarchical relationships. When entering a child task ID, ensure that you separate the presentation sequence numbers by a factor of X (10, 20, and so on). When you do this, you allow yourself the room to add extra
126
JD Edwards EnterpriseOne: The Complete Reference
FIGURE 3-24. Task Relationship Revisions dialog box task views or adjust the order without having to touch all of the sequence numbers. Tasks inserted under a parent task view should be grouped logically by function or business process.
Deleting a Task View To delete a task view from the system, log on to the Solution Explorer and access the Menu Design mode. Select the Work with Tasks option from the Tools menu. Once the Work with Tasks window appears, go to the Form Exit and select Task Views. This will open the Work with Task Views window. Search on the task view you would like to remove by entering it on the QBE (Query By Example) line and selecting Find. Highlight the task view and select Delete. This will remove the task view from the EnterpriseOne system.
Chapter 3:
Solution Explorer
127
NOTE If you delete a task from a task view, ensure that you repromote the entire task through the development life cycle. This will ensure that the other path codes match up with your change.
Modifying an Existing Task View If you want to adjust an existing task view to suit your purposes, ensure that you are in Menu Design mode and then right-click on the task view you are working with and select Task Revisions. This will open the Task Revisions application. This application will show you the following fields: ■
Task ID
■
Task Name This field provides a name or description of the task (For example, Object Management).
This is the unique ID that identifies the task.
On the Common tab, you will see the following fields: ■
Parent Task ID This field denotes the task view that this task is associated with (this presents the task views as nested).
■
Product Code This is the system code for the task view (for example, 55 would indicate a custom change).
■
Jargon The Jargon field provides you with the ability to define a system code.
■
Country Code Leave this field blank if you want this task to be available for all users. If you want this task to be specific to a region or country, enter your country code here. If you have a global implementation, this will become an important field as you roll out other countries.
On the Executable tab, in the Task Type area, you will see the following fields: ■
Interactive Select this option for a task that launches an interactive EnterpriseOne program.
When the Interactive task type is selected, the following fields will be displayed: ■
Application
■
Version Use this field only if you want to launch a specific version of the program.
Name of program.
128
JD Edwards EnterpriseOne: The Complete Reference
■
Form This optional field allows you to set a specific form to be called when the task is executed.
■
Option Code This field determines whether the user will be prompted for additional information prior to the application executing. It can be set to the following values: ■
No Processing Options processing options.
■
Blind Execution the user.
■
Prompt for Version This option will provide the user with a list of versions of the program to select from.
Used if the application does not have any
This setting will execute the program without prompting
NOTE The authors recommend using this option only when business needs require it. This option will allow a user to run any of the versions of an application, which could affect the user’s results. ■
Form Mode
■
Application Type
The Batch option in the Task Type area is used for tasks that launch EnterpriseOne batch applications. When this option is chosen, the Interactive Information area provides the following fields: ■
Application Enter the name of the report that you would like the task to call.
■
Version This optional field allows you to specify a specific version for the task to execute.
■
No Processing Options This option is used to execute a UBE that does not have processing options.
■
Blind Execution This selection executes the batch program without displaying its processing options.
■
Prompt for Version run at execution.
Allows the user to select which version of the report to
Chapter 3:
Solution Explorer
■
Prompt for Values This selection prompts the users to enter processing options values for the selected report.
■
Data Selection Prompts the user to enter data selection for the report at execution time.
■
Data Selection and Values This option prompts the user with both processing options values and data selection when the task is executed.
129
There are several additional options in the Task Type area: ■
URL This option can be leveraged to call a URL for a web-based application. This can be useful for linking calls to third-party applications from E1 task views.
■
Folder Turn on this option to use a task as an activity or nonsoftware placeholder. This will allow you to create subtasks under existing tasks. This will allow you to start your task view broad (for example, Finance) and narrow it down as you drill (for example, Month End G/L reports).
■
User Defined Code This option can be utilized for a task that launches a program that enables a user to modify UDC tables.
■
Crystal Enterprise task views.
■
EnterpriseOne Workflow
This option can be utlized to define Crystal reports on This task option displays workflow processes.
Once you have completed your modifications of the existing task view, you can select OK. This will update the task view in the table. It is important to note that task views are cached. For this reason, in order to guarantee that you will see the changes properly, you should log out and back in on a fat client and clear the cache for an HTML/Java application server (JAS) via the SAW (Server Administration Workbench) or Server Manager (8.97) applications. NOTE When you change a task in such a manner, you affect all instances of the task in any task view where it resides. This can often cause confusion for users who thought they were simply changing that one instance of the task. If you want to find out where else your change might be seen, you can search on where a task is used.
130
JD Edwards EnterpriseOne: The Complete Reference
Copying a Task At this time there is not a way to make a unique copy of a task. The best alternative is to write down the information and add it as a new task.
Applying Roles to a Task Now that you understand how to create a new task view, modify existing tasks, and insert a new task, we should review how to use the concept of EnterpriseOne roles to configure the system into role-based task views. The EnterpriseOne product provides the ability to add one or more roles to each task. When a user launches a role-based task view, the EnterpriseOne system applies the login role to the view. If the user has multiple roles defined for that user, they will be able to view the task view by any of these roles. For example, a user might have two roles, DEMOROLE (the user’s sign-on role) and TEST ACCNT. When the user launches a role-based task view, the system displays only those tasks to which the DEMOROLE has been applied. The user can apply the TEST ACCNT role to the task view. The system will then display only those tasks to which the TEST ACCNT has been applied. To apply roles to a task: 1. Select the task that you want to work with. 2. Right-click the task and select Task Revisions. 3. In the Task Revisions window, select Roles from the Form menu. This will display the Task Where Used window. 4. Click Find and highlight the parent of the task to which you want to apply roles and then click select. 5. The Role Definition window will appear (see Figure 3-25). 6. Select the role that you want to apply to the task. 7. Select Change Status from the Row menu. This will change if the task is enabled for the task view. 8. If you want to apply all roles to the task: a.
Select Enable All from the Form menu.
b. Click Close. c.
Then in the Task Revisions window you can click OK to save the changes.
Chapter 3:
Solution Explorer
131
FIGURE 3-25. Role Definition window
Adding a Task Relationship Now that we have discussed how to create a master task view and different types of tasks, we will review how to group those tasks that relate to common business systems, processes, or functions. Grouping tasks in this manner makes it easier for users to locate the functions that they require. Defining a relationship for a task view will provide this grouping of tasks together and allow the same task to be accessed from multiple task views. In this manner you can use the building blocks of the individual tasks and hang them from a number of different task views to meet your requirements. For example, we might want to add the Address Book application to the Report Management task view. To do this, you would log in to Solution Explorer,
132
JD Edwards EnterpriseOne: The Complete Reference
click Menu Design, right-click on Report Management task (GH9111), and select the Task Relationships application (see Figure 3-26). To add the address book task to the task view, you can type in the individual Child Task ID or use the Visual Assist. Enter or select the Child Task ID (the Child Task Name should then appear) as well as the presentation sequence. If you have a number of tasks grouped in a task view, this will determine what order they are displayed in. It is a good practice to leave space between your presentation sequence numbers by a factor of x (10, 100). This enables you to easily add new tasks without having to adjust all of the presentation sequence numbers. Once the task has been defined, click OK. You have now created a logical grouping of this task with the task view. By performing this type of action, you can build logical groupings of task views for specific business requirements (such as HR, A/R, and so on). Putting a little forethought into the grouping of your task views can also help when you are attempting to isolate which users can access these task views.
FIGURE 3-26. Task Relationship Revisions window
Chapter 3:
Solution Explorer
133
Copying an Existing Task and Its Relationships to a New Task View At times you will find that you have an existing parent task with relationships already existing within another task view. If you want to have this entire tree structure in a new custom task view, it is possible to copy the relationship in its entirety to the new task view. To copy a task and its relationships to a new task view: 1. Navigate to the existing task you want to copy. 2. Right-click on the task view and select the Send To option. 3. From the pull-down list (see Figure 3-27), select the task view you would like to copy to. 4. Select the options for Copy This Task and All of Its Children. The option for Copy This Task Only will have the same result as manually adding a single task to the task view. This will move the task and its children to your task view and automatically create the relationship.
FIGURE 3-27. Send To dialog box
134
JD Edwards EnterpriseOne: The Complete Reference
NOTE This is not a unique copy. The two tasks will retain the same task ID and if one task is changed, then both will be changed. The only way to get a unique ID is add a new task. (This is a common place where users get tripped up.)
Deleting a Task Relationship As we have been discussing, task views are simply logical groupings of tasks in a hierarchical tree structure. Task views are the “Christmas Tree” that allows for the grouping/hanging of tasks that relate to a common business process. By generating your tasks in this manner, you can make the process of accessing applications in EnterpriseOne easier for the end user. By defining a relationship for a task view, you not only enable all users to group similar tasks together but also allow the same task to be accessed from multiple task views. So now let’s assume we have an instance where we need to get rid of a relationship associated to a task view: 1. Highlight the parent task you are interested in. 2. Right-click and select Task Relationships. 3. Locate the child task that you would like to remove from the parent task. 4. Highlight the child task. 5. Click Delete. 6. Click OK.
Task Where Used As we are adding or modifying new tasks, it becomes necessary to have a clear view of where a task is used in the system. The reason for this is that any changes to a task are replicated throughout any task views utilizing that task. So how do I find out where a task might be used in the system so I can understand the scope that a change to this task would represent? To locate this type of information, ensure that you are in Menu Design mode and select Task Where Used from the Tools menu (see Figure 3-28). This application can be leveraged to determine on which task view(s) a task is used as well as additional information such as to which roles the task is assigned. When searching on a task, enter the Task ID in the field and select Find. The application will list the task views that this task is being utilized for. This provides you with a view of how prevalent a change to this task view might be and where in your task view structure this task is called.
Chapter 3:
Solution Explorer
135
FIGURE 3-28. Task Where Used window
Deleting Relationships When Multilevel Relationships Exist Within a task view, multilevel relationships between tasks can be established. To delete all of the levels of relationships defined in a multilevel relationship: Highlight the parent task, right-click, and select the option Delete Relationship.
Delete a Task When you determine that you have a task that you no longer need, how do you get rid of it? To delete a task from the EnterpriseOne system, ensure that you are in Menu Design mode on the Solution Explorer client and then: 1. Remove all task relationships involved in the task. 2. To determine where the task is used in the system, go to the Task Where Used option on the Tools menu. 3. Enter the Task ID and select Find. All parents of that task will be listed. 4. For each row in the list, highlight the row and choose Select.
136
JD Edwards EnterpriseOne: The Complete Reference
5. In the Task Relationship Revisions applications window, click on the row representing the task you would like to remove and click Delete. 6. Once this has been completed, choose Work With Tasks from the Tools menu. 7. Enter the desired task ID in the QBE line and choose Find. 8. Select the grid line displaying the task and choose Delete. 9. You would then promote the task views that this task was a part of via the OMW application. This will ensure that your changes move properly through the development life cycle and are propagated to the other environments.
Task Translations In today’s dynamic business environment, many companies have to maintain global implementations. So how do you effectively manage multiple languages in your implementation? The EnterpriseOne product allows you to apply translations to your custom task views. This will allow English-speaking users to see the view(s) in English and foreign users to be able to read the translation for the same task view in their own language (set in the P0092 user profile application). To set up a translation for a task view: 1. In Solution Explorer, click Menu Design. 2. On the Tools menu, select Work With Tasks. 3. In the Work with Tasks window, enter your Task ID and select Find. 4. Highlight the Task View and select the row exit Task Translation. 5. The Task Translation Revisions window will appear (see Figure 3-29). 6. Enter the language you would like to perform the translation for. For example if you typed an S in the Language field, you would be entering a translation for Spanish. To find out all of the User Defined Codes (UDCs) for each language, you can use the Visual Assist. 7. In the Task Name field you can enter your custom language translation. 8. Select OK to commit this translation. This capability allows companies to not only add custom translations to custom task views but to update existing task views.
Chapter 3:
Solution Explorer
137
FIGURE 3-29. Task Translation Revisions window
Filtering Task Views Once you have created custom task views for your business processes, how do you ensure that users only see the task views associated with their role/business process? The answer to this is Menu Filtering mode. Menu Filtering provides the ability to selectively enable or disable tasks by role in a task view. To leverage this functionality: 1. Access Solution Explorer. You will want to perform this action in the path code that you would like to filter for or in the path code that you are promoting task views from. 2. Select the task view that you want to redefine. 3. Locate and select the Menu Filtering button on the toolbar. When you enter Menu Filtering mode, as shown in Figure 3-30, you will notice that the task view changes to display enabled and disabled tasks. Enabled tasks are indicated by a green check mark and disabled tasks are indicated by a red X.
138
JD Edwards EnterpriseOne: The Complete Reference
FIGURE 3-30. Menu Filtering mode 4. Click the Enable or Disable button on the toolbar to disable the task view. You can also double-click on the task to flip between enabled and disabled conditions. 5. Once you have completed your changes, you can save them by clicking on the Save button on the toolbar. Saving your changes will update the Master Task Relationship table (F9001), so the changes will be available to all users who access the same database/environment. 6. You can use the Show All in Menu Design mode to switch between hiding and displaying disabled tasks in the current task view menu for the currently selected role.
Understanding Task View Roles You can use roles to customize task views or parts of task views for specific user roles. Roles are used in EnterpriseOne to define users to logical business processes/ actions. For example, you might set up a role for your accounting users. These roles could be utilized for EnterpriseOne Security, defining the environments the users have access to and what task view that the user can view. To filter a task view by a specific role, you refine the task view by using Menu Filtering mode (detailed in the preceding section). To take advantage of this: 1. Log in to the Solution Explorer. 2. Locate the task view you would like to work with and select the Menu Filtering button on the task bar.
Chapter 3:
Solution Explorer
139
3. Select the task(s) that you want to hide from view and click the Disabled button. 4. After disabling all of the tasks that you do not want to appear, select the parent task. 5. You can then right-click on the parent task and select Save Role. 6. In the Save Role application (see Figure 3-31), select an existing role or create a new role. This will allow the resource responsible for your task view creation to control what task views that particular role is able to see/access. This combined with EnterpriseOne security provides the ability to present a task view to roles based on their specific business processes. NOTE In order to see the roles in the Apply Role application, Role Chooser must be enabled.
FIGURE 3-31. Save Role application
140
JD Edwards EnterpriseOne: The Complete Reference
Changing a Role View of Task View Leveraging the modifications of roles allows you to control users’ task views. As you plan and implement your task view strategy in your EnterpriseOne implementation, you might not only want to control what task views a role sees, but also things like task view names. For example, if you had a couple of different roles (such as TEST ACCNT and DEMOROLE), changes that you make to a specific role (such as TEST ACCNT), like assigning new task names, will only display to users in that role. To change a role view on a task view: 1. Log in to the Solution Explorer application. 2. Locate the task view you would like to work with and select Menu Filtering on the toolbar. 3. Right-click the task and select the View by Role option. 4. Select the role that you would like to apply the change to (such as TEST ACCNT). 5. You can then: a.
Use Menu Filtering to enable or disable the view.
b. Right-click on the task and select Override Name. This enables you to display different task names for different roles (such as Corporate Accounting, Region 1 Accounting, and so on). 6. Once you have made the required changes, you can select the Save button on the toolbar.
Change Control and Task Views Now that we have reviewed all of these great options available for configuring task views, how do you effectively track changes through your system? The authors recommend that you select a primary environment for the creation and promotion of task views in your EnterpriseOne system. This is generally the Prototype environment as it will be the application users who validate the task views (but this effort could also start in development). This primary environment would be utilized to make changes to the task views in the implementation. Once validated these changes would be promoted through OWM just like any other object in EnterpriseOne. This provides logging and the ability to efficiently track changes. To ensure that your task views are configured, you need to ensure that the activity rules are updated to reflect the task views. You will need to add activity rules for:
Chapter 3:
■
SE_REL Solution Explorer Task Relationship
■
SE_RULE
Solution Explorer Qualifier Rule
■
SE_TASK
Solution Explorer Task
■
SE_VAR
Solution Explorer Variant
Solution Explorer
(These are not shipped by default.) By setting up activity rules for the transfer of task views, you can migrate task views through the change control process with your standard objects. This allows you to coordinate changes to your task views throughout your project life cycle.
Summary
This chapter has reviewed the components required to maintain, create, and manage task views in the EnterpriseOne product. This top-down review of the Solution Explorer and its task view administration programs provides a base on which you can start building your task view strategy. As with many things in EnterpriseOne, task views can be managed effectively and efficiently, but they require a little bit of planning.
141
This page intentionally left blank
CHAPTER
4
EnterpriseOne Servers
143
144
JD Edwards EnterpriseOne: The Complete Reference
A
s you continue learning about the basics of the EnterpriseOne system—what the building blocks are and what they do, how to successfully implement the system, and what types of topics to keep in mind before, during, and after an implementation—we need to take time out to talk about the underpinnings of the system itself (both hardware and software). Though we certainly don’t want to minimize the other topics we have discussed thus far, or the topics we will discuss later, we would be remiss in our duties as EnterpriseOne tour guides if we didn’t spend the appropriate amount of time on servers and the options surrounding them. One of the topics that requires consideration for every EnterpriseOne implementation is hardware. After all, this is one of the larger expenditures you will make (right next to the software itself). In truth, having a good understanding for the various types of servers and their functionality is an essential first step when planning your EnterpriseOne enterprise solution. During this chapter, we will discuss, at a high level, the platforms supported by EnterpriseOne, the deployment server, the database server, the application server, the enterprise server, the web server, and the portal server.
Does the Platform Matter?
Although the EnterpriseOne enterprise resource planning (ERP) package does not support all platforms, it does support a wide range of hardware platforms. Will EnterpriseOne work on the iSeries (also commonly referred to as the AS/400)? Yes! The HP9000? Yes! A WinTel (Window/x86) solution, such as xSeries, HP, or Dell? Yes! The pSeries (also commonly known as the RS6000)? Yes! The Sun Solaris? Yes! Can you mix and match servers and databases? Yes, within the limits of the hardware and databases themselves. We would be lying to you if we said that all of the platforms (both hardware and software) were created equal. However, the authors can honestly say that there are pros and cons to all of them. There is no one single best solution. Rather, there is a best solution per set of circumstances—yours may not be the same as other companies that are implementing this product. This chapter is devoted to the options available to the EnterpriseOne architect, rather than on what hardware and software to implement (though we go into that too). We will go into detail on the following: ■
The deployment server
■
The data server
■
The application server
■
The enterprise server
Chapter 4:
■
The web server
■
The Collaboration Portal server
■
The Windows client
EnterpriseOne Servers
145
The EnterpriseOne Deployment Server
What better way to start a chapter dedicated to servers and hardware than with the good old-fashioned deployment server? To assist you in this, we will discuss the following questions: ■
Exactly what is the deployment server?
■
Why do we have it?
■
Can it be used for other functions?
A deployment server is an integral part of the EnterpriseOne system and is always mentioned as part of the enterprise—so much so that you will notice that the simplest architectural models have one. The following illustration shows a standard “out of the box” EnterpriseOne configuration.
Web server
Enterprise server Ethernet
Deployment server
Collaboration Portal server
146
JD Edwards EnterpriseOne: The Complete Reference
In the least of terms, a deployment server is an x86 server running Microsoft Windows. When determining the system specifications needed for the deployment server, it is best to verify the minimum technical requirements (MTR) published by Oracle. When you do this, you will find that they highly recommend working directly with your hardware vendor and Independent Software Vendor (ISV). NOTE Your deployment server can exist on the iSeries (AS/400) because IBM offers an x86 Windows chipset that uses the iSeries’ disk space. When you use this chipset, your deployment server can then exist as part of the iSeries. Depending on your specific environment, the deployment server may perform several different functions.
Deployment Server Basics The deployment server acts as a primary deployment location in a centralized software deployment model. It is the primary location for all path codes in the system and normally maintains the actual C code that comprises the EnterpriseOne ERP system. It maintains the system’s license security and can build packages for both clients and application servers. It houses packages for deployment to workstations, servers, or other deployment locations.
Does the Deployment Server Have to Do All That? No! There are many circumstances where the deployment server functionality would be better decentralized. However, you won’t see all this functionality dispersed even on a highly decentralized architectural model. Many of these functions make sense and are logically located where they do the most good. The deployment server is where EnterpriseOne is first introduced to your enterprise. The CDs shipped by Oracle get installed here, the EnterpriseOne system is defined here through the installation process, and packages can be dispersed from this location. More importantly, however, this server contains the Table Access Manager files, or XML/TAM, that track EnterpriseOne licenses on the system. DEFINITION Table Access Manager (XML/TAM): The Table Access Manager can be thought of as an XML miniature database format. XML/TAM is used to locally store design specifications for applications (for example, window layouts or event rules).
Chapter 4:
EnterpriseOne Servers
147
Off with Its Power Many companies have asked if the deployment server can be shut off. Most of these companies do so because they are mainframe, UNIX, or iSeries shops and the introduction of Windows is neither wanted nor tolerable to the existing system staff. Regardless of various proofs to the contrary, many IT professionals still don’t view the Windows server as a hardened, production-ready system. Unfortunately, in some enterprises (and depending on your specific configurations), you simply shouldn’t shut this system down. We would ask why an x86/Windows machine couldn’t reside on the enterprise. It doesn’t require a huge amount of maintenance (apart from security, functionality, and base OS patches that come out on a fairly regular basis), it is a very easy operating system to support (good Windows administrators are neither hard to find nor expensive to maintain), and has cheap hardware. Let’s think again about what this system does for your organization: ■
Provides an initial point of installation, update, and upgrade
■
Maintains EnterpriseOne license security
■
Maintains C code for all path codes (under typical configuration)
■
May contain a series of databases housing the central objects
■
Can be used for building software deployment packages
■
Houses all software packages for deployment throughout the EnterpriseOne enterprise
Rules for Turning the Deployment Server Off With all these functions, we think you should simply leave the system on; however, there are some rules for turning the system off. First, it may contain databases that house central objects. You should be sure not to turn the deployment server off for a prolonged period of time if you’ve placed a database on this server. The system will not work correctly if you do. NOTE The deployment server should be backed up regularly to ensure disaster recovery capability. You really don’t want to spend millions of dollars on development only to lose it. Second, since this system houses the EnterpriseOne license security in XML/TAM files, you can turn the deployment server off; however, you need to turn it back on when it is time to renew the license for a workstation and the system security.
148
JD Edwards EnterpriseOne: The Complete Reference
Third, when you are building workstation or server EnterpriseOne software packages, this server must be on if it is used as a C code repository. Fourth, though you can turn this system off, depending on your software configuration, you may experience difficulty checking items into or out of the path code. NOTE Many users do not recognize when they have successfully checked modified objects into or out of their EnterpriseOne system. There will often be an error stating that the system could not access a file. Do not ignore these error messages. Instead, look at the log files (client, server, and so on) and find out why you got the message in the first place. We have seen companies ignore this type of error and fail to have their modifications carry forward to the next release of EnterpriseOne. Finally, and yes, this reiterates the rules we’ve outlined: If you plan to perform a lot of development, package deployments, or future upgrades and have not implemented multitier deployment or some other modification, it is not advisable to turn this system off for more than routine maintenance.
Rolling the Deployment Server into a Configuration Concerning the information already provided, we never recommend the particular Windows/x86 solution to implement. Whatever platform you are comfortable with works for the deployment server. Now we’ll get specific about the actual hardware configuration for this machine. It all comes down to what your company’s objectives are when implementing this ERP package. Let’s look at a couple of different scenarios under consideration.
EnterpriseOne and the iSeries In this particular case, we are going to make the following assumptions: ■
There is no special development for the implementation of this software.
■
The central objects are going to be housed in an RDBMS on the deployment server. Though this is not a common implementation option, it is a potentially viable configuration.
■
You are implementing E812.
Chapter 4:
EnterpriseOne Servers
149
Now the fun questions: What types of hardware do we need? Should we have system redundancy? What is the best configuration? Concerning hardware, you will need approximately 80 gigabytes just in EnterpriseOne hard drive space (this assumes 8GB per path code with two packages each). If this sounds like three 80GB drives in a RAID 5 configuration, you would be correct. When you consider the upgrade, you will minimally add another 100GB of required space. If you are housing a relational database, not only will you need additional disk space, but you might consider configuring these drives to maximize the database throughput. However, since your development is minimal, your optimizations can be also. NOTE If you perform some basic optimization procedures on both hardware and software configurations, you will decrease the time required to install or upgrade EnterpriseOne. Whenever possible, try to separate the data files and the archive/redo/log files onto separate physical and logical disks when loading databases (this assumes you’ve decided to place a database on the deployment server). This separation will improve your database read/write capabilities. If you have multiple controller cards in your server, separating the data and logs on these will also improve performance. The system we have just described is a mission-critical piece of the enterprise solution. As such, system redundancy is highly recommended. This redundancy could be as little as using RAID (we, of course, prefer hardware RAID with a 1/0 configuration for the RDBMS) or as much as having a real-time, hot-backup, offsite system. Your company must decide how important EnterpriseOne’s being online is against your internal ability to support this solution and its cost. It comes down to how long EnterpriseOne can be down. In this system, we would also recommend nightly backups (either full or incremental) with offsite storage. Depending on your hardware solution, go with a minimum of an 18GB system drive. This will be used for the operating system, a paging file, and the log files. Then add data drives (obviously several drives combined using some RAID technology to maximize read/write) to house the EnterpriseOne directory structure and the RDBMS data files. This would provide enough space for future growth.
15