Automic SaaS continues to be a major topic in the automation community, offering a cloud-based, fully managed Automic environment that simplifies administration while maintaining powerful automation capabilities. We’ve already covered the first five episodes of the Automic SaaS Diaries, which you can read about here.
Now, we’re diving deeper into five more episodes, tackling key aspects like agent installation, migration, scaling, object transport, and database reorganization. If you missed our detailed introduction to Automic SaaS, you can check out the blog post here.
Let’s take a look at the highlights from episodes 6–10.
You are currently viewing a placeholder content from YouTube. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationEpisode 6: Installing Agents on Automic SaaS
Before running jobs, agents need to be connected to your SaaS instance. Client 0 comes with pre-installed ActionPacks that simplify the setup. After creating an agent, you download a pre-configured package, install it, and then authorize it in Client 0. This extra authorization step ensures that only trusted agents connect, adding a security layer since communication happens over the internet.
You are currently viewing a placeholder content from YouTube. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationEpisode 7: Migrating an Existing OS Agent to Automic SaaS
Instead of installing a new agent, you can migrate an existing one with a few adjustments. The company key must be added, and the INI file needs to be updated with the SaaS system name and connection hostname. Once the agent is started, it appears in Client 0 but requires manual authorization before it can be assigned to clients. After this quick setup, it functions just like before—only now, in Automic SaaS.
Stay Updated with the Automic SaaS Diaries
The Automic SaaS Diaries provide hands-on insights into Automic SaaS, covering key functionalities, best practices, and migration strategies. Each episode focuses on a different topic, making it easier for you to explore the platform step by step. Follow us on LinkedIn or subscribe to our YouTube channel to ensure you never miss an episode!
You are currently viewing a placeholder content from YouTube. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationEpisode 8: Scaling on Automic SaaS
Unlike on-premise setups, where Worker Processes (WPs) are added via the Service Manager, SaaS scales dynamically. The Automic Automation Kubernetes Edition (AAKE) handles horizontal scaling, automatically adjusting the number of WPs based on load. Marcin tested this by increasing system load, which triggered additional WPs to start. Once the load was removed, the system scaled back down, ensuring optimal resource utilization.
You are currently viewing a placeholder content from YouTube. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationEpisode 9: Migrating Objects to Automic SaaS
Transferring objects from an existing Automic system to SaaS is straightforward. Small migrations can be done via XML import, while larger datasets can be transferred using the REST API. For full client migrations, the transport case is the most efficient method, allowing up to 30MB of data per transfer. Objects can be unloaded via the utility tool and imported directly into SaaS through AWI.
You are currently viewing a placeholder content from YouTube. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationEpisode 10: Data Reorganization in Automic SaaS
Regular database reorganization is essential for system performance, and in SaaS, Broadcom handles it entirely. Execution data is stored for 90 days, job reports for 30 days, and object versions for 30 days. Data is archived daily and accessible via SFTP from whitelisted IPs. While UC_UTIL variables are still part of the system, they are read-only in SaaS, with new clients automatically receiving pre-configured values within 24 hours.
Explore PEM and Elevate Your Automation Skills
Looking to deepen your Automic SaaS expertise? PEM provides:
- Exclusive learning paths designed for automation professionals.
- Hands-on lab environments where you can test and refine your skills.
- Webinars and expert-led video series, including the Automic SaaS Diaries.
🔗 Interested? Reach out to us via our Get in Touch form, and we’ll help you find a solution tailored to your needs.
Start today and see how PEM can support your journey in enterprise automation!