How to control log file creation when starting the Java Administration Console from a UNIX server

Description

On the UNIX Server where the Java Administration Console is being started, complete the following:

1. In the <install_path>/openv/java directory edit the Debug.properties file, making the following changes:
   • Remove the comments from the following lines:
     printcmds=true
     printCmdLines=true
      
   • Also add the following:
     debugMask= 0x00040000
      
2. Make sure the <install_path>/openv/netbackup/logs/user_ops/nbjlogs directory exists.
3. Change directory to <install_path>/openv/netbackup and edit the bp.conf file, adding the following to the bottom of the file:
   
   VERBOSE = 5
    
4. On the master server that is being logged into when starting the Java GUI, complete the following: 
   1. Increase the log file debug/verbose settings to 5. 
      *** A process recycle is not needed, but users will have to exit and restart the interface.
        
   2. Create the following log file directories:
       
      For Windows master servers:
      
      ​​​​​in <install_path>\VERITAS\NetBackup\logs:
      
      bpjava-msvc 
bpjava-susvc
      
      
      For UNIX master servers:
      
      in <install_path>/openv/netbackup/logs:
      
      bpjava-msvc
bpjava-susvc
       
   3. Start the Java interface using jnbSA
      
      WHILE the problem is occurring - run the following on the UNIX server being used to start the Java Administration GUI:
       
      /usr/openv/java/get_trace
      
      Running the above logs a stack trace from the current session log file.
       
   4. Collect the collect and review the bpjava-msvc and bpjava-susvc logs from the master server and the <install_path>/openv/netbackup/logs/user_ops/nbjlogs/jbp.<userid>.<pid>.log file from the current session.