IBM SG24-6526-00 Bedienungsanleitung

ibm.com/redbooksFront coverGeac System21 commerce.connectImplementation on the IBM iSeries ServerYessong JohngColin BrownJim HirschJohn LawlerGain us

viii Geac System21 commerce.connect: Implementation on the iSeries ServerTrademarksThe following terms are trademarks of the International Business M

88 Geac System21 commerce.connect: Implementation on the iSeries Server4.2.6 MQSeriesThis section explains how to set up MQSeries for vendor.connect

Chapter 4. Installing and setting up vendor.connect 894.2.7 Work Management Trigger Handler for the iSeriesThe OSLVCD3/TRGRHNDLR CL program is provi

90 Geac System21 commerce.connect: Implementation on the iSeries Servercom.Geac.erp.system21.aef/xml/maps. Inside these folders, there are additional

Chapter 4. Installing and setting up vendor.connect 91 <value_format>1</value_format> <value_format_string>STATIC</value_format

92 Geac System21 commerce.connect: Implementation on the iSeries Server4.2.9 JConnects serverThis links vendor.connect back in to System21. Copy the

Chapter 4. Installing and setting up vendor.connect 93<property id="ldap_server" value="ldap://server.domain.co.uk/" /><

94 Geac System21 commerce.connect: Implementation on the iSeries ServerUsing LDAPIf you are using LDAP, you must install an IBM SecureWay client to c

Chapter 4. Installing and setting up vendor.connect 955. The Directory Properties window (Figure 4-12) opens. Complete these tasks:a. Select the Star

96 Geac System21 commerce.connect: Implementation on the iSeries Server6. Click the Databases/Suffixes tab (Figure 4-13). a. Under Suffixes, enter a

Chapter 4. Installing and setting up vendor.connect 97If you don't do this and leave it set to localhost, you will receive a warning about attem

© Copyright IBM Corp. 2002. All rights reserved. ixPrefaceThis IBM Redbook introduces the new Geac commerce platform .connect applications – the call.

98 Geac System21 commerce.connect: Implementation on the iSeries Server5. In the left-hand panel, select Server-> Rebind. On the Rebind to server

