JD Edwards EnterpriseOne Tools 24.0.0 for Xe/8.0 Net Changes

May 2009

1

JD Edwards EnterpriseOne Tools 24.0.0 for Xe/8.0 Net Changes

Copyright Notice

Copyright © 2009, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Subject to patent protection under one or more of the following U.S. patents: 5,781,908; 5,828,376; 5,950,010; 5,960,204; 5,987,497; 5,995,972; and 6,223,345. Other patents pending.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS

Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are “commercial computer software” or “commercial technical data” pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

Hazardous Applications Notice

This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

Third Party Content, Products, and Services Disclaimer

This software and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content, products and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third party content, products or services.

Contains GNU libgmp library; Copyright © 1991 Free Software Foundation, Inc. This library is free software which can be modified and redistributed under the terms of the GNU Library General Public License.

Includes Adobe® PDF Library, Copyright 1993-2001 Adobe Systems, Inc. and DL Interface, Copyright 1999-2008 Datalogics Inc. All rights reserved. Adobe® is a trademark of Adobe Systems Incorporated.

2

3

Portions of this program contain information proprietary to Microsoft Corporation. Copyright 1985-1999 Microsoft Corporation.

Portions of this program contain information proprietary to Tenberry Software, Inc. Copyright 1992-1995 Tenberry Software, Inc.

Portions of this program contain information proprietary to Premia Corporation. Copyright 1993 Premia Corporation.

This product includes code licensed from RSA Data Security. All rights reserved.

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).

This product includes software written by Tim Hudson (tjh@cryptsoft.com). All rights reserved.

This product includes the Sentry Spelling-Checker Engine, Copyright 1993 Wintertree Software Inc. All rights reserved.

Open Source Disclosure

Oracle 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. The following open source software may be used in Oracle's JD Edwards EnterpriseOne products and the following disclaimers are provided.

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.

Table of Contents

CHAPTER 1: ABOUT THIS DOCUMENT .............................................................................................................5 CHAPTER 2: NAMING CONVENTIONS...............................................................................................................6 CHAPTER 3: VISUAL STUDIO 2005 COMPILER SETTINGS ..........................................................................7

DEPLOYMENT SERVER AND WINDOWS CLIENT SETUP REQUIREMENTS ....................................................................7 ENTERPRISE SERVER SETUP REQUIREMENTS.............................................................................................................8 ENVIRONMENT VARIABLE SETUP REQUIREMENTS ....................................................................................................8

CHAPTER 4: WINDOWS VISTA CLIENT ADOPTION ....................................................................................10 DEFAULT INSTALLATION LOCATION .......................................................................................................................10 SYMBOLIC LINKS.....................................................................................................................................................11 NEW DATA DIRECTORY...........................................................................................................................................12 CONFIGURATION......................................................................................................................................................12 SIGN-ON PACKAGE INSTALLATION .........................................................................................................................16 PUSH INSTALLER .....................................................................................................................................................17 WINDOWS CLIENT ...................................................................................................................................................19

Solution Explorer and OneWorldExplorer.........................................................................................................19 Design Tools ......................................................................................................................................................19 TypeAhead Feature ............................................................................................................................................20

MISCELLANEOUS UTILITY .......................................................................................................................................20 CHAPTER 5: REBRANDING .................................................................................................................................22

INSTALLER...............................................................................................................................................................22 WINDOWS CLIENT ...................................................................................................................................................23 WEB CLIENT............................................................................................................................................................25 JD EDWARDS ENTERPRISEONE PORTAL ..................................................................................................................27 COLLABORATIVE PORTAL .......................................................................................................................................28

CHAPTER 6: CONFIGURATION OF WEBSPHERE PORTAL .......................................................................29 COLLABORATIVE PORTAL 6.0.1.1 INSTALLATION....................................................................................................29

4

Chapter 1: About this Document

The Oracle JD Edwards EnterpriseOne Tools 24.0.0 for Xe/8.0 Net Changes document discusses the changes that are introduced in JD Edwards EnterpriseOne Tools 24.0.0 release for Xe/8.0.

