Tuesday, September 17, 2013

Infor EAM 10.1.2 Installation

The Infor EAM software and CD keys are available to channel partners, in addition to access to Infor Xtreme, the system for obtaining tech support and looking up the knowledge base. The installer consists of 3 CDs:
(i) Database objects setup (there's a CD for SQL Server and another for Oracle)
(ii) Application setup
(iii) Advanced Reports setup

The installation logs do not help much during the installation process for the database objects setup other than for verifying that the installation occurred as intended. If the directory locations provided to the Infor EAM database objects setup do not exist, the setup application goes all the way to the end without performing an installation. Ensure the installation paths exist, and set the path for the data files, log files, and index files to the data directory where you would normally store them for your database installation.

The application setup is just as tricky as the database objects setup - the installer doesn't tell you if you are missing the Visual C++ 10.0 run time DLL so make sure you install it before starting the application setup. You can tell if you are missing the Visual C++ 10.0 run time DLL if the Infor Application HTTP service is missing (you should see 2 services for Infor in services.msc). After the installation completes and the web server does display a login screen, you can check the WildFly/JBoss logs for additional error messages. You may have a warning in the logs indicating that the application server could not connect to the database - you can configure the database connection in the depconfig directory by editing the ewsconfig.xml file and then executing the deploy.bat batch file. Another common source of errors is when the deploy.bat file indicates that the tools.jar Java archive is missing - this message appears in the command prompt window when deploy.bat begins execution.

After sorted out all the errors and have the application running, you can browse to the application in the web browser and attempt to log in with the username "r5" and password "r5", which is the default account created within the application.

The installer could have been made to reduce the administration effort for installing the application, but once you've installed it, you can create a procedure manual for your team to follow the steps that you did for setting up the system.

No comments: