Update nexus: fix conflicts and sync local changes

This commit is contained in:
Shen Wei
2026-04-26 12:06:50 +08:00
parent 191797c01b
commit f09834b5a5
2443 changed files with 254323 additions and 255154 deletions

View File

@@ -1,168 +1,168 @@
# Process-for-license_709426883
Here you can fine a centralized licensing provisioning documentation:
[Edit Document](/plugins/servlet/confluence/editinword/709426883/attachments/Centralized_Licensing_Provisioning_Guide.docx)
Centralized Licensing Provisioning Documentation
## 1\. Where Licensing Provisioning Tickets Are Logged and Picked Up
Primary Source: MF SaaS Unified Tool (UT system)
<EFBFBD><EFBFBD> [MF SaaS Unified Tool](https://ut.ct-us2.saas.microfocus.com/sm/index.do)
\- Monitor emails from: [saas-support-do-not-reply@saas.microfocus.com](mailto:saas-support-do-not-reply@saas.microfocus.com) if the tickets are assigned to the user.
\- Look for subject lines like:
"Ticket SR00389815 has been assigned to you - OrderFulfillment - UpdateAccount..."
\- Monitor Teams channel: ESM SaaS Order Provision Working Group
⚠️ Note 1: The new user must be added to the chat. Request access from an existing user in the chat
⚠️ Note 2: Ignore ad-hoc requests via Teams from Customer Success Managers (CSMs).
## 2\. Reference Documentation
Confluence Articles for basic knowledge:
\- [ESM Cloud Ops New User Guide](https://confluence.opentext.com/pages/viewpage.action?spaceKey=ICSD&title=ESM+Cloud+Ops+-+New+User+Guide)
\- [ITOM ESM License Units Conversion](https://confluence.opentext.com/display/ICSD/ITOM+ESM+License+Units+conversion)
\- [ESM License Generation Detail](https://confluence.opentext.com/display/ICSD/ESM+license+generation+detail)
Control Tower:
\- [Control Tower Orders example](https://backoffice.saas.microfocus.com/home/bl/desktop.html?TENANTID=1#/ofs/orders/SB_712674)
\- Using filters by Order ID, Account Name, or Product from “ More filters ” if known usually are mentioned in the UT ticket attachment.
![](plugins/servlet/benryanconversion)
## 3\. Required Access Accounts
Pre-requisites:
✅ Get AWS access before BO access
✅ Get INFRA account before Unified Tool access
All sections below refer to the New User Guide:
| Account Type | Section in Guide |
| --- | --- |
| AWS Console | #1 |
| INFRA | #11 |
| SaaS Unified Tool (UT) | #12 |
| PCS WW (SMAX) | #5.1 |
| PCS EU SMAX | #5.2 |
| X4X (Internal Cloud Service) | #6 |
| Suite-Admin Personal Accounts | #13 |
UCMDB JMX Access: Request account from Alin Zirbo
## 4\. Useful Links
Tool Link/Example
[Control Tower Homepage](https://backoffice.saas.microfocus.com/home/bl/desktop.html?TENANTID=1#/dashboard)
[Unified Tool Homepage (UT)](https://ut.ct-us2.saas.microfocus.com/sm/index.do)
SMAX BO - https://<farm-name>-smax.saas.microfocus.com/bo
OO BO - https://oo.<farm-name>-smax.saas.microfocus.com/autopass/ls/license/tenant
UCMDB JMX Console - https://cms.<farm-name>-smax.saas.microfocus.com/jmx-console/
CMS BO - https://cms.<farm-name>-smax.saas.microfocus.com/ucmdb-browser/?customerID=<tenant#>&auth=db
[X4X Agent Interface](https://us2-smax.saas.microfocus.com/saw/ess?TENANTID=202385354)
[License SharePoint](https://opentextcorporation.sharepoint.com/sites/MFI-SMAXSaaSDevOps/Shared%20Documents/Forms/AllItems.aspx?isAscending=false&id=%2Fsites%2FMFI%2DSMAXSaaSDevOps%2FShared%20Documents%2F2%2DESM%20SaaS%20Customer%2FLicense&sortField=Modified&viewid=250c668f%2D9c3b%2D4ad9%2Db164%2D3d6ac18e50c3)
[PowerBI License Status](https://app.powerbi.com/groups/me/reports/cf509ffe-325f-4c1b-a507-44b93e6d85ca/ReportSection83e2db59c3f5174e72d9?experience=power-bi)
## 5\. Licensing Provisioning Process
## Steps for SMAX & AMX Licensing
\- Open SaaS Unified Tool (UT)
\- Go to Service Catalog > Search Customer Request, open the SD# (e.g. SD00499039). Or if SR# known, open it directly.
\- Download attached.xls file
\- Extract the details:
- ESM farm, name of the customer, Tenant ID (correlated to CT Tenant ID) and identify the correct Tenant ID for ITOM products within PowerBI
\- Open SMAX BO for the correct farm
\- Locate Tenant ID or name of the customer
\- In Excel file the license row holds the xml information that needs to be uploaded in SMAX BO, by copying the xml information and store it locally in a new xml file.
(eg. customerName\_SMAX\_40\_Premium\_licenses\_prod.xml)
\- In SMAX BO:
- Licenses > Upload > Select environment and import the xml created previously.
- Confirm “Success” status
\- Option 1:
- Open the license uploaded, go to Allocation, use the Concurrent User or Names user license, Click on Allocate and Add to license pool
\- Option 2:
- Go to License-Pools and identify the customers pool or create a new pool
- Open the relevant License Pool > Assignments and select the license that was uploaded previously and add the Capacity and Tenant
\- Go to the customer tenant to double check the licenses added.
\- Take a screenshot and attach it to the UT ticket and Teams Channel for Tenant provisioning
\- Closing the UT ticket will close the Control Tower order automatically.
\- Customer notification:
- Use X4X -> Set License Renewal offering
- Fill in: Farm, Customer, Tenant ID, license details
\- Revoke the expired lienses:
- Bo > Tenants > Licenses > Select the license > Revoke & Save
\- Upload the Excel file,.xml and Screenshots to SharePoint.
## CMS Licensing (UCMDB)
Installation
\- Open the UT ticket & download the attachment
\- Open UCMDB JMX console using suite-admin credentials
\- Search: addLicenseToPool
- Enter the license key from the excel file
- Click Invoke
\- Check via viewLicenseCapacity
- Locate installed key
- In Allocation Form:
- Set customerID = SMAX Tenant ID
- NOTE: To identify the SMAX Tenant ID check the PowerBI link
- Set featured (first in license block)
- Enter full capacity
\- Alternatively use allocateLicenseCapacity
\- Validate via viewLicenseCapacity
## CMS License Check (UCMDB Validation)
\- Open CMS UCMDB in Browser
\- Log in using cms-admin/password from Parameter Store if existing, or smax-admin/password from the correct Farm
\- Click on question icon? -> About and check the Licenses and capacity
# Process-for-license_709426883
Here you can fine a centralized licensing provisioning documentation:
[Edit Document](/plugins/servlet/confluence/editinword/709426883/attachments/Centralized_Licensing_Provisioning_Guide.docx)
Centralized Licensing Provisioning Documentation
## 1\. Where Licensing Provisioning Tickets Are Logged and Picked Up
Primary Source: MF SaaS Unified Tool (UT system)
<EFBFBD><EFBFBD> [MF SaaS Unified Tool](https://ut.ct-us2.saas.microfocus.com/sm/index.do)
\- Monitor emails from: [saas-support-do-not-reply@saas.microfocus.com](mailto:saas-support-do-not-reply@saas.microfocus.com) if the tickets are assigned to the user.
\- Look for subject lines like:
"Ticket SR00389815 has been assigned to you - OrderFulfillment - UpdateAccount..."
\- Monitor Teams channel: ESM SaaS Order Provision Working Group
⚠️ Note 1: The new user must be added to the chat. Request access from an existing user in the chat
⚠️ Note 2: Ignore ad-hoc requests via Teams from Customer Success Managers (CSMs).
## 2\. Reference Documentation
Confluence Articles for basic knowledge:
\- [ESM Cloud Ops New User Guide](https://confluence.opentext.com/pages/viewpage.action?spaceKey=ICSD&title=ESM+Cloud+Ops+-+New+User+Guide)
\- [ITOM ESM License Units Conversion](https://confluence.opentext.com/display/ICSD/ITOM+ESM+License+Units+conversion)
\- [ESM License Generation Detail](https://confluence.opentext.com/display/ICSD/ESM+license+generation+detail)
Control Tower:
\- [Control Tower Orders example](https://backoffice.saas.microfocus.com/home/bl/desktop.html?TENANTID=1#/ofs/orders/SB_712674)
\- Using filters by Order ID, Account Name, or Product from “ More filters ” if known usually are mentioned in the UT ticket attachment.
![](plugins/servlet/benryanconversion)
## 3\. Required Access Accounts
Pre-requisites:
✅ Get AWS access before BO access
✅ Get INFRA account before Unified Tool access
All sections below refer to the New User Guide:
| Account Type | Section in Guide |
| --- | --- |
| AWS Console | #1 |
| INFRA | #11 |
| SaaS Unified Tool (UT) | #12 |
| PCS WW (SMAX) | #5.1 |
| PCS EU SMAX | #5.2 |
| X4X (Internal Cloud Service) | #6 |
| Suite-Admin Personal Accounts | #13 |
UCMDB JMX Access: Request account from Alin Zirbo
## 4\. Useful Links
Tool Link/Example
[Control Tower Homepage](https://backoffice.saas.microfocus.com/home/bl/desktop.html?TENANTID=1#/dashboard)
[Unified Tool Homepage (UT)](https://ut.ct-us2.saas.microfocus.com/sm/index.do)
SMAX BO - https://<farm-name>-smax.saas.microfocus.com/bo
OO BO - https://oo.<farm-name>-smax.saas.microfocus.com/autopass/ls/license/tenant
UCMDB JMX Console - https://cms.<farm-name>-smax.saas.microfocus.com/jmx-console/
CMS BO - https://cms.<farm-name>-smax.saas.microfocus.com/ucmdb-browser/?customerID=<tenant#>&auth=db
[X4X Agent Interface](https://us2-smax.saas.microfocus.com/saw/ess?TENANTID=202385354)
[License SharePoint](https://opentextcorporation.sharepoint.com/sites/MFI-SMAXSaaSDevOps/Shared%20Documents/Forms/AllItems.aspx?isAscending=false&id=%2Fsites%2FMFI%2DSMAXSaaSDevOps%2FShared%20Documents%2F2%2DESM%20SaaS%20Customer%2FLicense&sortField=Modified&viewid=250c668f%2D9c3b%2D4ad9%2Db164%2D3d6ac18e50c3)
[PowerBI License Status](https://app.powerbi.com/groups/me/reports/cf509ffe-325f-4c1b-a507-44b93e6d85ca/ReportSection83e2db59c3f5174e72d9?experience=power-bi)
## 5\. Licensing Provisioning Process
## Steps for SMAX & AMX Licensing
\- Open SaaS Unified Tool (UT)
\- Go to Service Catalog > Search Customer Request, open the SD# (e.g. SD00499039). Or if SR# known, open it directly.
\- Download attached.xls file
\- Extract the details:
- ESM farm, name of the customer, Tenant ID (correlated to CT Tenant ID) and identify the correct Tenant ID for ITOM products within PowerBI
\- Open SMAX BO for the correct farm
\- Locate Tenant ID or name of the customer
\- In Excel file the license row holds the xml information that needs to be uploaded in SMAX BO, by copying the xml information and store it locally in a new xml file.
(eg. customerName\_SMAX\_40\_Premium\_licenses\_prod.xml)
\- In SMAX BO:
- Licenses > Upload > Select environment and import the xml created previously.
- Confirm “Success” status
\- Option 1:
- Open the license uploaded, go to Allocation, use the Concurrent User or Names user license, Click on Allocate and Add to license pool
\- Option 2:
- Go to License-Pools and identify the customers pool or create a new pool
- Open the relevant License Pool > Assignments and select the license that was uploaded previously and add the Capacity and Tenant
\- Go to the customer tenant to double check the licenses added.
\- Take a screenshot and attach it to the UT ticket and Teams Channel for Tenant provisioning
\- Closing the UT ticket will close the Control Tower order automatically.
\- Customer notification:
- Use X4X -> Set License Renewal offering
- Fill in: Farm, Customer, Tenant ID, license details
\- Revoke the expired lienses:
- Bo > Tenants > Licenses > Select the license > Revoke & Save
\- Upload the Excel file,.xml and Screenshots to SharePoint.
## CMS Licensing (UCMDB)
Installation
\- Open the UT ticket & download the attachment
\- Open UCMDB JMX console using suite-admin credentials
\- Search: addLicenseToPool
- Enter the license key from the excel file
- Click Invoke
\- Check via viewLicenseCapacity
- Locate installed key
- In Allocation Form:
- Set customerID = SMAX Tenant ID
- NOTE: To identify the SMAX Tenant ID check the PowerBI link
- Set featured (first in license block)
- Enter full capacity
\- Alternatively use allocateLicenseCapacity
\- Validate via viewLicenseCapacity
## CMS License Check (UCMDB Validation)
\- Open CMS UCMDB in Browser
\- Log in using cms-admin/password from Parameter Store if existing, or smax-admin/password from the correct Farm
\- Click on question icon? -> About and check the Licenses and capacity