The chapters within this guide provide information about:

• The compiler settings required for Visual Studio 2005. Discusses the setup requirements for the deployment server, windows client, and enterprise server.

• The adoption of Windows Vista Client for the standard user. Discusses enhancements and the configuration changes for enabling the Windows Vista standard users to run EnterpriseOne without administrator authority.

• The rebranding of the installer, clients, and the portal Windows. Discusses the changes to the user interface of the windows client, web client, and the client installer. This includes the re-branding of JD Edwards OneWorld Xe/8.0 web client, windows client, OneWorld Portal, Collaborative Portal, Client Installer, and Standalone Installer from JD Edwards/PeopleSoft to Oracle.

• The changes to installation and configuration of WebsSphere and Collaborative portals.

5

Chapter 2: Naming Conventions

The product versioning and naming conventions followed for the JD Edwards EnterpriseOne Tools 24.0.0 release for Xe/8.0 stick to the industry standards. The versioning is done as:

The major releases are planned usually with major application releases and the tools updates occur 2 or 3 times per year. These tools updates undergo a full testing cycle. A few of the examples of JD Edwards EnterpriseOne Tools 24.0.0 versioning are:

• Major release: 24.0.0

• First maintenance pack: 24.0.1

• First tools release update: 24.1.0

• First maintenance pack to 24.1.0: 24.1.1

• Second tools release update: 24.2.0

6

Chapter 3: Visual Studio 2005 Compiler Settings

Visual Studio 2005 (Visual C++ 8.0) support has been provided for the 24.0.0 tools release of JD Edwards EnterpriseOne Xe/8.0. However, Visual Studio 2005 is optional for 24.0.0. VC6 is also supported. This chapter discusses the basic setup requirements for the following, to use Visual C++ 8.0 as the compiler:

• Deployment Server and Windows Client

• Enterprise Server

Deployment Server and Windows Client Setup Requirements

1. Install Visual Studio 2005.

2. Ensure that jde.ini has the following entries under JDE_CG section: Key Name Value STDLIBDIR <Visual Studio 2005 Installation Path>\ VC\lib

INCLUDES <Visual Studio 2005 Installation Path>\VC\include; <Visual Studio 2005 Installation Path>\VC\atlmfc\Include; <Visual Studio 2005 Installation Path>\VC\PlatformSDK\Include;$(SYSTEM)\include;$(APP)\include;$(SYSTEM)\includev

LIBS <Visual Studio 2005 Installation Path>\VC\ PlatformSDK \Lib; <Visual Studio 2005 Installation Path>\VC\atlmfc\lib; <Visual Studio 2005 Installation Path>\VC\lib;$(SYSTEM)\lib32;$(APP)\lib32;$(SYSTEM)\libv32

VisualStudioVersion 8

3. Ensure that the path and environment variable are pointing to Visual Studio 2005. For more information on environment variables, see Environment Variable Setup Requirements.

The above deployment server setup requirements also apply for the windows client.

7

Enterprise Server Setup Requirements 1. Install Visual Studio 2005.

2. Ensure that jde.ini has the following entries under JDE_CG section: Key Name Value TARGET RELEASE

STDLIBDIR <Visual Studio 2005 Installation Path>\VC\lib

INCLUDES <Visual Studio 2005 Installation Path>\VC\include; <Visual Studio 2005 Installation Path>\VC\atlmfc\Include; <Visual Studio 2005 Installation Path> \VC\PlatformSDK\Include;$(SYSTEM)\include;$(SYSTEM)\cg;$(APP)\include;$(SYSTEM)\includev

LIBS <Visual Studio 2005 Installation Path>\VC\lib; <Visual Studio 2005 Installation Path>\VC\PlatformSDK\Lib;$(SYSTEM)\lib32;$(APP)\lib32;$(SYSTEM)\libv32

VisualStudioVersion 8

MAKEDIR <Visual Studio 2005 Installation Path>\VC\bin

3. Ensure that the path and environment variable are pointing to Visual Studio 2005. For more information on environment variables, see Environment Variable Setup Requirements.

