Ows wait4take что это

OpenWebStart FAQ

To perform a full text search in this page please press Ctrl+F on your keyboard.

Common information

1. Only in case you are not an employee of Mercedes-Benz Group AG or its subsidiaries: Please update your OpenWebStart installation to at least release 1.4.0. Check, whether this solves your problem.
2. In case of start problems with EVA, Logbus or SPPS: Please read the FAQ article Instructions how to delete the RIAD caches of EVA, Logbus and SPPS. and check, if the symptoms match your case.
3. For all users: Delete your .cache folder once and try one more time to launch your application with OpenWebStart.
4. Read and apply the FAQ article regarding the .appletTrustSettings file problem.
5. Read and apply the FAQ article regarding the global .appletTrustSettings file problem.
6. Check the other FAQ articles whether one of them could solve your problem.
7. If all steps above fail, contact your support unit for further help. Recommended support channels:
   • Dealers and Mercedes-Benz Group AG employees: Open an XSF ticket in XENTRY Portal.
   • Others: Contact your country’s Service and Parts or Mercedes-Benz Group AG representative

#015 Last update: 2022-07-12 12:00 CEST
Common: Instructions how to delete the RIAD caches of EVA, Logbus and SPPS.

Overview:
The following information does not describe the solution for an OpenWebStart problem, but for a launch problem of the applications EVA, Logbus and SPPS. These problems are often associated with OpenWebStart and result in support requests. Please perform the following steps first, before starting a support request for EVA, Logbus or SPPS due to launch problems.

Symptom:
The application launch works until the small black window with the Mercedes-Benz star is being displayed. After clicking on "Start application" some downloads may or may not occur, but then nothing else happens.

1. Make sure no OpenWebStart process and no EVA, Logbus or SPPS application are running at the moment.
2. Perform a new start attempt for the application, but don’t click on "Start application." in the black window!
3. Click on "Configuration and Extras".
   
   A dialog window opens.
4. On the left side in the new dialog click on the tab "Applications".
   
5. In the right pane unfold the row "aftersales.i.daimler.com" by clicking on the triangular arrow.
6. Click on your application, e.g. "EVA:EVA START EVA PROD", to highlight it in blue.
7. In the right bottom corner click on the button "Uninstall". This removes the program files which are stored in the cache directory on your computer for this application. Everything will be downloaded again with the next launch, you will not lose any data!
8. Click on the button "OK" to close this window.
9. Now click on "Start application." in the black window.

If the application still does not start after performing these steps, please contact your support unit. Problems, which occur after the grey window with the Mercedes-Benz star is already being displayed, usually are application specific and not caused by OpenWebStart.

#007 Last update: 2022-02-01 13:00 CET
How to collect helpful information to the support units in case of problems?

Important information for support units and administrators!

Provide the link to this article to the affected user, to enable her/him to collect the information. If necessary, support the user with the steps. Thank you!

Important! When you are using a terminal server solution (e.g. Citrix), or when you’re working on a managed workstation (your company has dedicated administrators), please always contact your administrator first. It’s best practice if the administrator first inspects the problem and supports you with preparing the following information.

Overview

Sometimes OpenWebStart does not work as expected. In theses cases our support tries to help you to get your OpenWebStart setup up and running, but in most cases additional information is required. This article shows you how to enable logging and debugging, collect all available information and prepare it for our support units.

Enable debug logging:

1. Start "OpenWebStart/OpenWebStart settings" from the Windows start menu.
2. In the "OpenWebStart settings" change to the page "Logging".
3. Check the option "Activate debug logging".
4. Leave the option "Log to standard out" enabled (Default).
5. Check the option "Log to file".
6. Remember the path from "Log folder:". You will need the underlined part, as well as the full path later:
7. Click the "OK" button to commit the changes.

Clear log directory

1. Open a Windows explorer (file manager) and navigate to the full path from "Log folder:", which you remembered in step 6.
2. If there are any files inside the "log" folder, delete them.

Run OpenWebStart:

