Below is some information on setting up WēPO both at the server and for the client PC. Additional information can be found in other knowledgebase articles on Print Wizard and WēPO and in the various user manuals.
At the PC
Normally, a web object such as WēPO is installed on client PC's as needed by simply clicking on the component on the web page. However, today's security is an issue and even though the WēPO product is signed, PCs may not allow it to be downloaded and installed automatically.
You can install the ActiveX object before hand and avoid having to set and reset Internet Explorer security. From our web site you can download either the .OCX or the .CAB file for Print Wizard OCX, also called WēPO. You can download either one, though manual installation of one is easier than the other. Both contain the Authenticode signature. The .OCX is the actual ActiveX control to install, whereas the .CAB file is compressed into a Windows "cabinet" file.
If you download the .CAB, you need to extract out the .OCX file from it. On Windows 2000/XP you can do this by bringing up Windows Explorer, click on the .CAB file and "explore" it. Then right click on the PWButtonXControl1.ocx file and "extract" it.
Once you have the .OCX, do a Start : Run and enter the following to install (register) it:
regsvr32 PWButtonXControl1.ocx
To uninstall (unregister) it, do
regsvr32 -u PWButtonXControl1.ocx
To do this automatically you could set up a small batch file to do the work or burn it to a CD with an autorun if needed, as the regsrv32 will act like an install and copy the .OCX from where it is to where it needs to be for Windows.
For future releases, we will be also making available a self-install copy of the program.
At the Host
In order for a client to download the WēPO ActiveX module, you still need to have it referenced somewhere from your web site. If you are running a licensed version of WēPO, you can include the license information and the download location in your web page script that calls this ActiveX. Check out our examples on our web site to get an idea of how to integrate this in at the server side.
Back to top