MultiUser Install issue

[JeffDG]

I’ve been walking through the Multi-User Installation directions (https://www.enterprise-architecture.org ... multi-user) and I’ve hit a bit of a snag.

My server is Windows Server 2016 Standard with 12GB of RAM. It’s a VM.

JVM is set up:
C:\WINDOWS\system32>java -version
java version "1.8.0_181"
Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)

Protégé is installed, and I’ve done the “Sort class tree” item:

I’ve installed the MS SQL JDBC drivers

Tomcat is installed. Version is 9.0.10 Server.

Graphviz is installed as specified:


The Essential Installer is where the directions diverge from what I’m seeing.

I run the java -jar essentialinstall62.jar and accept the license agreement.

The package list is much different (I selected all):

I installed Server components directly into the Protégé\examples\server directory

Where I’ve hit a roadblock is in 13.2

When I open Protégé and open the metaproject.pprj and go to the PolicyControlledObject class, the Essential AM Repository is not listed here to select.



Anyone know what I'm missing?

[jonathan.carter]

Hi,

Yes, there are a few more components in the installer now!

It looks like what's happened is that the Server Components have not been deployed to the expected location. What you're seeing is the out-of-the-box Meta Project as supplied with the base Protege platform.

You can re-run the installer, selecting ONLY the 'Server Components' and install them into the <PROTEGE>/examples/server folder. Make sure to 'Browse' to this folder and select it as you will see a path that reads {PROTEGE_HOME}/examples/server until you do.

Once you've re-run the installer, you should now see the 2 Projects when you open your metaproject, as described in the installation instructions.

Jonathan

[rudolf]

Hi Jonathan,

I'm having the same issue, even after reinstalling the Server components as you describe.

What could be going wrong?

This is on CentOS 7,

Thanks!

--rudolf

[rudolf]

It was an obvious problem in my case - I had run the Protege install as root, and therefore the Essential install couldn't write into it. Changed ownership of the Protege directory tree, and all is well again.

[jonathan.carter]

That's great to hear.

Thanks for posting back with the solution!

Jonathan