EDM for Sage X3 by V1 - Updating and Upgradingsupport.wearev1.com/software/x3/X3EDMHELP/files/EDM... · EDM for Sage X3 by V1 Updating and Upgrading EDM for Sage X3 by V1 Release

EDM for Sage X3 by V1 Updating and Upgrading EDM for Sage X3 by V1 Release 11.1 03 August 2015

2

Document Introduction

This document describes the installation steps required to update and upgrade the baseline

standard solution for the following:

� Upgrading licences for an existing system

� For example adding additional DbDeposit licences

� An update from Release 9 to Release 11.1

� For example updating a Release 9 EDM installation to Release 11.1 EDM

� Upgrading to add additional functionality

� For example upgrading a Release 9 EDM installation to add PIA. An

upgrade will require an update to be performed.

Any bespoke customer modifications beyond this standard installation will need to be

reinstated post update. Liaise with your Sage representative for more details.

Deviation from these steps can lead to unrecoverable issues and lengthy overruns for

the project.

3

An Update of R9, R10 or R10.1 to R11.1

An update of R9 to R11.1 adds no new software, but updates the currently installed

components to the latest version, for example:

� Sage X3 EDD Release 9 will be updated to EDD for Sage X3 by V1 Release 11.1

� OR

� Sage X3 EDM Release 10 will be updated to EDM for Sage X3 by V1 Release 11.1

� OR

� Sage X3 EDM with PIA Release 10.1 will be updated to PIA for Sage X3 by V1 Release 11.1

4

Step 1 – Preparation

THIS IS A CRITICAL STEP AND CANNOT BE IGNORED OR EXISTING SYSTEM

FUNCTIONALITY WILL BE COMPRIMISED.

THE CURRENT POOL ALIAS MUST BE RENAMED TO THE R11.1 NAMING

CONVENTION WHICH IS:

X3EDM<FOLDERNAME>

Assumptions:

� EDD / PIA / EDM components are in the c:\V1 directory

� You have knowledge of the current Sage X3 folder / Endpoint being used in

conjunction with EDD / EDM / PIA. For the purposes of these instructions, it will

be called PILOT.

� The current Pool Alias Name for PILOT is WSDEMOPRM

1. On the Sage Application Server, open the Safe x3 console

2. Click webservers

3. Click the web services button

4. Click the + next to the folder currently being used with EDD / EDM / PIA (in this

example, PILOT)

5. Click the blue cog and select the pool entry currently being used by EDD / EDM / PIA,

again in this example PILOT

6. In the pool.alias.def cell, double click in the cell and rename it to X3EDMPILOT (if not

already named that)

7. Click OK

8. Click apply at the top

9. Ensure a green tick is next to the pool alias to ensure it has started properly

10. Close the Safe X3 console

5

Step 2 – Core Software Update

Assumptions:


� You have knowledge of the current Sage X3 folder being used in conjunction with

EDD / EDM / PIA. For the purposes of these instructions, it will be called PILOT.

� The current Pool Alias Name for PILOT has been renamed and is now

X3EDMPILOT

� The R11.1 distribution has been downloaded to c:\R11.1INSTALLMEDIA

1. Run c:\R11.1INSTALLMEDIA\EDM for Sage X3 by V1- R11.1 - Installer.exe AS

ADMINISTRATOR

2. Click Next

3. Select Server Installation, click Next >

4. Select Update your system, click Next >

5. Browse to solution.xml if not displayed

6. Select PILOT folder from drop down

7. Confirm credentials of pool alias as configured in Step 1

8. Click Update

9. Close the R11.1 installer

6

Step 3 – Patching

Assumptions:




� The current Pool Alias Name for PILOT is now X3EDMPILOT


� The Core Software Update has been performed

� You have your new licences uncompressed and accessible to the Sage X3

application server

If patching to update a Sage X3 V6.5 system, consult the Installation Guide section 6.2 then

continue to Step 4.

