0 RPE document specifications are enhanced with the addition of a data source property that specifies the configuration URI. If this variable is defined RPE adds an OSLC Configuration HTTP header to every HTTP GET request made to the data service. This header will be processed by any configuration-capable data service The global configuration property value may be changed by scripts in the document template during document generation. RPE allows users to set/discover the value of the configuration URI. OSLC delegated UIs are used for the discovery process RPE discovers the URL of the OSLC delegated dialog by reading the service provider resource of the configuration service. RPE is enhanced with an embedded web browser that can display the OSLC delegated dialog for the user to select the configuration. Existing templates DO NOT have to change and neither the URLs used to configure the data sources Template design does not change, it DOES NOT become more complex Configuration aware document generation

1 Configuration selection – the discovery process Step 1: provide RPE with the URL of the rootservices document of the configuration provider

2 Configuration selection – the discovery process Step 2: select the OSLC Configuration provider and the OSLC Selection Dialog you want to use Depending on the selection status of the “external browser” checkbox you will proceed to steps 3a or 3b

3 Configuration selection – the discovery process Step 3a: use the picker in the embedded browser in RPE –checkbox from step 2 was not selected

4 Configuration selection – the discovery process Step 3b: use the picker in an external browser –checkbox from step 2 was selected

5 Configuration selection – the discovery process Step 4: complete the wizard. The selected value is set in the “Configuration- Context” property of the data source

Document generation – Configuration 1 (older)

Document generation – Configuration 2 (newer)