cancel
Showing results for 
Search instead for 
Did you mean: 

Changing OpenOffice Listening port

dewes
Champ in-the-making
Champ in-the-making
Where, on Alfresco 3.2 Community, I can change the port that soffice.bin listens?
2 REPLIES 2

dewes
Champ in-the-making
Champ in-the-making
better,

Where on alfresco, I change the port that alfresco conects on soffice bin, because the default is already on use I can't change the program that is already on that one. So I need to start soffice on a different port.

dward
Champ on-the-rise
Champ on-the-rise
You need to override this bean:


   <bean id="openOfficeStartupCommand" class="org.alfresco.util.exec.RuntimeExec">
      <property name="commandsAndArguments">
         <map>
            <entry key=".*">
               <list>
                  <value>${ooo.exe}</value>
                  <value>-accept=socket,host=localhost,port=8100;urp;StarOffice.ServiceManager</value>
                  <bean class="org.alfresco.util.StringAppendingFactoryBean">
                     <property name="items">
                        <list>
                           <value>-env:UserInstallation=</value>
                           <ref bean="userInstallationURI" />
                        </list>
                     </property>
                  </bean>
                  <value>-nologo</value>
                  <value>-headless</value>
                  <value>-nofirststartwizard</value>
                  <value>-nocrashrep</value>
                  <value>-norestore</value>
               </list>
            </entry>
         </map>
      </property>
      <property name="waitForCompletion">
         <value>false</value>
      </property>
      <property name="errorCodes">
         <value>2</value>
      </property>
   </bean>

In Alfresco v3.0, just put the edited bean in your custom-repository-context.xml. In v3.2, the bean lives in the thirdparty subsystem and would have to be overriden using the mechanism described here

http://wiki.alfresco.com/wiki/Alfresco_Subsystems#Spring_Beans

The mechanism was broken in the v3.2 community release, so you would need a v3.3. nightly build. But if you're on 3.0 you don't need to worry.