Environment Issues and Common Mistakes
This section describes problems that can occur during QXtend installation. For more detailed information regarding potential installation issues, visit the QAD KnowledgeBase or contact QAD support.
No X11 DISPLAY Variable was Set
This error appears when you try to run the install in a non-GUI console. To run the installer in console mode, add the -i console option to the command.
Unable to Deploy
If the Web Applications do not deploy properly, Tomcat may have failed to fully start during the installation. Verify that the Tomcat server is fully operational (a good test is to access the Manager application in your browser). If it is running, but produces out-of-memory exceptions, you can increase the maximum and default Tomcat heap size (-Xmx and -Xms). See your operating system documentation for further information.
Cannot Connect to Database
The install log reports this problem as an error code 14. If the installer is trying to connect to a database using client-server or shared-memory mode, this error probably means that the database is not running. It could also mean that the database is trying to run in single-user mode, but the database is already in use.
If the install log reports error messages like “SYSTEM ERROR: Shared memory access permission denied (1136),” log in as the user who created the database, restart the installer, and continue with the installation.
Default Configuration
A default configuration failure is often the result of a few issues.
• The Inbound Web application and Outbound AppServer must be running so that the Web Service can be accessed, and in turn, contact the AppServer.
• The QAD Enterprise Application databases must be running for the default configuration to create subscribers for the source application.
If the problem seems to be configuration related, consult the AppServer logs in the server installation logs directory.
No Features to Install on this Host
The following message can appear during QXtend installation:
“The information stored in the QAD Deployment Configuration Service indicates that there are no features to install on this host (xxx). If this is unexpected, you may wish to re-run the installer on a Windows or X-Platform and update the configuration. If this is correct, then continue the installer on the next host. The installer will now exit.”
This message indicates that there are no installs to do on the machine on which you are running the install. You can continue the install on the servers you are using.
This message can display for a number of reasons:
• When you first run the installer on a PC in a multi-tier install, it builds the QAD Deployment Service (QADDeployService.V1), interrogates the user for configuration values (data gathering), and checks if it should also deploy on the same PC. Generally, the answer is no because you are just building the configuration data through a GUI interface, but you plan to deploy the components on a different server or servers. In this case, you can safely ignore the message and proceed.
• During QXtend.bin -i console, you were prompted for an environment to install and entered an invalid environment name such as Test, Prod, and so on. If your answer was not valid, the installer looks in the respository.xml file for an environment tag called <what you entered>. The tag is missing, resulting in “nothing to install on this Host.” If you forgot your environment name, you can check the respository.xml file for the name you provided. You can also run a GUI installer and observe the option at the environment selection screen. Then rerun the installer.
• To determine if an incorrect host name was entered, compare xxx from the error message with the result of hostname or an equivalent command in a console window. When using the QXtend installer, always use the shortened host name (do not include the domain).
IATEMPDIR Space
The installer must self-extract several files before it can run. This requirement can cause an error before the installer finishes loading, particularly when using the bundled Java VM. This issue occurs because there is insufficient space in the default extract location. To resolve this problem, you can set the environment variable IATEMPDIR to use a storage area with sufficient space.
Java Memory
If you experience out-of-memory errors before the installer finishes initializing, do the following:
1 Create a directory called bin under $HOME as user mfg.
2 Create a file named java under the bin directory and add following parameters in the file:
• - /opt/java1.5/bin/java -verbose -Djava.awt.headless=true -XX:HeapDumpOnOutOfMemoryError -client
• -Xms1024M -Xmx2048M $@
• -XX:PermSize=512M
• -XX:MaxPermSize=512M
• Set JAVA_HOME to $HOME/bin.
• Add $HOME/bin in the beginning of the PATH.
The installer should now be able to complete the installation process.
UI API Adapter Performance
When using QXtend with AIX, change the AIX kernel setting tcp_nodelayack to 0. Otherwise, QXtend UI API performance is severely limited.