ISSUE/QUESTION:When users trying to reconfigure or Install delivery and reconfigure using Installer.cmd, IFS the database connection string is missing. Please refer bellow images,This is an image of the IFS Middleware Sever Admin Console. Here is the error message in Installer.cmd. Logging error messageLaunching Installer…Exception in thread "AWT-EventQueue-0" java.lang.NoClassDefFoundError: ifs/application/installer/tools/OracleConnectStringat ifs.application.installer.installationclasses.OracleConfigForm.showMe(OracleConfigForm.java:189)at ifs.application.installer.Installer.buttonNextActionPerformed(Installer.java:1132)at ifs.application.installer.Installer.access$500(Installer.java:44)at ifs.application.installer.Installer$7.actionPerformed(Installer.java:752)at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2022)at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2348)at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonMode
Issue:Database errors when trying to abort a remote installing in the middle of the execution. There it is trying to stop the process in the middle using (ctrl + c). The installation stops there, but the java process started on the DB side does not stop. Resolution: It is possible to end the running Java process by killing the particular Java process through the task manager when the DB installation process has been started.However, there is no way to roll back the work that has been carried out by the DB installer already. Depending on where you were in the DB installation process when you wanted to stop it you can rerun the same DB installation process from start without getting any errors. However, if the cre files have already been deployed, re-running the DB installer will result in errors. Therefore, it is best to start the DB installation process again on a freshly restored DB.
Issue:Users of IFS application may experience occasional login issues that are not persistent. Typically, after one or more attempts, users can log in successfully. It's common for users to find that they can log in again after waiting for some time. Resolution:This issue was resolved by setting the “idle time” to "UNLIMITED" in all Oracle profiles. Specifically, set the "idle time" to "UNLIMITED" for all profiles, which effectively disables the timeout feature. This was necessary because the timeout setting was not effective in our case, and actually caused issues when a specific value was set.To clarify, the idle timeout setting is typically used to manage sessions when dedicated connections are used between the middleware and the database. But IFS is using a session pool for that. As a result of that, IFS overrides the Idle timeout parameter from a client timeout parameter which we can find from the "System Parameters" window.To adjust the timeout, we followed these steps:Go to Solu
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
