New PCI Image Viewer Map for ArcSight ESM
- Pavan Raja
- Apr 8, 2025
- 7 min read
Summary:
The document titled "New (02/11) PCI Image Viewer Map for ArcSight ESM" is a comprehensive guide created by Gary Freeman and dated 02/11, which provides detailed instructions and troubleshooting tips for working with images in the ArcSight Console, specifically related to creating and managing Image Viewer Maps. This document is likely intended for users who have enabled the Image Editor within the ArcSight Console and need to customize their image setups.
### Key Points of the Document: 1. **Exporting Images**: The guide suggests exporting a .vsd file directly as a PNG using default settings after opening it with Visio. This step helps in customizing the images for use in the Image Viewer Maps within the ArcSight Console. 2. **Console Configuration**: To enable the Image Editor, users need to modify the `ARCSIGHT_HOME\Console\current\admin.ast` file by adding the line `console.ui.imageEditor=true`. This configuration setting allows users to use the hidden Image Editor within the ArcSight Console.
3. **Troubleshooting**: The document includes common issues and their solutions: - **Images Not Loading**: Ensure that the image paths are correctly configured. If necessary, edit `.jlx` and `.properties` files associated with ArcNet-Retail to reflect the correct path for images. - **Error Messages**: Adjusting properties like `console.ui.maxActiveChannels=20` can help manage multiple channels without reaching the system limit of 10 open channels per chart object.
4. **Creating New Image Viewer Maps**: Users should familiarize themselves with available help features within the ArcSight Console to understand how to add and populate controls for new maps effectively.
5. **Attaching Files and Managing Comments**: The document mentions that users can attach files related to their work in the system, such as images or documents, and manage comments associated with these documents.
### Interpretation of Version Number: The mention of "Version: 113816" within the context of Jive Software could be a specific version number used for development, testing, or deployment purposes. The term "AWESOME," in casual usage here, simply indicates that the user finds this version satisfactory and powerful enough to manage image setups effectively using the ArcSight Console.
### Usage Context: This document is likely part of an internal knowledge base or training materials provided by Jive Software for its customers or users who have implemented their software solutions within organizations. The guide serves as a resource manual for troubleshooting, configuration adjustments, and best practices in managing visual components like Image Viewer Maps within the ArcSight Console ecosystem.
Details:
The document "New (02/11) PCI Image Veiwer Map for ArcSight ESM" is a guide created by Gary Freeman to help users update and customize the existing PCI Image Viewers in ArcSight ESM version 5.0. This document serves as a tutorial since there was no previous documentation available, especially considering that it focuses on enhancing the functionality of the image viewer map within the software.
The main purpose of this guide is to provide detailed instructions for editing and personalizing the PCI Image Viewers by including customer logos or renaming elements in the Visio templates provided. The document also covers various aspects such as installation, constraints, tools used (Visio), elements of an image viewer, FAQs/troubleshooting, and ESM Image Editor usage.
To use this guide, users should have basic knowledge of using Visio and familiarity with ArcSight ESM version 5.0. The document is intended for organizational teams within the Sales Engineering department and can be accessed through various platforms like blogs, discussions, documents, etc., as mentioned in the summary provided by Emrah Alpa.
In 2010, Notepad++ introduced constraints related to Image Dashboards and Image Viewer Maps. These maps were intended as replacements for the now-extinct Image Viewer Maps, which became less relevant due to their resource-intensive nature and local user settings that required distribution of changes. The Image Editor was described as rudimentary with no online help, suggesting its limited functionality and difficulty in use.
For installation instructions:
1. Remove or rename the directory c:/arcsight/Console/lib/resources/views/ArcNet-Retail before extracting the zip file if necessary.
2. Extract the zip file into the specified path and confirm its existence with Explorer.
3. Start your ESM 5.0 demo VM, then load the Replay Connector to send PCI 2.3 events to ESM.
4. Open the ArcSight Console, load the "/All Active Channels/ArcNet Active Channels/PCI/PCI - All Events" channel, and select "Image Viewer > ArcNet-Retail".
5. Confirm that the images are working correctly by checking chart objects displaying PCI metrics.
The text discusses elements of an image viewer called ESM (Elementary Stream Mapper), installed under the ArcSight Console directory, and includes a description of various files used within this system. These components include JLX files, Properties files, PNG files, and Visio templates.
JLX files are related to chart objects in the JLoox charting engine, providing coordinates for rendering these charts. The Properties files serve as image mapping files similar to HTML image maps, with hotspots plotted and linked to drill-down images or channels. PNG files provide high compression and quality for images used within ESM. Additionally, BMP, GIF, and JPG formats are supported by the Image Viewer Maps. Lastly, Visio templates in .VSD format were created as 1011 x 636 pixel templates that users can modify to customize their drill-down functionality.
To customize elements in an Image Viewer Map within Visio and export them to PNG format, follow these steps:
1. **Template Dimensions**: The template dimensions are measured in points (Visio doesn't use pixels). A standard size is 755 pt x 430 pt, which equals approximately 1011 pixels x 636 pixels. Adjust the drawing size accordingly to maintain consistency with pixel measurements.
2. **Updating Dimensions in JLX and Properties Files**: When resizing the drawing, ensure that these changes are reflected in both the JLX and properties files. This can be done manually in any text editor by searching for and replacing outdated dimensions.
3. **Blank Squares Hosting Chart Objects**: If you modify the positions of the blank squares where chart objects reside, update the corresponding JLX and properties files accordingly. These changes can also be made through a console Image Editor (refer to the next section for detailed instructions).
4. **Image Format Changes**: When switching from PNG to GIF, BMP, or JPG formats, ensure that these modifications are reflected in both the JLX and properties files by using a text editor for search and replace operations.
5. **Managing Chart Objects**: Be mindful of the number of chart objects across all drill-downs; aim to keep this count under 10 to avoid negatively impacting demo performance.
**ESM Image Editor (hidden)**: For scenarios where you need to create content similar to PCI Demo image views:
1. **Original Visio Format**: Ideally, obtain the drawing in its original Visio format for easier editing.
2. **Exporting as PNG**: Open the .vsd file with Visio and export the drawing directly as a PNG using default settings.
3. **Console Configuration**: Close any instance of the ArcSight Console. Locate the `ARCSIGHT_HOME\Console\current\admin.ast` file (or adjust for the specific user) on the prospect’s computer, add the line `console.ui.imageEditor=true`, and save the file. Restart the ArcSight Console to activate the hidden Image Editor.
By following these steps, you can effectively customize and export Image Viewer Map elements within Visio to meet your requirements.
This is a guide about working with images in ArcSight Console, specifically for users who have enabled the Image Editor within the console. Here are some frequently asked questions along with their answers:
1. **Why are my images not loading on your Image Viewer Maps?**
Ensure that you have the correct path to the images, which should be `c:/arcsight/Console/lib/resources/views/ArcNet-Retail`. If the directory path is different, you need to edit `.jlx` and `.properties` files associated with ArcNet-Retail. Follow these steps:
Select all 14 files (both JLX and Properties), right-click and select "Edit with Notepad++".
In Notepad++, go to "Search > Replace", enter the old path as "Find What" and the new correct path as "Replace With".
Save all changes. Close and re-open the ArcSight Console, images should now load correctly.
2. **Why am I getting an error message regarding maximum number of channels exceeded?**
This occurs because each chart object on the Image Viewer Maps indicates an open channel, with a system default limit of 10. To increase this limit:
Edit `console.default.properties` (after backing up the file) to set `console.ui.maxActiveChannels=20`.
3. **How do I create a new Image Viewer Map from scratch?**
Enable the Image Editor in the ArcSight Console and follow these steps within the Image Editor:
Select the New Image Entry icon on the left-hand tool list, click anywhere to open the file dialog, and select the desired image as a background.
Resize the image appropriately; you can then add controls like pie charts and bar charts.
This guide provides troubleshooting steps and detailed instructions for managing images in ArcSight Console, ensuring that users can visualize data effectively through maps and charts.
This document outlines how to use an Image Editor and Image Viewer within a system, focusing on specific steps for editing images, saving them with customer names, and viewing the results. It mentions that users should familiarize themselves with available help features to understand how to add and populate controls, as well as noting potential variations in results due to different user setups. The document also includes details about attaching files and managing comments related to the document.
The text provided appears to be a reference or entry related to software, possibly indicating the version number of Jive Software. Here's a more detailed breakdown and possible interpretation of what it means:
**Jive Software**: It seems to refer to a specific type of software product named "Jive."
**Version: 113816**: This is likely the version number of the Jive Software. Version numbers are used by software developers to track and manage changes in their products, making it easier for users and developers to understand what features have been added or bugs have been fixed since previous versions. The version number "113816" could be a build number or a sequential identifier within the development cycle of Jive Software.
**AWESOME**: This is an expression that appears to express enthusiasm or approval, possibly related to the software version 113816. In informal contexts like this, it might simply mean "great" or "awesome" in terms of liking or appreciating something. The term AWESOME here doesn't have a clear technical meaning specific to Jive Software but suggests positive feelings towards the software based on its version number.
Given that there is limited context provided, interpreting this text fully requires understanding the broader environment where it was used (e.g., in an email, a project management tool comment, or a changelog). Without additional information, "AWESOME" could be a user expressing satisfaction with the software's performance based on its version number alone.
Comments