# Getting Started

## Configuring Lightweight Reporting

| ### Lightweight Reporting
| Ensure that a web environment is created and the web presentation service is started.
| In the Administrating Agile e6 tool create a new environment.
| Check the "Report_Service_URL" with the Administration Server tool. It has to be set to an existing web presentation service host and port: e.g. http://<host>:<port>/reporter/report
| Host and port have to match with the web environment that has been created previously.
| Detailed information about the Administration Server can be found in the Administration Manual for Agile e6. Administration Manual for Agile e6 > Administrating Agile e6
| Turn on Import/Export Functionality
| Select System > Packages.
| Select the Interchange Tools checkbox.
| Click the Save settings and then the Close window button.
| Select Manager > Tools > Im- / Export Facility. Define formats that are used to create the report. Examples are shown in the following figure.
| For each object that a report has to be created for an IEF-format needs to be defined.
| The reporter file uses the formats defined in the Definition of IEF-formats mask to generate the report.
| Add Menu Selections to Launch the Report
| Example: In the Item mask, you can add the following menu selections in a sub menu:
EDB-BAS-ART-REP-1 | 10 | Single Level | a | xtxt_tmp_men_rep | /TYPE=SingleBom /PARAM=T_MASTER_DAT.PART_ID
The user exit xtxt_tmp_men_rep has two parameters assigned to it. Type and Param. The value of the parameter Type has to match the report name in the reporter.xml (e.g. SingleBOM). With the parameter Param an ID field can be configured (e.g. Part ID). This has to be the same as in the reporter file.
| The report name (e.g. SingleBom) has to be the same as in the reporter.xml file! (Agile_e6\epclt\<webenv>\webapps\ROOT\jspreport\config\reporter.xml)
| Further information on the different sections of the XML file and on how to configure the IEF-formats can be found in the Enterprise Integration Platform Administration Manual > PLM Connector > Configuration Inside Agile e6.
| Reporter.xml The reporter.xml file is the central configurations file for the Lightweight Reporting.
Section | Explanation
<schemas> | In this section, different schemas can be defined. These schemas can be used by different reports. We recommend not to use too many different schemas because this can lead to performance problems.
<exports> | The used export name in the section <report> points to an XML file . This XML file defines the date that will be exported, e.g. field, relation, etc.
<transforms> | The used transform name in the section <report> points to an XSL file (style sheet) that should have the same name. The XSL file defines the format the report should be transformed into.
| Create the report. One record has to be selected.
| When the report gets created, the URL defined in step 1 is called.
| The Lightweight Reporting can be performed only for one record at a time!
| ### Configuration Parameter
| When Single Sign On is activated for Agile e6, the following configuration parameter has to be set to True in the webplm.properties file to allow switching between different Agile e6 clients. An additional login is not required.
| axalant.web.enable.ticket=[false|true] True = activated False = deactivated
| By default this configuration parameter is set to False!
| Web Client > Web Client Customizing Techniques > Customizing the webplm.properties File