A remote System i requestor can run Viewpoint functions on a server PC making it possible for users that do not have ViewPoint installed to create graphs and client report (CRO) results.

A typical example of this enables the SEQUEL Web Interface to run/display CRO results through a browser. This feature also enables scheduled execution of ViewPoint requests from a IBM i host.

The ViewPoint Server computer runs requests using the iSeries Access Incoming Remote Command facility. The steps below outline the process to configure the server computer so that it can successfully run remote ViewPoint requests.

Requirements

This is a very important step. The computer you select should meet these minimum requirements:

A server-class PC with at least 4GB of RAM, and a 2GHZ+ processor with at least two cores (8GB with 4 or more cores is recommended).

  • Windows 7 Professional / 8 Professional / 8.1 Professional / Windows Server 2003 / Windows Server 2008 / Windows Server 2008 R2 / Windows Server 2012 / Windows Server 2012 R2 (see Notes below)
  • IBM i (System i, iSeries, Client) Access for Windows version V6R1 service pack SI35607 (or higher), or V7R1 with the following installed components:
    • Client Access Express Required Programs
    • iSeries Navigator Base Support (an option under iSeries Navigator)
    • Commands Component (an option under iSeries Navigator - for prompting commands in the script designer)
    • OLE DB Provider (an option under Data Access)

The computer should be fast enough to run ViewPoint requests quickly, and have access to the local network so
that it can receive requests and route ViewPoint output to its desired location.

Notes:

  • If you use Windows (64-bit) on the ViewPoint Server, or the Unified Server, ViewPoint will install by default into the Program Files folder ‘C:\Program Files (x86)\SEQUEL ViewPoint’. If you install into a different directory, make sure to use the SWI command, SEQUELWI/SWIVPDFT, and set the ‘Program File Directory’ parameter (PGMFILEDIR) to the same path.
  • Although supported, we do not advise using a domain server for the server since it can create conflicts.
  • Important: ViewPoint Server cannot be configured on Windows 10.

Steps 

  1. Log onto the Server
    Access the ViewPoint Server PC directly or with Windows Remote Desktop Connection.
     
  2. Define the Operational User
    Choose or create a user that can access both the System i and the local computer. The server user should have the same name and password as the System i user profile that you want to run the ViewPoint requests. You may choose to use either a local computer user, or a domain authenticated user. The user must be assigned Administrative rights for the local computer since it will be used to start the incoming remote command service. (If it is imperative that the incoming remote command service not be run under a named user that has administrative rights, you may elect to start the service under the system account and choose not to define the user as a member of the administrators group. This will prevent a suc- cessful System i connection until the local computer has been signed on to the selected account however.)

    Use the Control Panel to access the User Accounts applet (or the Local Users and Groups sub tree available in the Computer Management applet of Administrative Tools) to define/verify that the selected account is part of the Administrators group. If you are using a domain authenticated account, it should be listed in the applet as domain/username.
     
  3. Use System i Navigator to Define the System i Systems
    Log on to the server using the user you have chosen and define the System i system(s) to be used by ViewPoint. It is best to configure the System i connection(s) to use the Windows user name and password—no prompting. If the ViewPoint server will be used to process requests submitted through the SEQUEL Web Interface, the System i connection name must match the system name of the System i requester. SEQUEL Web Interface determines the system name of the System i requester using RTVNETA (DSPNETA).

    The IBM i connection name is the connection name defined in Client Access (iNavigator) on the ViewPoint server.
     
  4. Specify Properties for the Incoming Remote Command Service
    Open the System i Access for Windows Properties window and select the "Incoming Remote Command" tab. The command mode should be "Normal". Select the "Allow generic security" option. Leave the "Generic security runs command as logged on user" option unchecked **.

    (** Selecting the "Generic security runs command as logged on user" option will cause the ViewPoint requests to be run using the user currently logged on to the server. If multiple users are logged on, the user that will be selected is indeterminate. If no users have been signed on and the service is started using the local system account, the requests will not work. If your environment requires all services to be started using the local system account, you must select the "Generic security runs command as logged on user" option, and the server must be logged on to the selected operational user before ViewPoint requests will work correctly. Additionally, remote requests will not work correctly until the operational user on the Viewpoint Server has logged into the IBM i. This step must be repeated after the server is rebooted.)
     
  5. Ensure Security Policies are set Properly for the Windows User
    The default policy settings are not sufficient to run the incoming remote command service. Once you are logged on as the Administrator level user, open the Control Panel, then open the Administrative Tools shortcut, and run the Security Policies tool. Open the Local Policies folder and select user rights assignment.

    Either the Administrator group or the user (specify domain\username for a domain authenti- cated user) that will handle the incoming requests must have these privileges:
    • Act as part of the operating system
    • Log on as a service
    • Replace process level token
    • Increase quotas (Win/2000 only)
       
  6. Prevent Windows Firewall from Blocking Access to the Server
    Your server may have firewall software installed that limits access to certain ports and/or pro- grams. Microsoft Windows Firewall is a frequently used program and may be running on your server. The default behavior of Windows Firewall requires administrators to explicitly enable the firewall for some applications that process incoming requests. Determine if Windows Fire- wall is running on your server by opening the Control Panel and running the Windows Fire- wall icon (in Windows 7, look for Control Panel\System and Security\Windows Firewall). If the Firewall is not enabled, skip the remaining part of this step.

    Enable System i Remote Command service by issuing the following command
    (Start\Run…\Cmd):
    netsh firewall add allowedprogram "%windir%\cwbrxd.exe" "iSeries Access Incoming Remote Command server"
    Verify that the command worked as expected by using the Firewall icon in the Control Panel. Ensure the "Don't Allow Exceptions" box is unchecked. Select the Exceptions tab and verify that an entry for iSeries Access Incoming Remote Command server appears and is checked.
     
  7. Configure and start the Incoming Remote Command service
    Open the Control Panel, then open the Administrative Tools folder, and run the Services shortcut (‘CWBRXD’ for Win 7). Double click the item for System i Access for Windows Remote Command.
    **You may elect to run the service under the local system account, however ViewPoint will be unable to connect to the System i unless the "Generic security runs command as logged on user" option has been selected for the incoming remote command definition and the selected user has been signed on to the computer. There can be further complications if more than one user is signed on to the local computer, or if the signed on user does not have System i connections defined through System i Access or a corresponding System i user profile with proper authority to run host requests.
     
    • On the General tab, specify that the service should start automatically.
    • On the "Log On" tab specify the operational user and password you have chosen to run the service and connect using System i Access**. If you are using a domain authenticated user, specify the user in the form domain/username Enter and confirm the password for the account. Apply the changes and start the service.
       
  8. Configure Access to the Server from the System i Computer(s)
    • Sign on as QSECOFR.
    • Verify the server computer can be located by running the command:
      PING <your_server_name>
    • If the request does not complete normally, run the CFGTCP command and use option 10 to work with the host table entries. Add a name entry for the server computer correspond- ing to its IP address. Retry the PING request in (b) above.
       
  9. Test the Remote Command Feature from the System i Computer
    From a command line, run the command:
    RUNRMTCMD CMD(SET) RMTLOCNAME(<> *IP)
    The command should complete in a few seconds and produce spooled output. Verify the out- put exists using WRKJOB and choosing option 4. The spooled file will show the values for various environment variables at the server, including the USERNAME running the request.
     
  10. Ensure ViewPoint is Working Properly from the Server
    • Install/Update ViewPoint on the server computer.
    • Run ViewPoint and prove that it works properly from the desktop.
       
  11. Edit the HostList.ini File
    When the remote request occurs at the server, ViewPoint will attempt to start a connection to the indicated System i computer. The process will run disassociated from the desktop. ViewPoint must be able to initiate a connection without intervention. A user ID and password must be available for the connection to occur.

    The SEQUEL Viewpoint installation folder contains a configuration file named HostList.ini. If ViewPoint's initial connection attempt is unsuccessful, ViewPoint will re-try the connection using the user/password values for the indicated system from the HostList.ini file.

    This makes it possible to run successfully when the user has not signed onto the Windows workstation, or if the Signon information in the System i Navigator's Connection properties tab for the system indicates either "use default" or a "prompt every time" setting.
     
  12. Test a Local ViewPoint Request from the Server's Command Line
    • From the Start Menu, choose Run and type "cmd".
    • At the command prompt, enter the following ViewPoint command:
      "\program files(x86)\sequel viewpoint\viewpnt"/v:xxxxxx/SEQUELEX/CUSTLIST /d:\custlist.txt /q

