Hello,

We are running on Experience Portal 7.0.1, but we have new application being developed on Orchestration Designer 7.1. In one server environment the licensing fails and calls don't work. On another environment the system licensing goes into grace period. Logs are below. We have OD 7.0.1 applications work fine with the same weblm that is not working with OD 7.1.
Questions:
1) Can we run OD7.1 application on EP 7.0.1? Any known issues with this?
2) Are there any licensing issues between OD7.1 and EP 7.0.1?
3) Any issues with weblem with our setup?

>>Log from server that is not working at all due to license issue.
22/03/2017 10:08:38:780 | DD685F5C59C20B000E31E6CA50301DC0 | INFO - B5F6D6D8675ECBB64DADEE684EC2EEF5:/CallHandler : runtime_platform : Experience Portal
22/03/2017 10:08:38:780 | DD685F5C59C20B000E31E6CA50301DC0 | INFO - B5F6D6D8675ECBB64DADEE684EC2EEF5:/CallHandler : runtime_asr : Nuance 9.0 (Quantum)
22/03/2017 10:08:38:780 | DD685F5C59C20B000E31E6CA50301DC0 | DEBUG - B5F6D6D8675ECBB64DADEE684EC2EEF5:/CallHandler : Refreshing License
22/03/2017 10:08:38:780 | DD685F5C59C20B000E31E6CA50301DC0 | INFO - B5F6D6D8675ECBB64DADEE684EC2EEF5:/CallHandler : Acquiring Avaya Platform runtime license
22/03/2017 10:08:38:795 | DD685F5C59C20B000E31E6CA50301DC0 | INFO - B5F6D6D8675ECBB64DADEE684EC2EEF5:/CallHandler : Using license check timeout :0
22/03/2017 10:08:59:824 | DD685F5C59C20B000E31E6CA50301DC0 | INFO - B5F6D6D8675ECBB64DADEE684EC2EEF5:/CallHandler : Runtime :false
22/03/2017 10:08:59:824 | DD685F5C59C20B000E31E6CA50301DC0 | INFO - B5F6D6D8675ECBB64DADEE684EC2EEF5:/CallHandler : IC :false
22/03/2017 10:08:59:824 | DD685F5C59C20B000E31E6CA50301DC0 | INFO - B5F6D6D8675ECBB64DADEE684EC2EEF5:/CallHandler : CTI :false
22/03/2017 10:08:59:824 | DD685F5C59C20B000E31E6CA50301DC0 | DEBUG - B5F6D6D8675ECBB64DADEE684EC2EEF5:/CallHandler : License is bad, grace period expired
22/03/2017 10:08:59:824 | DD685F5C59C20B000E31E6CA50301DC0 | DEBUG - B5F6D6D8675ECBB64DADEE684EC2EEF5:/CallHandler : License refresh timer started

>>Logs where the licensing goes into grace period.:
23/03/2017 11:19:17:154 | 23872F17543570E9CCF7BB6F14D45E68 | INFO - 7032BA28B5FF3A808BC89F9D9D80FEBD:/CallHandler : Acquiring Avaya Platform runtime license
23/03/2017 11:19:17:154 | 23872F17543570E9CCF7BB6F14D45E68 | DEBUG - 7032BA28B5FF3A808BC89F9D9D80FEBD:/CallHandler : PlatformParams:getPlatformParams: __VPVarGlobalDate is 1488397641970
23/03/2017 11:19:17:154 | 23872F17543570E9CCF7BB6F14D45E68 | DEBUG - 7032BA28B5FF3A808BC89F9D9D80FEBD:/CallHandler : PlatformParams:getPlatformParams:Timestamp is 03/01/17 13:47:21
23/03/2017 11:19:17:154 | 23872F17543570E9CCF7BB6F14D45E68 | DEBUG - 7032BA28B5FF3A808BC89F9D9D80FEBD:/CallHandler : License: Use the license server url in VPMS instead - https://weblm:52233/WebLM/LicenseServer
23/03/2017 11:19:17:154 | 23872F17543570E9CCF7BB6F14D45E68 | INFO - 7032BA28B5FF3A808BC89F9D9D80FEBD:/CallHandler : Using license check timeout :0
23/03/2017 11:19:17:154 | 23872F17543570E9CCF7BB6F14D45E68 | INFO - 7032BA28B5FF3A808BC89F9D9D80FEBD:/CallHandler : Runtime :false
23/03/2017 11:19:17:154 | 23872F17543570E9CCF7BB6F14D45E68 | INFO - 7032BA28B5FF3A808BC89F9D9D80FEBD:/CallHandler : IC :false
23/03/2017 11:19:17:154 | 23872F17543570E9CCF7BB6F14D45E68 | INFO - 7032BA28B5FF3A808BC89F9D9D80FEBD:/CallHandler : CTI :false
23/03/2017 11:19:17:154 | 23872F17543570E9CCF7BB6F14D45E68 | DEBUG - 7032BA28B5FF3A808BC89F9D9D80FEBD:/CallHandler : Remaining grace period 538209790
23/03/2017 11:19:17:154 | 23872F17543570E9CCF7BB6F14D45E68 | DEBUG - 7032BA28B5FF3A808BC89F9D9D80FEBD:/CallHandler : License is bad, allowing grace period
23/03/2017 11:19:17:154 | 23872F17543570E9CCF7BB6F14D45E68 | DEBUG - 7032BA28B5FF3A808BC89F9D9D80FEBD:/CallHandler : License refresh timer started

Best Regards,
Miki

1 - Yes
2 - see 3.
3 - see http://www.devconnectprogram.com/forums/posts/list/19126.page

If contacting the weblm server fails, then you have a 30 day grace period. It looks like one server has used up that grace period while the other has not.

Note that in one case no license server URL has been configured in the OD runtimeconfig and there fore we use the license server that the EPM is using

License: Use the license server url in VPMS instead - https://weblm:52233/WebLM/LicenseServer

Are you sure you have a license on that server for OD? My guess is that the issue is related to #3 above.

Thanks for the information. I'm pretty sure we support TLS, but we will double check.

The system where the grace period ended is the new system we built. What does the system use to track whether to allow or deny grace period? Is it based on IP, host, etc.?

Thanks,
MY

When a bad license is encountered the time + 30 days is recorded. If, via the refresh, a good license is seen before 30 then the value is set to 0. When the current time reaches the expiration, then the runtime will stop. This is recorded in the ddconfig.xml.