Prerequisites for Importing Logger Data
Does not apply in a SaaS environment
Since this process involves different ArcSight products interacting with each other, ensure that you have the correct credentials and requirements for all of them before you proceed.
Prerequisites for Logger
-
Admin user with SSH credentials.
-
The username and password that you use to import Logger data must match the OS credentials set in Logger.
-
The system directory must have enough space. For more information, see the Release Notes for ArcSight Logger.
-
Whether the Logger host is installed in the same machine or a different one, it will need to have the VSQL Client Driver installed (this will be explained inStep 1 of the procedure).
Prerequisites for the ArcSight Platform
-
Admin user with ArcSight Database credentials.
-
The system directory must have enough space. For more information, see the Technical Requirements for the Arcsight Platform.
-
If the ArcSight Platform capabilities are deployed on the same machine as Logger, make sure that the RHEL/CentOS version used in Logger is supported by Fusion. For more information, see the Release Notes for ArcSight Logger and the Technical Requirements for the Arcsight platform.
-
The ArcSight Platform capabilities must be reachable from the Logger instance (on port 5433).
Prerequisites for the ArcSight Database
-
For the migration process, the user must have the Logger Data Migration permission assigned in Fusion. This is assigned by default to the System Admin role, but the user could have a custom role that includes the permission.
-
For search execution after the data has been imported, users must have either the Default Role or a role with appropriate Search permissions.