A central theme in most middleware analyst roles is being able to articulate why Service Oriented Architecture (SOA) is important to the business.
A few examples of best practices are included here to provide some insight as to how middleware addresses key principles of standards-based computing.
Queue aliases[5] allow flexibility for middleware administrators to resolve or relieve production problems quickly.
By using queue aliases, middleware administrators can redirect message flow, in the event of a service problem, without changes to the user-defined application.
By pointing all user-defined application references to queue aliases, it preserves the flexibility that middleware admins would have to help with production issues that may occur.
Therefore, middleware analysts need to be skilled in SOA and enterprise service bus concepts first and foremost.
People that are designing and implementing the middleware message flow need to fully understand how the security model on each target platform works.
This may include Windows, Unix, z/OS or IBM i. Middleware protects data in transit through PKI and SSL technology.
These are SSL client authentication, DN filtering, CRL check by LDAP, and cryptographic hardware (IPSEC-level encryption).
If your enterprise handles HIPAA ePHI data, then your middleware analysts need to know and understand the requirements set forth by law.
[6] Failure to protect data at-rest may subject your organization to fines and penalties levied by the Federal government or other authority.
[8] System administrators, including middleware analysts, are not permitted to view unprotected ePHI data.