Server Explorer for Mac In addition to, of course, communicating with it from your client application, you will mostly use the Server Explorer application to work with Relativity Server, administer it, and develop and test schemas. Like Relativity Server, Server Explorer will be installed in the Applications folder of your when you install DA/Cocoa; it is also available on the for non-Data Abstract users who want or need to administer servers.
Download the latest from Windows, Windows Apps, Office, Xbox, Skype, Windows 10, Lumia phone, Edge & Internet Explorer, Dev Tools & more. Built in to Apple's OS X Server is the capability to manage your very own web server. With OS X Server's Websites service, you can host multiple websites — and you can host them based on unique.
![Internet Explorerdriver Standalone Server For Mac Internet Explorerdriver Standalone Server For Mac](/uploads/1/2/5/4/125404165/725516735.png)
 When you first start Server Explorer, you are greeted by a source list with available and known servers on the left and a welcome message on the right. Server Explorer uses Bonjour, also known as ZeroConf, to locate servers on the local network, so if you have Relativity Server running on your machine or anywhere else on your LAN, the server should automatically show up in the list, most likely with a yellow overlay icon like server “McMervyn” in Figure 10-6:  If your server is not found or you want to add a remote server that cannot be automatically discovered, you can click the “+” button in the bottom-left corner.
Enter the address of your server, such as and an optional name, and click Register, as shown in Figure 10-7.  Server Explorer can work with both Relativity Servers (indicated by the green-on-white Relativity logo) and custom Data Abstract servers (indicated by the black-on-green Data Abstract logo), although functionality for custom servers is limited, as there is not much to administer. The yellow icon overlay indicates, that while the server was found and connected to, no login information is known to authenticate with it.
To specify a login, select the server icon in the source list and then enter the username and password on the bottom right. The default administrator login for a fresh Relativity Server install is Administrator/Relativity.  A red cross overlay on a server icon indicates that there was a problem communicating with the server. This could mean the server is simply unavailable (once a server has been worked with and a login has been stored, Server Explorer will always show it in the source list, whether it is available or not; you can click the Action button in the bottom left and choose Forget Server to remove a server from the list if you no longer plan to work with it), or that there is a misconfiguration.
Selecting the server should show a message describing the problem. The source list item for each available server can be expanded to show more details about the server in question. The Drivers folder provides a summary of all the different database drivers that are available on the server, basically letting you know what kind of databases this Relativity Server can work with. The list of drivers might depend on the platform that the server is running on, and also on what database components were installed. Relativity Server automatically tests all drivers for functionality on startup, and only drivers that have been found to work properly on the server will show in the list. At the very least, you should see options for Microsoft SQL Server, Oracle, PostgreSQL, Firebird and SQLite. There’s not much to do with the Drivers folder, it is merely for informational purposes at this stage.
The Domains folder is more interesting; in here, you should see an entry for each domain configured on the server. For a fresh install of Relativity Server, you should have a sample domain called “PCTrade” set up for you already. This is the domain that’s used by the samples throughout this book. Once you’re familiar enough with Relativity Server and Data Abstract and no longer need the sample domain, you can of course always delete it, simply by selecting it, clicking the Action button in the bottom left and choosing Delete Domain (or by pressing ⌘⌫).
Just like with the server node, selecting a domain shows an info page for the domain, as shown in Figure 10-9. As you can see, there are two optional logins you can provide here. The first is the Developer Login, which is only active (and needed) if you did not provide an Administrator Login on the server level. We will talk more about that shortly. The second login is the Data Login. This is the same login your client applications would use, and Server Explorer will use that for any test queries or preview data you may request. You do not need to worry about filling this out right away – Server Explorer will ask you for the login, if necessary.
 Login Providers Relativity server uses so-called Login Providers to handle different authentication options. We’ve already seen three different places where Server Explorer allowed or needed us to specify a login, and to match those, there are also three different places where a Login Provider can be configured:. The server-wide Administrator Login Provider. This can be configured by selecting the Setup node right underneath the server node, as shown in Figure 10-10, below. There are two options available for the Administrator Login at this time: the StaticLoginProvider and the LdapLoginProvider. The Developer Login Provider for each domain. This can be configured by selecting the Setup node right underneath the domain node.
