Exposing the SessionXml and Source folders
To use the APIs, you must expose two shared folders on the Report Server: SessionXml and Source. On the Report Server, these folders are within the FsWebReports folder.
Typically, the path is: c:\inetpub\wwwroot\FsWebReports.
- SessionXml - This folder is where the report xml files are written.
- Source - This folder is where the .xsd, .xslt, and .rpt files are stored.
It is critical for the share names to be SessionXml and Source. Ensure that you do not have a share defined elsewhere on the system with these names.
Computer Management is an Administrative Tool on your system. You can use it to identify other shares on your system. In Computer Management, select
.If you have a share defined elsewhere on the system with the name of SessionXml and Source, then you will encounter these issues:
- The share names in the FsWebReports folder are renamed by the Windows operating system. For example, the share name may be renamed to SessionXml2.
- The APIs attempt to write to the SessionXml and Source folders that you have defined elsewhere on the system. (The APIs do not attempt to write to the folders in the FsWebReports folder.)
You must assign the read/write privileges to SessionXml and Source before you assign these privileges to the upper level folder, FsWebReports. Specific paths are searched by the system. These paths are: SessionXml and Source, not FsWebReports\SessionXml or FsWebReports\Source.
You must configure these folders to grant read/write permission to the PLM
Process Servers. For example, if the PLM Process server is called ABC1
, then grant read/write to <your domain>\ABC1$.
There are two ways to grant access to the PLM Process server. One way is to grant access to all the local accounts on the PLM Process Server by specifying the computer name (as in the your domain\ABC1$ example). The other way is to associate a domain account to the App Pool, and then grant access only to that user.
If you have installed the Report Server on the same machine as the PLM Process web server, you should grant read/write
permissions to the NetworkService
account.
Storing the .xml, .xsd, and .rpt files
- The
SaveReportData
method stores the .xml files in the SessionXML\tenantID folder on the Report Server. - The SaveReportSchema method stores the .xsd files in the Source\tenantID folder on the Report Server.
- Before 12.1, the reports (.rpt files) were stored in FsWebReports\Source. Beginning in 12.1, you must manually place these files in the FsWebReports\Source\tenantID folder. For example, if you have a tenant ID of Acme_Prod, then store your reports in Source\Acme_Prod. The .xsd files are written to the same folder.
- In 12.1, web reports can still publish the data to a location. In this scenario, the workflow can still be used to attach the report to Optiva business objects.
- A new Web.config setting,
RestrictFileRoot
, has been added to web reports. When you enable this setting, the XML, XSD and RPT files must be located under the web reports folder structure.