|
|
|
|
|
|
Return to Documents list
|
|
|
|
|
 Introduction
This paper discusses how to deploy a web-based application that uses the OPC Web Client ActiveX Controls to obtain OPC Data and publish it
to browser over the LAN/intranet/internet.
Who should read this document
- Web-developers
- IIS Admins
So what is deployment?
Deployment is the process of moving your developed application/system from your development computer(s) to your intended production computers.
To best guarantee the success of your deployment, be sure to read and understand the guidance that this page, and other pages offer.
Different applications require different deployment strategies
They way you deploy your web-based application will depend on your implementation.
|
Web Server Based Application
|
Web Browser Based Application
|
- OPC Web Client ActiveX Controls or OPCData.NET Components
is used by the Web Server.
(ASP, ASP.NET, PHP)
See "Server #1" above.
- OPC Web Client Web Service is used by the Web Server.
(ASP.NET)
See "Server #2" above.
|
- OPC Web Client ActiveX Controls component used within Internet Explorer browser.
See "Browser #1" above.
- OPC Web Client Web Service being consumed by the Internet Explorer browser.
See "Browser #2" above.
|
The Tabs at the top of this page will explain the deployment details for the scenarios listed above.
The key to a good deployment is to know and understand the software you are using, how
it works, and what it needs in order to work properly. Therefore, it is ALWAYS recommended that before you depoy your application to a production computer, that you:
- read through and understood all of the instructions these papers have provided.
- thoroughly test the deployment on "test computers" first!
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.
|
|
|
|
|
|
|
|
|
