\source
source directory contains all the example projects. Each project is put into a separate directory.
\report
report directory contains the report files needed by the example projects.
\download
download directory is used by example projects to store the downloaded files or reports. It is empty at very beginning.
\build
There are two sub-directories in the build directory, debug
and release. Each of them is used to contain the executables built from example
projects. Note that the DLL for server proxy is put directly into the build
directory. It is shared and referenced by other projects. Once you rebuild the
Server Proxy project in either debug or release mode, you need to copy “Server
Proxy.dll” and “Server Proxy.pdb” files into /Debug or /Release folder
respectively.
Building procedure is very simple for MS .NET example project. There are two solution description files in the root: examples.sln and “Server Proxy.sln”. After getting the source code, open the server proxy solution and build it, which will generate the proxy DLL (See note about DLL location above). Then open the examples solution and build it (it will build all sample projects).
Note that if there are some changes in the WSDL interface,
make sure download the latest WSDL file from the report server and put it in
the corresponding place in server proxy solution and rebuild the proxy first,
then rebuild all examples. The easiest way to update WSDL file is to make a
right-click on web reference “localhost” in Solution Explorer and choose
“Update Web Reference”. This will also update a local copy of the WSDL file.
The web reference is configured to retrieve WSDL file from
http://localhost:8000/wsdl/v11/net/all by default. You should change this URL
appropriatelly if you are using Report Server installed on another machine or
set up a different port.
Available sample program:
-
Login demonstrates
how to Login to the Actuate Server
-
Administrate demonstrates
Administrate operations, like CreateUser, CreateRole, CreateGroup etc.
-
UploadFile demonstrates
how to upload file using SOAP attachments (non-chunked)
-
DownloadFile demonstrates
how to download file as an embedded component
-
DownloadFile
(SOAP Attachment) demonstrates how
to download file as a SOAP attachment
-
ExecuteReport demonstrates
how to send immediate job request
-
SubmitJob demonstrates
how to submit a scheduled job with parameters
-
SelectFiles demonstrates
SelectFiles operation using FileSearch
-
GetFolderItems demonstrates
GetFolderItems request with fetching
The order above is recommended since some samples use
objects created by other samples. E.g. SelectFiles sample using files/folders
created in Administrate or UploadFile samples. After building, sample
applications can be executed from command line. Common command line parameters
are:
-h hostname host name and port number to connect to; default is
http://localhost:8000.
-u username username, default is administrator.
-p password password; default is ""(empty).
Samples don't create users that you provide names in command
line for. They should be created with Read privilege for /Report and underlying
files if you are going to use a user other than Administrator. Also see please
notes in source files (*.cs) for more details for each particular sample.
UploadFile -h http://localhost:8000 -f
d:\SampleBIRTReport.rptdesign
SelectFiles -h http://localhost:8000 -u
Administrator