I don’t have experience with configuring email or messaging in general in Cloud environments and will have get help from others on this topic. But you’ll still need to configure the MAIL_SENDER1 connector in a similar fashion as was done with Apps 10 in your Cloud instance (see below screen shot).From the Cloud training I’ve had to date I believe there will be an extra step on the host server to define a virtual port for use with the Kubernetes container, i.e. the container’s virtual port should defined and opened up for use to be associated with an actual port on the host server. I haven’t yet located documentation on that step and will have to defer to others on how exactly that can be done.I did manage to find the following in the Technical Documentation library on this topic:https://docs.ifs.com/techdocs/23r2/030_administration/010_security/040_iam_settings/060_smtp_email_server/#update_configuration MAIL_SENDER1 configuration in Cloud 23R2
This error can have varying causes. The 500 error message at login is a generic message.Since you have already checked on the deployments and found them to be “green” you could also run the mws-svr script which is found at the root directory of the middleware home of the host server where your application’s middleware is deployed. Be sure to run it as administrator. You’d use the same user credential as what you’ve used to log into the IFS Admin Console to run this script (you’ll be prompted for that user & password). Run this script with the STATUS option and ask for ALL when prompted.If this script replies and says “RUNNING” for all mws servers then you will have eliminated another possible cause of the error. But if any of the server responses show a status other than RUNNING you may need to restart or even reconfigure the mws. Restart can also be done by using the same mws-svr.exe script. Reconfigure is done with the IFS Installer application (found at the same location
Sayuru,FYI - I was trained as a Systems Engineer as part of the Consulting Services group some years ago. I’ve since moved over to IFS Unified Support and work in their ITAR vertical, specializing in Technical related issues.It would be helpful to know if you are an IFS employee, with a partner or work for an IFS customer. If you’re with IFS it would be good to know if you’re assigned to Unified Support, Success, R&D or other section of IFS.As far as general training, you can’t go wrong if you were to take the Middleware Administration courses both for the legacy IFS, Apps 10 as well as for IFS Cloud. Be sure to take all the Kubernetes / Docker training you can find for the Cloud infrastructure as well. There are other administrator / technical courses available in the IFS Academy application which you can find by searching there.There are multiple “add-on” features used with IFS such as Demand Planner, Constraint Based Scheduling, Print Agent, Business Reporter, Analysis Model
For Apps 10 you would need to ask for an add-on delivery to have the en-GB language additions to be sent and added to your Apps 10 build. Once this delivery’s been provided you could apply it to your existing Apps 10 environments using the same process as done for any other delivery. After this delivery were to be applied you’d then have en-GB added to the available languages of your instances.
Already have an account? Login
No account yet? Create an account
Enter your 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.
