Announcement

Collapse
No announcement yet.

rmi core api problem

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    rmi core api problem

    Hello!

    I use the rmi core api to sync between the mailserver and the ox-server.

    I used the command
    Code:
    UserModuleAccess access = new UserModuleAccess();  
access.enableAll();  // give access to all modules.
    to enable all user-modules. But unfortunately not all modules are enabled. By example the modules access-multiple-mail-accounts, access-collect-email-addresses, aso are not enabled.

    When I enable the modules in the command line, after every sync the modules are disabled. Is it possible to enable this modules through the rmi core api.

    best regards

    Christian
    Tags: None
  • #2
    When I enable the modules in the command line, after every sync the modules are disabled. Is it possible to enable this modules through the rmi core api.
    What do you mean with "sync"?
    How do you sync?

    Comment

    • #3
      Hello!

      I use the rmi core api to create or update the user. I sync between the mailserver with the ox-server (this are two different servers)

      I create or update the user from the mailserver to the ox-server. This program (java) runs with the crontab every hour.

      In the java program I use the code above to active all modules on the ox-server. But unfortunatly not all modules are enabled. I explained it in the post befor.

      mybe someone can help me, how to enable all modules.

      best regards

      Comment

      • #4
        And it does also not work on the commandline?
        Did you install the required packages? Please also give more information on what ox version you are using and post a list of all installed packages.

        In addition, please post the output of /opt/open-xchange/bin/listbundles

        Comment

        • #5
          Hello!

          In the command line it works to enable the modules. But every time i start syncing from the mailserver to the ox-server with the java rmi-api some modules are disabled. Then i have to enable them with the command line and than it works through the next synchronation.

          All i want is that the modules are enabled with the java rmi-api und not in the comamnd line.


          The output from the listbundles-command:
          Code:
          root@webmail:/opt/open-xchange/sbin# ./listbundles
