Hi aNm, What was your problem? Did you not use the solutionset.yaml file during the installation? I don´t understand the installation procedure…. If in the initial installation you do not put solutionset.yaml everything is installed as TRUE and it installs all the Kubs that you do not need (for example in my case Maintenix)… How is this fixed and what is the correct procedure? Thanks! Hi!I used the solutionset.yaml in every installation. But if U just install with build-home archive, even with the solutionset.yaml file, U will get all components installed and TRUE… etcU need to install 0 delivery (1.0.0). It will fix all this stuff.Maybe it was just an issue of 22.2.3 version.
It turned out that after installing the environment, the first step was to install the 1.0.0 distribution. 🤦 It is a pity that this is not written in the documentation.
https://docs.ifs.com/techdocs/22r2/070_remote_deploy/030_patching_system/100_solution_set/#installer_handling_of_solutionsetyaml_for_middle_tier As mentioned in this page: you can update the solution set file and trigger a delivery build: Adding or modifying a solution set must be done as a delivery. Such delivery might only contain the solutionset.yaml file as input, but it will generate an install.tem for redeploy of all clients and projections. Can u trigger a delivery build and see? Unfortunately, it did not help. @aNm were you able to solve the issue, if so please mark as answered then this information will help to someone else as well. Of course. I will share the solution if I find it.
Is there any possibility to reconfigurate components statement without fully reinstallation?Because it seems that even completely reinstalling the environment does not solve the problem. I have installed 3 environments, and on each of them this problem occurs.As I mantioned before, installer founds file and attached it:INFO: Remote solution solution set file found and is added C:\ifsremote\ifsroot\deliveries\build-home\ifsinstaller\solutionset.yaml Thank you for your participation!
What do you mean ALL components in ACTIVE state? where? In Module_Tab? Now in Cloud we install all components irrespective of the content of solution set. /Harshini Hi!I mean that all 233 components in “Solution Manager>System Information and Utilities>Installed Components” are in ACTIVE state. This can be seen from the attached screenshot in first post. There is a filter by state Active=NO and no data below.In my solutionset.yaml file, 159 components are set to False.I checked Module_tab in DB and I have all modules ACTIVE=trueIs it normal? Solutionset.yaml file placed in C:\ifsremote\ifsroot\deliveries\build-home\ifsinstallerThe installer log telling me:INFO: Remote solution solution set file found and is added C:\ifsremote\ifsroot\deliveries\build-home\ifsinstaller\solutionset.yaml
It seems that I did not fully explain the situation correctly.We have ALL components in Active state. Even those that are listed as False in the solutionset file.And can be this issue related to update errors? Thanks!
So, no one knows how to limit access to IFS Cloud with one active session per user?
How to limit one user’s login from multiple devices? In previous versions of IFS, it was not possible to log in under one user simultaneously from different devices. In IFS Cloud, it is possible. This worries our clients. Just out of curiosity, what is their concern with this? Violation of security requirements, obviously. Security requirements vary from company to company and are sometimes very confusing.
I want to understand - maybe this is normal behavior for the IFS cloud? Maybe this table is now obsolete?
Look for a table named FND_Client_logon_tab. Unfortunately, this table is empty.We’re using IFS Cloud 22R2 - if it matters.
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.
