A saved Solution Pack can be edited using Solution Designer. For information about deploying the changes into an existing system, see "Deploying an Edited Solution Pack."
When an existing Solution Pack is saved, the user has several options:
Save: Saves an updated version of the original Solution Pack. If the Solution Pack is re-imported into a Sentinel system, it replaces the old version.
Save As: Saves a renamed version of the original Solution Pack. If the Solution Pack is re-imported into a Sentinel system, it replaces the old version.
Save As New: Saves a Solution Pack with a new unique identifier. If the Solution Pack is imported into a Sentinel system, it does not impact any previously imported Solution Packs.
To edit a Solution Pack:
In Windows, use the Sentinel Solution Designer shortcut on the desktop, or start Solution Designer by executing one of the following commands:
solution_designer.bat (in %ESEC_HOME%\bin on Windows)
solution_designer.sh (in $ESEC_HOME/bin on Solaris/Linux)
The Sentinel Solution Designer login window displays.
Enter your login credentials. Check Work Offline checkbox if desired, then click Login. The Solution Designer displays.
To edit a Solution Pack, click File > Open. Browse and select the existing Solution Pack zip file. Click Open.
To update the Solution Pack with modified content from the source Sentinel system, drag and drop the content from the Content Palette to the appropriate Control.
Add or delete Controls as necessary.
Click File > Save, Save As, or Save As New.
If you selected Save or Save As and some of the content is out of sync, you will be prompted to synchronize.
If the content in the source system is modified, the content in the source system and the content in the original Solution Pack may be out of sync.
You can drag and drop the content from the Content Palette onto the control.
For simple content with no dependencies, the modified content is immediately updated. For example, a report has no dependencies.
For content with dependencies, the dependencies are checked and updates are made when you click Sync All Content or when you save the Solution Pack.
When a Solution Pack is modified and saved using the Save or Save As options in Solution Designer, it is considered a new version of the original Solution Pack. When it is imported, it replaces any older versions of the original Solution Pack. There is no immediate impact on any installed content in the target Sentinel system.
After the Solution Pack is installed, its behavior varies depending on the status of the original Solution Pack's content.
If the content from the original Solution Pack was not installed yet, the content is simply replaced. When a user installs content, the new content is installed to the target Sentinel system.
If the content from the original Solution Pack was installed (Not Implemented), Implemented, or Tested, the original content is compared to the new content.
If the content version is the same, the original content is still valid and no action is necessary.
If the content version is different, the content status is set to Out of Sync. The user must decide how to resolve the synchronization issue. For more information, see "Out of Sync."
If the content didn't exist in the original Solution Pack, it is displayed in Solution Manager as not installed. You can install, implement, and test the new content.
If the content existed in the original Solution Pack but has been deleted from the modified Solution Pack, it does not appear in the Solution Manager.
NOTE: The Solution Manager only handles differences in the contents of Solution Packs. It does not recognize manual content changes that are performed after content is installed.