Consultor Eletrônico

Status: Unverified

GOAL:

How to initially set a remote appServer to work with the default Dynamics installation

GOAL:

How to configure a remote AppServer to work with Dynamics

GOAL:

How to configure a remote Dynamics AppService

GOAL:

How to use Dynamics with a remote AppServer

GOAL:

Which files need to be copied for Dynamics to work with a remote AppServer

FIX:

In the windows machine where Dynamics was installed, ensure that all the Dynamics' sessions defined use specific host names and not "localhost" to make the connections and regenerate the icfconfig.xml file. Replace the icfconfig.xml file with the newly generated one in the following directories:

installed-dynamics-dir\gui\icf
installed-dynamics-dir\src\icf
installed-dynamics-dir\tty\icf

The reason for this is that this file will be copied over to the AppServer tty/icf directory.

Create a sub-directory on the AppServer machine named "tty" (it can be located under any base directory. I.e.: /usr/dynamics ).

Copy the following directories from wherever Dynamics was installed
on the Windows machine to the "tty" directory on the Unix/AppServer machine:

$InstallDir/tty/adm2 -> /usr/dynamics/tty/adm2
$InstallDir/tty/icf -> /usr/dynamics/tty/icf

This will copy all the required files for Dynamics.

If using ftp to transfer the files, ensure that all of the .r code is transferred in binary mode.

Make sure that the "case" of the files names stays the same (in particular the "tty", "icf" and "adm2" directories should be lower case.

The above assumes the remote AppServer is in a unix machine. If it is in a windows system, the only change is the base directory which could be something like this: C:\dynAS

Also, copy the as.pf file from your windows machine where dynamics was installed to the AppServer's Dynamics' base directory.

Once all the files have been copied over, configure a new appService such as the default 'icfrepos' on your windows machine. The configuration is the same, it should have all the default managers set and the propath should point to the new Dynamics' base directory. This should be the service name you use in the Dynamics session configuration for your appServer connection. If you configure an AppService with a name other than icfrepos, enter ·icfrepos· in the ·AppServer Name List· since this is defined by default in the Dynamics session.

The AppServer Agent Advanced features should be set as follows:

In the uborker.properties file in unix:

srvrActivateProc=as_activate.p
srvrConnectProc=as_connect.p
srvrDeactivateProc=as_deactivate.p
srvrDisconnProc=as_disconnect.p
srvrShutdownProc=as_shutdown.p
srvrStartupProc=as_startup.p

If setting up an AppServer broker in windows, use the Progress Explorer to specify the names of the Procedures in the Server Advanced Features properties:
as_activate.p
as_connect.p
as_deactivate.p
as_disconnect.p
as_shutdown.p
as_startup.p

(There are no parameters for the above startup procesdure)

The AppServer propath should be similar to the following in a windows system :

.;d:\dynAS\tty\icf;d:\dynAS\tty;d:\dynAS;@{WinChar Startup\PROPATH};@{WorkPath}

The AppServer propath should be similar to the following in a unix system:

PROPATH=.:/usr/dynamics/tty/icf:/usr/dynamics/tty:/usr/dynamics;${PROPATH}:${WRKDIR}

Modify the Propath in the Dynamics\bin\icf.ini file in the windows machine where Dynamics was installed to include the dynamics directories. It should look similar to the following:

PROPATH=c:\dynwrk,.,C:\Dynamics20A\gui\icf,C:\Dynamics20A\src\icf,C:\Dynamics20A\src\icf\af\sup2,C:\Dynamics20A\gui,C:\Dynamics20A\gui\adecomm.pl,C:\Dynamics20A\gui\adeicon.pl,C:\Dynamics20A\gui\adeshar.pl,C:\Dynamics20A\gui\adeuib.pl,C:\Dynamics20A\gui\protools.pl,C:\Dynamics20A\gui\adeedit.pl,C:\Dynamics20A\gui\adedict.pl,C:\Dynamics20A\gui\prodict.pl,C:\Dynamics20A\gui\adecomp.pl,C:\Dynamics20A\gui\adedesk.pl,C:\Dynamics20A\gui\adexml.pl,C:\Dynamics20A\gui\adeweb.pl,C:\Dynamics20A,C:\Dynamics20A\gui\aderes.pl,C:\Dynamics20A\gui\adetran.pl,C:\Dynamics20A\gui\as4dict.pl,C:\Dynamics20A\src,c:\Progress91D\gui,c:\Progress91D,c:\Progress91D\bin,c:\Progress91D\PROBUILD\EUCAPP\EUC.PL,c:\Progress91D\PROBUILD\EUCAPP

Start the appServer broker and test Dynamics using the &#82.20;Dynamics Runtime with AppServer· option from the start menu to bring up the Administration panel. Open the Help About window and see the appServer connection information.

It is not recommended to use the "Dynamics Development with Appserver" icon to try to do development with AppServer. Development should be done using the "Dynamics Development" menu option, and when testing the application with AppServer, launch the application using a "Dynamics Runtime" session type..