I changed the hostname so that it now ends in .<domain> which got past the previous error. Now when I run cluster.sh on a worker node it gets down to:[Wed Jul 19 09:02:27 CDT 2023] - INFO : <Jul 19, 2023 9:02:27 AM CDT> <Info> <Security> <BEA-090909> <Using the configured custom SSL Hostname Verifier implementation: weblogic.security.utils.SSLWLSHostnameVerifier$NullHostnameVerifier.>[Wed Jul 19 10:00:02 CDT 2023] - SEVERE : Operation takes too long time java.util.concurrent.TimeoutException at ifs.application.installer.util.main.MainBase.run(MainBase.java:154) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505)I suspect the timeout has to do with the asterisk in the certificate *.<domain>. Is there a way past this error?
I put this aside for a while and I’m back to looking at it. I created the folder ifsdoc in <ifs_home> and made an empty file named doc_node.conf in the folder. That allowed the script <ifs_home>/instance/<instance>/bin/cluster.sh to get past the error: Warning: Could not find file <ifs_home>/ifsdoc/doc_node.conf to copy.So now the cluster.sh script runs longer and I hit this error: 2023-07-18 08:32:13 [INFO ] <Jul 18, 2023 8:32:13 AM CDT> <Warning> <Security> <BEA-090504> <Certificate chain received from <hostname>.<domain> - 10.22.183.200 failed hostname verification check. Certificate contained *.<domain> but check expected <hostname>.<domain>2023-07-18 08:32:14 [INFO ] Exception when running method addMachine2023-07-18 08:32:14 [INFO ] Call to addMachine was not successful.Any thoughts on how to get the script to run to completion?
We are running UPD 8013 of Apps 10.
It was an open ended question from my Product Owner asking if it was possible. I haven’t heard what the users would want instead.
I saw the option to setup a ExternalNavigationLink custom command. The issue with that approach is that it is the same URL with parameters for the entire page. I’m working on the Document Revision page and I would like the URL to be different based on the revision that is selected. Unfortunately the URL is entirely different between revisions and not the same base URL that can be customized with parameters. Any thoughts on how to achieve this?
Correction, we are on update 9 currently.
We applied update 10 to our development environment. Now when we restart the server the changes that were only visible in Page Designer and now visible on the standard page. Clearing the meta data cache using the steps over here: sometimes works instead of having to do a full reboot.
Sounds like there’s some kind of cache issue if a reboot solved it. I haven't seen this happen before. Can you try using the following for the screen you are testing on? https://<server>:<port>/main/ifsapplications/web/server/clearmetadatacache?VALUE=<client_model> When you publish, can you have Chrome Debug open and see if there are any errors? I am not seeing errors in the debug console when publishing.The screen updated after pointing the browser to that URL. Thank you so much. This workaround will get us back going.
I gave that a shot and I’m not seeing a change in behavior after following that clearmetadatacache link.We did reboot the server yesterday. All of the changes that were visible in Page Designer and not on the screen were visible on the screen after the reboot. New changes made in Page Designer after the reboot are not publishing to the screen. Rebooting the server to see every change isn’t a viable workaround. Any thoughts on what needs to be done to get changes made in Page Designer to publish to the screen?
Is this for a specific screen, if so which screen? I’ve recreated this issue on multiple screens. What type of field is it? I’ve tried fields, lookup, tabs, groups, and selectors. None of the changes made in Page Designer are applying to the page. Are you adding the fields to the Global context or a user-defined context? I am working entirely in the global context.
On IFS 10 update 7 the field would display after waiting a couple of hours. We recently updated to 10 update 9 and now after a couple of hours the field is only showing in Page Designer and not on the page even after waiting a couple of hours.
I am still struggling with this. Does anyone have thoughts on how to configure conditional fields in Aurena? The environment I’m working in has been updated to IFS 10 update 9.
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.