Nexus Portal Support

Installation Instructions

These instructions are for new installs of Nexus 4.10 and later only. Please log in to myFreschesolutions.com to access the User Guide.

Step 3b: Install the IBM i Components on iASP.

As of version 6.9, the Nexus installer allows installing the IFS files and product library to an iASP.

IASP Considerations:

  • Before running the installer, the user needs to have the correct ASP group set. The installer will check that the selected iASP exists and is available to the user.
    • You can check that the ASP group is set in two ways:
      • This option may require elevated security Security priviledges. Run WRKUSRPRF command and find the Job Description. Then do a WRKJOBD on that Job Description name and find the Initial ASP Group. Change this value to the correct ASP group. Sign out and back in as that user for the change to take effect.
      • Use the command SETASPGRP to set the ASP group for just the current session. For example: SETASPGRP ASPGRP(MYIASP) SYSLIBL(*SYSVAL) CURLIB(*CURUSR)
  • Cloning from one iASP group to another is currently not possible. The installer will not allow installing the library to an iASP in one ASP group, then attempting to clone that library to a new library on the iASP of a different ASP group.

To run the install or upgrade, call the installer from the IBM i command line:

BCDINSTALL/BCDINSTALL

After choosing between a new install or clone, you'll be prompted for the IASP to install the product library. Specify the iASP you are installing to in the field 'Install to iASP' (the default is *SYSBAS):

Install screen

After entering the install library, you’ll be prompted for the IFS directory to be created for your Nexus environment:

Install screen

The default directory includes starting with a forward slash and the iASP name (e.g. /iasp/esdi/xl_nexus or your iASP and environment).

Once the installation is done, the IFS and product library will be on the iASP.

Apache Instance:

Before starting the Apache instance, we need to set the initial iASP group on the main HTTP job description. There are two ways to do this:

  1. If you only have one iASP, you can change the default QHTTPSVR/QZHBHTTP server:

    • WRKJOBD JOBD(QHTTPSVR/QZHBHTTP)
    • Option 2, F10 for all parms
    • Page down and look for Initial ASP group (INLASPGRP)
    • Set this to the name of your iASP
  2. If you have multiple iASP or would like to separate things, you can run Apache for Nexus in its own Subsystem (requires V7R1 or higher):

    • The following example is based on https://www.ibm.com/support/pages/how-run-http-apache-its-own-subsystem

      The example below creates a new subsystem called HTTPSVR24 that runs on the iASP1
      1. Create a new library to store all IBM i native objects like subsystem description, job queue and job description.
        • CRTLIB HTTPSVR24
      2. Create a job queue. This is where the job is submitted before it starts running.
        • CRTJOBQ JOBQ(HTTPSVR24/HTTPSVR24) OPRCTL(*YES) AUTCHK(*OWNER) AUT(*USE) TEXT('User defined HTTP Job queue')
      3. Create a job description. This defines how the job should be run and can be customized according to specific requirements as needed. To use *SYSBAS for the ASP, use *NONE for INLASPGRP.
        • CRTJOBD JOBD(HTTPSVR24/HTTPSVR24) JOBQ(HTTPSVR24/HTTPSVR24) TEXT('User defined HTTP job description') USER(QTMHHTTP) RTGDTA(HTTPSVR) JOBMSGQFL(*WRAP) INLASPGRP(IASP1)
      4. Create a subsystem description. Here’s where the HTTP server jobs actually run . Create the subsystem with the same name as the class defined in previous section, HTTPSVR24.
        • CRTSBSD SBSD(HTTPSVR24/HTTPSVR24) POOLS((1 *BASE)) MAXJOBS(*NOMAX) AUT(*USE) TEXT('User defined subsystem using *BASE pool')
      5. Add job queue entry.
        This command tells the subsystem which job queue it should search for jobs to run. Here we let subsystem HTTPSVR24/HTTPSVR24 search job queue HTTPSVR24/HTTPSVR24.
        • ADDJOBQE SBSD(HTTPSVR24/HTTPSVR24) JOBQ(HTTPSVR24/HTTPSVR24) MAXACT(*NOMAX) SEQNBR(10)
      6. Add routing entry. Adding the routing entry to subsystem defines the criteria of job selection and parameters used to start a job.
        • ADDRTGE SBSD(HTTPSVR24/HTTPSVR24) SEQNBR(10) CMPVAL(HTTPWWW) PGM(QSYS/QCMD) CLS(QHTTPSVR/QZHBHTTP)
      7. Modify the HTTP Apache configuration. Using the examples from the previous steps we would then add the following directives to the Apache configuration so that the server is pointing at the newly created Job Queue, Job Description, Routing Data, and Subsystem Description:
        • HTTPStartJobQueue HTTPSVR24/HTTPSVR24
        • HTTPStartJobDesc HTTPSVR24/HTTPSVR24
        • HTTPSubsystemDesc HTTPSVR24/HTTPSVR24

If you made any changes to the Apache config, you need to restart Apache for the changes to take effect. This can be done with the following commands:

ENDTCPSVR SERVER(*HTTP) HTTPSVR(XL_NEXUS)

STRTCPSVR SERVER(*HTTP) HTTPSVR(XL_NEXUS)

Upgrading Considerations:

  • You can upgrade an environment on *SYSBAS to an iASP, or from iASP to *SYSBAS. But cloning from one iASP group to another iASP group is currently not possible.