PEP Read Me First
-----------------

PEP Number: <Assigned by the build team>
Pep Title: "Cannot launch AppBuilder when upgrading from older AppBuilder to AB4.0 PEP+SU1"

(0) Target Release
------------------
CallPilot 4.0 SU01 PEP


(1a) Target Platform
-------------------
AppBuilder


(1b) Affected Connectivities
----------------------------
None


(1c) Risk Assessment
--------------------
LOW


(1d) List of files changed
--------------------------
 \mpcx\nmldap\src\client\NMldapCom\versinfo.rc2
 \mpcx\nmic\src\AppBuilder\appbuilder.wse


(2) Problem Description
-----------------------
Upgrade from AppBuilder 2.0/2.5/3.0 to AppBuilder 4.0 SU01.
Login to AppBuilder and connect to CP Server 4.0 SU01

Expected result:
AppBuilder logins successfully.

Actual result:
AppBuilder window disappears. 


(3) Problem Analysis
--------------------
AppBuilder installation is based on WISE installer. AppBuilder installation overwrites
files during the upgrade, only if file version from the installation package is older then
version of installed file. WISE checks not only file version, but other version info as well,
such as Description, Company, Internal Name, etc. If these fields do not much, file newer gets
overwritten. This behavior is not documented in WISE help.

In CP 4.0 release LDAP client COM dll nmldap.dll was overwritten. Old nmldap.dll source files
located at \mpcx\nmldap\src\client\nmldap\ new files located at \mpcx\nmldap\src\client\NMldapCom\.
Version info is stored in \mpcx\nmldap\src\client\nmldap\versinfo.rc2 and
\mpcx\nmldap\src\client\NMldapCom\versinfo.rc2 correspondingly. Version info of nmldap.dll
2.0/2.5/3.0 does not much to version info of nmldap.dll 4.0. I mean not version number, but other
fields in particular Description, Internal Name and Original File Name.

Due to this reason nmldap.dll does not get updated during the AppBuilder upgrade. AppBuilder 4.0
cannot work properly with nmldap.dll 2.0/2.5/3.0.


(4) Solution
------------
Synchronize nmldap.dll version info in CP 2.0/2.5/3.0 and CP 4.0. Substitute
\mpcx\nmldap\src\client\NMldapCom\versinfo.rc2 with \mpcx\nmldap\src\client\NMldap\versinfo.rc2.

Once version info is synchronized, AppBuilder installation will be able to upgrade AppBuilder
2.0/2.5/3.0 successfully, but won't be able to upgrade AppBuilder 4.0 GA. A kluge was added to
AppBuilder install script to upgrade from AppBuilder 4.0 GA. Install script reads nmldap.dll
version into script variable. If version is 4.4.4.0, then nmldap.dll is replaced without version
check.


(5) List of CRs that are fixed by this PEP 
-----------------------------------------
Q01209394/2/"Cannot launch AppBuilder when upgrading from older AppBuilder to AB4.0 PEP+SU1"


(6) Dependencies
----------------
None


(7) How to install this PEP
---------------------------
NOTE: AppBuilder.exe must be repackaged.

(i)  Close AppBuilder

(ii) On client's PC if you have Application Builder installed to default folder
     copy the files as follows below, otherwise copy the files to appropriate
     folder where you have Application Builder actually installed:

    #   File                    Destination directory
    --------------------------------------------------------------
    1.  nmldap.dll              C:\Nortel\Common\

(iii) Reboot is not required


(8) List of suggested test cases
--------------------------------

    - 1.
    Uninstall Application Builder if installed.
    Install Application Builder 2.0/2.5/3.0 (for instance CP202S04G01A).
    Install Application Builder with the fix.
    Launch Application Builder, login to CP server 4.0 SU01 or newer.
    Make sure Application Builder logins successfully.

    - 2.
    Uninstall Application Builder if installed.
    Install Application Builder 4.0 GA (AppBuilder version 04.04.04.00).
    Install Application Builder with the fix.
    Launch Application Builder, login to CP server 4.0 SU01 or newer.
    Make sure Application Builder logins successfully.


(9) Special instructions
------------------------
None