If patching to update a Sage X3 V7 or PU8 system, consult the Installation Guide section 6.3

then continue to Step 4.

*NOTE: When updating some patches, you may experience a blue warning on completion

regarding certain components, this is normal and can be ignored.

**NOTE: The following patches:

XV1OC_0110001_19_160.dat

XV1OC_0110001_19_170.dat

XV1OC_0110001_19_180.dat

May generate an error:

Incorrect File Structure

Some patches that have not had enhancement / change since a previous release and are

reapplied cause X3 to fail validation. This is usually not serious and you are safe to continue

to patch as directed by the patch assistant.

7

Step 4 – Folder Configuration

Assumptions:




� The current Pool Alias Name for PILOT is now X3EDMPILOT


� The Core Software Update has been performed

� The relevant patches have been applied to the PILOT folder

1. Run c:\R11.1INSTALLMEDIA\EDM for Sage X3 by V1- R11.1 – Installer.exe AS

ADMINISTRATOR

2. Click Next


4. Select Sage X3 Folder Management, click Next >

5. Select the option to ‘Import Sage X3 Folder access permissions’, Click Next >

6. Click Import

7. Close the R11.1 installer

8. Open DbLogin Admin Console and log in as administrator, (you will be prompted to

do this assuming it is installed on the Application server) for each user displayed in

the grid present in each folder who wishes to use the system as applied in the Multi

Folder Manager, Click the blue/green icon at the top User Details. Perform these

actions:

a. Click Add…

b. Enter the Username as displayed in the Multi Folder Manager

c. Confirm the remaining credentials ensuring the email address is the same as

the Sage X3 workflow email address

d. Un-tick Must Change

e. Click Update

f. Close User Management screen

PIA Only

In addition to the above steps, one extra task is required:

9. In the grid of users, using the tick boxes, select all those users that use PIA Ensure to select at least the administrator user when selecting users

10. Click the keys icon at the top of the screen

11. Left click on DbCapture in the tree

12. On the right, alter ENG_DbCapture so it reads PILOT_ENG_DbCapture

13. Click Save

8

Step 5 – Client Software Update

Every client machine must update their clients to accommodate the server update; this

includes any clients that are on the server.

Assumptions:


� The Sage Application Server is called X3APPSERVER

� All previous steps have been completed in full


ADMINISTRATOR

2. Click Next

3. Select Client Installation, click Next >

4. Existing clients will be detected, click Next >

5. Enter X3APPSERVER (replace this with the actual name of the Application Server)

You can also enter the IP address

6. Click Check

The licences on the server will be analysed and those clients found which require updating displayed

7. Although a specific selection is possible, it is advised to update all those found.

8. Click Install

9

An Upgrade of R9, R10, R10.1 or R11.1 adding additional features Assumptions:

� The system has been fully updated

� All users who wish to use the system have been created in the DbLogin Admin

Console


� Your new licences are uncompressed on the Sage X3 Application Server in the

c:\NEWEDMLICS directory


ADMINISTRATOR


3. Select Upgrade your system to add additional functionality, click Next >

4. Confirm the new licence file location, browse to c:\NEWEMDLICS

The system is analysed comparing what is currently installed, against the new

licences.

5. When analysis completes, click Next >

6. Only new components based on the new licences will be displayed for installation,

consult the installation guide for assistance.

7. Apply the patches necessary for the additional components

10

Post Update / Upgrade Checklist

As a best practice, it is advised to run through the following checks to ensure the server

update / upgrade has been applied successfully.

Assumptions:

� The system has been fully updated

� The installation is in the c:\V1 directory

1. Check each web service pool alias has been created, is correctly named and is

running using the Sage X3 Console.

2. Open the c:\v1\Process\unpackxml.def and check the #USES path reflects the

installation path.

3. Check c:\v1\Process\<FOLDERNAME>\\<FOLDERNAME>LOOKUPSV1.soap. (This

file is the description for requests / lookups to the Sage X3 system. It essentially is

the interface between the systems based on the pool alias configuration.)

