You can call EAServer components from within a Dynamo script as though they were stored procedures, Java objects, or ActiveX objects. As long as the client has been set up properly to access the component, you can write Dynamo scripts to use EAServer components as though a stored procedure was being called (referred to as the MASP feature in EAServer), or by creating an instance of a Java or ActiveX object.
The three main benefits to using EAServer components in Dynamo scripts are:
Business logic stored in one EAServer component becomes available to many clients.
EAServer makes powerful native code components such as C and C++ available for execution by Dynamo scripts that would otherwise not have access to methods written in C and C++. This extends Dynamo's capabilities to an even greater extent, as there are few limitations being put on the languages that Dynamo scripts may make use of.
You can update components in one location. Without EAServer, changes to a component or a stored procedure would be required at each client.
The way in which EAServer components are independently accessible by clients such as Dynamo is advantageous because no restrictions have been put on the way in which the client can manipulate the component results. The component results are wholly controlled by the client which, in the case of Dynamo, is by HTML pages.
The ability to access these components at one central repository is appealing from a setup point of view. Setting up Dynamo to access EAServer components can be as simple as creating a connection to EAServer or installing the ActiveX proxy automation server. For detailed information on setting up clients that require EAServer access, see the EAServer Programmer's Guide.
| Copyright © 2003. Sybase Inc. All rights reserved. |
|
|
