Shulou(Shulou.com)06/01 Report--

Xiaobian to share with you how to use IIS components in the virtual directory integration system integration, I believe most people do not know how, so share this article for your reference, I hope you read this article after a great harvest, let us go to understand it!

There are now more or less several IT applications within the enterprise. Such as enterprise portal website, enterprise mailbox system, OA office automation system and so on. Unfortunately, due to unreasonable planning, these information systems often work independently. Take a simple example. User login mailbox, OA system, or company document library, often need to enter different user names can be achieved. This leads to inefficiency. When this happens, the IT leader of the enterprise needs to figure out how to integrate these applications.

This integration can be accomplished through IIS components in Windows Server 2008.

Within this IIS component, there is the function of virtual directories. Simply put, a virtual directory links to another directory that is not contained in the home directory by providing an alias. This function can be used to expand the home directory of the website. For example, this virtual directory can make resources on another server (such as the entry interface of the OA system) and so on. As you can see, virtual directories allow you to link resources deployed on different servers together. Then through a certain identity authentication mechanism, to achieve an account login multiple systems.

1. Virtual directory mounts internal information web pages of enterprises.

Usually, there is some internal information that the company does not want customers or suppliers to see. This is often done as a separate website. But for ease of access, still want to hang on the enterprise portal. For example, the daily meals of the enterprise, the contact information of internal personnel, etc. This content is generally not hosted on the same server as the enterprise Web server. This is mainly because these internal information needs to be constantly updated, and the updated personnel are generally not IT personnel, but administrative personnel. However, delegating Web server change authority to these people will undoubtedly create security risks.

A safer way to do this is to make these content into a few simple web pages and then place them on other hosts. In any case, these contents are usually accessed by insiders, so there is no problem in performance. The main obstacle encountered is the need to associate these internal pages with the enterprise portal. In this way, enterprises do not need to apply for a domain name for this purpose, and can use the existing domain name to access.

This can be done through virtual directories. On the home Web server, turn on the virtual directory and connect it to a folder on another server. For users, it is as if they are accessing the same server. It's not true. It is transparent to users. How to configure, the author will also talk about it in the following content.

Second, virtual directory connection enterprise mailbox system or OA system.

Mailbox system and OA office automation system are essential office tools for many enterprises. However, due to the sequence of project implementation, these systems are often project-independent and lack effective integration mechanism. Simply put, users cannot log in to the mailbox system or OA system through the enterprise portal. This directly results in users having to enter different URLs to access the corresponding system. This may not be a big problem for users with a certain IT background. But in traditional enterprises, most people are ordinary employees after all. It is very difficult for them to memorize so many English characters. Ideally, they only need to know the company's main website. Then you can access the corresponding system through the connection on the company portal website.

In this case, integration can also be achieved through virtual directories. Generally speaking, OA systems or mailbox systems now allow access through web pages. At this point, you can design a login interface for the mailbox or OA system respectively. This difficulty is not very big, as long as there is a little experience in web page production users can achieve. Then in the virtual directory, point the path to this page. This completes the integration of the Web portal with these systems. Users can access these systems directly through connections on the portal.

However, it should be noted that this is only the initial integration. That is, if users need to log in to different systems, they still need to enter their respective accounts to access them. So I call it incomplete integration. If you want to achieve one-stop access, that is, like Netease and other portals, you can access multiple different systems with one pass account. This is also possible. However, it needs to be implemented with the help of another component of Microsoft Server Identity Authentication Service. The author will not talk about this aspect here. If necessary, the author will explain it in case form in subsequent articles.

Third, the virtual directory to achieve file sharing.

IT staff in daily management, document management and maintenance is a highlight. If the user's documents are stored locally, it is difficult to guarantee security. Such as accidental deletion of files by users, accidental changes to files, etc., are difficult to control. To do this, they need a unified platform to manage these files, such as antivirus, backup, recovery, etc. This can also be done through virtual directories.

In fact, the implementation mechanism is quite simple. Set up a shared folder on another server. Then connect it to this shared folder through the enterprise portal website (note that only users of enterprise content are allowed to access it when permissions are set, and access is not allowed through the external network). At this point, employees can view documents through this portal. You can upload files directly or make changes to files. For IT staff, only one file server needs to be maintained. without having to worry about files on individual clients. This undoubtedly reduces the workload of IT staff and improves productivity.

4. The main configuration process of virtual directory.

As can be seen from the above analysis, virtual directory is actually a path management. Channels can be created on an enterprise portal to connect content from other servers. Typically a virtual directory can contain documents and other information about a website at the level of a new website. To implement virtual directories in Windows Server, you must have relevant point permissions. If Web Server Administrator privileges are required. The configuration process is as follows:

From the Start menu, select IIS Management Tools. Virtual directories are a feature of IIS components in Microsoft Server. Then in the window that opens, expand the IIS server you want in the data structure and continue to expand the Sites node below.

If the administrator maintains multiple websites at the same time, all websites can be seen in this node. At this point, the administrator needs to determine which site to integrate on. Under normal circumstances, if the enterprise portal website (external) and internal website (internal) are separated, it is recommended to integrate internal services on the internal website, such as mailbox system, OA office automation system, etc. Integration for external services is implemented on external websites. Such as CRM system integration and so on. If there is only one portal site, you can only create channels on external sites. However, at this time, attention needs to be paid to the control of permissions. That is, OA and other internal user-oriented systems, only internal personnel can access. This can be achieved by IP address or authentication mechanism, etc. The administrator selects the desired Web site containing the new virtual directory, right-clicks on the Web site, and selects the Add Virtual Directory option.

3. In the dialog box, enter the name of the virtual directory. Under normal circumstances, if there are many virtual directories, an easy-to-understand alias is given to the virtual directory, which can bring greater convenience to subsequent maintenance. In addition, in order to improve compatibility, this alias *** should not use Chinese, but need to use English letters, and do not contain special characters. Then enter the physical network path to the back-ear folder of the virtual directory, or select through network neighbors. This can be resolved using IP addresses, DNS domain names or host names. I prefer to use IP addresses. Because this can improve the stability of the connection without worrying about DNS server problems.

*** A caveat is that if the virtual directory selected is a shared folder, additional credentials are required to associate the user with this access to the remote share. Note that this step is critical. If not configured, users may be denied access because they do not have relevant access rights.

The above is "how to use IIS components in the virtual directory integration system integration" all the content of this article, thank you for reading! I believe that everyone has a certain understanding, hope to share the content to help everyone, if you still want to learn more knowledge, welcome to pay attention to the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.