This could probably be a mismatch in between your App10 UPD and the TAS version you have installed. Make sure you have upgraded the TAS to the correct version which was delivered with your current Apps-10 Update OR with the latest Mobile Framework (FNDMOB) delivery you have installed.
Hi,You can refresh the credentials from the app itself as @anmise have pointed out.Also, there’s another way we can extended the logged in period. Increasing this will not increase CPU usage, this will only have the user logged in for a longer period.As per RnD, this timeout is based on the refresh token life time. This can be configured in the MWS.However, changing this will affect all the applications. (Eg: Both Enterprise Explorer and mobile applications timeout.)If the customer is okay with that, they can increase the refresh token life time. Please refer to this documentation on the steps to set the token life-time.https://<server>:<port>/f1docs/apps10/Foundation1/040_administration/210_security/015_authentication/040_configure_DBIDP/default.htm#Configure_behaviour_through_startup_paramtersNote: For <server>:<port>, use the server and port of the IFS Home page You can add startup parameters from the following path in the MWS Admin Console.MWS Admin-Console
Hi,Could you change the “Logoff Uncommit” rule parameter to 30 and check?Best regards,Pubudu
Hi,Please check the “enabled” SSL/TLS protocols in your Touch Apps Server as well. Since you have only allowed, TLS-1.2 in MWS, TAS should also be allowed to communicate with the same protocol.To check the enabled SSL/TLS protocols in your TAS server, please run a diagnostic by installing the following “IIS Crypto” tool in Touch Apps Server (machine). https://www.nartac.com/Products/IISCrypto/After running the scan, you can modify the SSL/TLS configuration as needed from this tool as well.Best regards,Pubudu
Hi Atheeq, Internally we could check this in the Archive by viewing the "ServiceEngApp.app" file in the location below.\\corpnet\files\Archive\Archive10\mwo\core\mwo 2.0.0\<UPD_Id>\model\mwoNote: you must replace the <UPD_Id> in above path accordingly.eg: For upd-11 the path would be: \\corpnet\files\Archive\Archive10\mwo\core\mwo 2.0.0\mwo\core\mwo 2.0.0\UPD11\model\mwoOnce you open the "ServiceEngApp.app" file in a text editor, you can see the corresponding version number as below. Not sure if there’s a simple way around this though..Best regards,Pubudu
Hi @CUCSOLUTIONS Some IFS mobile apps might be using specific SSL protocols when making connections with MWS via TAS server. May I know which IFS application version this is? Also, what are the mobile apps that seem to be not working when SSL-3 and SSL-2 are disabled?/Pubudu
Hi @VinuP,We cannot use comma separated values for the HierarchicalDatabaseMatrixId as per the current design. Instead, we must create separate PSO profiles if multiple HTMs are being used, Then, reference the Profile on the Dataset's Input_Reference when sending the xml in to the scheduling system.‘NA’ is of course the correct matrix-Id value we should use when using an NA V3 HTM.To narrow down the issues related to the warnings here, you may:Verify if IFS PSO services have been configured to access the HTM database using the correct user in the “connection string”. This can be done by using the installer to reinstall the services and setting the connection string on the databases page. Verify if the PSO parameter 'TravelCalculationOption' is set to 'HierarchicalTravelMatrix' Verify if the ‘HierarchicalDatabaseMatrixID’ is set to the correct value (eg: NA) Hope this will help.Best regards,Pubudu
Hi @TatKhandM You may need to run the PSO initialization for the active scheduling dataset from FSM, once you’ve marked a Person in FSM as a PSO system user.Best regards,Pubudu
Hi @nwallk,Incoming broadcast messages from PSO can be checked using “scheduling output history” screen in FSM. For this, we must enable the scheduling app param ENABLE_OUTPUT_LOGGING = ‘Y’ as well.Best regards,Pubudu
Hi,In PSO Administration Workspace under "Applications" screen, please check whether there are values exist for the remoting string column, for each and every SIM service instance.If not, you will need to restart the SIM service as a workaround.Also, the remoting string handling has been improved in PSO 6.9.0.18. Upgrading to this version (or later) will fix the issue.Best regards,Pubudu
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.
