How to: |
WebFOCUS Visual Discovery applications can be deployed over the web using the digitally signed Vz.cab file and the VzLicense.lpk file included on the WebFOCUS Visual Discovery VZ Web Server installation CD. The cabinet (Vz.cab) file installs the component files to the drive:\Program Files\Common Files\ADVIZOR Components directory. The license package (VzLicense.lpk) file allows the use of licensed ActiveX controls in an HTML page on a non-licensed computer.
Note:
<object classid="clsid:601CD7CF-7278-11D1-871D-00A02411D404" width="100%" height="100%" codebase="http://server/path/ Vz.cab#version=9.0.2011.509" >...</object>
To verify the current version number, you can look at the file version string on the Version tab of the file properties dialog box for DLLs like VzLib.dll.
Tip: During Managed Reporting remote development, users other than the developer may access the Visual Discovery webpage. Therefore, when you are developing webpages in Managed Reporting, you can follow these steps, but omit the command VIEWASTEXT. HTML Composer will display the component on the development canvas.
\ibi\WebFOCUS80\ibi_html\visdis
If the visdis directory does not exist, then you must create it manually.
Note: If using a UNIX platform, FTP the Vz.cab file and VzLicense.lpk file to the UNIX machine in BINARY format.
<OBJECT CLASSID = "clsid:5220cb21-c88d-11cf-b347-00aa00a28331" id=licensemgrobj VIEWASTEXT>
<PARAM NAME="LPKPath" VALUE="/ibi_html/visdis/VzLicense.lpk"></OBJECT>
codebase="http://server/ibi_html/visdis/
Vz.cab#version=9.0.2011.509" VIEWASTEXT
where:
Is the server that hosts each domain within Managed Reporting.
Note: If using a UNIX platform, FTP the Vz.cab file and VzLicense.lpk file to the UNIX machine in BINARY format.
<OBJECT CLASSID = "clsid:5220cb21-c88d-11cf-b347-00aa00a28331" id=licensemgrobj VIEWASTEXT>
<PARAM NAME="LPKPath" VALUE="/ibi_html/visdis/VzLicense.lpk"> </OBJECT>
codebase="http://server/approot/appname/ Vz.cab#version=9.0.2011.509" VIEWASTEXT
where:
Is the server that hosts the Visual Discovery pages.
Is the name of the application that contains the Visual Discovery pages.
http://server/approot/appname/htmpagename.htm
where:
Is the name of the web server hosting the thick-client webpage.
Is the name of the application that contains the thick-client webpage and the related application files.
Is the name of the thick-client HTM file.
If you are developing in the Projects area of Developer Studio, you have the option of using the Deploy Scenario Wizard to move your application files to your WebFOCUS run-time environment. The Deploy Scenario Wizard automatically edits the paths to the .txt files and .fex files in the HTML file, as well as updating the CAB version.
To add these file extensions to your project:
The New Scenario Wizard opens. For complete details on how to use the New Scenario Wizard, see the Creating Reporting Applications With Developer Studio manual or click Help from the wizard to view the online documentation.
You may specify the HTM file as your starting object, or simply deploy the files and open a browser window to execute your webpage.
If you chose to deploy and run, with a starting object specified, it will run when the files have finished deploying.
http://server:port/approot/appname/htmpagename.htm
where:
Is the name of the web server hosting the thick-client page.
Is the name of the thick-client HTM file.
WebFOCUS |