(where xxxxxx is the System i name defined in the System i Navigator)

  • The command should complete in a few seconds without opening any additional windows on the desktop and create a custlist.txt file on the root drive.
  • Ensure that the file was created and the contents are correct.
  • Delete the file from the server's root directory.
  1. Test a Remote ViewPoint Command with Local File Results
    • From a System i command line, run the command:
      RUNRMTCMD CMD('"\program files(x86)\sequel viewpoint\viewpnt"/v:xxxxxx/SEQUELEX/CUSTLIST /d:\custlist.txt /q') RMTLOCNAME(<> *IP)
      

(where xxxxxx is the IBM i name defined in the System i Navigator)

The command should complete in a few seconds and produce the indicated file in the root directory on the server. Depending on how quickly the process executes, you may be able to use the Task Manager at the server computer to watch the process start, run, and complete.

  • Delete the file from the server's root directory
  1. Test a Remote ViewPoint Command with LAN File Results
    Ensure the IFS directory you intend to save results to is Shared and Mapped. We suggest the '/TMP' directory for the share and mapped resource.
    • To share the folder, start System i Navigator and navigate to File Systems\ Integrated File Systems\Root. In the expanded Root directory, right-click the TMP folder, and select Sharing\Create Share. In the next window press OK to finish.
    • From a System i command line, run the command:
      RUNRMTCMD CMD('"\program files(x86)\sequel viewpoint\viewpnt"/v:xxxxxx/SEQUELEX/CUSTLIST /d:\\<>\custlist.txt /q') RMTLOCNAME(<> *IP)

(where xxxxxx is the IBM i name defined in the System i Navigator, and <> is a mapped network drive location)

The command should complete in a few seconds and produce the indicated file in the root directory on the server. Depending on how quickly the process executes, you may be able to use the Task Manager at the server computer to watch the process start, run, and complete.

  • This tests to ensure that the remote command process has the required privileges to store files on a LAN accessible share. Verify that the file is created and has proper content, then remove it.
     
  1. Set the Sequel Web Interface Default
    From an System i command line, prompt the SEQUELWI/SWIVPDFT command and set the remote server name and location for temporary results in the TARGET (Target Path) parameter. As a example, place results in the TMP folder by setting the target path to: \\IBMiServerName\tmp

    The temporary results location can be tested using Step 12 above.
     
  2. Run a SEQUEL Client Report via the SEQUEL Web Interface.
    Navigate to the SEQUEL Web Interface and validate that it is working by running a view, runtime prompted view, or report. Once you have received correct output, run a SEQUEL Client Report (SQLRPTC) object.

You have now successfully setup the ViewPoint server and should be able to use it to execute ViewPoint requests from either the SEQUEL Web Interface or the System i.

 

 


Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: November 20, 2018