MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "SMS_Twilio",
        "continue": "gapcontinue||"
    },
    "query": {
        "pages": {
            "800": {
                "pageid": 800,
                "ns": 0,
                "title": "Reseller Bundle",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "= Open-Xchange Reseller package =\n\nThe reseller package introduces an additional layer of permissions, so called subadmins.\n\n* subadmins can be managed by the oxadminmaster account\n* subadmins are oxadminmaster accounts with restricted rights:\n** they can only manage contexts (no database, filestore, etc)\n** they can only manage their own contexts (list/change/delete) \n** they might be able to create further subadmins (see below)\n\nThe corresponding documentation of restrictions available and what they do can\nbe found in the javadoc api documentation found in\n/usr/share/doc/open-xchange-admin-reseller/javadoc/doc on Debian.\n\n== Restrictions ==\n\nThese are basically the restrictions available:\n\n Subadmin.MaxOverallUser\n   - the maximum number of users a subadmin can create distributed over all it's\n     contexts\n\n Subadmin.MaxContext\n   - the maximum number of contexts a subadmin can create\n\n Context.MaxUser\n   - the maximum number of users in a single context a contextadmin can create\n     Note: this is a restriction, a subadmin can apply to each context\n\n Subadmin.MaxOverallContextQuota\n   - the maximum number of quota distributed over all contexts a subadmin\n     can use\n\n Subadmin.CanCreateSubadmin\n   - Should this subadmin be able to create subsubadmins? This is NOT allowed by default.\n     There's also only one additional level. '''Note:''' A subsubadmin cannot create any further\n     subadmins.\n\n Subadmin.MaxSubadmin\n   - If a subadmin is allowed to create subsubadmins, should there be a maximum?\n \nplus all the restrictions based on module access combinations as found in \n/opt/open-xchange/etc/ModuleAccessDefinitions.properties\n\n{{InstallPlugin|version=6.22 or later|pluginname=open-xchange-admin-reseller|toplevel=products|sopath=appsuite/stable/backend}}\n\n== Setup and Configuration ==\n\n\nThe reseller package requires additional tables in the configdb database\nas well as the package open-xchange-admin-autocontextid to be installed.\n\nopen-xchange-admin-autocontextid introduces the feature, that context ids\ncan no longer be specified and maintained by the system administrator, but are\nnow generated by open-xchange itself. This is a requirement since reseller\nadmins do not know, which context ids are already used.\n\nIn OX App Suite version 7.10.1 and before you need to add those tables manually. In newer versions the tables are added automatically.\nTo add the new tables to the configdb, either run\n\n $ mysql -u openexchange -p<YOURPW> configdb \\\n    < /opt/open-xchange/etc/mysql/reseller.sql\n $ mysql -u openexchange -p<YOURPW> configdb \\\n    < /opt/open-xchange/etc/mysql/autocid.sql\n\nor on a fresh setup, when running initconfigdb, add the following arguments:\n\n $ /opt/open-xchange/sbin/initconfigdb --configdb-pass secret -a \\\n    --addon-sql \"reseller.sql autocid.sql\"\n\n'''Important: It is required to NOT set MASTER_AUTHENTICATION_DISABLED=true or CONTEXT_AUTHENTICATION_DISABLED=true in <tt>/opt/open-xchange/etc/AdminDaemon.properties</tt>'''\n\n== Initializing the restrictions ==\n\nAfter the additional tables in the configdb have been created (may require restart), the restrictions\nmust be initialized. This can be done via RMI, SOAP or on commandline using\n\n $ initrestrictions -A oxadminmaster -P secret\n\n== Manage subadmins ==\n\nSubadmin accounts can be managed via the create/change/deleteadmin commands\ninstalled to /opt/open-xchange/sbin\n\nExample:\n\n $ /opt/open-xchange/sbin/createadmin -A oxadminmaster -P secret -u testadmin \\\n    -d \"Test Subadmin\" -p secret -a Subadmin.MaxContext=2000 \\\n    -a Subadmin.MaxOverallUser=2100 \\\n    -a Subadmin.MaxOverallUserByModuleaccess_webmail_plus=2010\n\nWould create a subadmin which is able to create max. 2000 contexts containing\nmax. 2100 users and of these users, max. 2010 can have the module access\ncombination webmail_plus.\n\nlist it with\n\n $ /opt/open-xchange/sbin/listadmin -A oxadminmaster -P secret\n Id Name      Displayname   Restrictions\n 36 testadmin Test Subadmin Subadmin.MaxOverallUser=2100,Subadmin.MaxOverallUserByModuleaccess_webmail_plus=2010,Subadmin.MaxContext=2000\n\n\n== Manage contexts ==\n\nWhen the reseller package has been installed, context listings contain\nadditional information such as the owner of the single contexts.\n\n $ /opt/open-xchange/sbin/listcontext -A oxadminmaster -P secret\n cid fid fname       enabled qmax qused name        lmappings   CustomID         Owner\n   1   3 1_ctx_store true     500     0 1                                        oxadminmaster\n   2   3 2_ctx_store true     500     0 example.com example.com                  oxadminmaster\n   3   3 3_ctx_store true     500     0 3                                        oxadminmaster\n   4   3 4_ctx_store true     500     0 4                       a custom id 1234 testadmin    \n\nThe subadmin called testadmin can only list it's own context(s):\n\n $ /opt/open-xchange/sbin/listcontext -A testadmin -P secret\n cid fid fname       enabled qmax qused name lmappings CustomID         Owner    \n   4   3 4_ctx_store true     500     0 4              a custom id 1234 testadmin\n\n== Using the SOAP Interface ==\n\nTo use the soap interface, you need to install <tt>open-xchange-admin-soap-reseller</tt> in addition.\n\nDue to the fact, that we cannot use the plugin mechanism we're using in Java to\nextend the existing objects, the APIs and objects\n\n* OXContext\n* OXGroup\n* OXResource\n* OXUser\n* Context\n\nhad to be wrapped into new APIs\n\n* OXResellerContext\n* OXResellerGroup\n* OXResellerResource\n* OXResellerUser\n* ResellerContext\n\nand the corresponding SOAP URLs\n\n* http://localhost/webservices/OXResellerContextService?wsdl\n* http://localhost/webservices/OXResellerUserService?wsdl\n* http://localhost/webservices/OXResellerGroupService?wsdl\n* http://localhost/webservices/OXResellerResourceService?wsdl\n\nand of course the additional API to manage the subadmin accounts: \n\n* http://localhost/webservices/OXResellerService?wsdl\n\nThat also means that the existing SOAP interfaces for the mentioned classes\nabove cannot be used anymore when installing the reseller package.\n\nResellerContext just adds some additional members to the existing Context\nobject and the corresponding APIs just oberate on and return this wrapped\nclass."
                    }
                ]
            },
            "1899": {
                "pageid": 1899,
                "ns": 0,
                "title": "Restrictions on importing data",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "There are [[:Category:Import|several ways to import data into Open-Xchange]], but all are restricted by the fact that OX uses a SQL database to store data about its core elements (contacts, appointments and tasks). That means that the field size is limited.\n\nIf there is such a problem, the data will be shortened/truncated to field the field. The technical details vary a little:\n* If your database is set to automatically truncate data, the content will be cut off at that part.\n* If your database is not to for automatic truncation, the server will try to do this. But the database only reports one oversized field at a time, so the server might need several attempts to trim the whole record in case more than one field is too big. This is slower.\n\nThe fields have been sized generously while still having efficient row sizes for fast SQL queries. If you encounter a problem, it usually lies with generic fields like \"description\" or \"comment\", which some other programs use to store vast amounts of data (for example a VCard representation of the same contact you just imported).\n\nTo determine whether data fits the database, the size of the database fields can be used. But two things should be kept in mind: Depending on the character set used, a character can take up more than one byte. The default character set used it a 3-byte UTF8 set. Chinese installations, for example, might use a set that takes up more bytes per character or not even UTF8 at all. Also, some installations have used different field sizes for reasons ranging from performance to missing updates (though updates to database tables are really rare).\n\nNow you have been sufficiently warned: What follows is the data of a typical default installation. Yours might vary.\n\n{{UnderConstruction|Currently collecting data from fresh installation}}\n\n[[Category: OX6]]\n[[Category: Import]]\n[[Category: Overview]]"
                    }
                ]
            }
        }
    }
}