UNPKG

adpa-enterprise-framework-automation

Version:

Modular, standards-compliant Node.js/TypeScript automation framework for enterprise requirements, project, and data management. Provides CLI and API for BABOK v3, PMBOK 7th Edition, and DMBOK 2.0 (in progress). Production-ready Express.js API with TypeSpe

535 lines (497 loc) 18.4 kB
# Azure Portal API Registration Guide # Manual API Center Setup - No CLI Required ## 🎯 **Why Portal Registration is Perfect for You** The Azure Portal approach bypasses all CLI subscription issues and gives you immediate visual results - perfect for demonstrating to PMI leadership! ## Step 1: Access Azure Portal ### **Navigate to API Centers** 1. **Open**: [Azure Portal](https://portal.azure.com) 2. **Sign in** with your Azure account 3. **Search**: "API Center" in the top search bar 4. **Select**: "API Centers" from the dropdown ### **Find Your API Center** - **Look for**: `svc-api-center` in `rg-api-center` - **Or**: Create new if it doesn't exist ## Step 2: Register Your APIs in Portal ### **2.1 Register Echo API** 1. **Navigate**: to your API Center (`svc-api-center`) 2. **Click**: "APIs" in the left navigation menu 3. **Click**: "Register API" or "Add API" button 4. **Fill in the form**: ``` API Name: Echo API API ID: echo-api Type: REST Description: Simple echo API for testing Azure API Center functionality Version: 1.0 ``` 5. **Click**: "Register" or "Create" ### **2.2 Register Standards Compliance API** 1. **Click**: "Register API" again 2. **Fill in the form**: ``` API Name: Standards Compliance & Deviation Analysis API API ID: standards-compliance-api Type: REST Description: PMI PMBOK and BABOK standards compliance analysis with deviation detection and executive reporting for project governance Version: 1.0 Tags: pmi, pmbok, babok, compliance, governance, standards ``` 3. **Click**: "Register" or "Create" ## Step 3: Add API Specifications ### **Upload OpenAPI Specification** 1. **Select**: your `standards-compliance-api` from the list 2. **Click**: "API definitions" or "Specifications" tab 3. **Click**: "Add definition" or "Upload specification" 4. **Choose**: "OpenAPI" as the specification type 5. **Upload method options**: #### **Option A: File Upload** - **Click**: "Upload file" - **Select**: `api-specs/standards-compliance-openapi.json` - **Configure**: Title as "OpenAPI 3.0 Specification" #### **Option B: Copy & Paste** - **Click**: "Paste specification" - **Copy**: The OpenAPI JSON content (see below) - **Paste**: into the text area ### **OpenAPI Specification Content** If you need to copy/paste, use this complete specification: ```json { "openapi": "3.0.0", "info": { "title": "Standards Compliance & Deviation Analysis API", "version": "1.0.0", "description": "PMI PMBOK and BABOK standards compliance analysis with executive reporting capabilities. Provides automated detection of project management deviations and generates actionable insights for governance teams.", "contact": { "name": "API Support", "email": "api-support@yourcompany.com" }, "license": { "name": "MIT", "url": "https://opensource.org/licenses/MIT" } }, "servers": [ { "url": "https://api.yourcompany.com/v1", "description": "Production server" }, { "url": "http://localhost:3001/api/v1", "description": "Development server" } ], "paths": { "/health": { "get": { "summary": "Health check endpoint", "operationId": "healthCheck", "tags": ["System"], "responses": { "200": { "description": "API is healthy", "content": { "application/json": { "schema": { "type": "object", "properties": { "status": {"type": "string", "example": "healthy"}, "timestamp": {"type": "string", "format": "date-time"}, "version": {"type": "string", "example": "1.0.0"} } } } } } } } }, "/compliance/analyze": { "post": { "summary": "Analyze project compliance against standards", "operationId": "analyzeCompliance", "tags": ["Compliance Analysis"], "security": [{"ApiKeyAuth": []}, {"BearerAuth": []}], "requestBody": { "required": true, "content": { "application/json": { "schema": {"$ref": "#/components/schemas/ProjectData"} } } }, "responses": { "200": { "description": "Compliance analysis completed successfully", "content": { "application/json": { "schema": {"$ref": "#/components/schemas/ComplianceReport"} } } }, "400": {"description": "Invalid project data provided"}, "401": {"description": "Authentication required"}, "500": {"description": "Internal server error"} } } }, "/compliance/deviations": { "get": { "summary": "Get compliance deviations for projects", "operationId": "getDeviations", "tags": ["Compliance Analysis"], "security": [{"ApiKeyAuth": []}, {"BearerAuth": []}], "parameters": [ { "name": "standard", "in": "query", "description": "Filter by specific standard", "schema": { "type": "string", "enum": ["PMBOK", "BABOK", "DMBOK"] } }, { "name": "severity", "in": "query", "description": "Filter by deviation severity", "schema": { "type": "string", "enum": ["LOW", "MEDIUM", "HIGH", "CRITICAL"] } }, { "name": "limit", "in": "query", "description": "Maximum number of results", "schema": {"type": "integer", "minimum": 1, "maximum": 100, "default": 20} } ], "responses": { "200": { "description": "List of compliance deviations", "content": { "application/json": { "schema": { "type": "object", "properties": { "deviations": { "type": "array", "items": {"$ref": "#/components/schemas/Deviation"} }, "totalCount": {"type": "integer"}, "hasMore": {"type": "boolean"} } } } } } } } }, "/reports/executive": { "post": { "summary": "Generate executive summary report", "operationId": "generateExecutiveSummary", "tags": ["Executive Reporting"], "security": [{"ApiKeyAuth": []}, {"BearerAuth": []}], "requestBody": { "required": true, "content": { "application/json": { "schema": {"$ref": "#/components/schemas/ExecutiveReportRequest"} } } }, "responses": { "200": { "description": "Executive summary generated successfully", "content": { "application/json": { "schema": {"$ref": "#/components/schemas/ExecutiveSummary"} } } } } } } }, "components": { "schemas": { "ProjectData": { "type": "object", "required": ["projectId", "name", "methodology"], "properties": { "projectId": {"type": "string", "example": "PROJ-2025-001"}, "name": {"type": "string", "example": "Digital Transformation Initiative"}, "description": {"type": "string"}, "methodology": { "type": "string", "enum": ["AGILE", "WATERFALL", "HYBRID"], "example": "AGILE" }, "industry": {"type": "string", "example": "HEALTHCARE"}, "documents": { "type": "array", "items": {"type": "string"}, "example": ["project-charter.pdf", "requirements.docx"] }, "stakeholders": { "type": "array", "items": { "type": "object", "properties": { "name": {"type": "string"}, "role": {"type": "string"}, "influence": {"type": "string", "enum": ["LOW", "MEDIUM", "HIGH"]} } } } } }, "ComplianceReport": { "type": "object", "properties": { "projectId": {"type": "string"}, "analysisDate": {"type": "string", "format": "date-time"}, "overallScore": {"type": "number", "minimum": 0, "maximum": 100}, "standardsAnalyzed": { "type": "array", "items": {"type": "string"} }, "deviations": { "type": "array", "items": {"$ref": "#/components/schemas/Deviation"} }, "recommendations": { "type": "array", "items": { "type": "object", "properties": { "priority": {"type": "string", "enum": ["LOW", "MEDIUM", "HIGH"]}, "description": {"type": "string"}, "estimatedEffort": {"type": "string"} } } }, "complianceMetrics": { "type": "object", "properties": { "pmbokCompliance": {"type": "number"}, "babokCompliance": {"type": "number"}, "dmbokCompliance": {"type": "number"} } } } }, "Deviation": { "type": "object", "properties": { "id": {"type": "string"}, "standard": {"type": "string", "enum": ["PMBOK", "BABOK", "DMBOK"]}, "category": {"type": "string"}, "severity": {"type": "string", "enum": ["LOW", "MEDIUM", "HIGH", "CRITICAL"]}, "description": {"type": "string"}, "recommendation": {"type": "string"}, "knowledgeArea": {"type": "string"}, "processGroup": {"type": "string"}, "detectedAt": {"type": "string", "format": "date-time"} } }, "ExecutiveReportRequest": { "type": "object", "required": ["timeframe"], "properties": { "projectIds": { "type": "array", "items": {"type": "string"} }, "timeframe": { "type": "string", "enum": ["LAST_30_DAYS", "LAST_90_DAYS", "LAST_6_MONTHS", "LAST_YEAR", "CUSTOM"] }, "customStartDate": {"type": "string", "format": "date"}, "customEndDate": {"type": "string", "format": "date"}, "includeRecommendations": {"type": "boolean", "default": true}, "includeMetrics": {"type": "boolean", "default": true}, "reportFormat": {"type": "string", "enum": ["SUMMARY", "DETAILED"], "default": "SUMMARY"} } }, "ExecutiveSummary": { "type": "object", "properties": { "reportId": {"type": "string"}, "generatedAt": {"type": "string", "format": "date-time"}, "executiveSummary": {"type": "string"}, "keyFindings": { "type": "array", "items": {"type": "string"} }, "strategicRecommendations": { "type": "array", "items": {"type": "string"} }, "complianceMetrics": { "type": "object", "properties": { "overallComplianceScore": {"type": "number"}, "projectsAnalyzed": {"type": "integer"}, "criticalDeviations": {"type": "integer"}, "improvementOpportunities": {"type": "integer"} } }, "riskAssessment": { "type": "object", "properties": { "riskLevel": {"type": "string", "enum": ["LOW", "MEDIUM", "HIGH"]}, "topRisks": { "type": "array", "items": {"type": "string"} } } } } } }, "securitySchemes": { "ApiKeyAuth": { "type": "apiKey", "in": "header", "name": "X-API-Key", "description": "API key for authentication" }, "BearerAuth": { "type": "http", "scheme": "bearer", "bearerFormat": "JWT", "description": "JWT token for authentication" } } }, "security": [ {"ApiKeyAuth": []}, {"BearerAuth": []} ], "tags": [ { "name": "System", "description": "System health and status endpoints" }, { "name": "Compliance Analysis", "description": "Project standards compliance analysis endpoints" }, { "name": "Executive Reporting", "description": "Executive summary and reporting endpoints" } ] } ``` ## Step 4: Configure API Environments ### **Add Development Environment** 1. **Click**: "Environments" in the left menu 2. **Click**: "Add environment" 3. **Fill details**: ``` Name: Development Type: Development Description: Local development and testing environment Server URL: http://localhost:3001/api/v1 ``` 4. **Click**: "Create" ### **Add Production Environment** 1. **Click**: "Add environment" again 2. **Fill details**: ``` Name: Production Type: Production Description: Production deployment environment Server URL: https://api.yourcompany.com/v1 ``` 3. **Click**: "Create" ## Step 5: Add Metadata and Tags ### **API Tags and Categories** 1. **Select**: your Standards Compliance API 2. **Click**: "Properties" or "Metadata" tab 3. **Add tags**: - `pmi` - `pmbok` - `babok` - `compliance` - `governance` - `standards` - `executive-reporting` ### **Custom Properties** (if available) ```json { "compliance-standards": ["BABOK_V3", "PMBOK_7", "DMBOK_2"], "industry-focus": ["HEALTHCARE", "FINANCE", "TECHNOLOGY"], "api-maturity": "PRODUCTION_READY", "business-value": "HIGH", "innovation-level": "ADVANCED" } ``` ## Step 6: Documentation and Descriptions ### **Enhanced API Description** Update your API description to: ``` PMI PMBOK and BABOK standards compliance analysis with deviation detection and executive reporting for project governance. Key Features: • Automated compliance analysis against PMI standards • Real-time deviation detection and alerting • Executive summary generation for board reporting • Support for PMBOK 7th Edition, BABOK v3, and DMBOK 2.0 • Integration-ready with enterprise project management tools Business Value: • Reduces manual compliance review time by 70% • Provides real-time governance insights • Enables proactive risk management • Supports PMI certification and professional development • Delivers board-ready executive reporting Target Users: • PMI-certified Project Managers (PMP, PMI-ACP, PfMP) • Project Management Offices (PMOs) • Executive leadership and board members • Compliance and audit teams • Business analysts and requirements specialists ``` ## Step 7: Verification and Testing ### **Portal Verification Checklist** ✅ **API Registered**: Both Echo API and Standards Compliance API appear in catalog ✅ **Specifications Loaded**: OpenAPI documentation is visible and readable ✅ **Environments Configured**: Development and Production environments exist ✅ **Metadata Complete**: Tags, descriptions, and properties are set ✅ **Documentation Ready**: API is ready for team discovery and use ### **Test API Center Features** 1. **Browse API Catalog**: Verify APIs appear in searchable catalog 2. **View Documentation**: Check OpenAPI spec renders correctly 3. **Environment Switching**: Test environment selector functionality 4. **Search and Filter**: Try searching for "compliance" or "PMI" ## Benefits of Portal Registration ### **✅ Immediate Advantages** - **No CLI Issues**: Bypass all subscription and authentication problems - **Visual Interface**: Easy to understand and navigate - **Professional Appearance**: Perfect for executive demonstrations - **Team Collaboration**: Multiple stakeholders can access and explore ### **🎯 Perfect for PMI Board Strategy** - **Tom Bloemers Appeal**: Visual governance dashboard for financial oversight - **Executive Ready**: Professional API catalog for board presentations - **Innovation Showcase**: Demonstrates technical leadership during PMI transition - **Stakeholder Engagement**: Self-service discovery for PMI-certified teams ### **📊 Business Value Demonstration** - **Governance Visibility**: Clear API portfolio management - **Compliance Documentation**: Built-in standards tracking - **Professional Standards**: Enterprise-grade API management - **Strategic Alignment**: Perfect foundation for PMI board engagement ## Next Steps After Portal Registration ### **Documentation for PMI Leadership** 1. **Take Screenshots**: Capture professional API catalog views 2. **Create Demo Script**: Prepare executive walkthrough 3. **Document Business Value**: Quantify governance and compliance benefits 4. **Prepare Board Presentation**: Align with Tom Bloemers' financial governance focus ### **Integration Planning** 1. **Team Onboarding**: Share API Center access with stakeholders 2. **Consumer Discovery**: Enable teams to find and use APIs 3. **Governance Policies**: Set up API lifecycle management 4. **Analytics Setup**: Monitor API usage and adoption The portal approach gives you immediate, visual results that perfectly support your PMI board candidate strategy - especially demonstrating the governance and financial oversight capabilities that make Tom Bloemers your ideal strategic partner! 🚀