Difference between revisions of "Draft: PEC-Hybrid/Current/Admin/About"
From Genesys Documentation
Line 13: | Line 13: | ||
|anchor=About | |anchor=About | ||
|freetext=To support the different authentication mechanisms in PureCloud Integration, you must create a transaction object in Genesys Configuration Server under the environment and associated script folder with the following data. PureEngage On-Premises Services, Components, and UIs will use this information to authenticate with the PureCloud Common Services and UIs. | |freetext=To support the different authentication mechanisms in PureCloud Integration, you must create a transaction object in Genesys Configuration Server under the environment and associated script folder with the following data. PureEngage On-Premises Services, Components, and UIs will use this information to authenticate with the PureCloud Common Services and UIs. | ||
+ | |||
Use Genesys Administrator Extension to manually create all of the PureCloud Common Service–related configuration information in Configuration Server at the Tenant level. | Use Genesys Administrator Extension to manually create all of the PureCloud Common Service–related configuration information in Configuration Server at the Tenant level. | ||
|Status=No | |Status=No |
Revision as of 17:48, May 15, 2019
This is a draft page; the published version of this page can be found at PEC-Hybrid/Current/Admin/About.
Manually provision PureCloud (by creating an Organization) and PureEngage Premise (using Genesys Administrator Extension).