Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
OLAT CI-CD Testing Project
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Requirements
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Deploy
Package Registry
Container Registry
Model registry
Operate
Terraform modules
Monitor
Service Desk
Analyze
Contributor analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Lars Oliver Dam
OLAT CI-CD Testing Project
Commits
5285fbf4
Commit
5285fbf4
authored
12 years ago
by
srosse
Browse files
Options
Downloads
Patches
Plain Diff
OO-423: remove a hard coded setting for testing, a first draft
parent
321f33e3
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
INSTALL.APPSERVER.README
+37
-0
37 additions, 0 deletions
INSTALL.APPSERVER.README
src/main/java/org/olat/search/_spring/searchContext.xml
+1
-17
1 addition, 17 deletions
src/main/java/org/olat/search/_spring/searchContext.xml
with
38 additions
and
17 deletions
INSTALL.APPSERVER.README
0 → 100644
+
37
−
0
View file @
5285fbf4
EXPERIMENTAL: Setting up latest OpenOLAT version on Eclipse With an Application Server
--------------------------------------------------------------------------------------
OpenOLAT supports only Tomcat officially, but it can also run on other application
servers like JBoss AS or Glassfish.
The beginning of the installation is the same as Tomcat, it's described in INSTALL.README.
To create your eclipse project, use these commands instead of the default one:
for JBoss AS:
mvn eclipse:clean eclipse:eclipse -P-tomcat,jbossas
and for Glassfish
mvn eclipse:clean eclipse:eclipse -P-tomcat,gae
I use a JBoss AS 7.1 with Hibernate upgraded to the latest version and Glassfish 3.1.2.2
community version. I created in them a JDBC connection Pool, a JMS connection factory
(which already exists in JBoss) and a topic for the sysbus and a queue for the search.
With this setup, OpenOLAT use the JDBC connection pool of your application server, the JMS
server and its JAX-RS implementation. JBoss delivers Hibernate too.
Features located on the application server:
OK JDBC Connections
OK JMS
OK JAX-RS (restapi)
x JAX-WS (onyx, vitero)
x Mail
x LDAP Connection
-- Hibernate/JPA (only JBoss because we depend on Hibernate)
x Infinispan for caching
This diff is collapsed.
Click to expand it.
src/main/java/org/olat/search/_spring/searchContext.xml
+
1
−
17
View file @
5285fbf4
...
@@ -258,7 +258,7 @@
...
@@ -258,7 +258,7 @@
<!-- SEARCH PROXY SIDE CONFIGURATION -->
<!-- SEARCH PROXY SIDE CONFIGURATION -->
<!-- =============================== -->
<!-- =============================== -->
<!-- OO-109: bypass the JMS server in no-cluster environment ==> use searchClientLocal if singleVM -->
<!-- OO-109: bypass the JMS server in no-cluster environment ==> use searchClientLocal if singleVM -->
<alias
alias=
"searchClient"
name=
"searchClient
C
luster"
/>
<alias
alias=
"searchClient"
name=
"searchClient
${c
luster
.mode}
"
/>
<bean
id=
"searchClientSingleVM"
class=
"org.olat.search.service.searcher.SearchClientLocal"
/>
<bean
id=
"searchClientSingleVM"
class=
"org.olat.search.service.searcher.SearchClientLocal"
/>
...
@@ -274,20 +274,4 @@
...
@@ -274,20 +274,4 @@
<import
resource=
"classpath:org/olat/search/_spring/searchJms_${jms.provider}.xml"
/>
<import
resource=
"classpath:org/olat/search/_spring/searchJms_${jms.provider}.xml"
/>
<!-- JMS Stuff -->
<alias
alias=
"searchConnectionFactory"
name=
"searchConnectionFactory.${jms.provider}"
/>
<!-- <bean id="searchConnectionFactory.activemq" class="org.apache.activemq.spring.ActiveMQConnectionFactory" lazy-init="true">
<property name="brokerURL" value="${search.broker.url}" />
</bean> -->
<bean
name=
"searchConnectionFactory.jndi"
class=
"org.springframework.jndi.JndiObjectFactoryBean"
lazy-init=
"true"
>
<property
name=
"jndiName"
><value>
java:/ConnectionFactory
</value></property>
</bean>
<alias
alias=
"searchQueue"
name=
"searchQueue.${jms.provider}"
/>
<!-- <bean id="searchQueue.activemq" class="org.apache.activemq.command.ActiveMQQueue" lazy-init="true">
<constructor-arg value="olat/searchQueue" />
</bean> -->
<bean
id=
"searchQueue.jndi"
class=
"org.springframework.jndi.JndiObjectFactoryBean"
lazy-init=
"true"
>
<property
name=
"jndiName"
><value>
java:jboss/exported/jms/queue/searchQueue
</value></property>
</bean>
</beans>
</beans>
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment