1 of 1 people found this helpful
Your CDR will be loaded from the server onto the client and executed on the client and therefore will need to have any required dependencies built into the CDR, included in a support assembly for the CDR (which will be loaded from the server onto the client with your CDR), or have it installed on each client.
To register support assemblies with your CDR, you can use the RegPlugIn or RegPlugIn64 utility (depending on the platform that you target). For example, if you implement both a .NET 3.5 and 4 version of the Plugin targeting AnyCPU with the corresponding implementations of the support assembly, then they are registered with the following command.
RegPlugIn /PISystem:MyPISystem PlugIns\MyPlugIn.dll PlugIns\Support.dll PlugIns\4.0\MyPlugIn.dll PlugIns\4.0\Support.dll
MyPlugIn.dll is the CDR assembly
Support.dll is the support assembly
On top of what Eugene said, for Oracle, it seems that the oracle libraries needed are the Oracle Instant Client.
This seems a complicated option to me.
If you really need a CDR I would think you'd be better to create one based on OLEDB. OSIsoft has a solution for that: the table lookup data reference. Here are some links that can help to get started with this:
Imported tables and linked tables --> what interests you is "linked tables"
Add table parameters to a linked table query --> this will be the key to limit the number of rows returned from the external database for each attribute.
Let us know how it goes for you.
What is the reason a linked AF Table would not work for you? Then you only need the Oracle client on the AFserver (newer versions of AF required though, i think 2.5 or up. Check release notes).
In any other case proxy webservice is an option to access remote systems through a custom DR.