"I'm Taniya Chaudhary. I have 5+ years of experience as a Service Reliability Engineer across British Telecom and HCL, managing enterprise network infrastructure, firewalls, and maintaining 99.99% uptime across 50+ global sites.

Alongside my core in networking and security, I handle day-to-day Linux administration—navigating CLI, checking system logs, managing processes, and monitoring server health—along with basic SQL queries and Cloud infrastructure.

I'm looking to leverage my infrastructure and troubleshooting background at PTC to support on Windchill"

Enterprise applications like Windchill rely on the same infrastructure fundamentals I deal with daily: network routing, firewalls, load balancers, and Linux servers. I want to move closer to enterprise application platforms and Cloud DevOps, where I can use my infrastructure troubleshooting skills on multi-tier software environments.

Windchill runs as a multi-tier distributed architecture. When users report connection drops, slow check-ins, or SSO login issues, the root cause usually points to ports, reverse proxies (Apache), load balancers, or firewall rules. My strong network foundation lets me quickly isolate whether an issue is network-related, server-related, or application-level.

• 443 / 80 : HTTPS / HTTP (Client web traffic to Apache or Load Balancer)
• 8080 : Windchill MethodServer (Internal application port)
• 1521 / 5432 : Oracle / PostgreSQL Database connection
• 389 / 636 : LDAP / LDAPS (User authentication & Directory Server)

I isolate the failure layer step-by-step:

• Network: ping <IP> and nc -zv <host> <port> to check if the server and required ports are reachable.
• Processes: ps -ef | grep MethodServer to see if the Windchill background process is running.
• Resources: top and df -h to check for CPU/RAM exhaustion or full disk partitions.
• Logs: Inspect MethodServer.log and Apache error_log for stack traces or DB connection drops.

• tail -f <file> : Watch real-time log output.
• grep -i "error" <file> : Filter specific error patterns.
• ps -ef : List all running background processes.
• top / free -h : Monitor CPU load and RAM usage.
• df -h : Check disk space across mount points.
• chmod 755 / chown user:group : Fix file permissions and ownership.

SSO lets users authenticate once using their corporate directory (like Azure AD or Okta) without retyping credentials.

It distributes incoming user requests evenly across multiple Apache web servers. It runs continuous health checks and automatically reroutes traffic away from failed nodes, ensuring continuous uptime.

• On the server: ss -tulnp | grep <port> or netstat -tulnp | grep <port>
• From a client/remote host: nc -zv <server_ip> <port> or telnet <server_ip> <port>

• Database (Oracle/PostgreSQL): Stores structured metadata—part numbers, BOM links, lifecycle states, and permissions.
• File Vaults (Local Disk or AWS S3): Stores actual files and zip streams with deduplication, preventing the database from bloating.

It is cloning a production Windchill environment—database, file vaults, and configuration files—into a non-production (staging/test) environment, followed by updating hostnames, base URLs, and LDAP endpoints so developers can safely validate patches and upgrades.

It's a background machine/service running Worker Service that automatically opens CAD files and converts them into lightweight 3D viewables for viewing in CreoView.

I run top to identify the top CPU/memory consuming PIDs. I check free -h for available RAM and swap usage.

It is a central directory service storing enterprise user accounts and groups. Windchill connects to LDAP (Port 389 / 636) to authenticate logins directly against corporate credentials.

Familiar through Cloud Management Web Consoles (UI): checking EC2/VM instances status, browsing S3/Blob storage buckets, viewing RDS database health, and verifying Security Group firewall rules.