|
|
(117 intermediate revisions by 5 users not shown) |
Line 1: |
Line 1: |
− | {{Article
| + | #REDIRECT [[ATC/ProvisioningMulticloudCX]] |
− | |Standalone=Yes
| |
− | |DisplayName=Provisioning PureEngage Hybrid Integrations
| |
− | |Platform=PureEngage
| |
− | |TocName=Provisioning
| |
− | |ComingSoon=No
| |
− | |Tags=Integration
| |
− | |Dimension=ATC/Current/WDEPlugin/Configure_GenAdmin
| |
− | |Context=Manually provision PureCloud (by creating an Organization) and PureEngage Premise (using Genesys Administrator Extension).
| |
− | |Section={{Section
| |
− | |sectionHeading=About Provisioning
| |
− | |Type=Unstructured
| |
− | |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.
| |
− | | |
− | | |
− | | |
− | | |
− | 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
| |
− | }}
| |
− | }}
| |
Latest revision as of 18:40, February 10, 2022