User-how to config

Mr. Ding Xiaofeng has completed the translation. For details, see the following!

Configure geoserver

Directory
1. Introduction to Web management tools
1.1. Getting started with Web management tools
1.2. Login
1.3. Change Password
1.4. Save changes
2. Management page
3. Configuration
3.1. Server
3.2. WFS and WMS
3.2.1. Content
3.2.2. WFS additional content
3.2.3. Description
3.3. Confirmation
This file and data file are designed to describe in detail how to configure geoserver. It focuses on the basic content of web management tools, and then the options for configuration and the metadata of the server. Data Files mainly describe how to add your own data to geoserver. Both files are run in Web management tools. For information on running files, see developer files.

1. Introduction to Web management tools

Geoserver 1.2 focuses on Web management tools. The Web management tool is built on Struts (Link) and provides a series of complete drawing user interfaces. Therefore, users do not even need to contact the configuration file. It also provides the ability to "CREATE" a new configuration before saving the configuration. This work is operated by excellent teams of refractions research and funded by the GeoConnections project. Note that the Web management tool does not need to operate geoserver. You can run it directly in the configuration file. We will discuss this in detail in the developer part. For more information, see geoserver config files. However, for user files, we assume that you are running through web management tools. Some advanced users may need to directly access the file. We will discuss this part in detail. In the future, desktop customers such as udig may be used to manage subtle geoserver, because we will design such a situation. Management tools will be as intuitive and self-help as possible, and you can get as much help as possible from management tools. When you hover the mouse over the top, the help information will appear in each step and link (after you place the mouse over the top for one second ). At the same time, the international trend of management tools has been designed and has been translated into French, and will be translated into Spanish in the near future. When the computer starts, the language of the management tool is the same as that set by geoserver. If you are interested in translating geoserver into other languages, see how to help for more information.

1.1 getting started with Web management tools

For a simple understanding of Web management tools, start your browser and press the address below to enter:

Http: // localhost: 8080/geoserver

You will see the following webpage content:

Configuration 1.

The loading time required for the first access to this page, because geoserver needs to compile the application page. This will only happen when we enter for the first time. For future geoserver versions, we will try to completely delete the loaded part (this is the opposite of JRE and JDK, because Java needs to compile web pages ). At this time, you will see the welcome page contains some geoserver-related information and links, and then display the WMS title and essentials, as well as the WFS capacity file.
When you edit the content, the modification content will be reflected on the welcome webpage. Therefore, this is a good example for your geoserver and is linked to the capacity file. It also contains the link content of the three main parts of geoserver. Demo is the only publicly available part. It contains a good web page for geoserver WMS and WFS requests, and some instances are also available. Both management and configuration require you to log on first. Management is more in the concept phase, which means to manage a running geoserver. The configuration contains a large number of Web management tools, which are also the place where all geoserver configurations occur.

1.2 Login

Not every user can access and modify the geoserver configuration. Therefore, we need to enter the login name in the management and configuration sections. If you have not logged on, clicking any of the Start pages will bring you into the login status, or you can click the login link in the upper right corner to bring you into the login status.

In this case, the applicant only has one user name and password. In the future, we hope to have multiple user names so that different users can have different logon standards. This will include geoserver management, but the idealism will extend the ability to access and transmit at a level. Your capacity file will be changed to the user file application, if they are allowed to see the level and modify.
The new default geoserver password is:

Username: Admin (username: Admin)
Password: geoserver (password: geoserver)

We strongly recommend that you change the password because accessing geoserver management is not made public to all users.

1.3 Change Password

Enter the configuration section to change the password. You can select the server section and the password section. Enter your new username and password, and save the password.

1.4 save changes

The geoserver management tool is created to "try" your modifications. No matter where you are applying for configuration, you will see three buttons on the left. The most common operation is to click the "application" button after the modification.

In this way, the modified content will be applied to the running geoserver. Therefore, you can operate on your normal WFS and WMS to create the modified content to check whether all the items have been correctly configured. However, these modifications have not yet taken effect after the application. If you are about to restart geoserver, these modifications will be lost. If you want to save these changes, click Save.

This will save the current configuration, such as the XML file. geoserver will read this content at the next startup. If you do not want to save the changes, click the "LOAD" key to delete the changes you have made, so that the geoserver returns to the last modification State (or the last startup state, if no changes are saved ). Note that you can view the current modification status through the tool menu on the left side. If some modifications have been submitted but no application is available, a prompt appears in the configuration column. Once you click the application column, a star will appear on the geoserver side, marking that the changes to the application are not saved. Note that if you have applied some modifications and submitted other modifications, both of them can be easily marked. Each date and time shows the last modification time. The last thing to note is that the status bar indicates the number of successfully loaded data repositories. For your verification. We admit that this is not completely useful, but it looks cool, isn't it?

2. Management page

In the future, the management page will assume the role of placeholder. Currently, it is mainly used to remove outdated locks. However, we know that no customer will use the WFS lock function, so this function does not seem very useful. At the same time, it also provides some information on JVM, if jai has been installed. Free memory tools play a more or less role, but usually report chaotic numbers. In the future, the management page will play a role in managing user roles and entering licenses, but there are still many other tasks to be done before we proceed.

3. Configuration

You can obtain the configuration-related main page content from the "configuration" column on the welcome page.

There are four options on the main configuration page. In general, we recommend that you run the configuration in any order from top to bottom. If you are creating a geoserver result instance, it is very important to fill in all the files. If you only evaluate geoserver and want to test your own data, you can focus only on the Data Section (if you want the most precise data, you only need to focus on storage and Type features ). Although the server is also very useful, especially when you need to correct some small errors.

