OneWorld B73.3x Service Pack 23 Installation Instructions PeopleBook

OneWorld B73.3x Service Pack 23Installation Instructions PeopleBook

September 1, 2004

All material contained in this documentation is proprietary and confidential to PeopleSoft, Inc. ("PeopleSoft"), protected by copyright laws and subject to the nondisclosure provisions of the applicable PeopleSoft agreement. No part of this documentation may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, including, but not limited to, electronic, graphic, mechanical, photocopying, recording, or otherwise without the prior written permission of PeopleSoft.

This documentation is subject to change without notice, and PeopleSoft does not warrant that the material contained in this documentation is free of errors. Any errors found in this document should be reported to PeopleSoft in writing.

The copyrighted software that accompanies this document is licensed for use only in strict accordance with the applicable license agreement which should be read carefully as it governs the terms of use of the software and this document, including the disclosure thereof.

PeopleSoft, PeopleTools, PS/nVision, PeopleCode, PeopleBooks, PeopleTalk, and Vantive are registered trademarks, and Pure Internet Architecture, Intelligent Context Manager, and The Real-Time Enterprise are trademarks of PeopleSoft, Inc. All other company and product names may be trademarks of their respective owners. The information contained herein is subject to change without notice.

Open Source Disclosure

This product includes software developed by the Apache Software Foundation (http://www.apache.org/). Copyright (c) 1999-2000 The Apache Software Foundation. All rights reserved. THIS SOFTWARE IS PROVIDED “AS IS’’ AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

PeopleSoft takes no responsibility for its use or distribution of any open source or shareware software or documentation and disclaims any and all liability or damages resulting from use of said software or documentation.

B73.3x Service Pack 23 Installation Instructions

B73.3.x SP23 One-Off Installation Instructions 1

Table of Contents

B73.3x SP23_One-Off Installation Instructions ..............................................................................2 Before You Begin ............................................................................................................................2

Readme File .................................................................................................................................2 Setting Up Multiple Foundations .................................................................................................2 Auditing Tool (21 CFR Part 11) Documentation.........................................................................2 APS Real-time Settings for JDE.INI (optional) ...........................................................................2 Updating the Java Connector and Kernel Files for OneWorld Xe and ERP 8.0..........................2 Package Build and Deployment Issues ........................................................................................3 Vertex Header Files (for Vertex users only) ................................................................................3 Database Password Encryption for Multiple Foundation Environments .....................................4 Things to keep in mind.................................................................................................................4

Installing the Service Pack...............................................................................................................6 Deployment Server Installation....................................................................................................7 AS/400 Server Installation ...........................................................................................................8 HP 9000 Server Installation .......................................................................................................11 RS/6000 Server Installation .......................................................................................................14 Sun Server Installation ...............................................................................................................18 Windows 2000 and Windows 2003 (Intel) Server Installation ..................................................21

Install the Service Pack ........................................................................................................................ 21

Creating Your Client Update Package .......................................................................................23 APS Real-time Events Settings for JDE.INI (optional).................................................................24 Defining Application Shortcut Types for External Messages .......................................................27 Database Password Encryption for Multiple Foundation Environments.......................................29

Configuration .............................................................................................................................29 Pre-Installation Process ..............................................................................................................29 Installation..................................................................................................................................30 Roll-back Procedures .................................................................................................................32

B73.3x SP23_One-Off Installation Instructions

Before You Begin This document includes instructions for installing the service pack on workstations and servers of all supported platforms running OneWorld versions, OneWorld Xe, or ERP 8.0. In addition, this document includes other tasks that fix specific problems or enhance the system performance. Read the instructions below and determine which of these tasks you need to perform. Note that some of these tasks must be performed before you install the service pack while others must be performed after you install the service pack.

These files are downloadable by SAR number for the different platforms. Based on the speed of your internet connection, you will need to determine whether to download the SAR or order the CD from Software Distribution.

Readme File

Before beginning installation of the service pack, check the associated README file for late-breaking information and requirements.

Setting Up Multiple Foundations

We strongly recommend that you set up multiple OneWorld foundations, including a test environment for applying service pack fixes. This helps ensure that a stable environment exists before you promote fixes to your production environment. To learn more about setting up multiple OneWorld foundations, visit Customer Connect under Support | Documentation | EnterpriseOne | EnterpriseOne Tools | Installation and Upgrade.

Auditing Tool (21 CFR Part 11) Documentation

The location of the Auditing Tool (21 CFR Part 11) documentation can be found on the Customer Connect under Support | Documentation | EnterpriseOne | EnterpriseOne Tools | Installation and Upgrade.

APS Real-time Settings for JDE.INI (optional)

This service pack contains instructions for enabling APS (Advanced Planning Solutions) integration by adding event generation settings to the JDE.INI file. These settings are optional and should be implemented after installing the service pack.

Updating the Java Connector and Kernel Files for OneWorld Xe and ERP 8.0

For the OneWorld adapter to connect to the PeopleSoft ERP 8.0 and OneWorld Xe enterprise server, and to run properly, the Java connector and kernel files must match or be compatible with the ERP 8.0 enterprise server version and XPI system. See Appendix G of the Enterprise XPI OneWorld Adapter Installation and Configuration guide.

Package Build and Deployment Issues

The package build and assembly process includes many critical tasks that must be successfully completed to correctly install packages. See OneWorld Package Management Guide for details on building, assembling, and deploying packages. This guide lists most of these tasks and gives step-by-step instructions for completing them. Before you build a package, review these tasks to ensure you complete all the required steps.

Vertex Header Files (for Vertex users only)

This applies to customers who use the Vertex Quantum Payroll Tax and Vertex Quantum Sales and Use Tax applications with OneWorld.

This service pack includes Vertex 2.0* header files for Sales & Use and Vertex 2.3.2 header files for Payroll Tax. Vertex 2.0* Sales & Use and Vertex 2.3.2 Payroll are now the required versions. You must rebuild seven business functions for Vertex to function properly after you apply the service pack. Depending on how you have these BSFNs mapped, you may need to do a server or client update package, or both.

The seven business functions that you must rebuild after applying the service pack are as follows:

Business Function Description

B0700058 Establish connection to Vertex B0000182 Initialize environment for vendor business functions B0000183 Free environment for vendor business function B7300004 Retrieve Quantum GeoCodes B7300002 Validate Quantum GeoCodes B7300012 Retrieve Quantum software information X00TAX Calculate and edit tax amounts

For more information about using Vertex Quantum applications with OneWorld, see “Configuring OneWorld for Use with Vertex Quantum Tax Applications” in the OneWorld Installation Guide or OneWorld Upgrade Guide.

*Vertex Sales and Use has different versions depending on the server platform it runs on. OneWorld supports the following versions:

AS/400 2.0.15 UNIX 2.0.16 Windows NT 2.0.17

Database Password Encryption for Multiple Foundation Environments

The algorithm used to encrypt and decrypt OneWorld passwords has been compromised and has been posted to web. This enhancement will address the vulnerability that exists when storing passwords in the database and the associated installation/migration issues. The solution will update the passwords stored in the database to a higher encryption standard.

Note: When applying the ESU available in SAR #6911235 or SAR #6945128 you must perform the instructions in the Database Password Encryption section at the end of this guide concurrently to the steps of applying this service pack. Please read the Database Password Encryption section before performing the update. Failure to perform the Database Password Encryption steps when applying the ESU and Service Pack may prevent you from being able to log on to your database.

More details can be found in the PeopleSoft Security Vulnerability Report under “PeopleSoft EnterpriseOne Password Encryption Vulnerability” (Security Vulnerability ID: 2004011901).

Things to keep in mind

1. Once the solution is deployed, the user records are encrypted with the new encryption as the user login occurs. There is no configuration to disable the conversion from the old encryption.

2. There is no conversion program to rollback user records to the old encryption nor is there one for converting all user records to the new encryption. Restoring a back up copy of the F98OWSEC table can be used to reset the user data.

3. The multiple foundation setup utilizes one security server process per port.

4. If the customer has multiple enterprise servers at different Service Pack levels, make sure each of them is pointing to the correct security data sources.

• If an enterprise server running an older Service Pack accesses data encrypted using the new encryption, authentication will fail and user will not be able to login.

• If an enterprise server running the new Service Pack accesses data encrypted using the old encryption, it will update the user records in Security tables to the new encryption on the fly.

5. If the customer has multiple foundations or multiple enterprise servers at different Service Pack levels, a dual maintenance of users and passwords is required. Once all the foundations are running SP22_P1 or newer,

a. The INI setting for SECURITY Data Source can be changed back to the SYSTEM Data Source value.

b. The F98OWSEC and F9312 tables from Server Map Data Source can be removed.

6. The ESU is not a planner ESU. Therefore, the customer will not be able to perform Administrative functionality of changing passwords, and copy user records encrypted using new encryption from the deployment server. They can continue to add user and copy user records encrypted using old encryption.

7. If the Service Pack is installed and the ESU is not installed,

a. To a workstation, the administrator will not be able to change passwords. The administrator will be able to add/delete/copy users. These users will have a password in the old encryption. The encryption change will occur when the user logs in.

8. If the ESU is installed and the Service Pack is not installed,

a. Since the ESU is backwards compatible, it detects that the Service Pack is not installed and will continue to function normally.

Installing the Service Pack

To completely install the service pack, you must update the servers and workstations in your OneWorld environment. Complete all the tasks below that are relevant to your OneWorld configuration.

! Deployment server installation

! AS/400 server installation

! HP 9000 server installation

! RS/6000 server installation

! Sun server installation

! Windows 2000 or Windows 2003 (Intel) server installation

! Creating your client update package

Deployment Server Installation

Use the following instructions to replace the system directory and its subdirectories on the deployment server:

1. On the deployment server, make a copy of your \System, \SystemComp, and \OneWorld Client Install directories.

# Do not modify the names of the original directories. The original directories are required to install the service packs.

2. Perform the following instructions for installing the Service Pack from either a download or CD.

For Downloads:

• Download the appropriate software update, using the SAR number for this service pack. (For more information about the SAR number, see the PeopleSoft Knowledge Garden.) A box showing the files extracting is displayed.

• If your deployment server is directly connected to the Internet, choose “Run this program from its current location” from the displayed dialog box, and continue with step 5.

• If your deployment server is not directly connected, you must select “Save this program to disk.” Transfer the .exe file to a directory of your choice (not in the JDE directory structure) and run the executable from there.

For CDs:

• Insert the service pack CD into the CD drive of the deployment server. A Readme.html file pops up. From the Readme.html file there is a link to start the setup.exe.

3. Click OK. The Installation Manager appears.

4. On the Installation Manager screen, select Install: Service Pack Install. The Installation Setup screen appears.

5. On the Installation Setup Screen, click Next. The package size is calculated (you may already have seen package size calculation information, as noted above). This can run for several minutes.

The system calculates the required disk space by subtracting the disk space used by the current foundation code from the space required for the new code. Thus the calculated number may be small, and in some cases negative.

The default directory path is set automatically to the directory that contains OneWorld version B73.3x.

6. Click Finish.

7. Install the appropriate ESU according to the following SARs to the deployment server and apply it to the path codes using the OneWorld Xe Software Update Installation guide.

Release SAR#Xe 6911235

ERP 8 6945128

Note: It is required that the ESU is deployed on enterprise servers, and clients in the respective order.

8. Continue with the appropriate host installation. See the following pages for instructions.

AS/400 Server Installation

Before beginning the installation on the AS/400 Server, perform the following step if using a Download Service Pack.

For Downloads:

• Before installation on the AS/400, download the service pack for AS/400 host installation to your deployment server. If your deployment server is directly connected to the Internet, choose “Run this program from its current location.” Otherwise, select “Save this program to disk,” copy the .exe file to the deployment server, and run the executable from there. It is recommended that you copy the executables to the Windows temp directory (do not save the executable to the JDE directory structure).

The following instructions explain how to replace the system library on the AS/400 for both CD and Download installations.

# Several commands below contain references to syslib. Replace these references with the names of the OneWorld SYSTEM libraries that currently exist on your AS/400. For example, you might replace syslib with B7333SYS or B7334SYS.

1. Sign onto the AS/400 as ONEWORLD, and select the release you want to apply this service pack to.

2. End OneWorld on the AS/400 by entering the following command:

ENDNET CLRIPC

3. Sign onto your AS/400 as QSECOFR, and rename the OneWorld SYSTEM library by entering the following command: RNMOBJ OBJ(QSYS/syslib) OBJTYPE(*LIB) NEWOBJ(syslibBK)

Do not delete these libraries because some of the objects are specific to your installation.

4. Move the kernel specs to a backup file: RNM OBJ(‘/B733xSYS’) NEWOBJ(‘B733xBAK’)

where x is the release number. (Ensure your NEWOBJ does not already exist, if it does choose a different backup file name.)

5. Create a new directory to put the new kernel specs in: MKDIR (‘/B7334SYS’)

6. Change the authority for the profile ONEWORLD by entering the following command: GRTOBJAUT OBJ(ONEWORLD) OBJTYPE(*USRPRF) USER(*PUBLIC) AUT(*USE)

7. Transfer the service pack software from the CD to the AS/400:

A. Create a temporary library for the service pack software by entering the following command:

CRTLIB JDETEMP

This library can be removed after the installation is complete.

B. Create a save file (SAVF) for the software in preparation for the transfer by entering the following command:

CRTSAVF JDETEMP/SYSTEM

C. Create a save file (SAVF) for the software in preparation for the transfer by entering the following command:

CRTSAVF JDETEMP/KRNLSPEC

8. From a DOS window on the computer which contains the SP CD or download, start a file transfer protocol (FTP) session to connect to your enterprise AS/400 by entering the following commands:

C:\>ftp yourAS400Name (where yourAS400Name is your AS/400 enterprise server) Connected to yourAS400Name 220-QTCP at yourAS400Name

(The 220 connection closes if idle longer than 5 minutes.) User <yourAS400Name:<none>>: qsecofr 331 Enter password. Password: 230 qsecofr logged on.

9. Change the directory to the JDETEMP library on the AS/400 by entering the following command: ftp> cd jdetemp 250 Current library changed to JDETEMP

10. Change the local directory to the CD directory containing the AS/400 SAVFs by entering the following commands.

ftp> lcd z:\hosts\as400 (where z: is the drive that contains the service pack CD or download)

Your local directory is now z:\hosts\as400.

11. Change the mode of transfer to binary by entering the following command: ftp> bin 200 Representation type is binary IMAGE

12. Upload the SYSTEM SAVFs to the AS/400 by entering the following commands: ftp> put SYSTEM 200 PORT subcommand request successful 150 Sending file to member SYSTEM in file SYSTEM in library JDETEMP 250 File transfer completed successfully nnnnn bytes sent in n.nn seconds <nnn.nn Kbytes/sec>

13. Upload the SYSTEM KRNLSPEC to the AS/400 by entering the following commands ftp> put KRNLSPEC 200 PORT subcommand request successful 150 Sending file to member KRNLSPEC in file KRNLSPEC in library

JDETEMP 250 File transfer completed successfully nnnnn bytes sent in n.nn seconds <nnn.nn Kbytes/sec>

14. Exit FTP by entering the following command: ftp> quit 221 QUIT subcommand received. C:\>

15. On the AS/400, restore the B733xSYS library by entering the following command: RSTLIB SAVLIB(B7334SYS) DEV(*SAVF) SAVF(JDETEMP/SYSTEM) RSTLIB(B7334SYS)

16. Copy the folder PRINTQUEUE from your backup of the SYSTEM library to the newly restored SYSTEM library by entering the following command: CPYF FROMFILE(syslibBK/PRINTQUEUE) TOFILE(B7334SYS/PRINTQUEUE)

FROMMBR(*ALL) TOMBR(*FROMMBR) MBROPT(*REPLACE) CRTFILE(*YES)

17. Copy the JDE.INI file from your backup of the SYSTEM library to the newly restored SYSTEM library by entering the following command: CRTDUPOBJ OBJ(INI) FROMLIB(syslibBK) OBJTYPE(*FILE) TOLIB(syslib) DATA(*YES)

18. Replace objects in IFS file system. RST DEV('/QSYS.LIB/JDETEMP.LIB/KRNLSPEC.FILE') OBJ(('/krnb733x' *INCLUDE syslib))

(where x is the release number)

19. If your prior OneWorld release level was not B7334 (for example, the syslib not B7334SYS), you will need to perform the following steps to ensure this version of OneWorld matches your naming convention. The OneWorld utility program CRTOWSBS sets up the subsystem name, and ensures that your current libraries are in sync with those in OneWorld objects.

A. Ensure you are signed on as QSECOFR.

B. Add the OneWorld SYSTEM library to your library list. For example, ADDLIBLE B7334SYS.

C. Do WRKSBSD in OneWorld to determine the name of the subsystem that was delivered in this service pack, for example, WRKSBSD SBSD(*ALL).

D. Enter the following command: CRTOWSBS subsystem(‘jdeb7334’) syslib(‘B7334SYS’)

where subsystemname is the name of the current subsystem description (*SBSD) in your OneWorld System library (syslib)

The CALL PGM command requires two parameters. Beginning with release B73.3 SP15, the last two parameters should be the subsystem name and the SYSTEM library.

20. Sign onto your AS/400 as ONEWORLD. To ensure the library list is set up correctly, verify that it contains the newly restored OneWorld system library (for example, B7334SYS). If it is not there, then run:

ADDLIBLE B7334SYS

21. If you changed your ADDLIBLE B7334SYS name during this install, you need to update your JDE.INI file, (for example, if your SYSLIB was B7333SYS before this upgrade and is now B7334SYS), with the following change:

[INSTALL]

DefaultSystem=B7334SYS

22. For each OneWorld path code, re-link the business functions located in the associated AS/400 library. The program LINKBSFN has been shipped with this service pack to simplify this process. The following commands must be executed against each full package for a specified path code: A. Run LINKBSFN against the path code’s full package.

Type LINKBSFN, and then press F4 to display the system prompt. Enter the package library name for the first parameter and the path code for the second parameter.

B. Wait until the previous step completes successfully before continuing to the next step. Repeat this step for every package and path code you are updating.

23. Sign off and then sign back on as user OneWorld. Verify your library list is set up correctly by performing your typical verification to ensure OneWorld is working properly, for example, PORTTEST and STRNET.

HP 9000 Server Installation

Before beginning the installation on the HP 9000 Server, perform the following step if using a Download Service Pack.

For Download:

• Before installation on the HP 9000, download the service pack for HP 9000 host installation to your deployment server. If your deployment server is directly connected to the Internet, choose “Run this program from its current location.” Otherwise, select “Save this program to disk,” copy the .exe file(s) to the deployment server, and run the executables from there. It is recommended that you copy the executables to the Windows temp directory (do not save the executable to the JDE directory structure).

• The download creates a file named system.Z in the \hosts\hp9000 directory on the deployment server. If there is already a read-only system.Z file on the Windows server, the Service Pack will not install correctly. To avoid this problem, move the system.Z files to a backup temp directory prior to installing the Service Pack.

The following instructions explain how to replace the system directory and its subdirectories on the HP 9000 installing from either CD or Download: 1. Log on to the enterprise server as your B733x administrative user, for example, jdeb733. 2. If installing Service Pack from CD, perform the following steps. For CD:

• Copy the system.Z file from the service pack (SP) CD \hosts\hp 9000 directory to the deployment server z:\JDEdwardsOneWorld\b733x\hosts\hp9000 directory, where z: is the drive where OneWorld is installed. If there is already a read-only system.Z file on the Windows server, the Service Pack will not install correctly. To avoid this problem, move the system.Z files to a backup temp directory prior to installing the Service Pack.

• On the enterprise server, create the following temporary directory, or verify its existence in the following path: /u01/jdedwardsoneworld/tmp (where u01 is the mount point for the installation. This may be different for your system.)

3. End Network Services on the enterprise server by entering the following commands:

cd $SYSTEM/bin32 ./EndOneWorld.sh ./rmics.sh

4. Go to the B733x directory (where x is the cume number of the current release) and rename system directory to systembak using the following commands: cd /u01/jdedwardsoneworld/b733x (where u01 is the mount on which OneWorld is installed. This may be different on your system.)

mv system systembak

Do not delete the original system directory, in case you need the previous version.

5. Change to the temporary install directory, for example, cd /u01/jdedwardsoneworld/tmp. 6. Using file transfer protocol (FTP), move the system.Z file located on the deployment server under

JDEdwardsOneWorld\b733x\hosts\hp9000\system.Z to the temporary install directory on your enterprise server. A. Type ftp and your deployment server name, for example, ftp devs1.

B. Log on as user JDE with password JDE. The password is case-sensitive.

C. Enter the following commands: cd z:/JDEdwardsOneWorld/b733x/hosts/hp9000 binary get system.Z bye

7. From the temporary directory on the enterprise server, enter the following commands: chmod 777 system.Z (to alter permissions on the system.Z file) zcat system.Z | (cd /u01/jdedwardsoneworld/b733x;tar xvf -)

(where u01 is the mount point for the installation. This may be different for your system.)

8. Copy your old RunOneWorld.sh and EndOneWorld.sh to your new system/bin32 by entering the following commands:

cp /u01/jdedwardsoneworld/b733x/systembak/bin32/RunOneWorld.sh /u01/jdedwardsoneworld/b733x/system/bin32/RunOneWorld.sh

cp /u01/jdedwardsoneworld/b733x/systembak/bin32/EndOneWorld.sh /u01/jdedwardsoneworld/b733x/system/bin32/EndOneWorld.sh

(where u01 is the mount point for the installation. This may be different for your system.) 9. Go to the B733x directory and change permissions by entering the following commands:

cd /u01/jdedwardsoneworld/b733x/

(where u01 is the mount point for the installation. This may be different for your system.) chmod 555 system/lib/* system/libv32/*

10. Follow the steps below to modify the RunOneWorld.sh and EndOneWorld.sh scripts to conform to your site. A. Using vi or another editor, open the RunOneWorld.sh script and locate the VARIABLE

DEFINITIONS section. Change the values for OWUSR, OWPWD, OWENV, OWQUE1, and OWQUE2 to match the user name, password, environment, and batch queue names you are using (as defined in the JDE.INI file).

Note that the scripts include detailed comments describing script function and the command line arguments that each script accepts. Read the Notes section of the script for specific instructions to set the variables listed above.

The following example shows the VARIABLE DEFINITIONS section of the RunOneWorld.sh script, including the variables you must edit.

RunOneWorld.sh VARIABLE DEFINITIONS section # VARIABLE DEFINITIONS LOGFILE=”$SYSTEM/bin32/startstop.log” ## Set START_NEW_LOGFILE=1 if you rewrite the logfile ## at each startup START_NEW_LOGFILE=0 OWUSR=”JDE” OWPWD=”JDE” OWENV=”PD7333” OWQUE1=”QB733” OWQUE2=”QB733” ## Set MULTI_INSTANCE=1 if you are running multiple ## instances of OneWorld under the same UNIX user ID. MULTI_INSTANCE=0

The RunOneWorld.sh script is set to run one spec install queue, one package queue, and two batch queues. See “Installing the Enterprise Server” in the OneWorld Installation Guide for information about changing these settings.

B. Make the same changes to the EndOneWorld.sh script. This script is nearly identical to the RunOneWorld.sh script.

11. Start Network Services by running the following commands: cd $SYSTEM/bin32

./RunOneWorld.sh 12. Successfully complete a porttest.

RS/6000 Server Installation

Before beginning the installation on the RS/6000 Server, perform the following step if using a Download Service Pack.

For Download:

• Before installation on the RS/6000, download the service pack for RS/6000 host installation to your deployment server. If your deployment server is directly connected to the Internet, choose “Run this program from its current location.” Otherwise, select “Save this program to disk,” copy the .exe file(s) to the deployment server, and run the executables from there. It is recommended that you copy the executables to the Windows temp directory (do not save the executable to the JDE directory structure).

• The download creates a file named system.Z in the \hosts\rs6000 directory on the deployment server. If there is already a read-only system.Z file on the Windows server, the Service Pack will not install correctly. To avoid this problem, move the system.Z files to a backup temp directory prior to installing the Service Pack.

The following instructions explain how to replace the system directory and its subdirectories on the RS/6000 installing from either CD or Download:

1. Log on to the enterprise server as your B733x administrative user, for example, jdeb733.

2. If installing Service Pack from CD, perform the following step: For CD: • Copy the system.Z file from the service pack CD \hosts\rs6000 directory to the deployment server

z:\JDEdwardsOneWorld\b733x\hosts\rs6000 directory, where z: is the drive on which OneWorld is located. If there is already a read-only system.Z file on the Windows server, the Service Pack will not install correctly. To avoid this problem, move the system.Z files to a backup temp directory prior to installing the Service Pack.

3. On the enterprise server, create the following temporary directory, or verify its existence in the following

path: /u01/jdedwardsoneworld/tmp (where u01 is the mount point for the installation. This may be different for your system.)

4. End Network Services on the enterprise server by entering the following commands: cd $SYSTEM/bin32 ./EndOneWorld.sh ./rmics.sh

5. Go to the B733x directory (where x is the cume number of the current release) and rename system

directory to systembak using the following commands: cd /u01/jdedwardsoneworld/b733x (where u01 is the mount on which OneWorld is installed. This may be different on your system.)

mv system systembak

6. Change to the temporary install directory, for example, cd /u01/jdedwardsoneworld/tmp.

7. Using the file transfer protocol (FTP), move the system.Z file located on the deployment server under JDEdwardsOneWorld\b733x\hosts\rs6000\system.Z to the temporary install directory on your enterprise server.

A. Type ftp and your deployment server name, for example, ftp devs1.

C. Enter the following commands: cd z:/JDEdwardsOneWorld/B733x/hosts/rs6000 binary get system.Z bye

8. Go to the tmp directory (/u01/jdedwardsoneworld/tmp) and enter the following commands:

chmod 777 system.Z (to alter permissions on the system.Z file)

zcat system.Z | (cd /u01/jdedwardsoneworld/b733x;tar xvf -)

9. Go to the B733x directory and change permission by entering the following commands:

cd /u01/jdedwardsoneworld/b733x

chmod 755 system/lib/* system/libv32/*

10. Copy your old RunOneWorld.sh and EndOneWorld.sh to your new system/bin32 by entering the following commands: cp /u01/jdedwardsoneworld/b733x/systembak/bin32/RunOneWorld.sh /u01/jdedwardsoneworld/b733x/system/bin32/RunOneWorld.sh

11. Rebuild the business functions (B73.3.2 only). (If you are installing this service pack on OneWorld version B73.3.2, you must complete the following instructions to rebuild business functions on the RS/6000 enterprise server.)

A. On the enterprise server, open the JDE.INI file.

B. Replace the [BSFN BUILD] section of the JDE.INI with the following: [BSFN BUILD] BuildArea=/u01/jdedwardsoneworld/b733x/packages OptimizationFlags=-O2 DebugFlags=-g -qfullpath -qdbextra -D_DEBUG -DJDEDEBUG InliningFlags= DefineFlags=-DKERNEL -DPRODUCTION_VERSION -DNATURAL_ALIGNMENT CompilerFlags=-qalign=natural -qflag=I:I -c OSReleaseLevel= LinkFlags=-bI:/u01/jdedwardsoneworld/tmp/system/bin32/funclist.imp -bM:SRE -bexpall -brtl -lc -lm -bnoentry -L. -L/u01/jdedwardsoneworld/tmp/system/lib -ljdelib -lcallobj -lerror -lgentext -ljdb -ljde_erk -ljdecache -ljdeddapi -ljdeknet -ljderepl -ljdeschr -ljdesec -ljdespec -ljdetam -llanguage -lmisc -lpackage -

lport -lqueueknl -lrdbapi -lruntime -lsrc -ltransmon -lube -lworkflow -ljdesaw -ljdenet -lowver -bloadmap:loadmap LinkLibraries= SimultaneousBuilds=5

C. Replace "b733x" in the above with the path to the current packages directory.

D. Save the JDE.INI file.

E. On a OneWorld client machine, set up and deploy the server package to the enterprise server.

This package recompiles and re-links the business functions with the new flags.

12. Go to the B733x directory and change permissions by entering the following commands: cd /u01/jdedwardsoneworld/b733x/

13. Follow the steps below to modify the RunOneWorld.sh and EndOneWorld.sh scripts to conform to your site. A. Using vi or another editor, open the RunOneWorld.sh script and locate the VARIABLE

DEFINITIONS section. Change the values for OWUSR, OWPWD, OWENV, OWQUE1, and OWQUE2 to match the user name, password, environment, and batch queue names you are using (as defined in the JDE.INI file).

RunOneWorld.sh VARIABLE DEFINITIONS section # VARIABLE DEFINITIONS LOGFILE=”$SYSTEM/bin32/startstop.log” ## Set START_NEW_LOGFILE=1 if you rewrite the logfile ## at each startup START_NEW_LOGFILE=0 OWUSR=”JDE” OWPWD=”JDE” OWENV=”PD7333” OWQUE1=”QB733” OWQUE2=”QB733” ## Set MULTI_INSTANCE=1 if you are running multiple ## instances of OneWorld under the same UNIX user ID. MULTI_INSTANCE=0

The RunOneWorld.sh script is set to run one spec install queue, one package queue, and two batch queues. See “Installing the Enterprise Server” in the OneWorld Installation Guide for information about changing these settings.

14. Verify that the JDE.INI file contains the following settings: [JDENET_KERNEL_DEF2] dispatchDLLName=libjdeknet.so [JDENET_KERNEL_DEF3] dispatchDLLName=libjderepl.so

[JDENET_KERNEL_DEF4] dispatchDLLName=libjdeknet.so [JDENET_KERNEL_DEF5] dispatchDLLName=libtransmon.so [JDENET_KERNEL_DEF6] dispatchDLLName=libjdeknet.so [JDENET_KERNEL_DEF7] dispatchDLLName=libjdeknet.so [JDENET_KERNEL_DEF8] dispatchDLLName=libjdeknet.so [JDENET_KERNEL_DEF10] dispatchDLLName=libjdeschr.so [JDENET_KERNEL_DEF11] dispatchDLLName=libjdeknet.so [JDENET_KERNEL_DEF12] dispatchDLLName=libjdeknet.so [BSFN BUILD] LinkFlags=-bI:/u01/jdedwardsoneworld/b733x/system/bin32/funclist.imp -bM:SRE -bexpall -brtl -lc -lm -bnoentry -L. -L/u01/jdedwardsoneworld/b733x/system/lib -ljdelib -lcallobj -lerror -lgentext -ljdb -ljde_erk -ljdecache -ljdeddapi -ljdeknet -ljderepl -ljdeschr -ljdesec -ljdespec -ljdetam -llanguage -lmisc -lpackage -lport -lqueueknl -lrdbapi -lruntime -lsrc -ltransmon -lube -lworkflow -ljdesaw -ljdenet -lowver -bloadmap:loadmap

15. Start Network Services by running the following commands cd $SYSTEM/bin32

./RunOneWorld.sh

16. Successfully complete a porttest.

Sun Server Installation

Before beginning the installation on the Sun Server, perform the following step if using a Download Service Pack.

For Download:

• Before installation on the Sun server, download the service pack for Sun host installation to your deployment server. If your deployment server is directly connected to the Internet, choose “Run this program from its current location.” Otherwise, select “Save this program to disk,” copy the .exe file(s) to the deployment server, and run the executables from there. It is recommended that you copy the executables to the Windows temp directory (do not save the executable to the JDE directory structure).

• The download creates a file named system.Z in the \hosts\sun directory on the deployment server. If there is already a read-only system.Z file on the Windows server, the Service Pack will not install correctly. To avoid this problem, move the system.Z files to a backup temp directory prior to installing the Service Pack.

The following instructions explain how to replace the system directory and its subdirectories on the Sun Server installing from either CD or Download:

1. If installing Service Pack from CD, perform the following step:

For CD:

• Copy the system.Z file from the service pack (SP) CD \hosts\sun directory to the deployment server z:\JDEdwardsOneWorld\b733x\hosts\sun directory, where z: is the drive on which OneWorld is located. If there is already a read-only system.Z file on the Windows server, the Service Pack will not install correctly. To avoid this problem, move the system.Z files to a backup temp directory prior to installing the Service Pack.

2. Log on to the enterprise server as your B733x administrative user, for example, jdeb7333.

# This user must be the same one who created the jdedwardsoneworld/tmp directory.

3. On the enterprise server, create the following temporary directory, or verify its existence in the following path: /u01/jdedwardsoneworld/tmp (where u01 is the mount point for the installation. This may be different for your system.)

4. End Network Services on the enterprise server by entering the following commands: cd $SYSTEM/bin32 ./EndOneWorld.sh ./rmics.sh

5. Go to the B733x directory (x is the cume number of the current release) and rename system directory to systembak using the following commands: cd /u01/jdedwardsoneworld/b733x/

(where u01 is the mount point for the installation. This may be different for your system.) mv system systembak

6. Change to the temporary install directory, for example, cd /u01/jdedwardsoneworld/tmp.

7. Using the file transfer protocol (FTP), move the system.Z file located on the deployment server under JDEdwardsOneWorld\b733x\hosts\sun\system.Z to the temporary install directory on your enterprise server.

A. Type ftp and your deployment server name, for example, ftp devs1.

C. Enter the following commands: cd z:/JDEdwardsOneWorld/B733x/hosts/sun binary get system.Z bye

8. From the temporary directory on the enterprise server, enter the following commands:

chmod 777 system.Z (to alter permissions on the system.Z file.) zcat system.Z | (cd /u01/jdedwardsoneworld/b733x;tar xvf -)

9. Copy your old RunOneWorld.sh and EndOneWorld.sh to your new system/bin32 by entering the following commands: cp /u01/jdedwardsoneworld/b733x/systembak/bin32/RunOneWorld.sh /u01/jdedwardsoneworld/b733x/system/bin32/RunOneWorld.sh

10. Go to the B733x directory and change permissions by entering the following commands: cd /u01/jdedwardsoneworld/b733x/

11. Follow the steps below to modify the RunOneWorld.sh and EndOneWorld.sh scripts to conform to your site.

A. Using vi or another editor, open the RunOneWorld.sh script and locate the VARIABLE DEFINITIONS section. Change the values for OWUSR, OWPWD, OWENV, OWQUE1, and OWQUE2 to match the user name, password, environment, and batch queue names you are using (as defined in the JDE.INI file).

RunOneWorld.sh VARIABLE DEFINITIONS section # VARIABLE DEFINITIONS LOGFILE=”$SYSTEM/bin32/startstop.log” ## Set START_NEW_LOGFILE=1 if you rewrite the logfile ## at each startup START_NEW_LOGFILE=0 OWUSR=”JDE” OWPWD=”JDE” OWENV=”PD7333” OWQUE1=”QB733”

OWQUE2=”QB733” ## Set MULTI_INSTANCE=1 if you are running multiple ## instances of OneWorld under the same UNIX user ID. MULTI_INSTANCE=0

The RunOneWorld.sh script is set to run one spec install queue, one package queue, and two batch queues. See “Installing the Enterprise Server” in the OneWorld Installation Guide for information to change these settings.

12. Start Network Services by running the following commands cd $SYSTEM/bin32

./RunOneWorld.sh

Windows 2000 and Windows 2003 (Intel) Server Installation

Complete the following task to install the service pack on a Windows 2000 or Windows 2003 enterprise server.

Install the Service Pack

Before beginning the installation on the Windows Server, perform the following step if using a Download Service Pack.

For Download:

• Before installation on the Windows 2000 or Windows 2003 server, download the appropriate service pack for host installation to your deployment server. If your deployment server is directly connected to the Internet, choose “Run this program from its current location.” Otherwise, select “Save this program to disk,” copy the .exe file to the deployment server, and run the executable from there. It is recommended that you copy the executable to the Windows temp directory (do not save the executable to the JDE directory structure).

• The download replaces any changed system files in the \host\IntelNT directory on the deployment server, adds any new system files to the \hosts\IntelNT directory on the deployment server, and copies installation instructions into the \documentation directory on the deployment server.

The following instructions explain how to replace the system directory and its subdirectories on the Windows 2000 and Windows 2003 servers from installing from CD or Download:

1. End Services for JDE B733x Queue followed by JDE B733x Network on the enterprise server:

A. From the Control Panel, choose Services. B. Choose JDE B733x Queue Services, and then Stop. C. Choose JDE B733x Network Services, and then Stop.

2. Make a backup copy of the enterprise server’s System directory.

# Do not delete the original system directory, in case you need the original version.

3. If installing Service Pack from CD, perform the following step:

For CD:

• From the \hosts directory, on the service pack CD, copy the \System directory for the appropriate platform to your z:\JDEdwardsOneWorld\ddp\b733x\ on the enterprise server, where z: is the drive on which OneWorld resides, and x is the cume number of your OneWorld release.

4. Copy the System folder from the \hosts\IntelNT directory on the deployment server to the enterprise server.

5. Change the attributes of each file and directory from Read Only to full permission by entering the following commands in a DOS command window: z: cd z:\JDEdwardsOneWorld\ddp\b733x\system attrib –R /S *.*

6. Copy the Resource folder from your backup system directory to your new system directory.

7. Copy the JDE.INI file from your backup system\bin32 directory to your new system\bin32 directory.

8. Start Services for JDE B733x Network then JDE B733x Queue on the enterprise server:

A. From the Control Panel, choose Services. B. Choose JDE B733x Network Services, and then Start. C. Choose JDE B733x Queue Services, and then Start.

Creating Your Client Update Package

This process will deploy changes from the service pack to your client workstations. If this service pack has an enterprise server download, you must first upgrade the enterprise servers before you upgrade the workstations. If the enterprise servers are not upgraded first, they may not be able to properly receive and process requests from workstations that are upgraded.

# The package build and assembly process includes many critical tasks that must be successfully completed to correctly install packages. See OneWorld Package Management Guide for details on building, assembling, and deploying packages. This guide lists most of these tasks and gives step-by-step instructions for completing them. Before you build a package, review these tasks to ensure you complete all the required steps.

Create a client update package following the instructions below. For more details on the process, refer to “Assembling Packages” in the OneWorld Package Management Guide.

1. On the Foundation Component screen, click Default for the foundation path.

2. Click Next repeatedly to navigate through the remaining Package Assembly screens.

# Include only Foundation in the package. Do not include Helps, Objects, or Database.

3. After completing the Package Assembly, click Activate, and then click Define Build.

4. Select Compress Foundation.

5. After completing the Package Build Definition, click Activate and then Submit Build.

6. Deploy this package to all OneWorld workstations.

You have now completed the installation of the service pack. See Before You Begin on page 2 to determine which of the following peripheral tasks apply to your system.

APS Real-time Events Settings for JDE.INI (optional)

Clients can activate APS (Advanced Planning Solutions) integration through OneWorld by adding APS event generation settings to the JDE.INI file on the enterprise server. To enable this integration:

• Configure events within JDE.INI by registering them and including associated data structures.

• Set event filtering to enable events.

# Before enabling APS integration, verify that the JDE.INI file contains the following settings:

[JDENET]

maxKernelRanges=20

[JDENET_KERNEL_DEF19]

krnlName=EVN KERNEL dispatchDLLName=jdeie.dll dispatchDLLFunction=_JDEK_DispatchITMessage@28 maxNumberOfProcesses=1 numberOfAutoStartProcesses=1

[JDENET_KERNEL_DEF20]

krnlName=IEO KERNEL dispatchDLLName=jdeieo.dll dispatchDLLFunction=_JDEK_DispatchIEOMessage@28 maxNumberOfProcesses=1 numberOfAutoStartProcesses=1

[JDEITDRV]

DrvCount=3 Drv1=RT:rtdrv.dll Drv2=Z:zdrv.dll Drv3=JDENET:jdetrdrv.dll

For APS integration, the EventType must be registered in the JDE.INI file on the server under the [INTEROPERABILITY] section in the RegisteredEvents key. The key contains comma-separated values, as shown in this example:

[INTEROPERABILITY]

RegisteredEvents=RTSOOUT,RTPOOUT,RTWOOUT

The data structures used by the particular event must be registered in the JDE.INI file on the server under the [EventType] section as keys, as shown in this example:

[RTSOOUT]

DS1=D4202150B DS2=D4202150C DS3=D34A1050C

To enable full XPI APS integration, specify the following aggregate events in the JDE.INI file:

[INTEROPERABILITY]

FilteredEvents=*ALL RegisteredEvents=RTSOOUT,RTPOOUT,RTWOOUT,RTIBOUT

[RTSOOUT]

DS1=D4202150B DS2=D4202150C DS3=D34A1050C

[RTPOOUT]

DS1=D4302150B DS2=D4302150C DS3=D34A1050E

[RTWOOUT]

DS1=D3102290B DS2=D34A1050D

[RTIBOUT]

DS1=D4101440B DS2=D34A1050F

Type FilteredEvents=*ALL to generate all registered events. Type FilteredEvents=*NONE to disable APS event generation. Activate selected events by typing FilteredEvents=SETTINGNAME, with multiple settings separated by commas. See the following table for individual events and descriptions.

The table below lists the settings for all events currently operative, including APS-specific events. Clients can decide which events they want to generate.

Event generation name Data structure names Event description

[RTSOOUT] DS1=D4202150B DS2=D4202150C DS3=D34A1050C

Aggregate event for Sales Order Outbound.

[RTSOHDR] DS1=D4202150B Single event for Sales Order Header Outbound.

[RTSODTL] DS1=D4202150C Single event for Sales Order Detail Outbound.

[RTSOAPS] DS1=D34A1050C Single event for Sales Order APS Outbound.

[RTPOOUT] DS1=D4302150B DS2=D4302150C DS3=D34A1050E

Aggregate event for Purchase Order Outbound.

[RTPOHDR] DS1=D4302150B Single event for Purchase Order Header Outbound.

[RTPODTL] DS1=D4302150C Single event for Purchase Order Detail Outbound.

[RTPOAPS] DS1=D34A1050E Single event for Purchase Order APS Outbound.

Event generation name Data structure names Event description

[RTIBOUT] DS1=D4101440B DS2=D34A1050F

Aggregate event for Inventory Outbound.

[RTIBDTL] DS1=D4101440B Single event for Inventory Outbound.

[RTIBAPS] DS1=D34A1050F Single event for Inventory APS Outbound.

[RTWOOUT] DS1=D3102290B DS2=D34A1050D

Aggregate event for Work Order Outbound.

[RTWOHDR] DS1=D3102290B Single event for Work Order Header Outbound.

[RTWOAPS] DS1=D34A1050D Single event for Work Order APS Outbound.

Defining Application Shortcut Types for External Messages With the software messaging system, software users can send e-mail messages to users of external messaging systems, such as Microsoft Outlook or Lotus Notes. External messages can include shortcuts to applications. Since software supports Windows and Web clients, the external message can contain a shortcut for a Windows application or a Web application.

Modify the JDEMAIL section of the jde.ini file to specify application shortcuts as the shortcut type for external messages. If a user is sending shortcuts from a fat client, modify the jde.ini file on the client workstation. If a user is sending shortcuts from a thin client through a function executed on the server, modify the jde.ini file on the enterprise server. The jde.ini file should be modified in both locations.

For Windows as the application shortcut type, modify the jde.ini file as follows:

[JDEMAIL]

Setting Value Purpose

ClientType= or ShortcutType=

• Windows Windows. The external e-mail message contains a Windows application shortcut. Windows is the default value for the setting.

For Web as the application shortcut type, modify the jde.ini file as follows:

[JDEMAIL]

ClientType= or ShortcutType=

• ActiveX • URL

Active X. The external e-mail message contains a Launch Application attachment that opens a Web application in a new session of the Web Client in Microsoft Internet Explorer.

URL. The external e-mail message contains a URL for a Web application shortcut.

Note: The ActiveX shortcut does not work with the Netscape browser. However, it is the preferred shortcut type for Web client users using Internet Explorer because it avoids potential conflicts between the application that is currently running and the application being launched.

[JAS PREFERENCE]

JasServer= Web server name

Port= Port number

Servlet If you are using the Portal: /jde/servlet/com.jdedwards.portal.PortalBuilderServlet

If you are not using the Portal: /jde/servlet/com.jdedwards.runtime.virtual.VCServlet

Default Login • Redirector • Standard

Use Redirector if the JAS server is a redirector Web server.

Use Standard if the JAS server is a PeopleSoft ERP Web server.

Protocol • http • https

Use http if you are using the http protocol.

Use https if you are using the https protocol.

Database Password Encryption for Multiple Foundation Environments The algorithm used to encrypt and decrypt OneWorld passwords has been compromised and has been posted to web. This enhancement will address the vulnerability that exists when storing passwords in the database and the associated installation/migration issues. The solution will update the passwords stored in the database to a higher encryption standard.

This document is intended for an administrator who is going to apply the Service Pack & ESU at the customer site. It is assumed that the reader has knowledge of OneWorld and CNC technology.

More details can be found in the PeopleSoft Security Vulnerability Report under “PeopleSoft EnterpriseOne Password Encryption Vulnerability” (Security Vulnerability ID: 2004011901)..

Configuration

Once the Service Pack is installed on the enterprise servers, security kernel will be storing passwords in the security tables using the new encryption. There is no configuration to disable usage of new encryption.

Pre-Installation Process

Before starting the pre-installation process, make sure you have created a backup copy of F98OWSEC table as identified in the ESU download.

To handle multiple foundations running different Service Packs, we recommend use of two data sources for security tables,

1. Existing data source (such as current system data source) to point Enterprise Servers running Service Packs older than SP22_P1.

2. For SP22_P1 or newer a second copy of the F98OWSEC will reside in your Server Map Data Source, such as SERVERNAME – B733x Server Map.

Note: If you are not using multiple foundations, your existing data source is sufficient.

Setting these data sources will help avoid any data conflict due to overlap between new and old Enterprise Servers.

Following steps are required before installing the Service Pack and/or ESU:

1. Login to the Deployment Server into the DEP733x environment.

2. Go to OMW and perform a copy table of the F98OWSEC table to the existing Server Map Data Source such as SERVERNAME – B733x Server Map where your security kernel is running.

3. Go to OMW and perform a copy table of the F9312 table to the existing Server Map Data Source such as SERVERNAME – B733X Server Map where your security kernel is running.

Note: Purpose of this copy table process to your server map is to create a secondary location that can support the new encryption

OneWorld B73.3x Service Pack 23 Installation Instructions PeopleBook

Documents

OneWorld Xe ESU Update Proceduresspla.sh/documents/OneWorld....

OneWorld Wat is OneWorld? Gebruik van data bij OneWorld...

PeopleSoft Enterprise HRMS Portal Pack 9.1...

Oneworld Accuracy User Guide · 2014. 3. 14. · ONEWORLD.....

Spring 2008 OneWorld Washu

EnterpriseOne Xe Administración de datos del producto...

Freedom TB - OneWorld

ONEWORLD. ONECOMPANY. ONETEAM. - AnnualReports.com

S7 Airlines & oneworld

Data Sheet NetSuite OneWorld€¦ · NetSuite OneWorld is.....

EnterpriseOne Xe Accounts Payable PeopleBook Payable...

PeopleSoft 8.8 HRMS Portal Pack PeopleBook - Oracle · The....

OneWorld #7

Citizenship by investment-Oneworld

EnterpriseOne JDE5 Advanced Cost Accounting PeopleBook ·.....

oneworld timetable Valid: August 29, 2008 - AirTimes ·...