Apigee Responsibility Matrix

Objective

To describe all areas required to support the API Management platform Apigee at UCSB, and the responsible people for each area. The platform consists of two main tools - the developer portal, and the gateway, both described below.

Developer Portal (https://developer.ucsb.edu/): used for API discovery and access/publishing requests. API users sign up for the developer portal, create an App, and request access to APIs for their app. An API key is given to them to be able to access the APIs. The API team has developed access request forms to manage the API publishing and API access requests and record the decisions. The API team has developed standards and guidelines for API use by employees, and by students.

Gateway (https://login.apigee.com/login): used for API publishing, execution, and statistics. Gateway accounts require Apigee license. Users publish APIs, grant API access to Apps, have access to Apigee reports in the gateway to troubleshoot errors and to view API usage statistics.

Team email address: support@developer.ucsb.edu. All team members receive all communications to this email.

Team members: listed on bottom of page

Apigee Responsibility Matrix

Area	Duties	Primary Responsible Person	Other Responsible People	Documentation Links
Developer Portal Account Approval	Verify a valid ucsb affiliation. Verify student or employee affiliation. Approve/deny account. Add to google groups.	Diana Antova / Steven Maglio	API team has access to approve/deny accounts	https://developer.ucsb.edu/docs/approving-accounts https://developer.ucsb.edu/docs/accounts/developer-portal
API Access Requests	Review API access requests Request access approval form submission. Review provided information on access request form is sufficient. Route requests through the workflow. Meet with the developer to understand the need and the best way to serve their need. Review technical information on API access requests, including security information. Approve API access request form. Approve API access request in gateway.	Diana Antova	Steven Maglio	https://developer.ucsb.edu/docs/applications/application-approval-request https://developer.ucsb.edu/docs/gateway-admin/processing-api-access-request
API Publishing Requests	Review API publishing requests. Route request through the workflow. Review that API meets the development standards. Publish the API in the gateway. Create API documentation in developer portal to make it available for access requests.	Steven Maglio	Kevin Wu / Gary Scott	https://developer.ucsb.edu/api-publishing-request
Application Development Support	Provide guidance on LDAP account creation API use guidelines for developers Security guidelines	Steven Maglio	Kevin Wu / Gary Scott	https://developer.ucsb.edu/docs/accounts/ldap-accounts https://developer.ucsb.edu/getting-started https://developer.ucsb.edu/creating-your-first-app https://developer.ucsb.edu/trying-out-apis https://developer.ucsb.edu/docs/applications/testing-applications https://developer.ucsb.edu/docs/security/overview https://developer.ucsb.edu/docs/security/application-security-review
Student Development Support	Provide guidelines to students on application development. Review security implementation for apps using APIs that require approval. Perform periodic code review for apps using APIs that require approval.	Steven Maglio	Diana Antova / Seth Northrop	https://developer.ucsb.edu/docs/applications/student-developed-applications
Business API Access Approval	Review API access requests. Approve/deny API access requests. Review API Publishing Requests. Approve/deny API publishing requests.	Diana Antova	Steven Maglio	https://developer.ucsb.edu/business-api-access-request-approver Each API Publishing Request form contains the name(s) of people that are allowed to approve the publishing of an API and access requests.
New API Development	Receive requests from customers for new APIs. Determine system of source. Work with developers to request the APIs. Provide guidance on API development.	Steven Maglio	Diana Antova
Developer Portal Development	Use the Drupal platform to maintain the developer portal. Add/edit pages. Create workflows and rules. Setup automatic emails. Plan, Manage & implement major Drupal upgrades	Ian Lessing (Unlicensed)	Diana Antova / Steven Maglio / Vince Nievares
Developer Portal Maintenance	Apply Drupal patches. Apply Apigee patches.	Ian Lessing (Unlicensed)	Steven Maglio / Vince Nievares	This is a manual process
API Documentation Support	Make sure all publishing requests have been filled and are in the correct workflow state Make sure all access requests have been filled and are in the correct workflow state	Diana Antova		Review the API documentation to make sure all is correct.
Slack commands support	Create new slack commands for gateway operations automation.	Kevin Wu	Steven Maglio	https://developer.ucsb.edu/docs/slack-chatbot
API Monitoring	Uptime Robot integration.	Steven Maglio	Reinard Dolleschel	https://developer.ucsb.edu/docs/gateway-admin/add-upcheck
Splunk integration	API event tracking in Splunk. Splunk reports and dashboards.	christian.montecino (Unlicensed)	Steven Maglio / Diana Antova	https://developer.ucsb.edu/docs/gateway-admin/edit-an-api-proxy
Developer engagement and account cleanup	Support for historical application inactivity database. User account cleanup.	Steven Maglio		Usage data is extracted on a weekly basis and recorded in a database along with user accounts, with the purpose to identify accounts that are not using APIs and disable access.
API Support SIS&T	Provide development support for all SIS&T APIs published in Apigee. Fix bugs. Modify APIs as requested by users.	Seth Northrop / Aurelian Marian	Steven Maglio	Each API has a corresponding API Publishing request, where the developer(s) and approver(s) are listed. https://developer.ucsb.edu/api-publishing-requests
API Support ARIT	Provide development support for all ARIT APIs published in Apigee. Fix bugs. Modify APIs as requested by users.	Gary Scott	Masha Aksenova	Each API has a corresponding API Publishing request, where the developer(s) and approver(s) are listed. https://developer.ucsb.edu/api-publishing-requests
API Support ETS	Provide development support for all ETS APIs published in Apigee. Fix bugs. Modify APIs as requested by users.	Kevin Wu	christian.montecino (Unlicensed)	Each API has a corresponding API Publishing request, where the developer(s) and approver(s) are listed. https://developer.ucsb.edu/api-publishing-requests
Project team management	Schedule weekly meetings Prepare agendas Issue and sprint tracking Project planning	Diana Antova	Steven Maglio	The team meets 3 times a month for 1.5 hours each meeting. Additional time is spent on project work outside of meetings as necessary.
Apigee Google Groups Support	Create and maintain the google groups in the developer.ucsb.edu domain.	Diana Antova	Steven Maglio / Vince Nievares	There are google groups for API consumers, API providers, Business Approvers, and other. They are used to communicate with the groups.
Apigee Executive and Financial Support	Provide executive leadership for the Apigee implementation and support. Provide funding for the annual Apigee subscription fees.	Matt Hall - UCSB CIO	Joe Sabado (Deactivated)
Apigee Annual Subscription Renewal	Receive the annual subscription invoice from Apigee. Process the payment.	Elise Mayer - ETS	Diana Antova

API Team Members:

All emails to suport@developer.ucsb.edu is routed to all API team members listed below.

Diana Antova - SIS&T

Steven Maglio - SIS&T

Ian Lessing (Unlicensed) - Library

Kevin Wu - ETS

christian.montecino (Unlicensed) - ETS

Vince Nievares - Academic Affairs IT

Reinard Dolleschel - Biological Sciences Administration IT

Gary Scott - ARIT (Former team member, has Apigee license)

Seth Northrop - SIS&T (Has Apigee license, not part of the team)