Creating a separate server in JBoss for Add-ins

It is recommended to set up a separate JVM for servicing requests from Microsoft Office Add-ins, so it doesn't impact performance on the LSF server(s). The configureJBossForLSF.pl script provides this automation for JBOSS.

  1. Run the ssoconfig utility.
  2. At the prompt, specify the password for the ssoconfig utility.
  3. At the Lawson Core Technology command line, specify ssoconfig -c
  4. Specify the number for Manage SSO Domains.
    Note: The SSO domain name must have already been created and associated with an endpoint before completing this procedure. See the information about Working with Single Sign-on Domains in Infor Lawson Administration: Server Setup and Maintenance.
  5. Specify perl createAddinsServer.pl tip10 lawson.

    When called in interactive mode, the Infor Interview Screen should be displayed.

  6. Specify this information:
    NUMSERVERS

    Specify the number of servers to create in the server group for Add-ins. The default value is 1.

    SOCKET_BINDING_GROUP_NAME

    Specify the name for the new socket binding group to be created for Add-ins. For example, addins-sockets.

    SERVERGROUP

    Specify the name of the server group for Add-ins. For example, addins-group.

    SERVERBASENAME

    Specify the root name of the application server/s to be created in the server group. For example, tip10-addins-server.

    MINHEAP

    Specify the heap size setting for the Add-ins server group. For example, 512M.

    MAXHEAP

    Specify the maximum heap size setting for the Add-ins server group. For example, 2048M.

    HTTP port

    Specify the port to be used for the Add-ins http access.

    HTTPS port

    Specify the port to user for the ADD-ins https access.

    SSO domain name

    Specify the domain name.

    Name of SSO endpoint group

    Specify the name of the SSO endpoint group. For example, PHLSFREL10.

    FQDN of new endpoint for Add-ins

    Specify the FQDN (Fully Qualified Domain Name) of the new endpoint for Add-ins. For example, PHLSFREL10.lpc.lawson.com.

  7. Click Finish.
  8. Run the WildFly admin console and verify if the new server group for Add-ins is created.