Environment Variable Setup Requirements Set up the following environment variables for enterprise server, deployment server, and windows client:

Environment Variable Name

Value

PATH <Visual Studio 2005 Installation Path>\Common7\IDE;C:\Program Files\Microsoft Visual Studio 8\VC\BIN;C:\Program Files\Microsoft Visual Studio 8\Common7\Tools;C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\bin;C:\Program Files\Microsoft Visual Studio 8\VC\PlatformSDK\bin;C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\bin;C:\Windows\Microsoft.NET\Framework\v2.0.50727;C:\Program Files\Microsoft Visual Studio 8\VC\VCPackages;%PATH%

INCLUDE <Visual Studio 2005 Installation Path>\VC\ATLMFC\INCLUDE;C:\Program Files\Microsoft Visual Studio 8\VC\INCLUDE;C:\Program Files\Microsoft Visual Studio 8\VC\PlatformSDK\include;C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\include;%INCLUDE%

8

LIB <Visual Studio 2005 Installation Path>\VC\ATLMFC\LIB;C:\Program

Files\Microsoft Visual Studio 8\VC\LIB;C:\Program Files\Microsoft Visual Studio 8\VC\PlatformSDK\lib;C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\lib;%LIB%

LIBPATH C:\Windows\Microsoft.NET\Framework\v2.0.50727; <Visual Studio 2005 Installation Path>\VC\ATLMFC\LIB

DevEnvDir <Visual Studio 2005 Installation Path>\Common7\IDE

Note: The environment variable “DevEnvDir” is applicable only to Visual Studio 2005. For VC6, the corresponding environment variable name is “MSDevDir”.

Visual Studio 2005 is the lowest version of the compiler that is supported by Windows Vista and Windows 2008. For prior releases of Windows, such as XP and Windows 2003, it is possible to install both VS 2005 and VC 6. But, only one compiler can be used at a time to build the business function. You can switch between the two compilers by performing the following steps:

1) Update JDE_CG section and environment variables for VC++6 and VC++ 8.0. 2) Configure the jde.ini file for VC++6 and VC++ 8.0, in both the deployment and

enterprise servers. For more information, see PeopleSoft EnterpriseOne System Administration Guide, Understanding Workstation jde.ini Settings.

3) Set the value of VisualStudioVersion key either as 6 for VC++6 or 8 for VC++ 8.0 under the JDE_CG section of jde.ini based on the requirement.

It is necessary to use the same version of the compiler on both the client and server to build the business functions successfully.

9

Chapter 4: Windows Vista Client Adoption

The JD Edwards EnterpriseOne Xe/8.0 windows client applications can run on Vista operating system as Standard User with the 24.0.0 tools release. End users who perform the development activities need administrative privileges on Vista machines. The latest enhancements introduced in the 24.0.0 tools release facilitate the standard users to perform the following activities:

• Run the business applications.

• Access jde.ini and log files.

• Submit the EnterpriseOne batch applications and Table conversions.

• Access and install sign-on packages.

• Use Solution Explorer and OneWorld Explorer.

This chapter discusses:

• Default Installation Location

• Symbolic Links

• New Data Directory

• Configuration

• Sign-on Package Installation

• Push Installer

• Windows Client

• Miscellaneous Utility

Default Installation Location The user with administrative privileges can install JD Edwards EnterpriseOne Xe/8.0. The default installation location of EnterpriseOne Xe/8.0 is changed from C: \<Install Directory> to C:\Program Files\Jdedwards\<Install Directory>. The user can also install JD Edwards EnterpriseOne in C:\B7, apart from the default location.

The default installation location is not applicable for users installing the update or sign-on packages on EnterpriseOne Xe/8.0 windows client machines.

10

The following table lists the changes in the installation location with reference to the change in installation type:

Installation Type Installation Location New Installation of JD Edwards EnterpriseOne Xe/8.0 on Windows Vista machine.

By default, the user is prompted to install EnterpriseOne on C:\Program Files\jdedwards\B7. It is also possible to install it on C:\B7.

Installing Sign-on package on JD Edwards EnterpriseOne Xe/8.0 installed Windows Vista machine.

