[Eagle-i-admins] Auto-complete in SWEET not working and Ontology Browser down
Faith Coldren
fcoldren at mail.med.upenn.edu
Wed Feb 26 14:27:15 EST 2014
Hi Sophia,
We restarted tomcat, and now the ontology browser link is functional.
However, we don't see a directory called "work" under ~tomcat. There is a
"work" directory under /opt/tomcat/ and inside this directory is another
directory called "Catalina".
Directory structure of ~tomcat:
/usr/share/tomcat6/
├── bin
└── eaglei
└── sparqler
├── logs
└── sesame
Directory structure of /opt/tomcat/work:
/opt/tomcat/work/
└── Catalina
└── localhost
├── _
│ └── org
│ └── apache
│ └── jsp
│ └── repository
│ ├── admin
│ ├── logout
│ └── query
├── ${catalina.base}
├── docs
├── examples
├── help
├── host-manager
├── institution
├── manager
│ └── org
│ └── apache
│ └── jsp
│ └── WEB_002dINF
│ └── jsp
├── ROOT.orig
├── sparqler
│ └── org
│ └── apache
│ └── jsp
│ ├── query
│ └── repository
│ └── admin
└── sweet
└── org
└── apache
└── jsp
├── cores
├── feedback
└── labs
Should we delete /opt/tomcat/work?
Thanks,
Faith
Faith Coldren, PhD
Biomedical Data Curator
ITMAT
University of Pennsylvania
215-573-9462
************************************
Discover.Accelerate.Promote
https://eagle-i.itmat.upenn.edu
On Wed, Feb 26, 2014 at 10:54 AM, Cheng, Sophia <
Sophia_Cheng at hms.harvard.edu> wrote:
> Hi Faith,
>
> The issue you were seeing with the ontology browser was due to a
> misconfiguration on our part (the navigation is pulling in the navigation
> from our server). We have fixed this and pushed the fix to the production
> tier.
>
> You will need to restart to pick up this change. When you restart, be
> sure to delete this folder ~tomcat/work. This is tomcat's working folder
> and we noticed that it was caching the link for the navigation.
>
> Thanks for your patience. Please let us know if you continue to have
> trouble with the ontology browser link in the top navigation.
>
> Sincerely,
> Sophia
>
> On Jan 31, 2014, at 5:10 PM, "Cherry, Michael" <
> Michael_Cherry at hms.harvard.edu> wrote:
>
> >> I updated property value for eagle.model.url.
> >> This fixed the problem.
> >
> >> Could you suggest where I should change the Ontology
> >> Browser link for the header in SWEET so that users
> >> have a functioning link?
> >
> > Hi Faith,
> >
> > I'm not sure but I don't know if the links in the application headers
> are locally configurable.
> >
> > We'll get an answer to you within the next few days.
> >
> > - Mike C
> >
> >
> > _______________________________________________
> > Eagle-i-admins mailing list
> > Eagle-i-admins at open.med.harvard.edu
> > https://open.med.harvard.edu/mailman/listinfo/eagle-i-admins
>
> _______________________________________________
> Eagle-i-admins mailing list
> Eagle-i-admins at open.med.harvard.edu
> https://open.med.harvard.edu/mailman/listinfo/eagle-i-admins
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://open.med.harvard.edu/pipermail/eagle-i-admins/attachments/20140226/dbd8afe8/attachment.html
More information about the Eagle-i-admins
mailing list