workspaces.rst 6.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166
  1. .. _data_webadmin_workspaces:
  2. Workspaces
  3. ==========
  4. This section describes how to view and configure workspaces. Analogous to a namespace, a workspace is a container which organizes other items. In GeoServer, a workspace is often used to group similar layers together. Layers may be referred to by their workspace name, colon, layer name (for example ``topp:states``). Two different layers can have the same name as long as they belong to different workspaces (for example ``sf:states`` and ``topp:states``).
  5. .. figure:: img/data_workspaces.png
  6. Workspaces page
  7. .. _data_webadmin_workspaces_add_workspace:
  8. Add a Workspace
  9. ---------------
  10. The buttons for adding and removing a workspace can be found at the top of the Workspaces view page.
  11. .. figure:: img/data_workspaces_add_remove.png
  12. Buttons to add and remove
  13. To add a workspace, select the :guilabel:`Add new workspace` button. You will be prompted to enter the workspace name and URI (as described in :ref:`data_webadmin_workspaces_edit` below).
  14. .. figure:: img/data_workspaces_sde.png
  15. New Workspace page with example
  16. Remove a Workspace
  17. ------------------
  18. To remove a workspace, select it by clicking the checkbox next to the workspace. Multiple workspaces can be selected, or all can be selected by clicking the checkbox in the header. Click the :guilabel:`Remove selected workspaces(s)` button. You will be asked to confirm or cancel the removal. Clicking :guilabel:`OK` removes the selected workspace(s).
  19. .. figure:: img/data_workspaces_rename_confirm.png
  20. Workspace removal confirmation
  21. .. _data_webadmin_workspaces_edit:
  22. Edit a Workspace
  23. ----------------
  24. To view or edit a workspace, click the workspace name. A workspace configuration page will be displayed.
  25. .. figure:: img/data_workspaces_basic_edit.png
  26. Workspace named "topp"
  27. A workspace is defined by a name and a Namespace URI (Uniform Resource Identifier).
  28. * :guilabel:`Name`: The workspace name, may not contain whitespace.
  29. The workspace name is used as an XML prefix for the Namespace URI when generating xml documents.
  30. The workspace name is used as a prefix when naming individual layers (unless :guilabel:`Default workspace` is used as described below).
  31. * :guilabel:`Namespace URI`: A URI is similar to a URL, except URIs do not need to point to an actual location on the web, and only need to be a unique identifier.
  32. For a Workspace URI, we recommend using a URL associated with your project, with perhaps a different trailing identifier. For example, ``http://www.openplans.org/topp`` is the URI for the "topp" workspace.
  33. * :guilabel:`Default Workspace`: One workspace can be nominated as the default.
  34. Layers belonging to the default workspace can be accessed directly, and do not require the workspace name as a prefix.
  35. A GeoServer configured with one workspace can use this setting to avoid using the workspace name when referencing layers. Keep in mind the workspace name will still be used in the generation of xml documents (where the name is used as an XML prefix to reference the workspace Namespace URI).
  36. * :guilabel:`Isolated workspace`: Isolated workspaces content so they are not included as part of global web services.
  37. The workspace contents will only be visible and queryable in the context of a :ref:`virtual_services` as described below :ref:`workspace_isolated`.
  38. .. _workspace_services:
  39. Workspace Services
  40. ^^^^^^^^^^^^^^^^^^
  41. Use the checkbox located next to each service to override the global service definition for the associated service.
  42. .. figure:: img/workspace_services.png
  43. Enable workspace services to provide default service description
  44. Once enabled clicking on the service link will open the settings page for the service, allowing default values for service title, abstract and other details to be supplied.
  45. .. figure:: img/workspace_wms_settings.png
  46. Workspace WMS Settings
  47. Clients accessing this workspace as a :ref:`virtual_services` will use the service metadata and settings provided here.
  48. .. _workspace_settings:
  49. Workspace Settings
  50. ^^^^^^^^^^^^^^^^^^
  51. Use :guilabel:`Enabled` checkbox to override the global configuration and contact information for this workspace.
  52. .. figure:: img/workspace_settings.png
  53. Enable workspace settings to provide default contact information
  54. Contact Information
  55. '''''''''''''''''''
  56. Clients accessing this workspace as a :ref:`virtual_services` will use the contact information provided here.
  57. Organization contact information:
  58. * The :guilabel:`Welcome` message is used as an introduction in the welcome page header for this workspace.
  59. * The :guilabel:`Organization` name and :guilabel:`Online Resource` are combined to form an organization link in the welcome page header for this workspace.
  60. .. figure:: img/workspace_orgaization.png
  61. Workspace Organization
  62. Primary contact information:
  63. * The :guilabel:`email` address if provided, will be used as the administrator contact in the welcome page footer for this workspace.
  64. .. figure:: img/workspace_contact.png
  65. Workspace Primary Contact
  66. Address contact information:
  67. .. figure:: img/workspace_address.png
  68. Workspace address
  69. If this information is not provided the contact information from the global :ref:`config_contact` page is used.
  70. Service Settings
  71. ''''''''''''''''
  72. Other settings provide additional :ref:`config_globalsettings` can be overridden on a workspace-by-workspace basis.
  73. * :guilabel:`Include Layer Prefix in Local Workspace Capabilities`: Enable this setting to force the inclusion of the workspace name as a prefix when accessing workspace contents as a virtual web service. The layer ``ne:countries`` is always referenced as ``ne:countries`` with this setting enabled.
  74. With this setting disabled layers may be referenced directly (with no prefix) when accessed by a virtual web service. The layer ``ne:countries`` can be referenced as ``countries`` when this setting is disabled (and the layer is being accessed via a ``ne`` virtual web service).
  75. * :guilabel:`Root Directory for REST PathMapper`: setting used by the RESTful API as the `Root Directory` for uploaded files, following the structure::
  76. ${rootDirectory}/workspace/store[/<file>]
  77. .. note:: This parameter is only used when the **Enabled** parameter of the *Settings* section is checked.
  78. .. figure:: img/workspace_settings_other.png
  79. Other Settings
  80. If this information is not provided the global settings will be used. For details on other settings see :ref:`config_globalsettings`.
  81. .. _workspace_security:
  82. Security
  83. ^^^^^^^^
  84. The Security tab allows to set data access rules at workspace level.
  85. .. note:: For more information on data access rules, please see the section on :ref:`security_webadmin_data`.
  86. .. figure:: img/data_workspaces_security_edit.png
  87. To create/edit the workspace's data access rules, check/uncheck checkboxes according to the desired role.
  88. The Grant access to any role checkbox grant each role for any access mode.