Application Configuration

Application Configurator

Proceed as follows to create a new application configuration or to change an existing configuration:

1. In the context menu of the application, choose Create/Change Configuration .

   A browser window is opened with the new configuration editor.

   The application name is already preset.

2. The following functions are available:

   Note

   If you want to edit/display/delete an existing configuration or use it as a template, you can enter its name manually or use the search help function to find it. You can search by the following criteria in the search help:

   • Application

   • Author (user name)

   • Package

   • Display Existing Configuration

     Enter the name of an existing configuration and choose Display .

   • Create New Configuration

     1. Enter a unique name for your new configuration and choose Create .

     2. Enter a description.

     3. Specify the package to which the configuration is to be assigned.

     4. Edit your configuration by changing the description or structure (you can also branch to the component configuration here), or specifying application parameters .

        Note

        You can check the consistency of configurations without having to save them. To do this, choose Check .

     5. Save your entries, restart the application, and display the configuration or test the application with the new configuration.

   • Change Existing Configuration

     1. Enter the name of an existing configuration and choose Change .

     2. Edit your configuration by changing the description or structure (you can also branch to the component configuration here), or specifying application parameters .

        Note

        You can check the consistency of configurations without having to save them. To do this, choose Check .

     3. Save your entries, restart the application, and display the configuration or test the application with the new configuration.

   • Delete Existing Configuration

     Enter the name of the existing configuration, choose Delete , and confirm the confirmation prompt if you are sure that you want to delete the configuration in question.

   • Use Existing Configuration as Template

     Enter the name of an existing configuration and choose Copy . Then enter a unique name for the copied configuration.

   • Use Other Functions

     • Rename existing configurations

     • Create enhancements (for use with the switch framework).

       Configuration K1 is copied to a new configuration K2 in a system with switch S1, and a delegation is run, which means that when configuration K1 is called, configuration K2 is automatically used if switch S1 is available in the system.

       Switchability is defined when the configuration is assigned to a package (the switch is attached to the package).

     • Change the assignment of the configuration ID to the application.

       Note

       Note that the configuration ID must always be unique. You can only ever have one configuration ID for the name in question in a system.

   • Terminate work with the configuration editor.

     Choose Cancel .

3. Save your entries.

   Note

   The configuration editor determines whether a configuration has been changed. This means that the save pop-up only appears in the configuration editor when a change has been made.

In-Place Navigation

When you navigate from one configuration to another configuration in the configuration editor (by choosing Go to Component Configuration under Assignment of Component Configurations ), a browser window is not opened by default. The new configuration that you selected is displayed in the same browser window. However, a Breadcrumb containing the existing configurations appears in this browser window. By clicking a previous configuration in the Breadcrumb, you can navigate back to this specific configuration.

If you do not want the configuration to be displayed in the same window, you can display your configuration in a new browser window by choosing New Window .

Assignment of the Configuration to the Application

Various configuration data records can be created and stored for an application. To start an application with a special configuration, there are different options available:

1. In the portal, you can define the assignment by specifying the configuration name as an application parameter in the iView wizard.

2. In SE80, you can call the application with the required configuration by choosing Test in the context menu for the selected application configuration.

3. The name of the configuration can be passed to the application or passed as a default value. For this reason, you can maintain the parameter WDCONFIGURATIONID for a Web Dynpro application. You enter it on the Parameter tab page of the application editor .

   The parameter WDCONFIGURATIONID can be assigned once only for each application.

   After you have saved the data, you now have the configured Web Dynpro application at your disposal.

Example Development Scenario

A component developer is setting up a component in order to represent a basic business function. In addition, he or she is integrating explicit configuration options at this early stage by creating a range of attributes in the configuration controller context and implementing the respective functions in suitable methods of the different component controllers.

An application developer wishes to use this component in a particular context. He or she first creates a component configuration for the component used, one that matches his or her requirements. For the application, he or she will use perhaps other components with special component configurations that either already exist or will have to be specially created for this purpose.

Afterwards, he or she sets up a main component and creates for this a new application as well as an application configuration. This has a unique name and contains a list of all the used components with the required component configuration in each case. Note that non-configurable used components are not displayed in the application configurator.

Finally, the application developer enters the name of the created application configuration as a default value for the WDCONFIGURATIONID parameter on the relevant tab page in the application editor.

When you start the application, all the required components are now fetched with the selected configuration.