requirement | What the resume shows |
Installing | "Installing and upgrading the server"; built four new 10.5 environments |
Upgrading | Moved from 9.5 to 10.5 when 9.5 support ended; has used versions 7.x through 10.15 |
Patching | No mention of fixes, Update Manager, Command Central or patch cycles |
Deploying | Deployer, CI/CD with Jenkins, Git and Azure DevOps, code across multiple environments |
Platform internals | Integration Server, Universal Messaging, MWS, Trading Networks, API Gateway, MFT/Active Transfer, Terracotta (only in tool lists) |
Compute | AWS EC2, Azure VMs, Docker and OpenShift in the skills list; no sizing or JVM tuning; "performance tuning" is mentioned only vaguely |
Network: F5, WAF | Not mentioned. Only ports, certificates, truststores and firewall requests. |
Storage: SSD, NFS | Worked with storage/firewall teams on NAS mounts and directory connectivity |
Database: relational, clustered | Oracle, SQL Server, DB2 and Postgres through JDBC adapters as a developer. Nothing on webMethods' own database setup (ISInternal, Trading Networks or MWS schemas) or clustered databases such as Oracle RAC. |
Load balancing, clustering | Terracotta appears only in tool lists. Nothing on Integration Server, Universal Messaging or Trading Networks clustering. |
Gateways, reverse proxies | Strong API Gateway work (policies, rate limiting, IP allowlisting, Availability API). No reverse proxy or DMZ design. |
Messaging | Universal Messaging, JMS, durable subscribers, message persistence, IBM MQ, ActiveMQ, Broker |
High availability / disaster recovery | "High availability" appears only for messaging. No disaster recovery, failover or active/passive design. |
Security / certificates | Users, groups, ports, SSL certificates, keystores and truststores, OAuth |
Operations / incidents | P1–P3 incident handling within SLA, root cause analysis, breach analysis, Splunk, ELK, App Insights |
