Getting Started with Automic SaaS for Administrators

Your company receives several key documents and emails upon subscribing to Automic SaaS. The Welcome to Automic SaaS email stands out, providing essential details like your account information, default system name, endpoint links, and initial credentials. The SaaS Listing document also merits close review, as it outlines your subscription scope and licensed features.

Store these materials securely, as they are sent only once.

Important!

Register on theBroadcom Support Portal if you haven't already.
Subscribe to the Broadcom's Service Status Portal for alerts on availability, performance issues, and maintenance.
Review and bookmark the Automic SaaS Upgrade Schedule to plan for release cycles and downtime.

For more information, see Automic SaaS Service Description .

Disclaimer:

Automic SaaS and Automic Automation follow slightly different release cadences. As a result, certain features described in the product documentation may not yet be available in your environment yet. This discrepancy occurs only briefly.

Technical Considerations

TLS Certificates

Automic SaaS uses TLS certificates that are signed by a public Certificate Authority (CA). This means that the root and intermediate certificates are already in Java and OS truststores and that there is no need to distribute certificates to enable Agents to connect to the JCP endpoint.

Automic SaaS uses the default HTTPS (443) and SFTP (22) ports.

About the Getting Started Guide for Administrators

As an administrator, your onboarding path varies depending on whether you are new to the Automic Automation world or transitioning from an on-premises deployment to Automic SaaS. This guide addresses both scenarios with dedicated sections: one for existing on-premises customers and another for new users. The remaining sections on Clients and Users, and Housekeeping, apply to all administrators.