Ensure line 5 HOST is the server name and port number of the Sage X3 Application

Apache, e.g. X3APPSERVER:80.

Ensure line 15 <ns1:codeLang>ENG</ns1:codeLang> matches your preferred

language.

Ensure line 17 <ns1:codeUser>ADMIN</ns1:codeUser> matches the username

required to access the Sage X3 application.

Ensure line 18 <ns1:password>PASSWORD</ns1:password> matches the

password required to access the Sage X3 database.

4. Check c:\v1\Process\<FOLDERNAME>\<FOLDERNAME>LOOKUPSX3.soap (This

file is the description for commits to Sage X3 from an external source, namely the V1

software.)

Ensure Line 2 Host: refers to the Sage X3 Application server and port

Host:X3APPSERVER:31491

Line 5 http://X3APPSERVER:31491/axis2/services/archive the section in bold should

be the DNS of the Sage X3 Application server.

5. If you are installing PIA for Sage X3 by V1, check

C:\v1\Process\<FOLDERNAME>sso_ocr.soap and <FOLDERNAME>object.soap

For both, ensure line 5 HOST is the server name and port number of the Sage X3

webserver, e.g. X3APPSERVER:80

For <FOLDERNAME>object.soap only, ensure line 16 reflects the name of the web

service pool alias as set at Step .1

6. Load the Safe X3 Client / Navigate to the V7 login page. Login to the folder(s) /

Endpoint(s) to which EDD/EDM/PIA capability has been added. Navigate to

Development > Data and Parameters > Miscellaneous Tables > Data (GESADI). In

the Table cell, enter 81 and press tab. Ensure the URL Base is correct. (This can be

tested manually by entering the URL in Internet Explorer. If you see a prompt for a

username and password assume it has been installed correctly)

If it is not correct, change to: http://X3APPSERVER:31491/V1 click Save and end.

11

7. Ensure the following environment variables are present in the PATH at the system

level on the Sage X3 Application server:

C:\v1\Process\axis2c-bin-1.6.0-win32\lib;C:\v1\Process\axis2c-bin-1.6.0-

win32\services\archive

If they are not present, add them to the system. (Ensure to log off and back in / reboot

when convenient to apply.)

8. Ensure all Sage X3 users wanting to use the system are given the EDM user profile.

These credentials should match those setup for the user in the DbLogin Admin

Console.

9. Ensure the following standard reports have a default destination Printer:

SBONFAC

BONCDE2

RELFAC

ARCCLIENT2

DEVICLIENT2

10. Ensure each of the reports your users wish to use are assigned a destination. E.g. My

Sage X3 user PETE wishes to physically print Sales Invoices when using the AUTO

destination, this means using the GESAIA function, they must be specified in this list.

11. If EDM has been installed and SQL used, log into the SQL management console and

ensure the table structure matches below:

12

12. If the above is not reflected or if the BLOBS table is missing, an issue has occurred

during initialisation. This can be recovered by following the procedure in the

Troubleshooting Guide supporting documentation.

13. If PIA for Sage X3 by V1 has been installed, log into the SQL management console

and in addition to Check 11, ensure the table structure contains at least a queue entry

for the folder(s).

14. If PIA for Sage X3 by V1 has been installed, ensure the Sage X3 users who wish to

use it have a work flow email address. In addition, ensure the same usernames are

setup in DbLogin Admin and have the same email address. This is how their access

credentials are ‘linked’ between systems. Further information is contained in the

Implementation Guide.

15. Open the c:\Window\DbMail.ini in notepad and ensure the DefaultReply,

Administrator and DefaultFrom addresses are set.

Documents

EDM for Sage X3 by V1 - Updating and Upgradingsupport.wearev1.com/software/x3/X3EDMHELP/files/EDM... · EDM for Sage X3 by V1 Updating and Upgrading EDM for Sage X3 by V1 Release