Chapter 4. Installing and setting up vendor.connect 996. Select Entries-> Add Entry in the left-hand panel. On the Add directory entry panel (Figu

100 Geac System21 commerce.connect: Implementation on the iSeries ServerCreating the vcadmin user in IBM SecureWayTo create the vcadmin user, follow

Chapter 4. Installing and setting up vendor.connect 1012. In the create an LDAP User window (Figure 4-18), complete these tasks:a. For Common name, e

102 Geac System21 commerce.connect: Implementation on the iSeries ServerFigure 4-19 Logging on as vcadmin3. Logging into the vendor.connect system

Chapter 4. Installing and setting up vendor.connect 1034.2.11 Database synchronization from System21 to the vendor.connect databaseTo set up the cor

104 Geac System21 commerce.connect: Implementation on the iSeries Server4. Run the set of SQL commands that are detailed in the following SQL example

Chapter 4. Installing and setting up vendor.connect 1054.2.12 Testing the vendor.connect Web siteYou are now in a position to test the Web applicati

106 Geac System21 commerce.connect: Implementation on the iSeries ServerUnder normal circumstances, the application (for example, VennConn) continues

© Copyright IBM Corp. 2002. All rights reserved. 107Chapter 5. Performance tuningThis chapter covers performance tuning of Geac System21 products.5

x Geac System21 commerce.connect: Implementation on the iSeries ServerFind out more about the residency program, browse the residency index, and appl

108 Geac System21 commerce.connect: Implementation on the iSeries Server5.1 HardwareWhen you tune your configuration and system for performance, alw

Chapter 5. Performance tuning 109򐂰 Model 270 feature 2252 Processor CPW 950 Interactive CPW 0򐂰 Model 820 feature 2396 Processor CPW 950 Interactive C

110 Geac System21 commerce.connect: Implementation on the iSeries Server򐂰 Native driver: This driver may only be used by a Java application that is r

Chapter 5. Performance tuning 111Figure 5-3 Display Prestart Job Entries list Figure 5-4 shows the Display Prestart Job Entry Detail for the progra

112 Geac System21 commerce.connect: Implementation on the iSeries ServerYou must coordinate the tuning of these server jobs with the tuning of the We

Chapter 5. Performance tuning 113command, by default, does not show prestart jobs that are waiting for a connection. However, if you press F14, they

114 Geac System21 commerce.connect: Implementation on the iSeries ServerIt is necessary to check carefully that the server jobs are not in use. You c

Chapter 5. Performance tuning 1155.2.3 Subsystems and memory poolsBy default, WebSphere jobs run in the QEJBSBS subsystem in the base memory pool. I

116 Geac System21 commerce.connect: Implementation on the iSeries Server2. End the QEJBSBS subsystem by using the following command:ENDSBS QEJBSBS3.

Chapter 5. Performance tuning 117Figure 5-9 The Display Pool Definitions display for QEJBSBS In this example, the modification was already made usi

© Copyright IBM Corp. 2002. All rights reserved. 1Chapter 1. The .connect applicationsThis redbook covers the two Geac .connect applications:򐂰 call.co

118 Geac System21 commerce.connect: Implementation on the iSeries ServerFigure 5-10 Display Routing Entry Detail display 12.End the SQL server pres

Chapter 5. Performance tuning 119assigned but this could vary. However because both this entry and the QEJBSBS entry above specify *SHRPOOL2, the two

120 Geac System21 commerce.connect: Implementation on the iSeries ServerFigure 5-13 WRKSYSSTS display showing the memory pool namesAs in the other

Chapter 5. Performance tuning 12126.On the Work with Active Jobs display (Figure 5-15), press F11 to see the Pool column. All the jobs, except the su

122 Geac System21 commerce.connect: Implementation on the iSeries ServerIf WebSphere is the only significant application on your system, then the per

Chapter 5. Performance tuning 1235.3.2 Stateless connectionsThe majority of call.connect beans and all vendor.connect beans are common stateless ses

124 Geac System21 commerce.connect: Implementation on the iSeries ServerFigure 5-17 The DataSource panel Advanced page of the WebSphere console 5.3

Chapter 5. Performance tuning 1255.4.1 Initial Java heap size–Xms is an important parameter that controls the initial Java heap size. It is followed

126 Geac System21 commerce.connect: Implementation on the iSeries Server5.4.3 Verbose garbage collectionThe JVM has an option called verbose garbage

Chapter 5. Performance tuning 127A simple way to view this file is to map a PC drive to the iSeries integrated file system (IFS) and then use a PC ed

2 Geac System21 commerce.connect: Implementation on the iSeries Server1.1 call.connectGeac call.connect fills two roles. First, it is a telesales-or

128 Geac System21 commerce.connect: Implementation on the iSeries ServerIf you have addressed most other performance issues, then you may want to try

Chapter 5. Performance tuning 129place of the OS/400 system class loader. This custom class loader does not detect the static programs. To enable the

130 Geac System21 commerce.connect: Implementation on the iSeries ServerIf you have a powerful editor, you may be able to replace all the colons with

Chapter 5. Performance tuning 131In this example, we completed the following tasks:1. The command line arguments were copied to one Notepad session a

132 Geac System21 commerce.connect: Implementation on the iSeries ServerFigure 5-23 Advanced tab of the Enterprise Bean panelPerformance requiremen

Chapter 5. Performance tuning 133If transactions fail for this reason, then the client receives such messages as JTA Transaction Aborted. If you see

134 Geac System21 commerce.connect: Implementation on the iSeries Server“Ping” in this context refers to sending a simple test message, which require

Chapter 5. Performance tuning 135Figure 5-26 The Advanced page of the DataSource panel Connection time outThis is the maximum time that WebSphere w

136 Geac System21 commerce.connect: Implementation on the iSeries Serverreceives an exception indicating that the connection was pre-empted. If valid

© Copyright IBM Corp. 2002. All rights reserved. 137Chapter 6. Tips and techniquesThis chapter offers various tips and techniques for using Geac Syste

Chapter 1. The .connect applications 3Figure 1-1 The call.connect buying listcall.connect is a flexible order capture process that includes the fol

138 Geac System21 commerce.connect: Implementation on the iSeries Server6.1 The iSeries integrated file systemSeveral releases ago, IBM reorganized

Chapter 6. Tips and techniques 139򐂰 QIBM: This directory does not have any special property, but most IBM supplied files are within this directory. T

140 Geac System21 commerce.connect: Implementation on the iSeries Server6.1.2 Mapping a PC drive to the iSeries IFSAn easy way to explore and view t

Chapter 6. Tips and techniques 141Figure 6-1 Creating a file share To create a more specific share, use a different name and select an appropriate

142 Geac System21 commerce.connect: Implementation on the iSeries Server6.1.3 Editing an iSeries stream file using a PC editorIf you exposed some or

Chapter 6. Tips and techniques 143If it is not easy to create the file again, then you can view it by using an OS/400 command, such as Edit File (EDT

144 Geac System21 commerce.connect: Implementation on the iSeries ServerLike cd, qualified names, except for /, must be in single quotation marks. Fi

Chapter 6. Tips and techniques 145The Save Object (SAV) command is slightly confusing since it does not want only the save device name (for example,

146 Geac System21 commerce.connect: Implementation on the iSeries ServerAnother common problem can be caused by inconsistent use of users. If you run

Chapter 6. Tips and techniques 147scrolls. There are few restrictions on commands and their parameters. The commands can be rather inconsistent and h

4 Geac System21 commerce.connect: Implementation on the iSeries Server1.2 vendor.connectGeac vendor.connect is a supplier self-service application.

148 Geac System21 commerce.connect: Implementation on the iSeries Serverprompt. DOS command screens commonly use the currently drive and directory na

Chapter 6. Tips and techniques 149Even Qshell may be confused by the unusual characters. However in this case, there is a solution. That is you may q

150 Geac System21 commerce.connect: Implementation on the iSeries ServerThis can be useful for monitoring log files in real time. The session in whic

Chapter 6. Tips and techniques 151This creates the variable DIRECTORY if necessary and set its value to /OrderManagement. There are no types for vari

152 Geac System21 commerce.connect: Implementation on the iSeries ServerThe following Qshell command runs the script myscript.sh and sends both stand

Chapter 6. Tips and techniques 153Figure 6-5 WRKACTJOB command showing the subsystem QEJBSBS6.3.1 Instance monitor jobsIf you want to confirm that

154 Geac System21 commerce.connect: Implementation on the iSeries ServerFigure 6-6 Job log of the QEJBADMIN job This confirms that this is an insta

Chapter 6. Tips and techniques 155Figure 6-7 The NETSTAT command showing ports 900 and 902 If you have trouble connecting a console to the adminis

156 Geac System21 commerce.connect: Implementation on the iSeries ServerThen look in the job log of the administration job of the instance where you

Chapter 6. Tips and techniques 157Figure 6-8 The WRKDTAARA command showing the SF99147 data area If you see a data area, type 5 next to it to displ

Chapter 1. The .connect applications 5򐂰Supplier planning: An enquiry allows the supplier to view the stock status and demand for products for which t

158 Geac System21 commerce.connect: Implementation on the iSeries ServerAn alternative way is to view the product.xml file. If you used the default d

Chapter 6. Tips and techniques 159Check that you specified the correct system name and port when you started the console. If you start the console fr

160 Geac System21 commerce.connect: Implementation on the iSeries Server6.5.3 Checking the iSeries database nameIn a few contexts, the name of the D

© Copyright IBM Corp. 2002. All rights reserved. 161Related publicationsThe publications listed in this section are considered particularly suitable f

162 Geac System21 commerce.connect: Implementation on the iSeries Server

© Copyright IBM Corp. 2002. All rights reserved. 163IndexSymbols# 150$ 147, 151$ prompt 147$1 150$2 150*BASE 115*INTERACT 115*LOCAL 1

164 Geac System21 commerce.connect: Implementation on the iSeries Servercreating an EJB container 60creating DataSources 58creating enterprise be

Index 165Java Web Start in test 67JConnects server 92JDBC database access 17JIT compiler 128JMS 9, 12JNDI/MQ objects 35JNI (Java Native

166 Geac System21 commerce.connect: Implementation on the iSeries Serverquote site namefmt 1 139QZDASOINIT 114RRational Rose 10Rational Unified

Index 167stateful connection 122supplier ID 92System21 data setup 87user ID 92user profile 87user profiles 87verbose garbage collection

6 Geac System21 commerce.connect: Implementation on the iSeries Server

168 Geac System21 commerce.connect: Implementation on the iSeries Server

(0.2”spine)0.17”<->0.473”90<->249 pagesGeac System21 commerce.connect: Implementation on the IBM ~ iSeries Server

®SG24-6526-00 ISBN 0738424005INTERNATIONAL TECHNICALSUPPORTORGANIZATIONBUILDING TECHNICAL INFORMATION BASED ON PRACTICAL EXPERIENCEIBM Redbooks are de

© Copyright IBM Corp. 2002. All rights reserved. 7Chapter 2. Architecture of the commerce.connect productsThe products that make up the commerce.conne

8 Geac System21 commerce.connect: Implementation on the iSeries Server2.1 The need for an architectureWhy is an architecture necessary? Can’t we sim

Chapter 2. Architecture of the commerce.connect products 9The EJB standard is a server-side Java-based component architecture for building multi-tier

10 Geac System21 commerce.connect: Implementation on the iSeries Server2.1.3 The development processGeac uses a development process based around the

Chapter 2. Architecture of the commerce.connect products 11Figure 2-1 shows an example of the primary relationship between the main SalesOrder subsys

12 Geac System21 commerce.connect: Implementation on the iSeries ServerFor vendor.connect, Figure 2-2 shows the relationship between the controlling

Chapter 2. Architecture of the commerce.connect products 13call.connect messaging is implemented using IBM’s implementation of the Java Message Servi

14 Geac System21 commerce.connect: Implementation on the iSeries Server2.2.2 vendor.connectvendor.connect uses messaging in conjunction with process

Chapter 2. Architecture of the commerce.connect products 15Figure 2-5 Relationship between the .connect applications 2.3 Overview of process.conne

16 Geac System21 commerce.connect: Implementation on the iSeries Servere-mail requesting information. The e-mail reply is then used to control the ne

Chapter 2. Architecture of the commerce.connect products 17to upgrade the hardware, software, or both. The minimum hardware requirements obviously de

International Technical Support OrganizationGeac System21 commerce.connect:Implementation on the IBM ~ iSeries ServerDecember 2002SG24-6526-00

18 Geac System21 commerce.connect: Implementation on the iSeries ServerThere are two disadvantages:򐂰 The first is primarily stylistic. Using Toolbox

© Copyright IBM Corp. 2002. All rights reserved. 19Chapter 3. Installing and setting up call.connectThis chapter explains how to install and set up ca

20 Geac System21 commerce.connect: Implementation on the iSeries Server3.1 Skills and prerequisites for installing, running WebSphere Application Se

Chapter 3. Installing and setting up call.connect 21Table 3-1 Disk space requirementsiSeries software requirementsThe minimum software required for

22 Geac System21 commerce.connect: Implementation on the iSeries Server򐂰 DB2 Query Manager and SQL Development Kit for iSeries (5769-ST1): This is an

Chapter 3. Installing and setting up call.connect 23Checklist of the basic stepsTable 3-2 summarizes the steps required to install and configure call

24 Geac System21 commerce.connect: Implementation on the iSeries Server1. From the CD, load the Order Management module as explained in the readme fi

Chapter 3. Installing and setting up call.connect 254. Select option 10 to view the job log. Wait until you see the message WebSphere administration

26 Geac System21 commerce.connect: Implementation on the iSeries ServerThe import includes:򐂰 The node򐂰 The SalesOrder application and all contents򐂰 T

Chapter 3. Installing and setting up call.connect 272. To start the console for the specified machine in the default environment, enter the command:a

© Copyright International Business Machines Corporation 2002. All rights reserved.Note to U.S. Government Users Restricted Rights -- Use, duplication

28 Geac System21 commerce.connect: Implementation on the iSeries ServerJournaling the files with an ASPTo journal the files using an ASP, follow thes

Chapter 3. Installing and setting up call.connect 29– Option = SJ – Command = STRJRNPF FILE(&L/&N) JRN(OSLF3/OSL) OMTJRNE(*OPNCLO) Press Ent

30 Geac System21 commerce.connect: Implementation on the iSeries ServerTo run SQL scripts, follow these steps:1. Open the /Ordermanagement/Stored Pro

Chapter 3. Installing and setting up call.connect 31Figure 3-5 Client Access server setup10.After you make all necessary changes, click Apply and t

32 Geac System21 commerce.connect: Implementation on the iSeries ServerThe prerequisites include:򐂰 WebSphere 3.5.5򐂰 MQSeries 5.2򐂰 MA88 MQSeries class

Chapter 3. Installing and setting up call.connect 33Creating a queueNow create a queue as explained here:1. On the Start Queue Manager display, type

34 Geac System21 commerce.connect: Implementation on the iSeries ServerFigure 3-8 Create MQM Object Authority display for your queue manager3. Ente

Chapter 3. Installing and setting up call.connect 35Additional files neededYou need the following files to configure and run your message receiver:򐂰

36 Geac System21 commerce.connect: Implementation on the iSeries ServerAdditional WebSphere configurationAdd the following argument to the command li

Chapter 3. Installing and setting up call.connect 37Sign on as QSECOFR and create the profile as shown here:CRTUSRPRF USRPRF(OMUSER) TEXT('call.

© Copyright IBM Corp. 2002. All rights reserved. iiiContentsNotices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

38 Geac System21 commerce.connect: Implementation on the iSeries Server5. On each display, press F15 to authorize the user to all options on that men

Chapter 3. Installing and setting up call.connect 393.2.7 System21 data set upSystem21 data setup is covered in the Basic System21 Setup for call.co

40 Geac System21 commerce.connect: Implementation on the iSeries Server4. Verify that the server is running. Enter the following command:WRKACTJOB 5.

Chapter 3. Installing and setting up call.connect 414. The IBM HTTP Server for AS/400 page appears as shown in Figure 3-12. Select the Configuration

42 Geac System21 commerce.connect: Implementation on the iSeries ServerConfiguring an HTTP Server for iSeries (original)To configure an IBM HTTP Serv

Chapter 3. Installing and setting up call.connect 43Creating a configurationFollow these steps to create a configuration:1. Under the Configurations

44 Geac System21 commerce.connect: Implementation on the iSeries Server4. The Request routing page (Figure 3-15) appears. Insert the following action

Chapter 3. Installing and setting up call.connect 456. The MIME types page (Figure 3-16) appears. Enter the following information for the system to r

46 Geac System21 commerce.connect: Implementation on the iSeries ServerCreating an instanceNow you must create a server instance: 1. On the left-hand

Chapter 3. Installing and setting up call.connect 47Configuring an HTTP Server for iSeries (powered by Apache)This section explains how to configure

iv Geac System21 commerce.connect: Implementation on the iSeries Server3.3.4 Restoring IFS objects . . . . . . . . . . . . . . . . . . . . . . . . .

48 Geac System21 commerce.connect: Implementation on the iSeries Server3. The Create HTTP Server page (Figure 3-19) appears. Fill in the following in

Chapter 3. Installing and setting up call.connect 49Figure 3-20 HTTP Server name (HOMERA) global settings page7. On the Serve New Directory wizard,

50 Geac System21 commerce.connect: Implementation on the iSeries Server9. On the Director /OrderManagement/client page (Figure 3-21), under Processin

Chapter 3. Installing and setting up call.connect 51Figure 3-22 Additional Meta (MIME) information for file extensions section11.At the top of the

52 Geac System21 commerce.connect: Implementation on the iSeries Server2. Launch Java Web Start for the first time. In a Web browser, go to:http://&l

Chapter 3. Installing and setting up call.connect 53Under normal circumstances, the application (for example, SalesOrder) continues to run in WebSphe

54 Geac System21 commerce.connect: Implementation on the iSeries Server3.4.1 WebSphere node nameThe node name in WebSphere is case sensitive. This i

Chapter 3. Installing and setting up call.connect 553.4.5 Log files and debuggingThere are log files for both the client and the server, where you c

56 Geac System21 commerce.connect: Implementation on the iSeries ServerLoadlog.batIf the logging level on the server is changed, these changes do not

Chapter 3. Installing and setting up call.connect 57/OrderManagement/test/cfg/log.cfgOpen this file in a notepad, and change the following line:log4j

Contents v5.3.3 Total connections and SQL server jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1245.4 Performance topics fo

58 Geac System21 commerce.connect: Implementation on the iSeries ServerFigure 3-23 WebSphere consoleCreating JDBC driversIn the WebSphere console,

Chapter 3. Installing and setting up call.connect 59After you decide a name, create the data source as explained here:1. Click the Types tab. On the

60 Geac System21 commerce.connect: Implementation on the iSeries Server5. Use the WRKLNK / command to ensure that *PUBLIC has *RWX authority to this

Chapter 3. Installing and setting up call.connect 61Figure 3-24 WebSphere console after deployment3.5.3 Manual client installationFor a simple set

62 Geac System21 commerce.connect: Implementation on the iSeries ServerLog.cfgCheck the following line:log4j.appender.basic.File=C:\\callConnect\\CCC

Chapter 3. Installing and setting up call.connect 63Table 3-4 Steps required to configure a WebSphere instance3.6.2 Setting up an iSeries server f

64 Geac System21 commerce.connect: Implementation on the iSeries ServerTest userYou must set up a test user profile, such as TSTUSR, for the JDBC con

Chapter 3. Installing and setting up call.connect 653.6.4 WebSphere administrationThis section covers the topics related to WebSphere.Starting the a

66 Geac System21 commerce.connect: Implementation on the iSeries Server򐂰 $appname$: This is the application name, such as SalesTest. It should be dif

Chapter 3. Installing and setting up call.connect 673. Verify that the files within c:\callConnect\CCClient are correctly configured as listed in the

vi Geac System21 commerce.connect: Implementation on the iSeries Server

68 Geac System21 commerce.connect: Implementation on the iSeries Servera. Insert the name of the configuration, such as the iSeries name. b. Select t

Chapter 3. Installing and setting up call.connect 691. At the top of the page, select Configuration. 2. Under Configuration structure, verify that HT

70 Geac System21 commerce.connect: Implementation on the iSeries ServerFigure 3-25 Manage HTTP Servers page: Stopping the serverConfiguring CallCon

Chapter 3. Installing and setting up call.connect 71The files to modify are:򐂰 ejb_default.cfg򐂰 log.cfg 򐂰 standard.propertiesSee 3.6.5, “Manual client

72 Geac System21 commerce.connect: Implementation on the iSeries Server

© Copyright IBM Corp. 2002. All rights reserved. 73Chapter 4. Installing and setting up vendor.connectThis chapter explains how to install and set up

74 Geac System21 commerce.connect: Implementation on the iSeries Server4.1 Preparing for the installation This section discusses the activities and

Chapter 4. Installing and setting up vendor.connect 75vendor.connect componentsSeveral different types of objects are required for this installation

76 Geac System21 commerce.connect: Implementation on the iSeries Server4.2.3 Restoring librariesThree additional libraries are delivered in the AS40

Chapter 4. Installing and setting up vendor.connect 77Wait for the $ sign to appear after each entry. Creating a new instanceTo create a new instance

© Copyright IBM Corp. 2002. All rights reserved. viiNoticesThis information was developed for products and services offered in the U.S.A. IBM may not

78 Geac System21 commerce.connect: Implementation on the iSeries ServerFigure 4-2 shows an example of an imported configuration.Figure 4-2 Importin

Chapter 4. Installing and setting up vendor.connect 79򐂰 $host$: This is the iSeries name and domain, such as needjava.jab.co.uk.򐂰 $port$: This is the

80 Geac System21 commerce.connect: Implementation on the iSeries ServerConfiguring the HTTP Server on the iSeriesTo configure the HTTP Server on the

Chapter 4. Installing and setting up vendor.connect 814. The IBM HTTP Server for AS/400 page appears as shown in Figure 4-4. Select the Configuration

82 Geac System21 commerce.connect: Implementation on the iSeries ServerAfter you select the Configuration and Administration icon, as stated in the p

Chapter 4. Installing and setting up vendor.connect 83Figure 4-6 Create configuration pageCreating an instanceNow you must create a server instance

84 Geac System21 commerce.connect: Implementation on the iSeries Server2. The Create server instance page (Figure 4-7) appears. Follow these steps:a.

Chapter 4. Installing and setting up vendor.connect 85You must journal the following files at a minimum:򐂰 All physical files in the OSLVCF3 library (

86 Geac System21 commerce.connect: Implementation on the iSeries Server3. The Specify Option File to Work With display (Figure 4-8) appears. Press En

Chapter 4. Installing and setting up vendor.connect 87– Name: *ALL– Type: *FILE– Attribute: PF-DTA9. On the following display, type SJ next to each f