|
|
|
|
|
|
Return to Documents list
|
|
|
|
|
Server Based Applications Developed With
The OPC Web Client Web Service
Introduction
This particular system, whereby all of the software is actually installed on a web-server, can actually be installed and developed on a production web-server.
Because no software will be physically running within the Web Browser, there is no need to even consider the web-browsers when deploying your system.
Fortunately, this configuration is relatively simple enough that deployment can be very straight-forward.
Deployment Options/Needs
Essentially, the following software and components will need to be deployed:
- The OPC Web Client itself
- The OPC Web Client Web Service
- The OPC Common files
- OPCEnum.exe
- OPCProxy.dll
- OPCProxy.dll
One other item that is equally important is the need to configure DCOM on the new computer.
Instructions
By far the quickest and easiest way to deploy your application to a new web-server is to simply run our install-set to install the OPC Web Client software. This
install-set will install the OPC Web Client, along with the OPC Common files.
The OPC Web Client Web Service will need to be configured within IIS (Internet Information Services) - instructions found here.
Once these common files are installed and registered on the web-server, you will of course need to make sure that the OPC Web
Client is licensed. If the OPC Web Client is not registered, then it will operate in a demo mode.
Once the OPC Web Client and the OPC Common files have been installed, and when the DCOM configuration has been configured, then you are ready to begin testing your
deployed application
Deployment Testing
Deployment is only as good as your testing!
Be sure to have a test-plan, or in this case a test web-page that you can quickly run and verify that all the functionality your application needs are in working order! You can of course save time and install & use our examples as part of your tests.
No other point or comment is as important as this...
Code defensively, look for errors and provide a means to log and display those errors at every opportunity - ESPECIALLY on your test page.
|
|
|
|
|
|
|
|
|
