After installation of OutBoard Housekeeping the next step will be to set up the systems that will be using in OutBoard Housekeeping. This can be done, by going to the Landscape Editor, which is found in the top menu under "Edit".

_{Figure 5: Navigating to Landscape Editor}

In the Landscape Editor, it is possible to:

Create System Categories: this allows for grouping of individual systems by a common denominator i.e. BW, ERP or CRM (in active Edit mode).
Add new system: enables the user to complete the necessary fields to enable OutBoard Housekeeping the necessary connection required to perform housekeeping tasks (in active Edit mode).
Display the logs relevant to Landscape editor (in both Display and Edit modes).

The fields required to add the new system successfully, are:

System name	Descriptive name of the system, it will be shown in the landscape tree.
System ID	ID of system, the same system cannot be added to the landscape twice.
RFC destination	The name for the RFC destination for the added system that needs to be defined on central system. OutBoard Housekeeping cockpit communicates with the systems via remote function calls. No matter if the cockpit populates settings, pushes task execution, communication always directs from cockpit to systems. So there's no need to configure fully bi-directional RFC connection in the system – RFC client is enough. In the RFC connection the logon user defined must be the type SYSTEM or SERVICE or DIALOG (see transaction su01, tab "Logon data"). SYSTEM type brings limitation in executing standard SAP tasks executed as transactions.
Secondary RFC	Optional parameter. If Primary RFC is not of a DIALOG type and the task requires it, the system checks for a Secondary RFC connection (of DIALOG type) and executes the task there. This is true for all standard transactional tasks (task type of STD_TRAN) as the system automatically executes the task on the Secondary RFC, if it is not in initial state.
System type	Depends on the purpose of the system; acceptable types are BW, ERP and CRM.

If central system is running in, for example, German language, RFC language is not set and satellite system doesn't have German language support installed, now, if the RFC connection tries to use German language connection to satellite, the connection fails and it looks like the system is not responding. The solution is to force the language existing on satellite in RFC connection settings.

RFC destination definition is case sensitive.

_{Adding a new system in the Landscape editor}

Once the OutBoard Housekeeping system landscape has been defined and saved, it will be visible in both the activity and system views.
It is important to get the hierarchy in a way that allows for efficient grouping of household tasks. By doing so, allows for experiencing the full benefit of features such as inheritance of settings. Recommendations are in Appendix A.
When the system landscape is defined, it is possible to utilize system-locking functionality. It enables to prevent access to selected group or system. In Landscape editor in Edit mode, there is "Locked" checkbox available for group/system. Once checked and confirmed by "Save" button, locked systems are not available for any activity.
If "Locked" status is modified on group level, after pushing "Save" button, all landscape changes are distributed downward to lower-level groups and systems. It is possible to lock/unlock part of landscape in one step. But required system (s) can be separately unlocked in locked landscape area.

_{System locking functionality in the Landscape editor}

It is possible to reorder the system landscape using drag and drop functionality. However, the systems and groups can be repositioned only within the original parent group.

_{Reorder of groups and systems in the Landscape editor}

Browser not supported