OMERO Application Programming Interface ======================================= All interaction with the OMERO server takes place via several API services available from a ServiceFactory. A service factory is obtained from the client connection e.g. Python: :: client = omero.client("localhost") session = client.createSession("username", "password") # this is the service factory adminService = session.getAdminService() # now we can get/create services - The :javadoc:`Service factory API ` has methods for creating Stateless and Stateful services (see below). - Stateless services are obtained using "get…" methods e.g. ``getQueryService()`` - Stateful services are obtained using "create…" methods e.g. ``createRenderingEngine()`` - Services will provide access to omero.model.objects. You will then need the :javadoc:`API for these objects `, e.g. Dataset, Image, Pixels etc. Services list ------------- The :sourcedir:`ome.api ` package in the common component defines the central "verbs" of the OMERO system. All external interactions with the system should happen with these verbs, or services. Each OMERO service belongs to a particular service level with each level calling only on services from lower levels. Service Level 1 (direct database and Hibernate connections) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - AdminService: :source:`src `, :javadoc:`API ` for working with Experimenters, Groups and the current Context (switching groups etc). - ConfigService: :source:`src `, :javadoc:`API ` for getting and setting config parameters. - ContainerService: :javadoc:`API ` for loading Project, Dataset and Image hierarchies. - LdapService: :source:`src `, :javadoc:`API ` for communicating with LDAP servers. - MetadataService: :javadoc:`API ` for working with Annotations. - PixelsService: :javadoc:`API ` for pixels stats and creating Images with existing or new Pixels. - ProjectionService :javadoc:`API ` - QueryService: :source:`src `, :javadoc:`API ` for custom SQL-like queries. - RenderingSettingsService :javadoc:`API ` for copying, pasting & resetting rendering settings. - RepositoryInfo :javadoc:`API ` disk space stats. - RoiService :javadoc:`API ` working with ROIs. - ScriptService :javadoc:`API ` for uploading and launching Python scripts. - SessionService :javadoc:`API ` for creating and working with OMERO sessions. - ShareService :javadoc:`API ` - TimelineService :javadoc:`API ` for queries based on time. - TypesService :javadoc:`API ` for Enumerations. - UpdateService: :source:`src `, :javadoc:`API ` for saving and deleting omero.model objects. Service Level 2 ^^^^^^^^^^^^^^^ - :source:`IContainer ` - :source:`ITypes ` Stateful/Binary Services ^^^^^^^^^^^^^^^^^^^^^^^^ - RawFileStore: :source:`src `, :javadoc:`API ` - RawPixelsStore: :source:`src `, :javadoc:`API ` - RenderingEngine: :source:`src `, :javadoc:`API ` (see :doc:`/developers/Server/RenderingEngine` for more) - ThumbnailStore: :source:`src `, :javadoc:`API ` - :source:`IScale ` A complete list of service APIs can be found :javadoc:`here ` and some examples of API use in Python are provided. Java or C++ code can use the same API in a very similar manner. Discussion ---------- Reads and writes ^^^^^^^^^^^^^^^^ IQuery and IUpdate are the basic building blocks for the rest of the (non-binary) API. IQuery is based on QuerySources and QueryParemeters which are explained under :doc:`/developers/Server/Queries`. The goal of this design is to make wildly separate definitions of queries (templates, db-stored, Java code, C# code, …) runnable on the server. IUpdate takes any graph composed of :source:`IObject ` objects and checks them for dirtiness. All changes to the graph are stored in the database if the user calling IUpdate has the proper permissions, otherwise an exception is thrown. Dirty checks follow the Three Commandments: #. Any IObject-valued field with unloaded set to true is treated as a place holder (proxy) and is re-loaded from the database. #. Any collection-valued field with a null value is re-loaded from the database. #. Any collection-valued field with the FILTERED flag is assumed to be dirty and is loaded from the database, with the future option of examining the filtered collection for any new and updated values and applying them to the real collection. (Deletions cannot happen this way since it would be unclear if the object was filtered or deleted.) Administration ^^^^^^^^^^^^^^ The :source:`IAdmin ` interface defines all the actions necessary to administer the :doc:`/sysadmins/server-security` . It is explained further on the :doc:`/developers/Modules/Api/AdminInterface` page. Pojos ^^^^^ Certain operations, like those dealing with data management and viewing, happen more frequently than others (like defining microscopes). Those have been collected in the :source:`IContainer ` interface. IContainer simplifies a few very common queries, and there is a related package ("pojos.\*") for working with the returned graphs. OMERO.insight works almost exclusively with the IContainer interface for its non-binary needs. Examples -------- :: // Saving a simple change Dataset d = iQuery.get( Dataset.class,1L ); d.setName( "test" ); iUpdate.saveObject( d ); // Creating a new object Dataset d = new Dataset(); d.setName( "test" ); // not-null fields must be filled in iUpdate.saveObject( d ); // Retrieving a graph Set ds = iQuery.findAllByQuery( "from Dataset d left outer join d.images where d.name = 'test'",null ); Stateless versus stateful services ---------------------------------- A stateless service has no client-noticeable lifecycle and all instances can be treated equally. A new stateful service, on the other hand, will be created for each client-side proxy (see the ``ServiceFactory.create\*`` methods). Once obtained, a stateful service proxy can only be used by a single user. After task completion, the service should be closed (``proxy.close()``) to free up server resources. How to write a service ---------------------- A tutorial is available at :doc:`/developers/Server/HowToCreateAService`. In general, if a properly annotated service is placed in any JAR of the OMERO EAR file (see :doc:`/developers/build-system` for more) then the service will be deployed to the server. In the case of :doc:`/developers/server-blitz`, the service must be properly defined under :sourcedir:`components/blitz/resources`. OMERO annotations for validation -------------------------------- The server-side implementation of these interfaces makes use of ((JDK5)) :doc:`/developers/Model/StructuredAnnotations` and an :doc:`AOP ` interceptor to validate all method parameters. Calls to ``pojos.findContainerHierarches`` are first caught by a method interceptor, which checks for annotations on the parameters and, if available, performs the necessary checks. The interceptor also makes proactive checks. For a range of parameter types (such as Java Collections) it requires that annotations exist and will refuse to proceed if not implemented. An API call of the form: :: pojos.findContainerHierarches(Class,Set,Map) is implemented as :: pojos.findContainerHierarchies(@NotNull Class, @NotNull @Validate(Integer.class) Set, Map) .. seealso:: :doc:`/developers/Server/Queries`, :doc:`/developers/Server/RenderingEngine`, :doc:`/developers/Modules/ExceptionHandling`