Setting Up the Proxy Server

101 18
Here we describes the configuration steps that are necessary to get an Oracle Unified Directory proxy instance up and running. We provide an overview of the tested Oracle Unified Directory proxy deployments. Other deployments do not have sufficient test evidence.
To set up the proxy, you must have one or more remote LDAPv3-compliant directory servers. Oracle Unified Directory proxy has been tested with Oracle Unified Directory and Oracle Directory Server Enterprise Edition 11g Release 1.
Before you start to set up the proxy, decide on the type of deployment architecture that you want to implement from the following list:
• Simple load balancing
• Simple distribution
• Distribution with load balancing
• Failover between data centers
• Distribution with failover between data centers
A global index catalog can be incorporated into any scenario that uses distribution. For information about creating a global index catalog.
Methods of creating a proxy set up:
• Graphical user interface (GUI). The GUI setup is a Java-based graphical installer that enables you to configure all the elements required for specific Oracle Unified Directory proxy deployments.
You can use the GUI setup only once per instance. If you want to modify an installation after you have run the GUI setup, you must use the dsconfig command.
• Command-line interface (CLI). The interactive command-line setup prompts you for the first few steps of the Oracle Unified Directory proxy installation. To complete the deployment, you must configure a number of additional elements (such as distribution and/or load balancing) using the dsconfig command.

How to set up proxy server with a GUI
Here is a methodical installation guide using the oud-proxy-setup graphical interface, including configuration examples for simple deployments.
Before running the command, make sure that you have determined the best
Presentation of the GUI Setup Wizard
The GUI setup wizard is organized as follows:
• The panel on the left hand side has a the steps of the setup process. It also contains deployment sub-steps.The arrow in the left hand pane indicates the current step.
• The main area on the right is the action pane, where the definition of your deployment is given.
• At the bottom of the window you have the option to go back and forth (or quit) to modify and complete your installation.

Proxy servers currently play an important role in a network by making an efficient use of bandwidth through caching. They are primarily designed around the idea of reusing cache objects to save bandwidth and improve performance.
In doing we need to check which objects to cache and which not to. In order to conserve bandwidth and other storage resources cache servers are configured to prefer small cache objects over large cache objects. The cache size is also limited. These proxy servers are now unable to cache video, music and photos.

Architecture:
Cache objects in current caching servers are not accessible from external applications directly or otherwise in any meaningful manner since they are stored on disk using a custom format specific to the cache server. The next generation proxy servers will save the actual data along with its meta data that is described in a RDBMS and provide access to it via Web services.

A new proxy server with caching server consists of two layered stacks. The first is the Cache Messaging Service ( CMS) that consists of a set of web services used for communicating with clients to offer discovery, query and exchange of application specific messages.
The second layered stack is the Object Transpor Service (OTS) that is used for transferring of cached objects between the client and Next Generation proxy server.
Both of these layered stacks are designed with extendability in mind to offer multiple implementations.
For instance. CMSi can he transported over standard HTTP traffic. via XMPP or even possibly over a GNUTella like P2p network.
Likewise OTS can make use of http, ftp, XMPP or Bit torrent to deliver the cached objects.

Figure 1 – CMS Layers
Figure 1 describes how layers of the CMS are organized. The first layer n the cache object index. which keeps be m.ping between a URI and the corresponding local cache object.
The first layer is the cache object index which keeps the mapping between a URI and the corresponding local cache object.
This is implemented using a RDBMS to store the mapping data for efficient storage a. retrieval purposes.
The next layer is the middleware that implements services for accessing Cache Object meta data. This layer will expose a web services API using SOAP in the form of the Cache Communication Protocol Layer.

Potential Uses of Caching in future:
1. Search Engine Integration: Searching the cache using the popular search engines would be another useful idea. It would be quite convenient and interesting if we integrate this search mechanism with search engines such as googletm. One method of doing this would be to assign the tags assigned to cached objects to be used as key words.
2. UPnP support: Universal Plug and Play is an emerging technology for smart spaces and a generic protocol for device communication used by portable media devices and media servers. Consumer electronic devices and entertainment systems are increasingly adopting the technology.
Source...
Subscribe to our newsletter
Sign up here to get the latest news, updates and special offers delivered directly to your inbox.
You can unsubscribe at any time

Leave A Reply

Your email address will not be published.