01.06.2013 Views

OpenEdge Getting Started: Installation and Configuration - Product ...

OpenEdge Getting Started: Installation and Configuration - Product ...

OpenEdge Getting Started: Installation and Configuration - Product ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Progress messages<br />

Table 127 illustrates another example of how this process works, using more detailed<br />

data for you to review.<br />

The first column of Table 127 elaborates on the installation sequence outlined earlier<br />

in this section. In Step 1, the user initially installs <strong>OpenEdge</strong> Studio with a PROMSGS file<br />

for American English. The file header date of this newly installed PROMSGS file is<br />

04/14/2007. In Step 2, when the user installs an add-on product, the add-on product<br />

installation compares the header date of its American English PROMSGS file, 04/15/2007,<br />

with the header date of the existing American English PROMSGS file, 04/14/2007. Since<br />

the header date of the PROMSGS file associated with the add-on product is later than the<br />

existing PROMSGS file, the PROMSGS file is updated or synchronized.<br />

This example helps to illustrate the criterion for updating PROMSGS files. Only PROMSGS<br />

files associated with languages that are currently installed in the <strong>OpenEdge</strong> will be<br />

updated by the add-on installation process.<br />

In Step 3, when the user installs another <strong>OpenEdge</strong> product, such as the <strong>OpenEdge</strong><br />

AppServer, <strong>and</strong> identifies the Spanish PROMSGS file, the PROMSGS file with the date of<br />

04/14/2008 is installed. This latter part of the example illustrates how the PROMSGS files<br />

can become out of sync per the date information in the respective headers.<br />

Table 127: Example of PROMSGS files being out of sync<br />

<strong>Installation</strong><br />

step order Install...<br />

1. A product such as<br />

<strong>OpenEdge</strong> Studio<br />

As Table 127 indicates, the installation of previously non-existing Spanish PROMSGS file<br />

dated 04/14/2008 into the <strong>OpenEdge</strong> installation is now out of synchronization with the<br />

updated American English PROMSGS file dated 04/15/2008, which updated the original<br />

American English PROMSGS file.<br />

When an additional <strong>OpenEdge</strong> installation is performed <strong>and</strong> the <strong>OpenEdge</strong> <strong>Installation</strong><br />

program detects that a PROMSGS language has been installed that did not previously<br />

exist as illustrated by Step 3 in Table 127, the <strong>OpenEdge</strong> installation program displays<br />

a message. This message indicates the following:<br />

• The add-on product name that contains the latest PROMSGS<br />

• The destination path of the add-on product<br />

And the PROMSGS<br />

file is...<br />

Installed for<br />

American English<br />

2. An add-on product Updated for<br />

American English<br />

3. A product such as<br />

Application Server<br />

Installed for Spanish<br />

PROMSGS<br />

Which contains<br />

this header date...<br />

04/14/2008<br />

04/15/2008<br />

04/14/2008<br />

The <strong>OpenEdge</strong> installation message only displays this message when it detects that<br />

add-on products have been installed <strong>and</strong> it reads a new file called addons. The addons<br />

file is a text file defined as a Windows initialization (.ini) file. This file is created <strong>and</strong>/or<br />

updated in the <strong>OpenEdge</strong> destination directory by the add-on installation program. To<br />

resynchronize your PROMSGS file, you must reinstall your add-on product.<br />

<strong>OpenEdge</strong> <strong>Getting</strong> <strong>Started</strong>: <strong>Installation</strong> <strong>and</strong> <strong>Configuration</strong> 481

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!