<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Automation on Steffen Hoppe – Infrastructure Reality &amp; Insight</title>
    <link>https://www.sh-soft.de/tags/automation/</link>
    <description>Recent content in Automation on Steffen Hoppe – Infrastructure Reality &amp; Insight</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 26 Jun 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.sh-soft.de/tags/automation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Sales System Project – Overview</title>
      <link>https://www.sh-soft.de/posts/sales-system/sales-system-overview/</link>
      <pubDate>Thu, 29 May 2025 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/posts/sales-system/sales-system-overview/</guid>
      <description>📦 The Sales System Project – Overview Link to heading This series dives into a complex, long-running engagement centered on a fragile in-house sales system.&#xA;The customer hosted 1,000+ Windows systems across development, test, and production stages.&#xA;What began as firefighting evolved into automation, observability, and ultimately organizational change.&#xA;The Journey begins Link to heading About 14 years ago, I took over responsibility for a single, large, in-house-developed sales system.</description>
    </item>
    <item>
      <title>Sales System Project: Automation Boundaries</title>
      <link>https://www.sh-soft.de/posts/sales-system/automation-boundaries/</link>
      <pubDate>Thu, 26 Jun 2025 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/posts/sales-system/automation-boundaries/</guid>
      <description>🚧 Automation Boundaries Link to heading Summary: Automation helped us move faster, reduce errors, and scale operations.&#xA;But it didn’t solve everything — especially when our systems had to interact with others.&#xA;Where the Boundaries Appeared Link to heading Active Directory and DNS: We didn’t own it. Scripted group changes or DNS edits weren’t possible without external coordination. Firewall Rules and Load Balancers: Managed by a different team. Automation stopped at the request ticket.</description>
    </item>
    <item>
      <title>Sales System Project: Setup and Problems</title>
      <link>https://www.sh-soft.de/posts/sales-system/setup-problems/</link>
      <pubDate>Thu, 29 May 2025 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/posts/sales-system/setup-problems/</guid>
      <description>🏗️ Setup and Problems Link to heading Setup Link to heading Customer Landscape:&#xA;Initially ~200 Windows servers, later scaled to over 1,000 across development, test, and production as new services were added and integrated into our automation Primarily Windows-based infrastructure: IIS, MSMQ, MSSQL, and some JBoss AD integrated authentication via NTLM and Kerberos, sometimes Basic Auth, host backend integration via IBM MQ Business-critical data processed via mainframe interfaces Different teams have control over: Active Directory: DNS / Users / Groups Firewall and Security Infrastructure Reverse Proxies Virtualization platform PKI Internal traffic often unencrypted due to lack of automated PKI or cert lifecycle Problems Link to heading Initial Challenges:</description>
    </item>
  </channel>
</rss>
