Difference between revisions of "GOCDB/Relase4/XML Input/Entities/Service Endpoint"
< GOCDB
Jump to navigation
Jump to search
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
{{Template:Op menubar}} | |||
{{Template:GOCDB_menubar}} | |||
{{TOC_right}} | |||
[[Category:GOCDB]] | |||
[[GOCDB/Release4/XML_Input#Mandatory_Relationships|<< Back to Mandatory Relationships]] | [[GOCDB/Release4/XML_Input#Mandatory_Relationships|<< Back to Mandatory Relationships]] | ||
=Service Endpoint= | =Service Endpoint= |
Latest revision as of 13:30, 18 December 2012
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
GOC DB menu: | Home • | Documentation Index • |
<< Back to Mandatory Relationships
Service Endpoint
In order for a service endpoint to be visible in the web portal and the programmatic interface, the following mandatory relationships are needed.
A site must participate in exactly one of each link below to be visible in the web portal and programmatic interface.
Core PROM Object: service_endpoint
Primary Key: ENDPOINT
Parent Objects
Description | Object Type | Link Type | Notes |
---|---|---|---|
Child service endpoint has parent service type | service_type | 4 | |
Child service endpoint belongs to parent site | site | 6 | |
Child service endpoint is (in)visible to EGI | tag | 43 | The parent tag must be named either "EGI" or "Local" |
Child Objects
None.