Test Automation

Agent

Prerequisites

• For executing Oracle Automation test cases, the Oracle Client needs to be installed with Admin options on a Windows 32-bit machine.
• Install oracle client with administrator privileges and create a file tsnames.ora at the following location:

  Oracle_home\network\admin

• When you are using the test automation package for the Oracle iDataAgent on the client that has Oracle 10g database, the 10g cx_Oracle module will be installed automatically.
• If you are using the Test Automation Package for the client that has Oracle 11g database. uninstall the 10g cx_Oracle module and install the 11g cx_Oracle module

• Client computer needs to have multiple volumes to enable mount point creation for the tests.
• To utilize data archiving capability, the Driver for File System Data Archiver needs have been to be installed.

• The iDataAgent & Automation Package have to be installed directly on Exchange Server.
• Automation Package should be installed on a path that doesn't contain any spaces.
• Duplicate Exchange Databases shouldn’t be used for automation. The Database name given as input for automation should be unique in the Exchange Server.
• Automation will fail if PowerShell SCOPE is not set correctly in Exchange Management Shell. Make sure Exchange Management Shell has the correct DOMAIN name set for the SCOPE.
• In order to set the scope to correct domain, set a GLOBAL variable ‘AdminSessionADSettings.DefaultScope’ as follows:
  1. Go to Exchange server installation directory and open bin folder (like C:\Program Files\Microsoft\Exchange Server\bin)
  2. Find the file name “Exchange.ps1”
  3. Find the block (like ######## Exchange Variables ####### ) in that Exchange.ps1 file
  4. In that block if the variable $AdminSessionADSettings.DefaultScope exists then set the value of it to your machine’s domain name like $AdminSessionADSettings.DefaultScope = “medusa.loc”
  5. Be sure that the variable $AdminSessionADSettings.DefaultScope must occur after the occurrence of the variable $AdminSessionADSettings.ViewEntireForest(if this exist)
  6. If that variable $AdminSessionADSettings.DefaultScope does not exist then first find another variable called $AdminSessionADSettings.ViewEntireForest and delete it and then add the variable $AdminSessionADSettings.DefaultScope = <machine domain name>.

     For Example:  $AdminSessionADSettings.DefaultScope = “medusa.loc”)

  7. Reboot the machine after the above steps
  8. If problem still persists, make sure the DNS Entries are correct. If required, try removing all the DNS entries and have only PRIMARY DNS address
• You must configure the Storage Policy manually and give as input to the test cases
• Following registry keys should be created in the machine where CommServe is installed. You must restart the Services after creating these registry keys:

  nAllowHugeMessageSize, DWORD, under CommServe key, set to 1

  QCMD_SUPPORT_MODIFY_SUBCLIENT, DWORD, under EventManager, set to 1

• Exchange Database iDataAgent installation is required on any instance for Test case 8720
• Some test cases will try to create storage groups and databases. The Exchange Server should be able to accommodate them. The total number of storage groups present on the Exchange Server and total number of databases that are mounted should be less than the maximum limit permissible by the Exchange Server.
• Ensure that the Active Directory Snap-In for PowerShell is installed on the machine for Test case 30099.
• Set the limits for Exchange database where the subclient content mailboxes are created using the Exchange Management Console.  Once you set the limits, the generation of messages by automation script is not disrupted due to exceeding the warning limits.

• Domino Admin client must be installed on a Windows client machine.
• Domino Admin client should be connected to the Domino server.
• User logged into Admin client should be the Domino Administrator.
• User has to create a subclient, add content to it and specify the subclient name in answer file.

• MySQL Server should be configured with following user grant permission for both Windows / Linux Clients:

  GRANT ALL PRIVILEGES ON *.* TO '<dba_username>'@'<automation_controller_box_ip>' IDENTIFIED BY '<password>'

• Since Instance (New MySQL Server) creation is not supported for MySQL iDataAgent from command line, it has to be configured first manually in GUI.
• On the registry of Commserve computer, under the HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\<Instance>\EventManager section, create a DWORD type key QCMD_SUPPORT_MODIFY_SUBCLIENT with value set to 1.

• The default subclient of the instance (s) being used must be configured to use a valid storage policy.
• The date and time on the client computer must be in synchronized with CommServe computer.

• The test automation package needs to be installed on a windows computer and all the UNIX AGENT test cases need to be executed from the windows computer.

Agent / Feature

Pre-requisites

• Local Instance needs to be configured for the client.
 
• An Archiverset must be configured to use a valid storage policy.
• Ensure that on the windows computer, a value of ‘0’ is set for the registry key NtfsDisableLastAccessUpdate at location SYSTEM\CurrentControlSet\Control\FileSystem\

• From the computer where Oracle Test Automation is launching, ensure that there is no duplicate entry of the same connect string in the Tnsnames.ora.
• Disable flashback Recovery area from the Oracle DB. If Flashback recovery is enabled, Rman may complain about particular archive logs being missing, in which case the user have to manually crosscheck archivelogs by connecting the Rman.
• Ensure that the Oracle Service name and oracle connect string are the same.  If they are different, user has to manually update the Tnsnames.ora file on the controller from where Oracle Automation is being launched.
• Ensure that Time zone on the Client computer and Commserver computer are the same.  Redirect and Partial restore test cases may fail if different.

• You must create database inside Domino directory with at least one document in it.  qcreate support is not available for Lotus Notes iDataAgent for databases to be created automatically inside Domino directory.

• A SMB/CIFS share needs to be created on UNIX Client Computer which can be accessible from the windows computer, where Automation package is installed and test cases will be executed. The data will be created in the SMB/CIFS share.
• For executing Add-On Archiver Test cases on Unix File System iDataAgent, ensure that on the windows computer:
  • the DMFSWIN Driver for Data Archiver is installed.
  • A value of ‘0’ is set for the registry key NtfsDisableLastAccessUpdate at location SYSTEM\CurrentControlSet\Control\FileSystem\

• The default sub client of the default Backupset must be configured to use a valid storage policy.
• For executing Add-On Archiver Test cases on Windows File System iDataAgent, ensure that on the windows computer:
  • the DMFSWIN Driver for Data Archiver is installed.
  • A value of ‘0’ is set for the registry key NtfsDisableLastAccessUpdate at location SYSTEM\CurrentControlSet\Control\FileSystem\
• To execute test cases verifying the archiving feature,  the archiving capability at the agent level must be turned on.

• The default sub client of the instance (s) being used must be configured to use a valid storage policy

• There are no prerequisites before executing these test cases.

• Ensure the checkbox 'Enable Auto Discovery' on the General tab of Sybase Server Properties dialog is checked if the Sybase Instance was created manually. Failure to ensure this may result in Automation jobs to fail with an error. If the Instance was created through Automation, the option is automatically checked.