1. E.g. start it from the application list page by pressing the respective tile, or start from use cases like "technical job" or "service management".
2. When beginning with the start steps, the browser usually offers to save or open a "JNLP" file. If possible, try to save the *.jnlp file and to remember the store location. This file should be sent to the support unit along with the other files.
3. In case an error dialog has popped up, please close it before continuing with the next steps.

Create ZIP archive and send email:

1. Open a Windows explorer (file manager) and navigate to the underlined part of the path from "Log folder:", which you remembered in step 6. E.g. "C:\Users\yourid" You will find two folders (among others) on this directory level, which are named ".cache" and ".config".
2. Right click on the ".config" folder. A context menu will open. Click on "Sent to. $gt; Compressed (zipped) folder".
3. Rename the file ".config.zip", which has been created, to "config.zip.txt". While renaming, confirm the warning "If you change a file name extension, the file might become unusable.", presented by Windows. The renaming is necessary, because the file will be sent as mail attachment and many mail servers remove .zip attachments from emails for security reasons.
4. Create a new email for your support unit. Describe the error briefly in your words, maybe one or two screenshots of the error messages will be helpful.
5. In case the file "config.zip.txt" is smaller than 10 Megabytes, attach it to the email draft.
6. In case the file "config.zip.txt" is bigger than 10 Megabytes, inform your support unit in the email, that an archive for analysis is available, but it’s got oversize. The support unit will clarify with you, how the file can be transferred.
7. Attach the following files additionally to the email:
   1. Navigate to your "Downloads" folder and locate the *.jnlp file you remembered from the section "Run OpenWebStart:". Attach this file to the email.
   2. Go back to "C:\Users\yourid". Navigate to the sub folder ".cache\icedtea-web\jvm-cache". Attach the file "cache.json" to the email. Do not add any further file or sub folder from this level!

   Disable debug logging:

   1. Start "OpenWebStart/OpenWebStart settings" from the Windows start menu.
   2. In the "OpenWebStart settings" change to the page "Logging".
   3. Set the "Show log window" drop down to "Disable".
   4. Uncheck the option "Activate debug logging".
   5. Leave the option "Log to standard out" enabled (Default).
   6. Uncheck the option "Log to file".
   7. Click the "OK" button to commit the changes.

   #014 Last update: 2021-08-27 10:00 CEST
   You're using Microsoft Edge and the browser blocks the download of the JNLP file.

   

   Details:
   You’re using the Microsoft Edge browser on your computer. When trying to launch an Java Web Start application a message appears "<filename>.jnlp was blocked because this type of file can harm your device."

   Cause:
   Newer versions of the Edge browser are configured in a way to prevent the download of .jnlp files for security reasons. This inhibits the usage of .jnlp files for our applications, too.

   Solution:
   You can enter a key into the Windows registry which allows the download of .jnlp files from daimler.com and mercedes-benz.com websites. This requires administrative rights on your computer.

   If required, contact your administrator to perform the following steps for you.

   1. Perform a download of the following file: daimler-edge-jnlp01.zip — ZIP 1 kB)
   2. Extract the ZIP archive using the Windows Explorer. This will result in a file named "daimler-edge-jnlp01.reg" with the following content:

   Windows Registry Editor Version 5.00

   • Please mind: These settings only affect the function of the Microsoft Edge browser based on Chromium. Other browsers may require diffent configuration to work correctly.
   • Edge expects a discrete entry in the Windows registry for each file extension. If you want to reuse the solution for other extensions than .jnlp, please create one index entry for each file extension.
   • In case of bigger installations it is recommended to not perform the registry configuration on your own, but instead let your administrator prepare and implement a central rollout of this change.
   • For administrators: In case the name index "254" for the key collides with already existing entries, just change the index to some other suitable value.

   #013 Last update: 2021-07-07 11:00 CEST
   When trying to start an application, only a small window appears without any content.

   Details:
   When trying to start an application, only a small window appears without any content. This problem typically starts shortly after an OWS installation or after performing an update. When inspecting the file system of the affected computer (using the Windows file manager) one can find a file named ".appletTrustSettings" in the subdirectory "C:\Windows\Sun\Java\Deployment".

   Cause:
   Probable cause is, that OpenWebStart once has been started with administrative rights on the computer. This means, the administrator clicked on a JNLP file or launched it through the browser. In this case OWS creates a file named ".appletTrustSettings" at this special location. All standard user accounts on this computer aren’t allowed to access this file read-write, which results in the error symptoms as described.

   1. Open the Windows Explorer (File Manager) on your computer.
   2. Navigate to the folder "C:\Windows\Sun\Java\Deployment"
   3. Delete the file ".appletTrustSettings". Administrator-rights will be required for this step!
   4. Start your JNLP file now as standard user. Please take care to never start JNLP files on your computer as administrator.

   #012 Last update: 2021-06-28 16:00 CEST
   Common: HowTo delete cache and config folders of OpenWebStart.

   Overview:
   Operating errors or malfunction can cause OpenWebStart to inhibit the start of an application. Instead of analysing the exact problem, the user can simply delete its OWS cache and config directories and try another launch of the application. This is quicker and often successful. The article describes how to delete these directories.

   • If you are working on a Citrix / Windows terminal server: Please contact your local administrator and provide the information of this FAQ article. The administrator can perform the removal for you.
   • If you are using the Aftersales applications through the Mercedes-Benz WCP platform: Please open an XSF ticket in XENTRY Portal, describing the problem in short. Press the copy button at the top of this FAQ article to copy a link to the clipboard, and paste this link into your XSF ticket details.

   Recommendation:
   Some errors have been fixed with OpenWebStart release 1.4.0. We strongly recommend to update to V1.4.0 or newer before applying workarounds.

   1. Make sure no OpenWebStart process is running at the moment.
   2. Open the Windows Explorer (File Manager) on your computer.
   3. Navigate to the folder "%USERPROFILE%\.cache"
      You can enter this string into the address bar of the Windows Explorer. On standalone PCs this location usually is "C:\Users\[userid]\.cache", Where [userid] is the id of the respective user.
   4. Delete the folder "icedtea-web".
   5. Try to launch the OpenWebStart application again.
   1. Make sure no OpenWebStart process is running at the moment.
   2. Open the Windows Explorer (File Manager) on your computer.
   3. Navigate to the folder "%USERPROFILE%\.config"
      You can enter this string into the address bar of the Windows Explorer. On standalone PCs this location usually is "C:\Users\[userid]\.config", Where [userid] is the id of the respective user.
   4. Delete the folder "icedtea-web".
   5. Try to launch the OpenWebStart application again.

   #011 Last update: 2021-06-20 12:01 CEST
   Rel 1.3.3. only: When trying to start an application, after the OpenWebStart splash screen nothing else happens.

   Prerequisite: Installed OWS release is 1.3.3

   Details:
   When trying to start an application, the OpenWebStart splash screen appears for a short moment. Then nothing else happens.

   Cause:
   OpenWebStart release 1.3.3 introduced new methods to improve data integrity in its caching directories, which was a problem in earlier OWS releases. The new locking mechanism uses a file "%USERPROFILE%\.cache\icedtea-web\cache\recently_used.lock" to gain exclusive access to the cached content. Sometimes the OWS process "fails" to remove this lock file after accessing the cache. All subsequent OWS processes now wait indefinitely for this file to disappear, because a method to detect and recover from a stale lockfile was missing until release 1.4.0.

   • You are working on a Citrix / Windows terminal server: Please contact your local administrator and provide the information of this FAQ article. The administrator should update to OWS V1.4.0 or newer as soon as possible.
   • You are using the Aftersales applications through the Mercedes-Benz WCP platform: Please open an XSF ticket in XENTRY Portal, describing the problem in short. Press the copy button at the top of this FAQ article to copy a link into the clipboard, and paste this link into your XSF ticket details. Please note: The problem will be fixed on this platform very soon.
   • Permanent solution if you are working on a local PC: Please update to OWS V1.4.0 or newer.
   • Workaround: Perform the following steps on your PC:
     1. Open the Windows Explorer (File Manager) on your computer.
     2. Navigate to the folder "%USERPROFILE%\.cache\icedtea-web\cache"
     3. Delete the file "recently_used.lock". This will allow all already waiting OWS processes to continue their start.

   #010 Last update: 2021-06-20 12:00 CEST
   When trying to start an application, a dialog box opens stating "Fatal: Initialization Error: Could not initalize application.".

   Details:
   When trying to start an application a dialog appears "Fatal: Initialization Error: Could not initalize application. The application has not been initialized, for more information execute javaws from the command line."
   When clicking on "Show details", then one of the error messages states the following:
   "Caused by: net.sourceforge.jnlp.LaunchException: The application uses non-codebase resources, which do match its Application-Library-Allowable-Codebase Attribute, but was blocked from running by the user."

   Cause:
   OpenWebStart displays the user different security prompts when starting an application. In case the user decides to store the decisions permanently, they will be saved into the file "%USERPROFILE%\.config\icedtea-web\.appletTrustSettings". Unfortunately the default selection which is being saved is the option "For Applet". For unknown reasons this selection sometimes leads to the described error symptoms when continuing to use OpenWebStart.

   • You are working on a Citrix / Windows terminal server: Please contact your local administrator and provide the information of this FAQ article. The administrator can fix this for you.
   • You are using the Aftersales applications through the Mercedes-Benz WCP platform: Please open an XSF ticket in XENTRY Portal, describing the problem in short. Press the copy button at the top of this FAQ article to copy a link to clipboard, and paste this link into your XSF ticket details.
   • You are working on a local PC: Please perform the following steps on your PC:
     1. Open the Windows Explorer (File Manager) on your computer.
     2. Navigate to the folder "%USERPROFILE%\.config\icedtea-web"
     3. Delete the file ".appletTrustSettings". This file contains the security prompt decisions the user has made so far when starting applications via OWS. Wrong decisions can inhibit the start. As there is no way to edit the decisions, the easiest way is to delete the file containing all stored decisions.
     4. Now start an application through OWS. IMPORTANT: When saving security prompt decisions, the radio button in the dialog must be switched from "( ) For Applet" to "( ) For Website . ". This is described in our online documentation for OWS usage.

   #009 Last update: 2020-12-16 16:46 CET
   When trying to start an application, a dialog box opens stating "KeyStore Error" and displaying a password prompt.

   Cause:
   For unknown reasons sometimes errors occur in one of the files, which store user specific certificates during the usage of OpenWebStart.

   

   1. Open the Windows Explorer (File Manager) on your computer.
   2. Navigate to the folder "%USERPROFILE%\.config\icedtea-web\security":
   3. Delete all the trusted.* files in this folder (marked yellow).
   4. Launch the desired application again from the application list or from XENTRY. The deletion removed the broken file, OpenWebStart will recreate the files with the next start without errors.

   In case the application start fails on a terminal server system, please contact your administrator for help, referring to this support article.

   #008 Last update: 2020-07-15 20:06 CEST
   When trying to start an application, a dialog box opens stating "Warning — Unavailable Version of Java Requested".

   

   Cause:
   Oracle Java is installed on your system, and OpenWebStart wasn’t installed at all, or it was installed additionally, without removing Oracle Java. The Java Web Start of Oracle can’t process some attributes of the JNLP file and asks the user how to proceed further:

   1. Click on "Run with the latest version". The application will be launched with Oracle JRE. Currently it is still compatible. This dialog box usually only appears once.
   2. On occasion install OpenWebStart according to our installation instructions. If OpenWebStart is already installed, consider uninstallation of Oracle JRE if it’s no longer used.

   #006 Last update: 2020-02-24 13:07 CET
   When trying to start an application, OpenWebStart fails, displaying the message: "No suitable JVM was found to start the application."

   1. In the OpenWebStart settings the settings of the JVM Manager have been changed in a way, that the Java Virtual Machine required for Aftersales applications can’t be downloaded and used by OWS.
   2. Your proxy settings might be incorrect, OWS can’t access the internet as required. In this case please mind the information on the Configuration page.
   1. Start "OpenWebStart/OpenWebStart settings" from the Windows start menu.
   2. In the "OpenWebStart settings" change to the page "JVM Manager".
   3. In the bottom right corner click on "Settings".
   4. Following values must be set for a correct function:

   If you click now again on an Aftersales rich client application in the application list and open the JNLP file, the required JVM package should be downloaded from xentryportal.i.daimler.com and the application should be started.

   #005 Last update: 2020-02-07 10:03 CET
   I firstly installed OWS "for the current user only" and then "For all users", but it still doesn't start. (Uninstallation as Standard User)

   • The OpenWebStart installation "for the current user only" sometimes leaves artefacts, which inhibit the "For all users" installation to work correctly.

   Solution:
   If OpenWebStart has been installed "for the current user only", it must be uninstalled again and some registry keys must be deleted carefully. Perform the following steps for check and removal of these artefacts.

   1. Make sure, you are logged in as the correct "non admin" user.
   2. Make sure, that no instance of OpenWebStart is running for your user anymore.
   3. Open a Windows Explorer (file manager).
   4. Navigate to %USERPROFILE%\AppData\Local
   5. Open the folder "OpenWebStart". If it does not exist, either you don’t have a "non admin" installation, or you have to contact your local administrator for further help.
   6. In the "OpenWebStart" folder, launch the application "uninstall"
   7. Perform the uninstallation steps as requested by the application.
   1. In the bottom left corner press the Windows start icon.
   2. Start typing "cmd" (without double quotes). Windows suggests you "Command Prompt" as search result. Launch this application.
   3. Remove user level javaws definition
      Enter the following command (yellow text) into the command prompt:

   C. Final step:
   Log out your current user from Windows and log in again.

   #003 Last update: 2020-02-06 16:19 CET
   How can I identify, whether OpenWebStart has been installed as admin or as standard user?

   1. OpenWebStart is only functioning for the user, which performed the installation.
   2. The start of WIS/ASRA does not work in multiple variations (XENTRY Portal linkout, DMS start)

   Please notice: In case you are working with a terminalserver solution, please contact your administrator in case of problems. The following tasks are only valid for standalone systems.

   1. In the bottom left corner press the Windows start icon.
   2. Start typing "cmd" (without double quotes). Windows suggests you "Command Prompt" as search result. Launch this application.
   3. Enter the following command (yellow text) into the command prompt:

   #004 Last update: 2020-02-06 12:59 CET
   When trying to start WIS/ASRA, an error message is being displayed: "An error has occurred. An application start error occurred. Possible reason are that the Java Web Start executable could not be determined, opening the EWA Download Area in the browser failed or the start of WIS/ASRA Standalone failed. Fault code: 1005"

   1. OpenWebStart hasn’t been installed with the option "For all users", but instead "for the current user only". This causes some important keys missing in the Windows registry.
      Solution:
      Uninstall OpenWebStart according to the Troubleshooting guide "Uninstallation as standard user". Then install OpenWebStart according to the Installation guide.
   2. An outdated version of OpenWebStart has been installed.
      Solution:
      Uninstall OpenWebStart as administrator using the Windows system control panel. Then install OpenWebStart according to the Installation guide.Important! When performing the installation, download the latest OpenWebStart version from our Downloads page!

   #002 Last update: 2020-02-06 06:32 CET
   Download of the required JVM fails.

   When trying to launch one of the Aftersales applications, the download of the required JVM fails with a nonspecific error message:
   

   One possible root cause could be a missing configuration of the JVM Manager in the OpenWebStart settings:
   

   The option "Nutzung von Server aus JNLP Datei erlauben" must be set.

   Прежде чем перейти к Google

   Если вы выберете «Принять все», мы также будем использовать файлы cookie и данные, чтобы:

   • Разрабатывать и улучшать новые сервисы.
   • Показывать рекламу и оценивать ее эффективность.
   • Показывать персонализированный контент (в зависимости от выбранных вами настроек).
   • Показывать персонализированную рекламу (в зависимости от выбранных вами настроек).

   Если вы выберете «Отклонить все», мы не будем использовать файлы cookie для этих дополнительных целей.

   Неперсонализированные материалы подбираются с учетом таких факторов, как контент, который вы просматриваете в данный момент, ваши действия в текущем сеансе поиска и ваше местоположение. Неперсонализированная реклама подбирается с учетом контента, который вы просматриваете в данный момент, и вашего местоположения. Персонализированные материалы и реклама также могут включать более актуальные результаты, рекомендации и объявления, подобранные с учетом истории ваших действий в текущем браузере, например поисковых запросов в Google. Если это необходимо, мы также используем файлы cookie и данные, чтобы показывать материалы в соответствии с возрастом пользователей.

   OWS Context User Guide

   Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights. Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.

   This document is a user guide created as a deliverable in an OGC Interoperability Initiative as a user guide to the work of that initiative and is not an official position of the OGC membership. There may be additional valid approaches beyond what is described in this user guide.

   POINTS OF CONTACT

   1. Introduction

   While over the last 10 years use of open standards compliant geospatial web services such as WMS, WMTS, WFS, WCS and CSW has grown massively, there has not been an effective open standards mechanism to assemble a collection of information such that it can be exchanged easily among a community. While some GIS vendors support such a capability the solution is typically not portable between vendors. The OGC did develop the Web Map Context standard (05-005) but this only supported WMS and so was relatively limited. The OWS Context Standard (OWC) was developed to allow advanced sharing ofgeospatial ‘Context’ or ‘view’ between users across a wide range of application types (browser, desktop applications, apps) and technologies (desktop, mobile, embedded etc). The standard is modular and easily implemented, and supports a wide range of OGC service standards as well as in-line or local content.

   OWS Context offers a solution to a wide range of sharing requirements. Chapter 1 describes a list of use case examples. Chapter 2 will provide a detailed description of each of these examples.

   1.1. Usage Example — Shared Situational Awareness

   Users in a range of environments have access to the central services, but typically wish to collaborate using a range of information. In a collaboration built on for example an emergency response there is typically a wide range of stakeholders and a need to provide them with relevant common information.

   1.2. Usage Example — Sharing Catalogue Searches

   A users wishes to save or exchange the query and results from various catalogue searches to avoid duplication of effort. In this case a user would execute one or more searches and retain each search request and possibly results set and be able to exchange the search and results set with others so that they could review the results or modify and re-execute the search.

   1.3. Usage Example — Processing Services Management

   A user wishes to save and/or exchange the configuration and/or results of an analysis or processing activity. The process to be executed will be stored in the context document as well as inline or referenced results.

   1.4. Usage Example — Index or Catalogue of Data Collections

   A user wishes to create a collection of datasets, for example OGC GeoPackages which are split geospatially (tiled) and/or based on themes. The OWS Context document can provide a catalogue or inventory of these.

   1.5. Benefits of OWS Context Documents

   Some of the key benefits of OWS Context are:

   OWC is open standards compliant allowing sharing between different system technologies.

   OWC documents are easily created, exchanged, catalogued and read.

   OWC documents can be encoded in XML/ATOM or GeoJSON. The two formats are interchangable.

   OWC supports not only WMS but a wide range of other OGC Services (CSW, WFS, WCS, WPS, WMTS etc)

   OWC Supports inline content in well known encodings such as GML and KML.

   OWS Context Documents can reference local files in for example GeoTIFF.

   OWC is easily extensible to include new service types, inline content and file = formats (OGC and non-OGC) without the need for a change in the standard.

   An OWS Context Document primarily contains references to information and so is itself relatively small in size. It therefore is easy to exchange and access.

   1.6. Normative References

   The following normative references are used in this document.

   OGC 14-055r2, OGC OWS Context GeoJSON Encoding Standard 2016-10-08. This document has now been approved as an OGC Standard but has yet to be published to the OGC Standards registry.

   OGC 15-113r2, OGC CDB Core Standard. This document has now been approved as an OGC Standard but has yet to be published to the OGC Standards registry.

   GeoRSS Geographically Encoded Objects for RSS Feeds. (http://www.georss.org/)

   2. Common Use Cases

   The Context Document goal is to support the exchange of a set of information elements between human users or application programs for a range of purposes such that the Area of Interest, time range, resources and their configuration is unambiguously exchanged between applications.

   2.1. Use Cases

   The OWS Context document is aimed at meeting a range of user context exchange requirements around sharing information. This section provides more detail on the primary use cases described in section 1 including a definition ofcommon sub use-cases.

   2.1.1. Shared Situational Awareness/COP Exchange

   Users in a range of environments have access to the central services, but typically wish to collaborate using a shared set of information of information. In a collaboration built on for example an emergency response there is typically a wide range of stakeholders and a need to provide them with relevant common information. Often one person or group (typically geo-support) has the responsibility to provide a set of information to other users (in this case commanders and on-scene responders) in time sensitive situations to allow them to deal with the evolving situation; given that they do not have time to assemble information themselves. The OWS Context Document standard allows the geo-support personnel to assemble a set of relevant information, accessible via web services, and pass it to other users (by email message, file transfer or by storing it within an OGC catalogue).

   On-Line COP Use Case

   The exchange of a common operating picture or view of information is recognized as one of the most important uses of the OWS Context Document. Often a COP defines a geographic Area of Interest and a set of information layers and queries to specific points of interest. The content of a COP may be made up of both web services and local content, and the OWS Context document allows this to be supported. It also allows the inclusion of alternatives for a given layers.

   A critical element of a shared situational awareness environment, whether used in a military, civil incident management or any other situational awareness context is the ability to exchange COPs between systems based on different technology. There are many equivilent approaches to OWS Context, but none which offer a vendor agnostic approach. This hetrogeneous model means COPs can be shared in a number of environments, for example between command centers and deployed users in vehicles or on foot, and using everything from laptops in mobile vehicles through to tablets, mobile devices or wearable technology (see figure 2.1).

   

   Figure 2.1 — OWS Context SSA Use Case

   A COP may take many forms and have many uses, it may represent a 2D map display, a 3D map display, an augmented reality view, or a textual representation of geospatial information.

   The COP exchanged is not simply a graphic but a ‘live’ view. When loaded it should show the latest state of the information referenced. This is a capability of OWS Context.

   In this basic COP use case, OWS Contexts are simply exchanged between systems using a file system or via a messaging system such as email. More advanced exchanges are possible via a catalogue where users can identify groups of context documents relevant to them directly or incidentially. In addition it is possible that users could be notified on new contexts using a subscription scheme (potentially based on the OGC PubSub Standard).

   

   Figure 2.2 — OWS Context SSA Use Case

   On-Line COP Exchange Via Catalogue

   OGC Compliant catalogue services provide a useful way to manage OWS Context Documents.

   

   Figure 2.2 — OWS Context Catalogue Storage Use Case

   Off-Line COP Exchange

   As part of this there is the recognition that in some cases the services referenced may not be available, and therefore some information (for example overlays or thumbnails) may need to be carried in the context document itself or alongside it. The context document layers may need to support both an on-line and an off-line alternative. One delivery model for a range of geospatial information is the GeoPackage standard. One specific model is to use the OWS Context document to provide a defintion of the services to be harvested into a GeoPackage so that the content can then be used off-line. Either a WPS service (GeoPackager) or the client itself can use the context document to load the GeoPackage with data and potentially update a GeoPackage which was already created. The context document allows the layers (WMS or WMTS) and feature types (WFS) required to be defined but also the geo-extent of data to be harvested.

   Of course GeoPackage is not the only carrier encoding that could be used in this way, and evolving standards such as CDB [Ref 4] could potentially be created from an OWS Context defintion. Alternatively completely proprietary caches could be created on a client, once again using OWS Context to define the content of a cache. The attractive element of this overall workflow is that a client can see what will be cached using the normal on-line access, before executing the process to cache the data.

   

   Figure 2.4 — OWS Context Off-line Use Case

   2.1.2. Exchange of a Catalogue Query and Results

   This use case relates to the exchange of discovery results from various catalogue searches, to avoid duplication of effort. In this case a user would execute one or more searches and retain each search request and possibly results set and be able to exchange the search and results set with others so that they could review the results or modify and re-execute the search. To do this primarily CSW requests and optionally results will be stored in the context document. This allows the retrieved results to be reviewed but also allows the query used to obtain the results to be re-run or modified and rerun.

   2.1.3. Exchange of the Configuration and Results of a Process

   A user wishes to save and/or exchange the configuration and/or results of an analysis or processing activity. The process to be executed will be stored in the context document as well as inline or referenced results. This type of context document might use WPS to define the processing, with results returned by the WPS, inline in the Context document in GML, in a referenced image, or available via another OGC service (WMS, WMTS etc).

   2.2. Requirements

   The above use cases lead to the following general requirements for an OWS Context document.

   The Context Document shall provide the capability to identify the temporal extent of the COP (one or more time envelopes). (See Chapter 5 — Time Interval of Interest Metadata)

   The Context Document shall provide the capability to define a series of configured resources together which provide relevant information to the COP User. (See Chapter 5 — Resources)

   The Context Document shall define the order of precedence of the resources included (this could be interpreted as, for example, the order of display by visualization clients) (See Chapter 5 — Ordering of Resources)

   The Context Document shall allow any service type to be specified and any rules to be specified. (See Chapter 5 — Offering)

   The Context Document shall provide information to allow clients to test if a service matches a supported profile in order to understand if they can interpret it. (See Chapter 5 — Telling if an XML/GeoJSON Document is a Context Document)

   The Context Document shall allow information targeted at different representations to be included (i.e. not just targeted at geographic visualization or just visualization). (See Chapter 6 — Terradue — Using OWS Context to store Searches)

   The Context Document shall allow information to be marked as enabled or disabled, i.e. it is to be presented to the user when the context is opened or isn’t. Source: WMC Specification: which has and on/off option (layer not displayed or not when loaded). (See Chapter 5 — Visibility Attribute)

   It shall be possible to associate information with embedded graphics information. (See Chapter 5 — Content Offerings)

   The Context Document should allow the in-line inclusion of a resource (literal value of a resource) in the context document. (See Chapter 5 — Content Offerings)

   The Context Document should allow the parameters which define the resource or processing service steps to be captured. (See Chapter 5 — Envitia_TB12_OWC.xml and Envitia_TB12_OWC.json)

   3. The OWS Context Document Structure

   An OWS Context (OWC) document consists of a number of key elements. These are shown in figure 3.1.

   Saved searches

   Use saved searches to filter your results more quickly

   You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

   Dartanlla / OWS Public

   Open World Server system

   License

   Dartanlla/OWS

   Name already in use

   • Local
   • Codespaces

   Use Git or checkout with SVN using the web URL.

   Work fast with our official CLI. Learn more about the CLI.

   Sign In Required

   Please sign in to use Codespaces.

   Launching GitHub Desktop

   If nothing happens, download GitHub Desktop and try again.

   Launching GitHub Desktop

   If nothing happens, download GitHub Desktop and try again.

   Launching Xcode

   If nothing happens, download Xcode and try again.

   Launching Visual Studio Code

   Your codespace will open once ready.

   There was a problem preparing your codespace, please try again.

   Latest commit

   Git stats

   Files

   Failed to load latest commit information.

   README.md

   Open World Server (OWS)

   By SabreDartStudios

   Open World Server (OWS) is a server instance manager designed to create large worlds in UE4. Either by stitching together multiple UE4 maps or by splitting a single large map into multiple zones, OWS will spin up and shut down server instances as needed based on your world population. OWS can load balance your world across multiple hardware devices. OWS can support thousands of players in the same world by instancing up and out. A single zone can be instanced multiple times to support a large population in one area. Areas of a map can also be split up into multiple zones to support a larger population. In addition to server instance management, OWS also handles persistence for Accounts, Characters, Abilities, Inventory and more.

   Похожие публикации:

   1. Как выпустить пластиковую карту если есть виртуальная
   2. Как зайти в сбербанк с другого телефона
   3. Как оформить рассрочку сбербанк
   4. Что предприятие вправе самостоятельно устанавливать в сфере трудовых отношений