bundlename: org.eclipse.osgi status: ACTIVE
bundlename: com.openexchange.authentication.imap status: ACTIVE
bundlename: com.openexchange.axis2 status: ACTIVE
bundlename: com.openexchange.caching status: ACTIVE
bundlename: com.openexchange.calendar status: ACTIVE
bundlename: com.openexchange.calendar.printing status: ACTIVE
bundlename: com.openexchange.charset status: ACTIVE
bundlename: com.openexchange.common status: ACTIVE
bundlename: com.openexchange.configjump.generic status: ACTIVE
bundlename: com.openexchange.configread status: ACTIVE
bundlename: com.openexchange.contactcollector status: ACTIVE
bundlename: com.openexchange.control status: ACTIVE
bundlename: com.openexchange.conversion.engine status: ACTIVE
bundlename: com.openexchange.conversion status: ACTIVE
bundlename: com.openexchange.conversion.servlet status: ACTIVE
bundlename: com.openexchange.crypto status: ACTIVE
bundlename: com.openexchange.data.conversion.ical.ical4j status: ACTIVE
bundlename: com.openexchange.dataretention.csv status: ACTIVE
bundlename: com.openexchange.dataretention status: ACTIVE
bundlename: com.openexchange.datatypes.genericonf status: ACTIVE
bundlename: com.openexchange.datatypes.genericonf.storage status: ACTIVE
bundlename: com.openexchange.easylogin status: ACTIVE
bundlename: com.openexchange.global status: ACTIVE
bundlename: com.openexchange.group.managerequest status: ACTIVE
bundlename: com.openexchange.groupware.settings.extensions status: ACTIVE
bundlename: com.openexchange.i18n status: ACTIVE
bundlename: com.openexchange.imap status: ACTIVE
bundlename: com.openexchange.mail.filter status: ACTIVE
bundlename: com.openexchange.management status: ACTIVE
bundlename: com.openexchange.monitoring status: ACTIVE
bundlename: com.openexchange.passwordchange.database status: ACTIVE
bundlename: com.openexchange.passwordchange.servlet status: ACTIVE
bundlename: com.openexchange.pop3 status: ACTIVE
bundlename: com.openexchange.publish.basic status: ACTIVE
bundlename: com.openexchange.publish status: ACTIVE
bundlename: com.openexchange.publish.json status: ACTIVE
bundlename: com.openexchange.publish.microformats status: ACTIVE
bundlename: com.openexchange.publish.online.infostore status: ACTIVE
bundlename: com.openexchange.push.udp status: ACTIVE
bundlename: com.openexchange.resource.managerequest status: ACTIVE
bundlename: com.openexchange.server status: ACTIVE
bundlename: com.openexchange.sessiond status: ACTIVE
bundlename: com.openexchange.smtp status: ACTIVE
bundlename: com.openexchange.spamhandler.default status: ACTIVE
bundlename: com.openexchange.sql status: ACTIVE
bundlename: com.openexchange.subscribe.crawler status: ACTIVE
bundlename: com.openexchange.subscribe status: ACTIVE
bundlename: com.openexchange.subscribe.json status: ACTIVE
bundlename: com.openexchange.subscribe.microformats status: ACTIVE
bundlename: com.openexchange.templating status: ACTIVE
bundlename: com.openexchange.threadpool status: ACTIVE
bundlename: com.openexchange.unifiedinbox status: ACTIVE
bundlename: com.openexchange.user.json status: ACTIVE
bundlename: com.openexchange.usm.api status: ACTIVE
bundlename: com.openexchange.usm.configuration.impl status: ACTIVE
bundlename: com.openexchange.usm.configuration.ox status: ACTIVE
bundlename: com.openexchange.usm.configuration status: ACTIVE
bundlename: com.openexchange.usm.contenttypes.calendar status: ACTIVE
bundlename: com.openexchange.usm.contenttypes.contacts status: ACTIVE
bundlename: com.openexchange.usm.contenttypes.folder status: ACTIVE
bundlename: com.openexchange.usm.contenttypes.mail status: ACTIVE
bundlename: com.openexchange.usm.contenttypes.manager status: ACTIVE
bundlename: com.openexchange.usm.contenttypes.tasks.calendar.commons status: ACTIVE
bundlename: com.openexchange.usm.contenttypes.tasks status: ACTIVE
bundlename: com.openexchange.usm.contenttypes.util status: ACTIVE
bundlename: com.openexchange.usm.database.ox status: ACTIVE
bundlename: com.openexchange.usm.eas status: ACTIVE
bundlename: com.openexchange.usm.journal.impl status: ACTIVE
bundlename: com.openexchange.usm.journal status: ACTIVE
bundlename: com.openexchange.usm.mapping status: ACTIVE
bundlename: com.openexchange.usm.ox_event.impl status: ACTIVE
bundlename: com.openexchange.usm.ox_event status: ACTIVE
bundlename: com.openexchange.usm.ox_json.impl status: ACTIVE
bundlename: com.openexchange.usm.ox_json status: ACTIVE
bundlename: com.openexchange.usm.session.dataobject status: ACTIVE
bundlename: com.openexchange.usm.session.impl status: ACTIVE
bundlename: com.openexchange.usm.util status: ACTIVE
bundlename: com.openexchange.usm status: ACTIVE
bundlename: com.openexchange.xerces.sun status: ACTIVE
bundlename: com.openexchange.xml status: ACTIVE
bundlename: javax.activation status: ACTIVE
bundlename: javax.servlet status: ACTIVE
bundlename: net.freeutils.jcharset status: ACTIVE
bundlename: org.apache.commons.cli status: ACTIVE
bundlename: org.apache.commons.lang status: ACTIVE
bundlename: org.apache.commons.logging status: ACTIVE
bundlename: org.eclipse.equinox.ds status: ACTIVE
bundlename: org.eclipse.equinox.event status: ACTIVE
bundlename: org.eclipse.equinox.util status: ACTIVE
bundlename: org.eclipse.osgi.services status: ACTIVE
root@webmail:/opt/open-xchange/sbin#
          Best regards

          Christian

          Comment

          Previous template Next
          Working...
          X