EnterpriseOne will remain installed on old location itself without moving to the new location. However, installer will create new folder named jdedata and do necessary modification on system to enable standard users to run EnterpriseOne on Vista.

New installation of EnterpriseOne Xe/8.0 on Windows XP machine.

By default the user will be prompted to install on C:\Program Files\jdedwards\B7. It is also possible for the user to install it on C:\B7.

Installing Sign-on package on EnterpriseOne Xe/8.0 installed Windows XP machine.

Installer installs the update package at the same location.

Symbolic Links In Windows Vista, the standard users are restricted from access to certain locations, such as C:\, C:\Program Files, and C:\Windows. EnterpriseOne has configuration files located in restricted locations. The installer creates symbolic link for such files to make it accessible for the standard users. The following table lists the symbolic links created during installation:

Symbolic Link Target File C:\Windows\jde.ini <EnterpriseOneInstallDir>\jdedata\jde.ini

C:\ jdeapp.ddp <EnterpriseOneInstallDir>\jdedata\ jdeapp.ddp

C:\ jdeapp.xdp <EnterpriseOneInstallDir>\jdedata\jdeapp.xdp

C:\ jdeauth.dda <EnterpriseOneInstallDir>\jdedata\jdeauth.dda

C:\ jdeauth.xda <EnterpriseOneInstallDir>\jdedata\jdeauth.xda

C:\ jdemod.ddm <EnterpriseOneInstallDir>\jdedata\jdemod.ddm

C:\ jdemod.xdm <EnterpriseOneInstallDir>\jdedata\ jdemod.xdm

C:\ jdesec.dds <EnterpriseOneInstallDir>\jdedata\ jdesec.dds

C:\ jdesec.xds <EnterpriseOneInstallDir>\jdedata\ jdesec.xds

C:\jdeinst.html C:\users\public\documents\jdeinst.html

C:\jdeinst.log C:\users\public\documents\jdeinst.log

C:\Windows\fonts\Adobefnt06.lst <EnterpriseOneinstalldir>\jdedata\Adobefnt06.lst

11

New Data Directory During the installation process, a new directory called “jdedata” is created within the EnterpriseOne Installation Directory, EnterpriseOne InstallDir. This new directory is used for storing configuration, licensing, and the log files.

Configuration The CNC administrator needs to make the following configuration changes to enable the standard user to run JD Edwards EnterpriseOne on Vista machines without administrative authority:

1. Create new security group

A new Windows security group named E1Group is created during the 24.0.0 windows client installation. This group has the necessary rights for running the EnterpriseOne Xe/8.0 applications. The administrator can add standard users into this group so that they can run the EnterpriseOne applications. Users who are members of the E1Group can run EnterpriseOne without administrative privileges. It is possible to add users, domain users, and domain groups to the E1Group. This is depicted in the following diagram:

The administrator has to list the user and group details under the E1GLOBALGROUP section of install.inf of deployment server. These users will be added as member of the E1Group during installation. The installer captures the user’s information from the E1GLOBALGROUP section of install.inf file of the deployment server.

An example of how the values are specified in the E1GLOBALGROUP section of install.inf file is given below:

[E1GlobalGroup]

E1Group1=<Domain>\Group1

E1Group2=<Domain>\Group2

12

Note: On the fresh installation of EnterpriseOne Xe/8.0, users will not be able to run EnterpriseOne without administrative privileges unless the administrator or the end user logs off and logs back into the system. After the Client Workstation setup for JD Edwards EnterpriseOne is completed, the system prompts the user to log off to complete the installation process, as shown here:

2. Download Windows Help Update patch

The Windows Help program (WinHlp32.exe) is used for displaying the EnterpriseOne help topics to the users. This program is not available with the Windows Vista operating system. As per Microsoft’s policy, the Windows Help Update patch cannot be distributed with JD Edwards EnterpriseOne. So, the administrator must download the Windows Help update patch and stored it in the ThirdParty folder on deployment server. The Windows Help Update patches for Windows Vista and Windows Server 2008 are different and have to be stored under different folder names, as shown below:

