#Intermapper support updateThis is handled through the create, update and delete method and should not really be used. Used in combination with the header and the format method in Net::Intermapper to perform CRUD actions. Returns the object data formatted in XML format. Returns the object data formatted in Comma Separated delimited format. Returns the object data formatted in TAB delimited format. Returns the directive aka data header required by the Intermapper API to perform CRUD actions. Corresponds to the device with a matching VertexID in the devices table. Vertical map coordinate, the positive direction is to the bottom. Horizontal map coordinate, the positive direction is to the right. True if the vertex is a vantage point of the graph XCoordinate (read-write) Vertex shape (rect, oval, wire, cloud, text, or icon name). Valid values: center, top, left, right, botom, topleft, topright, bottomright, bottomleft. The origin determines whether the vertex coordinates are relative to the center or one of the sides of the vertex. The unique Id of the map file containing the vertex. True if the vertex label is visible (only used when the device is represented by an icon) MapId (read-only) Valid values are topleft, top, topright, left, center, right, bottomleft, bottom, bottomright LabelTemplate (read-write) FontStyle (read-write)įont style (bold, italic, plain) Label (read-only) Bodoni MT FontSize (read-write)įont size in points. Color (read-write)Ĭolor (valid names: white, black, red, orange, yellow, blue, green, brown) FontName (read-write)įont name, eg. The name is the first non-empty line in a device or network's label on a map. This value is used for lookups in the users method in Net::Intermapper. The id will be unique across all maps on a single InterMapper server. Id (read-only)Ī unique, persistent identifier for this vertex instance. Name of the map file containing the vertex. Returns object of Net::Intermapper::Vertice on succes. This will NOT affect the smart-caching (only explicit calls to create, update and delete do this - for now).Ĭlass constructor. # But it can be done with users, devices, interfaces, maps and vertices # At this point, there is no real reason to do this as update, create and delete work with explicit arguments. # Retrieve all vertices from Intermapper, Net::Intermapper::Vertice instances My $vertices_ref = $intermapper->vertices # Retrieve all interfaces from Intermapper, Net::Intermapper::Interface instances My $interfaces_ref = $intermapper->interfaces My %interfaces = $intermapper->interfaces # Retrieve all maps from Intermapper, Net::Intermapper::Map instances # Retrieve all devices from Intermapper, Net::Intermapper::Device instances # Returns hash or hashref, depending on context # Retrieve all users from Intermapper, Net::Intermapper::User instances # cache - Boolean to enable smart caching or force network queries # modifyport - TCP port for modifying information. # port - TCP port for querying information. # ssl - SSL enabled (1 - default) or disabled (0) # username - Username of Administrator user # hostname - IP or hostname of Intermapper 5.x and 6.x server My $intermapper = Net::Intermapper->new(hostname=>"10.0.0.1", username=>"admin", password=>"nmsadmin") Net::Intermapper::Vertice - Interface with the HelpSystems Intermapper HTTP API - Vertices SYNOPSIS use Net::Intermapper
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |