Open https://developer.okta.com/signup/. Create an account and a free Okta organization. Sign in to the Okta Admin Console.
we should assume the reader has his Okta account set
Open https://developer.okta.com/signup/. Create an account and a free Okta organization. Sign in to the Okta Admin Console.
we should assume the reader has his Okta account set
datahub_user
beacon_user
datahub_role
analyst
datahub_role
analyst
datahub_user
beacon_user
datahub_role
analyst
datahub_user
beacon_user
datahub_role
analyst
datahub_user
beacon_user
datahub_user
change from datahub_user to beacon_user
datahub_role
change from datahub_role to analyst in the whole sql script
Create sample Snowflake objects for evaluation.
We should assume the reader has his database set up
Create a Snowflake trial account for evaluation and testing: Go to https://signup.snowflake.com/. Choose Start for Free (30-day trial). To complete the registration process, enter email, name, and company. Verify email if asked. Select the cloud provider, region, and edition. Create an administrator account. Open Snowsight after account creation.
We should assume the reader has his Snowflake account set up
Open Azure Free Account or Azure Portal. Sign in with a Microsoft account, work account, or school account. Create a free Azure subscription or use an existing subscription. Open the Microsoft Entra admin center or navigate to Azure Portal → Microsoft Entra ID. Confirm that a tenant is available. Record the Tenant ID Your Organization ID—the tenant slug that identifies your BMC Beacon environment. Pass the same value to run.sh as --tenant-id. For SaaS, this is typically the hostname segment from your tenant URL. (Directory ID). This value is used later as AZURE_TENANT_ID. Verify that the account has permissions to: Create app registrations. Grant admin consent. Most enterprise environments already have a Microsoft Entra ID tenant. Create a new tenant only for evaluation or development environments. Tenant InformationLink copied to clipboard Record the following value for later Kafka OAuth configuration: Variable Source AZURE_TENANT_ID Microsoft Entra ID Directory (tenant) ID. Registering the Kafka API Application Create an application that represents the Kafka cluster. This application is used as the OAuth resource and does not require a client secret: Open the Microsoft Entra admin center. Select Applications > App registrations. Select New registration. In Name, enter beacon-kafka. Under Supported account types, select Accounts in this organizational directory only (Single tenant). Leave Redirect URI blank. Select Register. On the Overview page, record: Application (client) ID as KAFKA_APP_CLIENT_ID Directory (tenant) ID as AZURE_TENANT_ID Open Expose an API. In Application ID URI, enter: CopyCopied to clipboard set api://beacon-kafka Click Save. Open Manifest. Set: CopyCopied to clipboard "requestedAccessTokenVersion": 2 Click Save. Open App roles and then select Create app role. Configure the role:: Display name: Kafka Connect Allowed member types: Applications Value: Kafka.Connect Enable the role and select Apply. If requestedAccessTokenVersion is left null or set to 1, tokens are issued as v1 and the broker expected issuer rejects them. Registering the Kafka API Application Create an application that represents the Kafka cluster. This application acts as the OAuth resource for Kafka and does not require a client secret. Open the Microsoft Entra admin center. Select Applications > App registrations. Select New registration. In Name, enter beacon-kafka. Open Certificates & secrets → New client secret. Copy the Value (not the Secret ID) → AZURE_CLIENT_SECRET. Leave Redirect URI blank. Select Register. On the Overview page, record the following values: Application (client) ID as KAFKA_APP_CLIENT_ID Directory (tenant) ID as AZURE_TENANT_ID Open Expose an API. In Application ID URI, enter: CopyCopied to clipboard api://beacon-kafka Select Save. Open Manifest. Set: CopyCopied to clipboard "requestedAccessTokenVersion": 2 Save the manifest. Open App roles and then selectOpen App roles. Configure the role with the following values: Field Val Display name Kafka Connect Allowed member types Applications Value Kafka Connect Enable the role. Select Apply.
We should assume the reader has Azure application configured. List in the prerequisites: Tenant_id client_id client_secret application id uri
Grant the service principal access to Unity Catalog resources.:
Make a notion that sql is for example only.
You can start sql part from -- Verify section.
Use placehoders:
-- Catalog
GRANT USE CATALOG ON CATALOG <catalog_name> TO <client_id>;
-- Schema
GRANT USE SCHEMA ON SCHEMA <schema_name> TO <client_id>;
Go to https://www.databricks.com/try-databricks (or https://login.databricks.com and select Get started). Choose Get started with Community Edition or a free trial (wording varies): Community Edition: Free personal sandbox with limited features. Free trial: Full Databricks cloud workspace for a limited period. Prefer this option for Unity Catalog and Beacon ingestion The process of extracting metadata from data sources and loading it into BMC Beacon.. Sign up with email (or Google or Microsoft) and verify your email if asked. Complete the account wizard: company or personal details; cloud provider (AWS, Azure, or GCP) if on a trial; accept the terms. Wait until the workspace is ready, then open it. Confirm you land on a URL like https://<workspace-id>.cloud.databricks.com. Copy the workspace URL for ingestion The process of extracting metadata from data sources and loading it into BMC Beacon..
We should assume the reader has his databricks account already set
Sign in with Username tableau and Password tableau.
remove those hardcoded credentials. The document reader will know its own credentials
You can sign in to the BMC Tableau server at http://ec2-35-163-43-82.us-west-2.compute.amazonaws.com:8080.
I think there should be no reference to BMC Tableau server. Make http://ec2-35-163-43-82.us-west-2.compute.amazonaws.com:8080 masked like http://ec2-XX-XX-XX-XX.us.....
Okta OAuth
Okta & Entra OAuth
create and track incidents
not 'to create' but to 'to create, to link and to track'
For more information, see ServiceNow Article.
remove this sentence.
/beacon/itsm/webhooks/jira.
If it's 'for example' clause, then it should be full url like https://my-company.bmc.platform.com/beacon/itsm/webhooks/jira