The Data Login Provider for each domain. This can also be configured by selecting the Setup node right underneath the domain node. In addition to the StaticLoginProvider and LdapLoginProvider, the per-Domain logins can choose from three other options: DbTableLoginProvider, DbCommandLoginProvider and AdminServicesLogin. Let’s have a closer look at what these login providers do. StaticLoginProvider is the simplest of the login providers, and the most useful for admin/developer login, or in the early development phase of your project.
It works by simply letting you specify a list of valid usernames and passwords that will be accepted. This is the default login provider for all logins on a freshly installed Relativity Server or a freshly created domain.  DbTableLoginProvider validates the username and password against a table in your database. It allows you to select a table from your schema, as well as two fields from that table that contain usernames and passwords, respectively. The Login will be verified by selecting from the table, and access will be granted if a row with matching username and password is found. DbCommandLoginProvider also lets you validate the login against your database, but instead of simply querying a table, it will execute a command defined in your schema.
You could implement the command to run a query, execute a stored procedure, or perform more some complex SQL. In order to qualify, the command must take two parameters (username and password) and return a Boolean. Tip: in order to avoid full access to your login table by client applications, it is usually sensible to mark the command or data table used for login as Private in the schema. We will learn more about data tables and commands in the next chapter. Since both of these options are based on information in the database, they are only available on domain level. LdapLoginProvider is the most complex one of the available login provider options. It can be used to connect Relativity to an existing LDAP server in your organization to validate logins.
This can be very useful if you want your application to automatically share usernames and passwords with other non-Relativity, non-Data Abstract services in your company. Getting into the details of LDAP would go beyond the scope of this text, but if your organization is using LDAP, your LDAP administrator should be familiar with the required options.  Finally, the AdminServiceLogin option, available for the per-domain login providers, simply indicates that rather than using separate logins, the same settings as for the server-wide Admin Login should be used here. So what is the difference between administrator and developer login? Essentially, the admin login is a superset of the developer login.
If you provide an admin login in Server Explorer, you have access to the full server, including the ability to:. Change global server options (such as the Admin Login Provider itself). Create or remove domains. Create, change and remove Connections.
Do anything else that can also be done with a developer login If you only have a developer login for a specific domain, you can only work within the confines of that domain.
In this tutorial, we will install Webdriver (Java only) and Configure Eclipse Step 1 - Install Java on your computer Download and install the Java Software Development Kit (JDK). Next – This JDK version comes bundled with Java Runtime Environment (JRE), so you do not need to download and install the JRE separately. Once installation is complete, open command prompt and type “java”. If you see the following screen you are good to move to the next step Step 2 - Install Eclipse IDE Download latest version of 'Eclipse IDE for Java Developers'. Be sure to choose correctly between Windows 32 Bit and 64 Bit versions.
You should be able to download an exe file named 'eclipse-inst-win64' for Setup. Double-click on file to Install the Eclipse.
A new window will open. Click Eclipse IDE for Java Developers. After that, a new window will open which click button marked 1 and change path to 'C: eclipse'. Post that Click on Install button marked 2 After successful completion of the installation procedure, a window will appear.
On that window click on Launch. This will start eclipse neon IDE for you. Step 3 - Download the Selenium Java Client Driver You can download the Selenium Java Client Driver. You will find client drivers for other languages there, but only choose the one for Java. This download comes as a ZIP file named 'selenium-2.25.0.zip'.
For simplicity, extract the contents of this ZIP file on your C drive so that you would have the directory 'C: selenium-2.25.0 '. This directory contains all the JAR files that we would later import on Eclipse.
Step 4 - Configure Eclipse IDE with WebDriver. Launch the 'eclipse.exe' file inside the 'eclipse' folder that we extracted in step 2. If you followed step 2 correctly, the executable should be located on C: eclipse eclipse.exe. When asked to select for a workspace, just accept the default location.
Create a new project through File New Java Project. Name the project as 'newproject'. A new pop-up window will open enter details as follow. Project Name. Location to save project. Select an execution JRE.
Select layout project option. Click on Finish button 4. In this step,. Right-click on the newly created project and.
Select New Package, and name that package as 'newpackage'. A pop-up window will open to name the package,. Enter the name of the package. Click on Finish button 5. Create a new Java class under newpackage by right-clicking on it and then selecting- New Class, and then name it as 'MyClass'.
Your Eclipse IDE should look like the image below. When you click on Class, a pop-up window will open, enter details as. Name of the class. Click on Finish button This is how it looks like after creating class. Now selenium WebDriver's into Java Build Path In this step,.
Right-click on 'newproject' and select Properties. On the Properties dialog, click on 'Java Build Path'.
Click on the Libraries tab, and then. Click on 'Add External JARs.' When you click on 'Add External JARs.' It will open a pop-up window.
Select the JAR files you want to add. After selecting jar files, click on OK button. Select all files inside the lib folder. Select files outside lib folder. Once done, click 'Apply and Close' button 6.
Add all the JAR files inside and outside the 'libs' folder. Your Properties dialog should now look similar to the image below. Finally, click OK and we are done importing Selenium libraries into our project. Different Drivers HTMLUnit and Firefox are two browsers that WebDriver can directly automate - meaning that no other separate component is needed to install or run while the test is being executed.
For other browsers, a separate program is needed. That program is called as the Driver Server. A driver server is different for each browser. For example, Internet Explorer has its own driver server which you cannot use on other browsers.
Below is the list of driver servers and the corresponding browsers that use them. You can download these drivers Browser Name of Driver Server Remarks HTMLUnit HtmlUnitDriver WebDriver can drive HTMLUnit using HtmlUnitDriver as driver server Firefox Mozilla GeckoDriver WebDriver can drive Firefox without the need of a driver server Starting Firefox 45 & above one needs to use gecko driver created by Mozilla for automation Internet Explorer Internet Explorer Driver Server Available in 32 and 64-bit versions. Use the version that corresponds to the architecture of your IE Chrome ChromeDriver Though its name is just 'ChromeDriver', it is, in fact, a Driver Server, not just a driver. The current version can support versions higher than Chrome v.21 Opera OperaDriver Though its name is just 'OperaDriver', it is, in fact, a Driver Server, not just a driver.
PhantomJS GhostDriver PhantomJS is another headless browser just like HTMLUnit. Safari SafariDriver Though its name is just 'SafariDriver', it is, in fact, a Driver Server, not just a driver. Summary Aside from a browser, you will need the following to start using WebDriver. Java Development Kit (JDK).
Eclipse IDE -. Java Client Driver - When starting a WebDriver project in Eclipse, do not forget to import the Java Client Driver files onto your project. These files will constitute your Selenium Library. With new version of Selenium, there is no browser that you can automate without the use of a Driver Server.