- Deploying 1.4/2.0/2.1 WAR to JBoss AS 4.0.5/4.2.X
- Additional instructions for installing on JBoss 4.2.X GA
Tip: By default jboss server is only bound to localhost or 127.0.0.1. This means that if you want to allow LAN/Internet access to alfresco you should bind network interfaces you want to provide access. To bind all interfaces, simple run jboss (JBOSS_HOME/bin/run.bat) with the "-b 0.0.0.0" option. Remember you have to secure your jboss server first (JMX Console, Web Console, etc). Refer to this link for more information.
The next step was installing the Web Content Management (WCM) extension. No problem there. Just had a minor change since I'm using virtualization to preview sandboxes. I had to tweak the configuration to allow LAN users to access the WCM preview website feature. Alfresco's virtual hyperlink format is like follows:
http://virtual-hostname.www--sandbox.127-0-0-1:8180/request-path
This link obviously only works accessing it from the Alfresco Server. Change:
$VIRTUAL_TOMCAT_HOME/conf/alfresco-virtserver.properties
file. Look for the following line:
http://virtual-hostname.www--sandbox.127-0-0-1:8180/request-path
and change it to:
alfresco.virtserver.domain=192-168-0-12.ip.alfrescodemo.net
* 192.168.0.12 is my LAN address, change accordingly.
That takes care of the Alfresco installation. One additional thing I must do since I'm installing on a windows environment :( I must run Jboss and the virtualization server as a windows service.
More on that.... on the next post!
No comments:
Post a Comment