Difference between revisions of "ProtegeDevDocsGeneral"
(→Testing firewalls and web proxies) |
(→Testing firewalls and web proxies) |
||
| Line 29: | Line 29: | ||
Occasionally we get questions from people who are behind a firewall. In the past, we have had no way to simulate and test how Protege behaves in their environment and so our answers on the mailing list have been somewhat limited. But it turns out, as many IT types probably know well, that it is relatively easy to create a virtual network that lives behind an open source firewall, such as the [http://www.endian.com/us endian firewall]. There is an excellent and fun online [http://www.danscourses.com/Network-Security/create-a-virtual-network-with-virtual-routerfirewall.html course] that describes how to setup such a network either using [https://www.virtualbox.org VirtualBox] or [http://www.vmware.com VMware]. If you create a virtual network in this way, the virtual firewall machine will have two virtual network interfaces, the external network interface (the red one) which points to the network of the host machine, and another network interface (the green one) which can be shared by other virtual machines. The endian firewall can be configured by accessing the web page https://192.168.0.15:10443 on the green network. | Occasionally we get questions from people who are behind a firewall. In the past, we have had no way to simulate and test how Protege behaves in their environment and so our answers on the mailing list have been somewhat limited. But it turns out, as many IT types probably know well, that it is relatively easy to create a virtual network that lives behind an open source firewall, such as the [http://www.endian.com/us endian firewall]. There is an excellent and fun online [http://www.danscourses.com/Network-Security/create-a-virtual-network-with-virtual-routerfirewall.html course] that describes how to setup such a network either using [https://www.virtualbox.org VirtualBox] or [http://www.vmware.com VMware]. If you create a virtual network in this way, the virtual firewall machine will have two virtual network interfaces, the external network interface (the red one) which points to the network of the host machine, and another network interface (the green one) which can be shared by other virtual machines. The endian firewall can be configured by accessing the web page https://192.168.0.15:10443 on the green network. | ||
| + | |||
| + | So when I got a question on the web about how to make Protege work with a web proxy, I set about configuring a virtual network protected by a firewall that I had put together using the directions above. I used a virtual machine on the green network to configure the firewall using the web interface that I accessed using the https://192.168.0.15:10443 web address. I made two changes to the firewall configuration: | ||
| + | * I went to the firewall tab and then clicked "Outgoing traffic". From there I disabled the two firewall rules that allowed outgoing http and https traffic. As a result of this, machines on the green network are no longer able to access web pages and Protege will not be able to access many ontologies on the web including the proverbial pizza ontology. | ||
| + | * I went to the Proxy tab and enabled a non-transparent http proxy on port 8080. | ||
Revision as of 14:31, May 24, 2013
General Protege Developer Documentation
Contents
Using and Configuring Protege Ant Build Scripts
See Protege Ant Scripts.
Connect to the Protege Subversion repository from Eclipse
If you want to view and/or checkout Protege source code from the Eclipse IDE, the first step is to install the Subclipse plug-in. Subclipse provides support for Subversion from within Eclipse. Installation instructions are available on the Subclipse website.
Once you have successfully installed Subclipse, launch Eclipse and go to the SVN Repository Exploring perspective. Click the "Add SVN Repository" button to bring up the "Add SVN Repository" dialog. In the "Url" text box, type the following URL:
http://smi-protege.stanford.edu/repos/protege/
... and click Finish. Eclipse should look like the following screenshot:
Where is Java 6?
I am working on solving the problem of Apple's missing Java 6.
Testing firewalls and web proxies
Occasionally we get questions from people who are behind a firewall. In the past, we have had no way to simulate and test how Protege behaves in their environment and so our answers on the mailing list have been somewhat limited. But it turns out, as many IT types probably know well, that it is relatively easy to create a virtual network that lives behind an open source firewall, such as the endian firewall. There is an excellent and fun online course that describes how to setup such a network either using VirtualBox or VMware. If you create a virtual network in this way, the virtual firewall machine will have two virtual network interfaces, the external network interface (the red one) which points to the network of the host machine, and another network interface (the green one) which can be shared by other virtual machines. The endian firewall can be configured by accessing the web page https://192.168.0.15:10443 on the green network.
So when I got a question on the web about how to make Protege work with a web proxy, I set about configuring a virtual network protected by a firewall that I had put together using the directions above. I used a virtual machine on the green network to configure the firewall using the web interface that I accessed using the https://192.168.0.15:10443 web address. I made two changes to the firewall configuration:
- I went to the firewall tab and then clicked "Outgoing traffic". From there I disabled the two firewall rules that allowed outgoing http and https traffic. As a result of this, machines on the green network are no longer able to access web pages and Protege will not be able to access many ontologies on the web including the proverbial pizza ontology.
- I went to the Proxy tab and enabled a non-transparent http proxy on port 8080.