Operating System Folder Name Windows Vista ThirdParty\Client\<downloaded file>

Windows Server 2008 ThirdParty\Server\<downloaded file>

You can download the corresponding Windows Help Update patch for client and server from the following locations:

o Download details WinHlp32.exe for Windows Vista

o Download details WinHlp32.exe for Windows Server 2008

You can install Windows Help Update, which is stored in the ThirdParty folder during the installation of JD Edwards EnterpriseOne:

13

Microsoft delivers different versions of patch for 64 bit and 32 bit operating systems. The installer identifies whether the operating system is 32 bit or 64 bit and then runs the corresponding executable from ThirdParty\<Client/Server> folder.

If Windows Help Update patch is not installed and the user tries to open the EnterpriseOne help, then the following messages are displayed:

14

3. Enable E1Install Service

JD Edwards EnterpriseOne Xe/8.0 supports sign-on package installation. These packages are provided by the administrator for installing some mandatory patches into the client machine. A new install service named E1InstallService is introduced to support sign-on package installation by a standard user. The administrator must add the following entry under [File Locations] section of install.inf file on deployment server to enable installation of E1InstallService on Vista or later OS: OracleE1InstallService =<deployment server install path>\E1ServiceInstallation,Setup.exe,/s

The installer reads the E1InstallService entry from install.inf of deployment server to get the E1InstallService installer location.

15

Sign-On Package Installation The process of sign-on package installation has changed for Vista or later operating system (OS). InstallMonitor manages the installation of sign-on package for standard users. It detects the OS and then queries the status of service from the service manager. If the Windows service is running, then it reads the MandatoryInstallPort entry under the Install section of jde.ini and tries to connect with the service at the given port or default port of 8552. After establishing the connection, it sends the message for installing the required package. E1InstallService runs the setup and updates the InstallMonitor with setup progress and setup completion status.

This section discusses the updated installation process of sign-on packages of JD Edwards EnterpriseOne on Windows Vista:

1. As the installation process is initialized, the system waits for the EnterpriseOne application to exit and it displays the following message:

2. E1InstallService runs the setup with package information and updates the InstallMonitor with setup progress and setup completion statuses. The following message is displayed when the installation is in progress:

3. The user is notified about the success or failure of installation.

4. The Solution Explorer/OneWorld Explorer is launched after the successful installation of sign-on package.

16

Push Installer Push installation is the only deployment method that provides automatic and unattended package deployment. Through this, the system administrator can deploy packages to a workstation or group without requiring any action from workstation users. There are two types of push installation:

• Network installation

• Local installation

Vista supports only Network type push installation. Administrator can select the Network type push installation through the following window:

The installation location of Client Listener of the Push Installer is changed to make JD Edwards EnterpriseOne Xe/8.0 compatible on Windows Vista machines. The default location for the push install service is same as that of EnterpriseOne install location. That is, C:\Program Files\jdedwards. It is also possible to change the installation location of push install service, if required.

17

Only the end user with administrative privileges can run the Listener Monitor on Windows Vista. The Listener Monitor is used for setting up the parameters used for push installation. Administrators can initialize and run the Listener Monitor as given in the following windows:

18

Windows Client This section discusses the changes to the following:

• Solution Explorer and OneWorldExplorer

• Design Tools

• TypeAhead feature

Solution Explorer and OneWorldExplorer A standard user can run both the OneWorldExplorer and SolutionExplorer executables on Windows Vista. If a user, who is not a member of E1Group, tries to run the Solution Explorer or OneWorldExplorer without admin privileges, then the system prompts that user to elevate the process or exit. The system does not support a non-E1Group user to run the EnterpriseOne processes without elevation; and the same will be prompted:

Design Tools Only administrative users can run the design tool executables. If the Vista standard user tries to run the design tool executable, then the system prompts a message accordingly. The following window shows an example of the warning message that is displayed when the standard user tries to run Form Design without administrative privileges:

It is recommended that the design tool executable files be run by an end user with administrative privileges. However, the standard user, who is member of E1Group, can also run the Design Tool.

19

Trying to run the design tool executables by a standard user, who is not a part of E1Group, will result in prompting the user to elevate or quit the application through the following message:

TypeAhead Feature Prior to 24.0.0, the TypeAhead.tae file was always located under the Windows directory. This is a restricted location for standard user on Vista. The location of the file is changed from Windows directory to <EnterpriseOneInstallDir>\jdedata directory on the Vista operating system. The following table lists the location of TypeAhead.tae file for different operating systems:

Operating System Location Windows XP and Windows 2003 (Normal mode)

C:\Windows\TypeAhead.tae

Windows Vista <EnterpriseOneInstallDir>\jdedata\TypeAhead.tae

Windows 2003 (Terminal Server) and Windows 2008 (Terminal Server)

<UserProfileDir>\Windows\TypeAhead.tae

Miscellaneous Utility A few changes have been introduced to the SnapShot utility. The JD Edwards EnterpriseOne SnapShot application enables the administrator to install multiple versions of JD Edwards EnterpriseOne on a single workstation. With SnapShot, administrator can rename the installation directory and move executable files, security tables, jde.ini file, and registry settings to the renamed directory. After the administrator renames the installation directory, it is possible to install a new version of JD Edwards EnterpriseOne without overwriting the previous version. It is also possible to switch between the versions without performing any administrative tasks.

It is necessary to restore the SnapShot file to a true JD Edwards EnterpriseOne installation before you can run the software from that installation. You cannot begin an instance of JD Edwards EnterpriseOne from the SnapShot file.

Only an administrator can run Snapshot on Vista or higher operating system. If a standard user tries to run SnapShot, then EnterpriseOne prompts the user to elevate or quit.

20

The E1Groups are created during the installation on Vista. The Save feature of SnapShot renames the E1Group to E1Group_SnapshotName. On restoring the SnapShot, the E1Group_SnapshotName is renamed to E1Group.

21

Chapter 5: Rebranding

This chapter discusses the changes to the JD Edwards EnterpriseOne user interface for the Xe and 8.0 product releases. The changes include removing or replacing the corresponding company logo, copyright, and legal information from the user interfaces of:

• Installer

• Windows Client

• Web Client

• OneWorld Portal

• Collaborative Portal

Installer The installer window has been updated to include: the Oracle logo and updated legal information. An example of the installer window with the latest changes is displayed:

Client Workstation Setup Window

22

Windows Client The Windows client window includes the Oracle name, Oracle logo and updated legal information, and other updates. Examples of Windows client windows with the latest changes follow:

Login Window

23

JD Edwards Solution Explorer Window

24

Web Client The web client windows include the Oracle name, Oracle logo and updated legal information, and other updates. A few of the web client windows with the latest changes are displayed here as examples:

Login Window

25

Task Explorer Window

26

JD Edwards EnterpriseOne Portal The JD Edwards EnterpriseOne Portal includes the Oracle name and Oracle logo, and other updates. The JD Edwards EnterpriseOne Portal with the latest changes is displayed:

27

Collaborative Portal The Collaborative Portal includes the Oracle name, Oracle logo, and other updates. The Collaborative Portal with the latest changes is displayed:

28

29

Chapter 6: Configuration of WebSphere Portal

This chapter discusses the changes to the Collaborative Portal 6.0.1.1 Installation.

Collaborative Portal 6.0.1.1 Installation WebSphere Portal 6.0.1.4 supports JD Edwards EnterpriseOne Collaborative Portal on 24.0.0 release. This is accomplished through some configuration changes for the WebSphere Application Server (WAS) security:

The value of “com.ibm.SOAP.loginSource” is changed in the soap.client.props file. The Collaborative Portal installation fails if the soap.client.props file is not updated. You must locate “com.ibm.SOAP.loginSource” in the soap.client.props file and change “com.ibm.SOAP.loginSource=prompt” to “com.ibm.SOAP.loginSource=”.

WAS security configuration details are required for the successful installation of Collaborative Portal. Incomplete WAS security configuration prompts the user to enter user ID and password.