Résumé du contenu de la page N° 1
Front cover
Geac System21
commerce.connect
Implementation on the IBM iSeries Server
Gain useful insights through the
product overview
Follow the step-by-step guide to
install commerce.connect
Learn helpful usage and
performance tips and techniques
Yessong Johng
Colin Brown
Jim Hirsch
John Lawler
ibm.com/redbooks
Résumé du contenu de la page N° 2
Résumé du contenu de la page N° 3
International Technical Support Organization Geac System21 commerce.connect: Implementation on the IBM ~ iSeries Server December 2002 SG24-6526-00
Résumé du contenu de la page N° 4
Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (December 2002) This edition applies to Geac call.connect Version 1.1, vendor.connect 1.1, and System21 3.5.2b SP4 or SP5. © Copyright International Business Machines Corporation 2002. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Résumé du contenu de la page N° 5
Contents Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix The team that wrote this redbook. . . . . . . . . . . . . . . . . . .
Résumé du contenu de la page N° 6
3.3.4 Restoring IFS objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 3.4 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 3.4.1 WebSphere node name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 3.4.2 Errors on starting the client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 3.
Résumé du contenu de la page N° 7
5.3.3 Total connections and SQL server jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 5.4 Performance topics for Java virtual machine (JVM) settings . . . . . . . . . . . . . . . . . . . 124 5.4.1 Initial Java heap size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 5.4.2 Maximum Java heap size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 5.4.3 Verbose garbage collection . . .
Résumé du contenu de la page N° 8
vi Geac System21 commerce.connect: Implementation on the iSeries Server
Résumé du contenu de la page N° 9
Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, progra
Résumé du contenu de la page N° 10
Trademarks The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both: Redbooks(logo)™ iSeries™ S/390® AS/400® MQSeries® SecureWay® DB2® OS/390® SP™ DB2 Universal Database™ OS/400® TCS® IBM® Perform™ VisualAge® IBM eServer™ Redbooks™ WebSphere® The following terms are trademarks of International Business Machines Corporation and Lotus Development Corporation in the United States, other countries, or both: Lotus® Notes®
Résumé du contenu de la page N° 11
Preface This IBM Redbook introduces the new Geac commerce platform .connect applications – the call.connect and vendor.connect applications. These applications extend and enhance the capabilities of Geac System21 into the intranet and Internet. This redbook targets consultants or customers who work with these .connect applications. It explains how to install, maintain, integrate, and manage these applications on the IBM ~ iSeries server. It also helps you to understand the architecture and
Résumé du contenu de la page N° 12
Find out more about the residency program, browse the residency index, and apply online at: ibm.com/redbooks/residencies.html Comments welcome Your comments are important to us! We want our Redbooks to be as helpful as possible. Send us your comments about this or other Redbooks in one of the following ways: Use the online Contact us review redbook form found at: ibm.com/redbooks Send your comments in an Internet note to: redbook@us.ibm.com Mail your comments to: IBM Corporation, Internat
Résumé du contenu de la page N° 13
1 Chapter 1. The .connect applications This redbook covers the two Geac .connect applications: call.connect vendor.connect This chapter introduces you to these two applications. Geac also offers the following applications, which provide security, process control and messaging, and integration with System21: secure.connect process.connect inter.connect These are part of the commerce platform. commerce.platform is the element of commerce.connect that supports the integration of applic
Résumé du contenu de la page N° 14
1.1 call.connect Geac call.connect fills two roles. First, it is a telesales-oriented product. It is intended to help call center personnel actively sell to the customer and create and foster personal relationships. To support this type of active sales, call center personnel need instant access to all relevant information for the calling customer. Typical information includes order history, account information, and product information. The ability to quickly enter an order (complete with st
Résumé du contenu de la page N° 15
Figure 1-1 The call.connect buying list call.connect is a flexible order capture process that includes the following facilities: Dynamic buying lists: The lists of products that the customer is likely to purchase is created by combining a fixed list of products with a dynamic list, based on rules applied to previous purchase history. Call management: Supervisors have access to a call-management application that allows them to track the progress of calls and re-assign them to operators t
Résumé du contenu de la page N° 16
1.2 vendor.connect Geac vendor.connect is a supplier self-service application. It is designed to support a cooperative relationship between customers using System21 and their suppliers. It makes information available, exchanges business documents, and allows controlled direct update facilities. vendor.connect improves supplier communication, aids planning, and reduces inventory investment in the supply chain. Figure 1-2 shows an example of the vendor.connect Replenishment page. Figure 1-2
Résumé du contenu de la page N° 17
Supplier planning: An enquiry allows the supplier to view the stock status and demand for products for which they are the preferred supplier. The demand enquiry includes relevant information from System21 – unallocated sales orders, expected demand from Material Requirements Planning (MRP), expected demand from Distributed Requirements Planning (DRP), and a historical demand element based on sales and customer-specific filters (for example, sales current year to date or previous year to d
Résumé du contenu de la page N° 18
6 Geac System21 commerce.connect: Implementation on the iSeries Server
Résumé du contenu de la page N° 19
2 Chapter 2. Architecture of the commerce.connect products The products that make up the commerce.connect platform originate from a diverse background. The challenge and vision is to bring these applications together into a single coherent, product strategy. This requires an architecture that can encompass the entire technology spectrum from the legacy applications to the leading-edge Enterprise Java applications. This chapter explains the key parts of the architecture, specifically the arc
Résumé du contenu de la page N° 20
2.1 The need for an architecture Why is an architecture necessary? Can’t we simply write programs that deliver the function that is required? The reasons for having an architecture are: Ever increasing demands are placed on systems in terms of security and availability. The need to extend the system to both customers and suppliers across the Internet is growing rapidly. Applications need to have this capability “architected in”. The need to reduce the product development life-cycle, wh
