Register xUI in ArcGIS Enterprise Portal

1. Confirm the requirements

• ArcGIS Enterprise 11.0 or later.
• An account with Portal administrator privileges.
• A purchased xUI production license.
• The xUI manifest built for your Experience Builder version.
• HTTPS and anonymous browser access to the hosted manifest.
• Azure Blob Storage CORS configured to allow your Portal origin.

2. Copy and test the manifest URL

1. Open the xUI Downloads page.
2. Expand the row matching your Experience Builder version.
3. Choose the xUI release you want to register.
4. Select Copy URL beside View manifest.
5. Select View manifest and confirm the JSON opens without a sign-in prompt.

For example:

https://xui.blob.core.windows.net/v21/0.7.1/manifest.json

3. Add the widget to Portal

1. Sign in to your ArcGIS Enterprise Portal as an administrator.
2. Select Content from the top navigation.
3. Open My Content.
4. Select New item or Add item, depending on your Enterprise version.
5. Choose Application.
6. Select Experience Builder widget.
7. Paste the xUI manifest URL into the URL field.
8. Click in the Title field. Portal should read the manifest and populate the title.

Name the registered version clearly

Use a title that identifies both the xUI and Experience Builder versions:

xUI 0.7.1 — Experience Builder 1.21

Suggested tags:

xUI, Experience Builder, Custom Widget, EXB 1.21, xUI 0.7.1

Suggested summary:

xUI custom widget release 0.7.1 for ArcGIS Experience Builder 1.21.
A valid xUI production license is required for deployment.

Complete the form and select Add item or Save.

4. Share xUI with its users

1. Open the new xUI item's details page.
2. Select Share.
3. Share it with the appropriate Portal groups or the organization.
4. Share with everyone only when it is intentionally used by a public application.
5. Select Save.

5. Verify xUI in Experience Builder

1. Open Experience Builder from your Enterprise Portal.
2. Create a test experience or edit an existing one.
3. Open the Insert widget panel.
4. Find the Custom group.
5. Confirm xUI appears, then add it to the experience.
6. Configure xUI and complete a functional test before using it in production.

6. Register a newer xUI release

Register each xUI release as a new Portal item instead of silently changing the previous registration:

Existing: xUI 0.7.1 — Experience Builder 1.21
New:      xUI 0.7.2 — Experience Builder 1.21

1. Register the new version using its new manifest URL.
2. Test the new widget in a nonproduction experience.
3. Move applications to the new version through your normal release process.
4. Retain the prior item temporarily for rollback.
5. When it is no longer needed, unshare or remove the older item.

7. Troubleshooting

Portal cannot read the manifest

• Open the manifest URL in a private or incognito browser window.
• Confirm it does not require authentication.
• Confirm the address uses HTTPS and returns JSON.
• Confirm Azure Blob Storage allows CORS requests from the exact Portal origin.
• Check the browser developer console for CORS, certificate, or 404 errors.

xUI does not appear in Experience Builder

• Confirm the item type is Experience Builder widget—not AppBuilder Extension.
• Confirm the item is shared with your account or organization.
• Confirm the widget is registered in the same Portal organization as the experience.
• Sign out and back in, then reopen Experience Builder.

xUI appears but does not load

• Confirm the xUI release matches the Enterprise Experience Builder version.
• Confirm all hosted widget resources are publicly accessible through HTTPS.
• Inspect the browser console and Network panel for blocked or missing resources.