3.1 servers

The password is the unique segment of the server. For more information, see create a password.

The contact information is used in the capacity file section of the WMS server and appears in the contact bar of the Web management tool. We recommend that you fill in this information so that you can contact others when they need it. This is your own Information Description, because we will not repeat each item and will only explain the other parts:

The maximum type is used to establishing the largest feature that can return to a customer. This will result in incomplete WFS reflection, not returning all features, but for a particularly large desktop, when the customer (User) it was inadvertently proposed that some information would be returned when billions of bytes of data were sent to them.

Details control whether the returned XML contains a more user-friendly format. It contains relatively good indentation and new lines of blank space, but we only recommend that you use it for testing. The reason is that it will increase the amount of data fully returned by geoserver (So broadband is used), and most geoserver consumers will become users in extra space.

Verbose exceptions is one of the most useful options for configuration. Reporting minor program errors that you may encounter on geoserver is the most basic. Normally, geoserver only returns an error message. With verbose exceptions, the server will be able to return a series of detailed information for the programmer to solve the problem. For more details about the minor errors reported by geoserver, see how to help.

Feature setting specifies that feature encoding will be used in the XML section returned by geoserver. The default is UTF-8, which we recommend to most users. However, if the language you use requires different features, you should establish this option. If you have any questions, please submit a report because we fully believe in the importance of geoserver internationalization, but lack the actual testing time and capability. Note that feature settings must be listed in the Lana charset registry column and a Java command must be run. Most Java versions support a series of good features. If you do not have any features, you can add jars.

The number of geoserver login information is set up at the logon level. The list shows the number of Logon entries at the top of the list. Start debugging information for any information better than info. We recommend either info or fine. Note that you can only log on to the console during binary installation. We are trying to make it easier to save files. We are also studying the types of information that developers are more interested in. geoserver managers are more interested in this type of information, such as entering information, who is requesting and requesting content.

After completing the preceding information, click Submit. Then you can enter the normal save program and try to use the apply key to apply changes. If you want to save these changes, click Save.

3.2 WFS and WMS

In the next step, configure the WMS and WFS sections. These two parts are very similar. In most cases, you can set meta information for each part. The WFS section also provides some special WFS configuration items and the entry to the confirmation interface. If you only evaluate geoserver, you do not need to configure meta information. However, if you are providing public services for geoserver, we strongly recommend that you enter this information correctly, you will not be confused about the default geoserver layer. If you are only using one of WFS and WMS, we recommend that you delete another unused one in the content section. Each service has a directory and description. The Content Part controls the detailed options for each item **, while the description part focuses on the meta information of the capacity file.

3.2.1 content

The content section contains an activation check box-if you are not using any service (or are using another software, such as mapserver, serving another service), we recommend that you delete it, in this way, the user cannot access. This part also contains the online information section. We think it is more appropriate to put this part in the getcapabilities section, so we will skip this section for the time being. It should be assumed as the homepage of the service according to the specification. Some websites you have selected will tell you about WMS and/or WFS geoserver services. If you have not installed either of them, we recommend that you only install the geoserver website management tools page, because this is designed for this purpose. You only need to put the external address that the geoserver will enter. Use geoserver/without WFS or WMS.

Geoserver-* EXE is the simplest installation operation. Double-click to download the file and follow the Windows installer. Note that the pop-up standard Windows window will tell you which Java version is in use. If you cannot find a suitable Java version, an alert will be sent to you. You should install Java before using installer, so the link to the application will run correctly. Click "location" to install geoserver. The Windows Start Menu is displayed on the webpage.

3.2.2 additional WFS content

The WFS content contains two additional options. Srs xml determines whether the getfeature result will have srsname components, such as XML features, as follows:

<GML: multilinestring srsname = "http://www.opengis.net/gml/srs/epsg.xml#27354">

All examples of WFS specifications are as follows or are more concise:

<GML: multilinestring srsname = "epsg: 27354">

We recommend that you use the former (srsname and XML). The latter is provided mainly because it is difficult for some customers to parse the former for some reasons. Therefore, if users complain about the difficulty in correct parsing with their customers, you can also try not to check srsname such as XML.

Another option is service level, which allows you to close the entry to the processing. If you are opening your geoserver, this is usually very cautious, so that not anyone can access and modify your configuration. In the future, we hope to provide more complex configurations, rather than simple basic and transactional. For example, we hope to provide support for user level proofs and preferences, rather than just a simple switch. You can directly modify the configuration to get more control, indicating which is the insert you want to use, which is the update, and which is the Delete. Note that these changes are not reflected in the capacity file at this time. For example, it will still inform the address to be processed, so that no one can pass.

3.2.3 description

3.3 confirmation

Geoserver1.2 includes the latest validation capacity, well developed by refractions research, which has acknowledged with gratitude that the geoconnection institution has provided financial support for its development through the GEO update project. They also provide a mechanism to ensure that the features edited by geoserver have been cleaned before the spatial reversal data is inserted. If you are working with geoserver to its full WFS-1, we strongly recommend that you set up some validation tests. These tests can be easily set to ensure that simple things, such as no length, no curve. However, it can also express more complex tests, such as defining houses to ensure that there is no street crossover, and street names are defined in gazetteer. Confirm the configuration settings in the WFS section.
In section 1.2.4, we do not have time to further refine the validation guide. So far, only files created by refractions are available. For details, click here.

Reprinted please declare, and clearly indicate the translator, reprinted source thank you.