The service consumers are primarily mobile or mobile web client applications, There are bandwidth and client performance constraints The service is fine-grained or specific to a narrow business function or transaction, There are a very large number of consumers that are less well-known The service API and/or the consuming application need to evolve rapidly and share in that rapid change, There is a large volume of service requests that benefit from caching and other native benefits of REST. EAI.017 All Common Services shall be planned, designed, developed, managed and governed by a formally-recognized team. EAI.018 All Common Services should incorporate Collect, store and present data on request monitoring, logging and instrumentation for transaction volume, response time, number of availability, utilization, responsiveness and consumers and other metrics to facilitate adoption to facilitate Service Management. Service Management EAI.019 A Service Wrapper shall be implemented as Service wrapper will simplify consuming of a Common Service around COTS API’s to COTS service API’s (e.g. FileNet P8) and ease better govern consumer access to COTS transition to another COTS in the future. functionality and to insulate consumers from complexity and change. EAI.020 Solution-Specific Services are to be used Mandating Common Services for all services only for specialized integration requirements will create bottlenecks, increase costs and between a provider and a number of consumers, where broad reuse is not an anticipated requirement. Identity & Access Management The following are PennDOT’s Technical Architecture Guidelines for Identity & Access Management: TAG# Guideline Statement Additional Explanation IAM.001 All enterprise applications shall leverage This means Microsoft Active Directories Commonwealth enterprise employee, CWOPA (employee/internal consultant), business partner and citizen directories for Managed_Apps (business partner) and managing user identities and credentials. SR_PROD (citizen).
The service consumers are primarily mobile or mobile web client applications, There are bandwidth and client performance constraints The service is fine-grained or specific to a narrow business function or transaction, There are a very large number of consumers that are less well-known The service API and/or the consuming application need to evolve rapidly and share in that rapid change, There is a large volume of service requests that benefit from caching and other native benefits of REST. EAI.017 All Common Services shall be planned, designed, developed, managed and governed by a formally-recognized team. EAI.018 All Common Services should incorporate monitoring, logging and instrumentation for availability, utilization, responsiveness and adoption to facilitate Service Management. Collect, store and present data on request transaction volume, response time, number of consumers and other metrics to facilitate Service Management EAI.019 A Service Wrapper shall be implemented as a Common Service around COTS API’s to better govern consumer access to COTS functionality and to insulate consumers from complexity and change. Service wrapper will simplify consuming of COTS service API’s (e.g. FileNet P8) and ease transition to another COTS in the future. EAI.020 Solution-Specific Services are to be used only for specialized integration requirements between a provider and a number of consumers, where broad reuse is not an anticipated requirement. Mandating Common Services for all services will create bottlenecks, increase costs and Identity & Access Management The following are PennDOT’s Technical Architecture Guidelines for Identity & Access Management: TAG# Guideline Statement Additional Explanation IAM.001 All enterprise applications shall leverage Commonwealth enterprise employee, business partner and citizen directories for managing user identities and credentials. This means Microsoft Active Directories CWOPA (employee/internal consultant), Managed_Apps (business partner) and SR_PROD (citizen).
Solicitation_10.docx&OriginalFileName=Appendix%20G%20-%20Enterprise%20IT%20Standards.docx