Model Persistence

Visual Composer models and related objects can be stored in the local Application Server Java (AS Java) database or deployed to a remote DTR. When a model is first created, it is saved as an empty component with all of its auxiliary files. With each subsequent save, all of the model data is saved once again, including its generated XGL.

Import and Export Mechanism

The  Model Export to File option in Storyboard enables users to export a .zip file containing the model .gml file and all related files. The .zip file can be saved on any computer or server in the network. Subsequently, using the  Model Import from File option, users can import the file back into a development component from which Visual Composer opens models. The Storyboard contains no function that can determine if the model file has been corrupted or otherwise altered since it was exported.

Virus Scanner

Each model imported into Visual Composer or migrated to this version of Visual Composer can be scanned for viruses. If you have configured the virus scan interface to include external virus scanners on the AS Java, you can activate the visualcomposer virus scan profile in NetWeaver Administrator to automatically scan models for viruses during Visual Composer import and migration operations.

For information on the SAP Virus Scan Interface, see Defining Virus Scan Profiles.

Support Operations Utility

Visual Composer provides a utility ('corrective commands') that allows direct access to Visual Composer model content located on the server. The utility is used for support operations and is accessed via the Telnet console, which is accessible only to administrators on the NetWeaver AS Java. It is therefore secure by default. Care must be exercised when considering who is allowed to access these commands