The GNU Affero General Public License is a free, copyleft license\nfor software and other kinds of works, specifically designed to ensure\ncooperation with the community in the case of network server software.
\n\n
The licenses for most software and other practical works are\ndesigned to take away your freedom to share and change the works. By\ncontrast, our General Public Licenses are intended to guarantee your\nfreedom to share and change all versions of a program--to make sure it\nremains free software for all its users.
\n\n
When we speak of free software, we are referring to freedom, not\nprice. Our General Public Licenses are designed to make sure that you\nhave the freedom to distribute copies of free software (and charge for\nthem if you wish), that you receive source code or can get it if you\nwant it, that you can change the software or use pieces of it in new\nfree programs, and that you know you can do these things.
\n\n
Developers that use our General Public Licenses protect your rights\nwith two steps: (1) assert copyright on the software, and (2) offer\nyou this License which gives you legal permission to copy, distribute\nand/or modify the software.
\n\n
A secondary benefit of defending all users' freedom is that\nimprovements made in alternate versions of the program, if they\nreceive widespread use, become available for other developers to\nincorporate. Many developers of free software are heartened and\nencouraged by the resulting cooperation. However, in the case of\nsoftware used on network servers, this result may fail to come about.\nThe GNU General Public License permits making a modified version and\nletting the public access it on a server without ever releasing its\nsource code to the public.
\n\n
The GNU Affero General Public License is designed specifically to\nensure that, in such cases, the modified source code becomes available\nto the community. It requires the operator of a network server to\nprovide the source code of the modified version running there to the\nusers of that server. Therefore, public use of a modified version, on\na publicly accessible server, gives the public access to the source\ncode of the modified version.
\n\n
An older license, called the Affero General Public License and\npublished by Affero, was designed to accomplish similar goals. This is\na different license, not a version of the Affero GPL, but Affero has\nreleased a new version of the Affero GPL which permits relicensing under\nthis license.
\n\n
The precise terms and conditions for copying, distribution and\nmodification follow.
\n\n
TERMS AND CONDITIONS
\n\n
0. Definitions.
\n\n
"This License" refers to version 3 of the GNU Affero General Public\nLicense.
\n\n
"Copyright" also means copyright-like laws that apply to other kinds\nof works, such as semiconductor masks.
\n\n
"The Program" refers to any copyrightable work licensed under this\nLicense. Each licensee is addressed as "you". "Licensees" and\n"recipients" may be individuals or organizations.
\n\n
To "modify" a work means to copy from or adapt all or part of the work\nin a fashion requiring copyright permission, other than the making of an\nexact copy. The resulting work is called a "modified version" of the\nearlier work or a work "based on" the earlier work.
\n\n
A "covered work" means either the unmodified Program or a work based\non the Program.
\n\n
To "propagate" a work means to do anything with it that, without\npermission, would make you directly or secondarily liable for\ninfringement under applicable copyright law, except executing it on a\ncomputer or modifying a private copy. Propagation includes copying,\ndistribution (with or without modification), making available to the\npublic, and in some countries other activities as well.
\n\n
To "convey" a work means any kind of propagation that enables other\nparties to make or receive copies. Mere interaction with a user through\na computer network, with no transfer of a copy, is not conveying.
\n\n
An interactive user interface displays "Appropriate Legal Notices"\nto the extent that it includes a convenient and prominently visible\nfeature that (1) displays an appropriate copyright notice, and (2)\ntells the user that there is no warranty for the work (except to the\nextent that warranties are provided), that licensees may convey the\nwork under this License, and how to view a copy of this License. If\nthe interface presents a list of user commands or options, such as a\nmenu, a prominent item in the list meets this criterion.
\n\n
1. Source Code.
\n\n
The "source code" for a work means the preferred form of the work\nfor making modifications to it. "Object code" means any non-source\nform of a work.
\n\n
A "Standard Interface" means an interface that either is an official\nstandard defined by a recognized standards body, or, in the case of\ninterfaces specified for a particular programming language, one that\nis widely used among developers working in that language.
\n\n
The "System Libraries" of an executable work include anything, other\nthan the work as a whole, that (a) is included in the normal form of\npackaging a Major Component, but which is not part of that Major\nComponent, and (b) serves only to enable use of the work with that\nMajor Component, or to implement a Standard Interface for which an\nimplementation is available to the public in source code form. A\n"Major Component", in this context, means a major essential component\n(kernel, window system, and so on) of the specific operating system\n(if any) on which the executable work runs, or a compiler used to\nproduce the work, or an object code interpreter used to run it.
\n\n
The "Corresponding Source" for a work in object code form means all\nthe source code needed to generate, install, and (for an executable\nwork) run the object code and to modify the work, including scripts to\ncontrol those activities. However, it does not include the work's\nSystem Libraries, or general-purpose tools or generally available free\nprograms which are used unmodified in performing those activities but\nwhich are not part of the work. For example, Corresponding Source\nincludes interface definition files associated with source files for\nthe work, and the source code for shared libraries and dynamically\nlinked subprograms that the work is specifically designed to require,\nsuch as by intimate data communication or control flow between those\nsubprograms and other parts of the work.
\n\n
The Corresponding Source need not include anything that users\ncan regenerate automatically from other parts of the Corresponding\nSource.
\n\n
The Corresponding Source for a work in source code form is that\nsame work.
\n\n
2. Basic Permissions.
\n\n
All rights granted under this License are granted for the term of\ncopyright on the Program, and are irrevocable provided the stated\nconditions are met. This License explicitly affirms your unlimited\npermission to run the unmodified Program. The output from running a\ncovered work is covered by this License only if the output, given its\ncontent, constitutes a covered work. This License acknowledges your\nrights of fair use or other equivalent, as provided by copyright law.
\n\n
You may make, run and propagate covered works that you do not\nconvey, without conditions so long as your license otherwise remains\nin force. You may convey covered works to others for the sole purpose\nof having them make modifications exclusively for you, or provide you\nwith facilities for running those works, provided that you comply with\nthe terms of this License in conveying all material for which you do\nnot control copyright. Those thus making or running the covered works\nfor you must do so exclusively on your behalf, under your direction\nand control, on terms that prohibit them from making any copies of\nyour copyrighted material outside their relationship with you.
\n\n
Conveying under any other circumstances is permitted solely under\nthe conditions stated below. Sublicensing is not allowed; section 10\nmakes it unnecessary.
\n\n
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
\n\n
No covered work shall be deemed part of an effective technological\nmeasure under any applicable law fulfilling obligations under article\n11 of the WIPO copyright treaty adopted on 20 December 1996, or\nsimilar laws prohibiting or restricting circumvention of such\nmeasures.
\n\n
When you convey a covered work, you waive any legal power to forbid\ncircumvention of technological measures to the extent such circumvention\nis effected by exercising rights under this License with respect to\nthe covered work, and you disclaim any intention to limit operation or\nmodification of the work as a means of enforcing, against the work's\nusers, your or third parties' legal rights to forbid circumvention of\ntechnological measures.
\n\n
4. Conveying Verbatim Copies.
\n\n
You may convey verbatim copies of the Program's source code as you\nreceive it, in any medium, provided that you conspicuously and\nappropriately publish on each copy an appropriate copyright notice;\nkeep intact all notices stating that this License and any\nnon-permissive terms added in accord with section 7 apply to the code;\nkeep intact all notices of the absence of any warranty; and give all\nrecipients a copy of this License along with the Program.
\n\n
You may charge any price or no price for each copy that you convey,\nand you may offer support or warranty protection for a fee.
\n\n
5. Conveying Modified Source Versions.
\n\n
You may convey a work based on the Program, or the modifications to\nproduce it from the Program, in the form of source code under the\nterms of section 4, provided that you also meet all of these conditions:
\n\n
\n\n
a) The work must carry prominent notices stating that you modified\n it, and giving a relevant date.
\n\n
b) The work must carry prominent notices stating that it is\n released under this License and any conditions added under section\n 7. This requirement modifies the requirement in section 4 to\n "keep intact all notices".
\n\n
c) You must license the entire work, as a whole, under this\n License to anyone who comes into possession of a copy. This\n License will therefore apply, along with any applicable section 7\n additional terms, to the whole of the work, and all its parts,\n regardless of how they are packaged. This License gives no\n permission to license the work in any other way, but it does not\n invalidate such permission if you have separately received it.
\n\n
d) If the work has interactive user interfaces, each must display\n Appropriate Legal Notices; however, if the Program has interactive\n interfaces that do not display Appropriate Legal Notices, your\n work need not make them do so.
\n\n
\n\n
A compilation of a covered work with other separate and independent\nworks, which are not by their nature extensions of the covered work,\nand which are not combined with it such as to form a larger program,\nin or on a volume of a storage or distribution medium, is called an\n"aggregate" if the compilation and its resulting copyright are not\nused to limit the access or legal rights of the compilation's users\nbeyond what the individual works permit. Inclusion of a covered work\nin an aggregate does not cause this License to apply to the other\nparts of the aggregate.
\n\n
6. Conveying Non-Source Forms.
\n\n
You may convey a covered work in object code form under the terms\nof sections 4 and 5, provided that you also convey the\nmachine-readable Corresponding Source under the terms of this License,\nin one of these ways:
\n\n
\n\n
a) Convey the object code in, or embodied in, a physical product\n (including a physical distribution medium), accompanied by the\n Corresponding Source fixed on a durable physical medium\n customarily used for software interchange.
\n\n
b) Convey the object code in, or embodied in, a physical product\n (including a physical distribution medium), accompanied by a\n written offer, valid for at least three years and valid for as\n long as you offer spare parts or customer support for that product\n model, to give anyone who possesses the object code either (1) a\n copy of the Corresponding Source for all the software in the\n product that is covered by this License, on a durable physical\n medium customarily used for software interchange, for a price no\n more than your reasonable cost of physically performing this\n conveying of source, or (2) access to copy the\n Corresponding Source from a network server at no charge.
\n\n
c) Convey individual copies of the object code with a copy of the\n written offer to provide the Corresponding Source. This\n alternative is allowed only occasionally and noncommercially, and\n only if you received the object code with such an offer, in accord\n with subsection 6b.
\n\n
d) Convey the object code by offering access from a designated\n place (gratis or for a charge), and offer equivalent access to the\n Corresponding Source in the same way through the same place at no\n further charge. You need not require recipients to copy the\n Corresponding Source along with the object code. If the place to\n copy the object code is a network server, the Corresponding Source\n may be on a different server (operated by you or a third party)\n that supports equivalent copying facilities, provided you maintain\n clear directions next to the object code saying where to find the\n Corresponding Source. Regardless of what server hosts the\n Corresponding Source, you remain obligated to ensure that it is\n available for as long as needed to satisfy these requirements.
\n\n
e) Convey the object code using peer-to-peer transmission, provided\n you inform other peers where the object code and Corresponding\n Source of the work are being offered to the general public at no\n charge under subsection 6d.
\n\n
\n\n
A separable portion of the object code, whose source code is excluded\nfrom the Corresponding Source as a System Library, need not be\nincluded in conveying the object code work.
\n\n
A "User Product" is either (1) a "consumer product", which means any\ntangible personal property which is normally used for personal, family,\nor household purposes, or (2) anything designed or sold for incorporation\ninto a dwelling. In determining whether a product is a consumer product,\ndoubtful cases shall be resolved in favor of coverage. For a particular\nproduct received by a particular user, "normally used" refers to a\ntypical or common use of that class of product, regardless of the status\nof the particular user or of the way in which the particular user\nactually uses, or expects or is expected to use, the product. A product\nis a consumer product regardless of whether the product has substantial\ncommercial, industrial or non-consumer uses, unless such uses represent\nthe only significant mode of use of the product.
\n\n
"Installation Information" for a User Product means any methods,\nprocedures, authorization keys, or other information required to install\nand execute modified versions of a covered work in that User Product from\na modified version of its Corresponding Source. The information must\nsuffice to ensure that the continued functioning of the modified object\ncode is in no case prevented or interfered with solely because\nmodification has been made.
\n\n
If you convey an object code work under this section in, or with, or\nspecifically for use in, a User Product, and the conveying occurs as\npart of a transaction in which the right of possession and use of the\nUser Product is transferred to the recipient in perpetuity or for a\nfixed term (regardless of how the transaction is characterized), the\nCorresponding Source conveyed under this section must be accompanied\nby the Installation Information. But this requirement does not apply\nif neither you nor any third party retains the ability to install\nmodified object code on the User Product (for example, the work has\nbeen installed in ROM).
\n\n
The requirement to provide Installation Information does not include a\nrequirement to continue to provide support service, warranty, or updates\nfor a work that has been modified or installed by the recipient, or for\nthe User Product in which it has been modified or installed. Access to a\nnetwork may be denied when the modification itself materially and\nadversely affects the operation of the network or violates the rules and\nprotocols for communication across the network.
\n\n
Corresponding Source conveyed, and Installation Information provided,\nin accord with this section must be in a format that is publicly\ndocumented (and with an implementation available to the public in\nsource code form), and must require no special password or key for\nunpacking, reading or copying.
\n\n
7. Additional Terms.
\n\n
"Additional permissions" are terms that supplement the terms of this\nLicense by making exceptions from one or more of its conditions.\nAdditional permissions that are applicable to the entire Program shall\nbe treated as though they were included in this License, to the extent\nthat they are valid under applicable law. If additional permissions\napply only to part of the Program, that part may be used separately\nunder those permissions, but the entire Program remains governed by\nthis License without regard to the additional permissions.
\n\n
When you convey a copy of a covered work, you may at your option\nremove any additional permissions from that copy, or from any part of\nit. (Additional permissions may be written to require their own\nremoval in certain cases when you modify the work.) You may place\nadditional permissions on material, added by you to a covered work,\nfor which you have or can give appropriate copyright permission.
\n\n
Notwithstanding any other provision of this License, for material you\nadd to a covered work, you may (if authorized by the copyright holders of\nthat material) supplement the terms of this License with terms:
\n\n
\n\n
a) Disclaiming warranty or limiting liability differently from the\n terms of sections 15 and 16 of this License; or
\n\n
b) Requiring preservation of specified reasonable legal notices or\n author attributions in that material or in the Appropriate Legal\n Notices displayed by works containing it; or
\n\n
c) Prohibiting misrepresentation of the origin of that material, or\n requiring that modified versions of such material be marked in\n reasonable ways as different from the original version; or
\n\n
d) Limiting the use for publicity purposes of names of licensors or\n authors of the material; or
\n\n
e) Declining to grant rights under trademark law for use of some\n trade names, trademarks, or service marks; or
\n\n
f) Requiring indemnification of licensors and authors of that\n material by anyone who conveys the material (or modified versions of\n it) with contractual assumptions of liability to the recipient, for\n any liability that these contractual assumptions directly impose on\n those licensors and authors.
\n\n
\n\n
All other non-permissive additional terms are considered "further\nrestrictions" within the meaning of section 10. If the Program as you\nreceived it, or any part of it, contains a notice stating that it is\ngoverned by this License along with a term that is a further restriction,\nyou may remove that term. If a license document contains a further\nrestriction but permits relicensing or conveying under this License, you\nmay add to a covered work material governed by the terms of that license\ndocument, provided that the further restriction does not survive such\nrelicensing or conveying.
\n\n
If you add terms to a covered work in accord with this section, you\nmust place, in the relevant source files, a statement of the\nadditional terms that apply to those files, or a notice indicating\nwhere to find the applicable terms.
\n\n
Additional terms, permissive or non-permissive, may be stated in the\nform of a separately written license, or stated as exceptions;\nthe above requirements apply either way.
\n\n
8. Termination.
\n\n
You may not propagate or modify a covered work except as expressly\nprovided under this License. Any attempt otherwise to propagate or\nmodify it is void, and will automatically terminate your rights under\nthis License (including any patent licenses granted under the third\nparagraph of section 11).
\n\n
However, if you cease all violation of this License, then your\nlicense from a particular copyright holder is reinstated (a)\nprovisionally, unless and until the copyright holder explicitly and\nfinally terminates your license, and (b) permanently, if the copyright\nholder fails to notify you of the violation by some reasonable means\nprior to 60 days after the cessation.
\n\n
Moreover, your license from a particular copyright holder is\nreinstated permanently if the copyright holder notifies you of the\nviolation by some reasonable means, this is the first time you have\nreceived notice of violation of this License (for any work) from that\ncopyright holder, and you cure the violation prior to 30 days after\nyour receipt of the notice.
\n\n
Termination of your rights under this section does not terminate the\nlicenses of parties who have received copies or rights from you under\nthis License. If your rights have been terminated and not permanently\nreinstated, you do not qualify to receive new licenses for the same\nmaterial under section 10.
\n\n
9. Acceptance Not Required for Having Copies.
\n\n
You are not required to accept this License in order to receive or\nrun a copy of the Program. Ancillary propagation of a covered work\noccurring solely as a consequence of using peer-to-peer transmission\nto receive a copy likewise does not require acceptance. However,\nnothing other than this License grants you permission to propagate or\nmodify any covered work. These actions infringe copyright if you do\nnot accept this License. Therefore, by modifying or propagating a\ncovered work, you indicate your acceptance of this License to do so.
\n\n
10. Automatic Licensing of Downstream Recipients.
\n\n
Each time you convey a covered work, the recipient automatically\nreceives a license from the original licensors, to run, modify and\npropagate that work, subject to this License. You are not responsible\nfor enforcing compliance by third parties with this License.
\n\n
An "entity transaction" is a transaction transferring control of an\norganization, or substantially all assets of one, or subdividing an\norganization, or merging organizations. If propagation of a covered\nwork results from an entity transaction, each party to that\ntransaction who receives a copy of the work also receives whatever\nlicenses to the work the party's predecessor in interest had or could\ngive under the previous paragraph, plus a right to possession of the\nCorresponding Source of the work from the predecessor in interest, if\nthe predecessor has it or can get it with reasonable efforts.
\n\n
You may not impose any further restrictions on the exercise of the\nrights granted or affirmed under this License. For example, you may\nnot impose a license fee, royalty, or other charge for exercise of\nrights granted under this License, and you may not initiate litigation\n(including a cross-claim or counterclaim in a lawsuit) alleging that\nany patent claim is infringed by making, using, selling, offering for\nsale, or importing the Program or any portion of it.
\n\n
11. Patents.
\n\n
A "contributor" is a copyright holder who authorizes use under this\nLicense of the Program or a work on which the Program is based. The\nwork thus licensed is called the contributor's "contributor version".
\n\n
A contributor's "essential patent claims" are all patent claims\nowned or controlled by the contributor, whether already acquired or\nhereafter acquired, that would be infringed by some manner, permitted\nby this License, of making, using, or selling its contributor version,\nbut do not include claims that would be infringed only as a\nconsequence of further modification of the contributor version. For\npurposes of this definition, "control" includes the right to grant\npatent sublicenses in a manner consistent with the requirements of\nthis License.
\n\n
Each contributor grants you a non-exclusive, worldwide, royalty-free\npatent license under the contributor's essential patent claims, to\nmake, use, sell, offer for sale, import and otherwise run, modify and\npropagate the contents of its contributor version.
\n\n
In the following three paragraphs, a "patent license" is any express\nagreement or commitment, however denominated, not to enforce a patent\n(such as an express permission to practice a patent or covenant not to\nsue for patent infringement). To "grant" such a patent license to a\nparty means to make such an agreement or commitment not to enforce a\npatent against the party.
\n\n
If you convey a covered work, knowingly relying on a patent license,\nand the Corresponding Source of the work is not available for anyone\nto copy, free of charge and under the terms of this License, through a\npublicly available network server or other readily accessible means,\nthen you must either (1) cause the Corresponding Source to be so\navailable, or (2) arrange to deprive yourself of the benefit of the\npatent license for this particular work, or (3) arrange, in a manner\nconsistent with the requirements of this License, to extend the patent\nlicense to downstream recipients. "Knowingly relying" means you have\nactual knowledge that, but for the patent license, your conveying the\ncovered work in a country, or your recipient's use of the covered work\nin a country, would infringe one or more identifiable patents in that\ncountry that you have reason to believe are valid.
\n\n
If, pursuant to or in connection with a single transaction or\narrangement, you convey, or propagate by procuring conveyance of, a\ncovered work, and grant a patent license to some of the parties\nreceiving the covered work authorizing them to use, propagate, modify\nor convey a specific copy of the covered work, then the patent license\nyou grant is automatically extended to all recipients of the covered\nwork and works based on it.
\n\n
A patent license is "discriminatory" if it does not include within\nthe scope of its coverage, prohibits the exercise of, or is\nconditioned on the non-exercise of one or more of the rights that are\nspecifically granted under this License. You may not convey a covered\nwork if you are a party to an arrangement with a third party that is\nin the business of distributing software, under which you make payment\nto the third party based on the extent of your activity of conveying\nthe work, and under which the third party grants, to any of the\nparties who would receive the covered work from you, a discriminatory\npatent license (a) in connection with copies of the covered work\nconveyed by you (or copies made from those copies), or (b) primarily\nfor and in connection with specific products or compilations that\ncontain the covered work, unless you entered into that arrangement,\nor that patent license was granted, prior to 28 March 2007.
\n\n
Nothing in this License shall be construed as excluding or limiting\nany implied license or other defenses to infringement that may\notherwise be available to you under applicable patent law.
\n\n
12. No Surrender of Others' Freedom.
\n\n
If conditions are imposed on you (whether by court order, agreement or\notherwise) that contradict the conditions of this License, they do not\nexcuse you from the conditions of this License. If you cannot convey a\ncovered work so as to satisfy simultaneously your obligations under this\nLicense and any other pertinent obligations, then as a consequence you may\nnot convey it at all. For example, if you agree to terms that obligate you\nto collect a royalty for further conveying from those to whom you convey\nthe Program, the only way you could satisfy both those terms and this\nLicense would be to refrain entirely from conveying the Program.
\n\n
13. Remote Network Interaction; Use with the GNU General Public License.
\n\n
Notwithstanding any other provision of this License, if you modify the\nProgram, your modified version must prominently offer all users\ninteracting with it remotely through a computer network (if your version\nsupports such interaction) an opportunity to receive the Corresponding\nSource of your version by providing access to the Corresponding Source\nfrom a network server at no charge, through some standard or customary\nmeans of facilitating copying of software. This Corresponding Source\nshall include the Corresponding Source for any work covered by version 3\nof the GNU General Public License that is incorporated pursuant to the\nfollowing paragraph.
\n\n
Notwithstanding any other provision of this License, you have permission\nto link or combine any covered work with a work licensed under version 3\nof the GNU General Public License into a single combined work, and to\nconvey the resulting work. The terms of this License will continue to\napply to the part which is the covered work, but the work with which it is\ncombined will remain governed by version 3 of the GNU General Public\nLicense.
\n\n
14. Revised Versions of this License.
\n\n
The Free Software Foundation may publish revised and/or new versions of\nthe GNU Affero General Public License from time to time. Such new\nversions will be similar in spirit to the present version, but may differ\nin detail to address new problems or concerns.
\n\n
Each version is given a distinguishing version number. If the\nProgram specifies that a certain numbered version of the GNU Affero\nGeneral Public License "or any later version" applies to it, you have\nthe option of following the terms and conditions either of that\nnumbered version or of any later version published by the Free\nSoftware Foundation. If the Program does not specify a version number\nof the GNU Affero General Public License, you may choose any version\never published by the Free Software Foundation.
\n\n
If the Program specifies that a proxy can decide which future\nversions of the GNU Affero General Public License can be used, that\nproxy's public statement of acceptance of a version permanently\nauthorizes you to choose that version for the Program.
\n\n
Later license versions may give you additional or different\npermissions. However, no additional obligations are imposed on any\nauthor or copyright holder as a result of your choosing to follow a\nlater version.
\n\n
15. Disclaimer of Warranty.
\n\n
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY\nAPPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT\nHOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY\nOF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,\nTHE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR\nPURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM\nIS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF\nALL NECESSARY SERVICING, REPAIR OR CORRECTION.
\n\n
16. Limitation of Liability.
\n\n
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING\nWILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS\nTHE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY\nGENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE\nUSE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF\nDATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD\nPARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),\nEVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF\nSUCH DAMAGES.
\n\n
17. Interpretation of Sections 15 and 16.
\n\n
If the disclaimer of warranty and limitation of liability provided\nabove cannot be given local legal effect according to their terms,\nreviewing courts shall apply local law that most closely approximates\nan absolute waiver of all civil liability in connection with the\nProgram, unless a warranty or assumption of liability accompanies a\ncopy of the Program in return for a fee.
\n\n
END OF TERMS AND CONDITIONS
\n\n
How to Apply These Terms to Your New Programs
\n\n
If you develop a new program, and you want it to be of the greatest\npossible use to the public, the best way to achieve this is to make it\nfree software which everyone can redistribute and change under these terms.
\n\n
To do so, attach the following notices to the program. It is safest\nto attach them to the start of each source file to most effectively\nstate the exclusion of warranty; and each file should have at least\nthe "copyright" line and a pointer to where the full notice is found.
\n\n
<one line to give the program's name and a brief idea of what it does.>\n Copyright (C) <year> <name of author>\n\n This program is free software: you can redistribute it and/or modify\n it under the terms of the GNU Affero General Public License as\n published by the Free Software Foundation, either version 3 of the\n License, or (at your option) any later version.\n\n This program is distributed in the hope that it will be useful,\n but WITHOUT ANY WARRANTY; without even the implied warranty of\n MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n GNU Affero General Public License for more details.\n\n You should have received a copy of the GNU Affero General Public License\n along with this program. If not, see <http://www.gnu.org/licenses/>.\n
\n\n
Also add information on how to contact you by electronic and paper mail.
\n\n
If your software can interact with users remotely through a computer\nnetwork, you should also make sure that it provides a way for users to\nget its source. For example, if your program is a web application, its\ninterface could display a "Source" link that leads users to an archive\nof the code. There are many ways you could offer source, and different\nsolutions will be better for different programs; see section 13 for the\nspecific requirements.
\n\n
You should also get your employer (if you work as a programmer) or school,\nif any, to sign a "copyright disclaimer" for the program, if necessary.\nFor more information on this, and how to apply and follow the GNU AGPL, see\n<http://www.gnu.org/licenses/>.
\n\n\n"
},
{
"path": "tigase-server 7.1.0/conf/config.properties",
"content": "# Licensed to the Apache Software Foundation (ASF) under one\n# or more contributor license agreements. See the NOTICE file\n# distributed with this work for additional information\n# regarding copyright ownership. The ASF licenses this file\n# to you under the Apache License, Version 2.0 (the\n# \"License\"); you may not use this file except in compliance\n# with the License. You may obtain a copy of the License at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required by applicable law or agreed to in writing,\n# software distributed under the License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY\n# KIND, either express or implied. See the License for the\n# specific language governing permissions and limitations\n# under the License.\n\n#\n# Framework config properties.\n#\n\n# To override the packages the framework exports by default from the\n# class path, set this variable.\n#org.osgi.framework.system.packages=\n\n# To append packages to the default set of exported system packages,\n# set this value.\n#org.osgi.framework.system.packages.extra=javax.*\n\n# The following property makes specified packages from the class path\n# available to all bundles. You should avoid using this property.\norg.osgi.framework.bootdelegation=sun.*,com.sun.*,org.xml.sax.*\n\n# Felix tries to guess when to implicitly boot delegate in certain\n# situations to ease integration without outside code. This feature\n# is enabled by default, uncomment the following line to disable it.\n#felix.bootdelegation.implicit=false\n\n# The following property explicitly specifies the location of the bundle\n# cache, which defaults to \"felix-cache\" in the current working directory.\n# If this value is not absolute, then the felix.cache.rootdir controls\n# how the absolute location is calculated. (See next property)\n#org.osgi.framework.storage=${dollar}{felix.cache.rootdir}/felix-cache\n\n# The following property is used to convert a relative bundle cache\n# location into an absolute one by specifying the root to prepend to\n# the relative cache path. The default for this property is the\n# current working directory.\n#felix.cache.rootdir=${dollar}{user.dir}\n\n# The following property controls whether the bundle cache is flushed\n# the first time the framework is initialized. Possible values are\n# \"none\" and \"onFirstInit\"; the default is \"none\".\norg.osgi.framework.storage.clean=onFirstInit\n\n# The following property determines which actions are performed when\n# processing the auto-deploy directory. It is a comma-delimited list of\n# the following values: 'install', 'start', 'update', and 'uninstall'.\n# An undefined or blank value is equivalent to disabling auto-deploy\n# processing.\nfelix.auto.deploy.action=install,start\n\n# The following property specifies the directory to use as the bundle\n# auto-deploy directory; the default is 'bundle' in the working directory.\nfelix.auto.deploy.dir=jars\n\n# The following property is a space-delimited list of bundle URLs\n# to install when the framework starts. The ending numerical component\n# is the target start level. Any number of these properties may be\n# specified for different start levels.\n#felix.auto.install.1=\n\n# The following property is a space-delimited list of bundle URLs\n# to install and start when the framework starts. The ending numerical\n# component is the target start level. Any number of these properties\n# may be specified for different start levels.\n#felix.auto.start.1=\n\nfelix.log.level=1\n\n# Sets the initial start level of the framework upon startup.\n#org.osgi.framework.startlevel.beginning=1\n\n# Sets the start level of newly installed bundles.\n#felix.startlevel.bundle=1\n\n# Felix installs a stream and content handler factories by default,\n# uncomment the following line to not install them.\n#felix.service.urlhandlers=false\n\n# The launcher registers a shutdown hook to cleanly stop the framework\n# by default, uncomment the following line to disable it.\nfelix.shutdown.hook=true\n\n#\n# Bundle config properties.\n#\n\nosgi.shell.telnet.ip=127.0.0.1\nosgi.shell.telnet.port=9070\nosgi.shell.telnet.maxconn=2\nosgi.shell.telnet.socketTimeout=0\n\n# debugging\n#felix.log.level=4\n#org.apache.felix.http.debug=true"
},
{
"path": "tigase-server 7.1.0/database/derby-installer-create-db.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n"
},
{
"path": "tigase-server 7.1.0/database/derby-installer-post.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n"
},
{
"path": "tigase-server 7.1.0/database/derby-schema-4-props.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- This is a dummy user who keeps all the database-properties\n-- QUERY START:\ncall TigAddUserPlainPw('db-properties', NULL);\n-- QUERY END:\n\n-- QUERY START:\ncall TigPutDBProperty('schema-version', '4.0');\n-- QUERY END:\n"
},
{
"path": "tigase-server 7.1.0/database/derby-schema-4-schema.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- QUERY START:\ncreate table tig_users (\n\tuid BIGINT GENERATED BY DEFAULT AS IDENTITY NOT NULL PRIMARY KEY,\n\n\t-- Jabber User ID\n\tuser_id varchar(2049) NOT NULL,\n\t-- User password encrypted or not\n\tuser_pw varchar(255) default NULL,\n\t-- Time the account has been created\n\tacc_create_time TIMESTAMP DEFAULT CURRENT_TIMESTAMP,\n\t-- Time of the last user login\n\tlast_login timestamp,\n\t-- Time of the last user logout\n\tlast_logout timestamp,\n\t-- User online status, if > 0 then user is online, the value\n\t-- indicates the number of user connections.\n\t-- It is incremented on each user login and decremented on each\n\t-- user logout.\n\tonline_status int default 0,\n\t-- Number of failed login attempts\n\tfailed_logins int default 0,\n\t-- User status, whether the account is active or disabled\n\t-- >0 - account active, 0 - account disabled\n\taccount_status int default 1\n);\n-- QUERY END:\n\n-- QUERY START:\ncreate unique index user_id on tig_users ( user_id );\n-- QUERY END:\n-- QUERY START:\ncreate index user_pw on tig_users (user_pw);\n-- QUERY END:\n-- QUERY START:\ncreate index last_login on tig_users (last_login);\n-- QUERY END:\n-- QUERY START:\ncreate index last_logout on tig_users (last_logout);\n-- QUERY END:\n-- QUERY START:\ncreate index account_status on tig_users (account_status);\n-- QUERY END:\n-- QUERY START:\ncreate index online_status on tig_users (online_status);\n-- QUERY END:\n\n-- QUERY START:\ncreate table tig_nodes (\n\tnid BIGINT GENERATED BY DEFAULT AS IDENTITY NOT NULL PRIMARY KEY,\n\tparent_nid bigint,\n\tuid bigint NOT NULL references tig_users(uid),\n\tnode varchar(255) NOT NULL\n);\n-- QUERY END:\n-- QUERY START:\ncreate unique index tnode on tig_nodes ( parent_nid, uid, node );\n-- QUERY END:\n-- QUERY START:\ncreate index node on tig_nodes ( node );\n-- QUERY END:\n-- QUERY START:\n-- The new index is a duplicate of an existing index\ncreate index nuid on tig_nodes (uid);\n-- QUERY END:\n-- QUERY START:\ncreate index parent_nid on tig_nodes (parent_nid);\n-- QUERY END:\n\n-- QUERY START:\ncreate table tig_pairs (\n\tnid bigint references tig_nodes(nid),\n\tuid bigint NOT NULL references tig_users(uid),\n\tpkey varchar(255) NOT NULL,\n\tpval long varchar\n);\n-- QUERY END:\n-- QUERY START:\n-- The new index is a duplicate of an existing index\ncreate index pkey on tig_pairs ( pkey );\n-- QUERY END:\n-- QUERY START:\n-- The new index is a duplicate of an existing index\ncreate index puid on tig_pairs (uid);\n-- QUERY END:\n-- QUERY START:\ncreate index pnid on tig_pairs (nid);\n-- QUERY END:\n\n-- QUERY START:\ncreate table short_news (\n\tsnid BIGINT GENERATED BY DEFAULT AS IDENTITY NOT NULL PRIMARY KEY,\n\tpublishing_time timestamp default current timestamp,\n\tnews_type varchar(10),\n\tauthor varchar(128) NOT NULL,\n\tsubject varchar(128) NOT NULL,\n\tbody varchar(1024) NOT NULL\n);\n-- QUERY END:\n-- QUERY START:\ncreate index publishing_time on short_news (publishing_time);\n-- QUERY END:\n-- QUERY START:\ncreate index author on short_news (author);\n-- QUERY END:\n-- QUERY START:\ncreate index news_type on short_news (news_type);\n-- QUERY END:\n\n-- QUERY START:\ncreate table xmpp_stanza (\n\tid BIGINT GENERATED BY DEFAULT AS IDENTITY NOT NULL PRIMARY KEY,\n\tstanza long varchar NOT NULL\n);\n-- QUERY END:\n"
},
{
"path": "tigase-server 7.1.0/database/derby-schema-4-sp.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- QUERY START:\nCREATE function TigGetDBProperty(tkey varchar(255)) returns long varchar\n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tREADS SQL DATA\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigGetDBProperty';\n-- QUERY END:\n\n-- QUERY START:\nCREATE procedure TigPutDBProperty(tkey varchar(255), tval varchar(32672)) \n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tMODIFIES SQL DATA\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigPutDBProperty';\n-- QUERY END:\n\n-- QUERY START:\nCREATE procedure TigInitdb() \n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tMODIFIES SQL DATA\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigInitdb';\n-- QUERY END:\n\n-- QUERY START:\nCREATE procedure TigAddUser(userId varchar(2049), userPw varchar(255)) \n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tMODIFIES SQL DATA\n\tDYNAMIC RESULT SETS 1\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigAddUser';\n-- QUERY END:\n\n-- QUERY START:\nCREATE procedure TigAddUserPlainPw(userId varchar(2049), userPw varchar(255)) \n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tMODIFIES SQL DATA\n\tDYNAMIC RESULT SETS 1\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigAddUserPlainPw';\n-- QUERY END:\n\n-- QUERY START:\nCREATE procedure TigGetUserDBUid(userId varchar(2049)) \n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tREADS SQL DATA\n\tDYNAMIC RESULT SETS 1\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigGetUserDBUid';\n-- QUERY END:\n\n-- QUERY START:\nCREATE procedure TigRemoveUser(userId varchar(2049)) \n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tMODIFIES SQL DATA\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigRemoveUser';\n-- QUERY END:\n\n-- QUERY START:\nCREATE procedure TigGetPassword(userId varchar(2049)) \n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tREADS SQL DATA\n\tDYNAMIC RESULT SETS 1\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigGetPassword';\n-- QUERY END:\n\n-- QUERY START:\nCREATE procedure TigUpdatePasswordPlainPwRev(userId varchar(2049), userPw varchar(255))\n PARAMETER STYLE JAVA\n LANGUAGE JAVA\n MODIFIES SQL DATA\n EXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigUpdatePasswordPlainPwRev';\n-- QUERY END:\n\n-- QUERY START:\nCREATE procedure TigUpdatePasswordPlainPw(userId varchar(2049), userPw varchar(255)) \n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tMODIFIES SQL DATA\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigUpdatePasswordPlainPw';\n-- QUERY END:\n\n-- QUERY START:\nCREATE procedure TigUpdatePassword(userId varchar(2049), userPw varchar(255)) \n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tMODIFIES SQL DATA\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigUpdatePassword';\n-- QUERY END:\n\n-- QUERY START:\nCREATE procedure TigOnlineUsers() \n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tREADS SQL DATA\n\tDYNAMIC RESULT SETS 1\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigOnlineUsers';\n-- QUERY END:\n\n-- QUERY START:\nCREATE procedure TigOfflineUsers() \n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tREADS SQL DATA\n\tDYNAMIC RESULT SETS 1\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigOfflineUsers';\n-- QUERY END:\n\n-- QUERY START:\nCREATE procedure TigAllUsers() \n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tREADS SQL DATA\n\tDYNAMIC RESULT SETS 1\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigAllUsers';\n-- QUERY END:\n\n-- QUERY START:\nCREATE procedure TigAllUsersCount() \n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tREADS SQL DATA\n\tDYNAMIC RESULT SETS 1\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigAllUsersCount';\n-- QUERY END:\n\n-- QUERY START:\nCREATE procedure TigUserLoginPlainPw(userId varchar(2049), userPw varchar(255)) \n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tMODIFIES SQL DATA\n\tDYNAMIC RESULT SETS 1\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigUserLoginPlainPw';\n-- QUERY END:\n\n-- QUERY START:\nCREATE procedure TigUserLogin(userId varchar(2049), userPw varchar(255)) \n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tMODIFIES SQL DATA\n\tDYNAMIC RESULT SETS 1\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigUserLogin';\n-- QUERY END:\n\n-- QUERY START:\nCREATE procedure TigUserLogout(userId varchar(2049)) \n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tMODIFIES SQL DATA\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigUserLogout';\n-- QUERY END:\n\n-- QUERY START:\nCREATE procedure TigDisableAccount(userId varchar(2049)) \n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tMODIFIES SQL DATA\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigDisableAccount';\n-- QUERY END:\n\n-- QUERY START:\nCREATE procedure TigEnableAccount(userId varchar(2049)) \n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tMODIFIES SQL DATA\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigEnableAccount';\n-- QUERY END:\n\n-- QUERY START:\nCREATE procedure TigActiveAccounts() \n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tREADS SQL DATA\n\tDYNAMIC RESULT SETS 1\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigActiveAccounts';\n-- QUERY END:\n\n-- QUERY START:\nCREATE procedure TigDisabledAccounts() \n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tREADS SQL DATA\n\tDYNAMIC RESULT SETS 1\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigDisabledAccounts';\n-- QUERY END:\n\n-- QUERY START:\nCREATE procedure TigAddNode(parentNid bigint, uid bigint, node varchar(255)) \n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tMODIFIES SQL DATA\n\tDYNAMIC RESULT SETS 1\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigAddNode';\n-- QUERY END:\n\n-- QUERY START:\nCREATE procedure TigUpdatePairs(nid bigint, uid bigint, tkey varchar(255), tval varchar(32672)) \n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tMODIFIES SQL DATA\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigUpdatePairs';\n-- QUERY END:\n"
},
{
"path": "tigase-server 7.1.0/database/derby-schema-4.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- LOAD FILE: database/derby-schema-4-schema.sql\n\n-- LOAD FILE: database/derby-schema-4-sp.sql\n\n-- LOAD FILE: database/derby-schema-4-props.sql\n\nrun 'database/derby-schema-4-schema.sql';\n\nrun 'database/derby-schema-4-sp.sql';\n\nrun 'database/derby-schema-4-props.sql';\n"
},
{
"path": "tigase-server 7.1.0/database/derby-schema-5-1-props.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- This is a dummy user who keeps all the database-properties\n-- QUERY START:\ncall TigAddUserPlainPw('db-properties', NULL);\n-- QUERY END:\n\n-- QUERY START:\ncall TigPutDBProperty('schema-version', '5.1');\n-- QUERY END:\n"
},
{
"path": "tigase-server 7.1.0/database/derby-schema-5-1-schema.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\nrun 'database/derby-schema-4-schema.sql';\n\n-- LOAD FILE: database/derby-schema-4-schema.sql\n\n-- QUERY START:\nalter table tig_pairs ADD column pval2 CLOB;\n-- QUERY END:\n\n-- QUERY START:\nupdate tig_pairs set pval2=pval;\n-- QUERY END:\n\n-- QUERY START:\nalter table tig_pairs drop column pval;\n-- QUERY END:\n\n-- QUERY START:\nRENAME COLUMN tig_pairs.pval2 to pval;\n-- QUERY END:\n"
},
{
"path": "tigase-server 7.1.0/database/derby-schema-5-1-sp.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\nrun 'database/derby-schema-4-sp.sql';\n\n-- LOAD FILE: database/derby-schema-4-sp.sql\n\n-- QUERY START:\ndrop procedure TigUpdatePairs;\n-- QUERY END:\n\n\n-- QUERY START:\nCREATE procedure TigUpdatePairs(nid bigint, uid bigint, tkey varchar(255), tval clob) \n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tMODIFIES SQL DATA\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigUpdatePairs';\n-- QUERY END:\n"
},
{
"path": "tigase-server 7.1.0/database/derby-schema-5-1.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\nrun 'database/derby-schema-5-1-schema.sql';\n\nrun 'database/derby-schema-5-1-sp.sql';\n\nrun 'database/derby-schema-5-1-props.sql';\n\n-- LOAD FILE: database/derby-schema-5-1-schema.sql\n\n-- LOAD FILE: database/derby-schema-5-1-sp.sql\n\n-- LOAD FILE: database/derby-schema-5-1-props.sql\n"
},
{
"path": "tigase-server 7.1.0/database/derby-schema-5.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\nrun 'database/derby-schema-4-schema.sql';\n\nrun 'database/derby-schema-4-sp.sql';\n\nrun 'database/derby-schema-4-props.sql';\n\n-- LOAD FILE: database/derby-schema-4-schema.sql\n\n-- LOAD FILE: database/derby-schema-4-sp.sql\n\n-- LOAD FILE: database/derby-schema-4-props.sql"
},
{
"path": "tigase-server 7.1.0/database/derby-schema-7-1-props.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2016 \"Tigase, Inc.\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n--\n\n-- This is a dummy user who keeps all the database-properties\n-- QUERY START:\ncall TigAddUserPlainPw('db-properties', NULL);\n-- QUERY END:\n\n-- QUERY START:\ncall TigPutDBProperty('schema-version', '7.1');\n-- QUERY END:\n"
},
{
"path": "tigase-server 7.1.0/database/derby-schema-7-1-schema.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2016 \"Tigase, Inc.\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n--\n\nrun 'database/derby-schema-5-1-schema.sql';\n\n-- LOAD FILE: database/derby-schema-5-1-schema.sql\n\n-- QUERY START:\nALTER TABLE tig_pairs ADD COLUMN PID INTEGER GENERATED BY DEFAULT AS IDENTITY (START WITH 1, INCREMENT BY 1) NOT NULL PRIMARY KEY;\n-- QUERY END:\n\n"
},
{
"path": "tigase-server 7.1.0/database/derby-schema-7-1-sp.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2016 \"Tigase, Inc.\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n--\n\nrun 'database/derby-schema-5-1-sp.sql';\n\n-- LOAD FILE: database/derby-schema-5-1-sp.sql\n\n-- QUERY START:\ndrop procedure TigPutDBProperty;\n-- QUERY END:\n\n\n-- QUERY START:\nCREATE procedure TigPutDBProperty(tkey varchar(255), tval varchar(32672)) \n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tMODIFIES SQL DATA\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigPutDBProperty';\n-- QUERY END:"
},
{
"path": "tigase-server 7.1.0/database/derby-schema-7-1.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2016 \"Tigase, Inc.\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n--\n\nrun 'database/derby-schema-7-1-schema.sql';\n\nrun 'database/derby-schema-7-1-sp.sql';\n\nrun 'database/derby-schema-7-1-props.sql';\n\n-- LOAD FILE: database/derby-schema-7-1-schema.sql\n\n-- LOAD FILE: database/derby-schema-7-1-sp.sql\n\n-- LOAD FILE: database/derby-schema-7-1-props.sql\n"
},
{
"path": "tigase-server 7.1.0/database/derby-schema-upgrade-to-5-1.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n\n-- QUERY START:\ncall TigPutDBProperty('schema-version','5.1');\n-- QUERY END:\n\n-- QUERY START:\ndrop procedure TigUpdatePairs;\n-- QUERY END:\n\n\n-- QUERY START:\nCREATE procedure TigUpdatePairs(nid bigint, uid bigint, tkey varchar(255), tval clob) \n PARAMETER STYLE JAVA\n LANGUAGE JAVA\n MODIFIES SQL DATA\n EXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigUpdatePairs';\n-- QUERY END:\n\n"
},
{
"path": "tigase-server 7.1.0/database/derby-schema-upgrade-to-7-1.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2016 \"Tigase, Inc.\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n--\n\n\n\n\n-- QUERY START:\ndrop procedure TigPutDBProperty;\n-- QUERY END:\n\n\n-- QUERY START:\nCREATE procedure TigPutDBProperty(tkey varchar(255), tval varchar(32672)) \n\tPARAMETER STYLE JAVA\n\tLANGUAGE JAVA\n\tMODIFIES SQL DATA\n\tEXTERNAL NAME 'tigase.db.derby.StoredProcedures.tigPutDBProperty';\n-- QUERY END:\n\n-- QUERY START:\nupdate tig_pairs set nid = (select nid from tig_nodes where uid=(select uid from tig_users where user_id='db-properties') and node='root') where uid=(select uid from tig_users where user_id='db-properties');\n-- QUERY END:\n\n-- QUERY START:\nALTER TABLE tig_pairs ADD COLUMN PID INTEGER GENERATED BY DEFAULT AS IDENTITY (START WITH 1, INCREMENT BY 1) NOT NULL PRIMARY KEY;\n-- QUERY END:\n\n\n-- QUERY START:\ncall TigPutDBProperty('schema-version','7.1');\n-- QUERY END:\n\n"
},
{
"path": "tigase-server 7.1.0/database/mysql-installer-create-db.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- QUERY START: create database\n\ncreate database ${dbName};\n\n-- QUERY END: create database\n\n-- QUERY START: add user\n\nGRANT ALL ON ${dbName}.* TO ${dbUser}@'%' IDENTIFIED BY '${dbPass}';\n\n-- QUERY END: add user\n\n-- QUERY START: add user\n\nGRANT ALL ON ${dbName}.* TO ${dbUser}@'localhost' IDENTIFIED BY '${dbPass}';\n\n-- QUERY END: add user\n\n-- QUERY START: add user\n\nGRANT ALL ON ${dbName}.* TO ${dbUser} IDENTIFIED BY '${dbPass}';\n\n-- QUERY END: user\n\n-- QUERY START: update user privileges\n\nGRANT SELECT, INSERT, UPDATE ON mysql.proc TO ${dbUser}@'localhost';\n\n-- QUERY END: update user privileges\n\n-- QUERY START: update user privileges\n\nGRANT SELECT, INSERT, UPDATE ON mysql.proc TO ${dbUser}@'%';\n\n-- QUERY END: update user privileges\n\n-- QUERY START: update user privileges\n\nGRANT SELECT, INSERT, UPDATE ON mysql.proc TO ${dbUser};\n\n-- QUERY END: update user privileges\n\n-- QUERY START: flush privileges\n\nFLUSH PRIVILEGES;\n\n-- QUERY END: flush privileges\n\n"
},
{
"path": "tigase-server 7.1.0/database/mysql-installer-post.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n"
},
{
"path": "tigase-server 7.1.0/database/mysql-schema-3.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- To load schema to MySQL database execute following commands:\n--\n-- mysqladmin -u root -pdbpass create tigase\n-- mysql -u root -pdbpass tigase < database/mysql-schema.sql\n-- echo \"GRANT ALL ON tigase.* TO tigase_user@'%' \\\n-- IDENTIFIED BY 'tigase_passwd'; \\\n-- FLUSH PRIVILEGES;\" | mysql -u root -pdbpass mysql\n-- echo \"GRANT ALL ON tigase.* TO tigase_user@'localhost' \\\n-- IDENTIFIED BY 'tigase_passwd'; \\\n-- FLUSH PRIVILEGES;\" | mysql -u root -pdbpass mysql\n-- echo \"GRANT ALL ON tigase.* TO tigase_user \\\n-- IDENTIFIED BY 'tigase_passwd'; \\\n-- FLUSH PRIVILEGES;\" | mysql -u root -pdbpass mysql\n\n\ncreate table short_news (\n -- Automatic record ID\n snid bigint unsigned NOT NULL auto_increment,\n -- Automaticly generated timestamp and automaticly updated on change\n publishing_time timestamp,\n\t-- Optional news type: 'shorts', 'minis', 'techs', 'funs'....\n\tnews_type varchar(10),\n -- Author JID\n author varchar(128) NOT NULL,\n -- Short subject - this is short news, right?\n subject varchar(128) NOT NULL,\n -- Short news message - this is short news, right?\n body varchar(1024) NOT NULL,\n primary key(snid),\n key publishing_time (publishing_time),\n key author (author),\n key news_type (news_type)\n)\nENGINE=InnoDB default character set utf8 ROW_FORMAT=DYNAMIC;\n\ncreate table xmpp_stanza (\n\t\t\t id bigint unsigned NOT NULL auto_increment,\n\t\t\t stanza text NOT NULL,\n\n\t\t\t primary key (id)\n)\nENGINE=InnoDB default character set utf8 ROW_FORMAT=DYNAMIC;\n\ncreate table tig_users (\n uid bigint unsigned NOT NULL,\n\n user_id varchar(128) NOT NULL,\n\n primary key (uid),\n unique key user_id (user_id)\n)\nENGINE=InnoDB default character set utf8 ROW_FORMAT=DYNAMIC;\n\ncreate table tig_nodes (\n nid bigint unsigned NOT NULL,\n parent_nid bigint unsigned,\n uid bigint unsigned NOT NULL,\n\n node varchar(64) NOT NULL,\n\n primary key (nid),\n unique key tnode (parent_nid, uid, node),\n key node (node),\n\t\t\t constraint tig_nodes_constr foreign key (uid) references tig_users (uid)\n)\nENGINE=InnoDB default character set utf8 ROW_FORMAT=DYNAMIC;\n\ncreate table tig_pairs (\n nid bigint unsigned,\n uid bigint unsigned NOT NULL,\n\n pkey varchar(128) NOT NULL,\n pval varchar(65535),\n\n key pkey (pkey),\n\t\t\t constraint tig_pairs_constr_1 foreign key (uid) references tig_users (uid),\n\t\t\t constraint tig_pairs_constr_2 foreign key (nid) references tig_nodes (nid)\n)\nENGINE=InnoDB default character set utf8 ROW_FORMAT=DYNAMIC;\n\n-- create table tig_max_ids (\n-- max_uid bigint unsigned,\n-- max_nid bigint unsigned\n-- )\n-- ENGINE=InnoDB default character set utf8 ROW_FORMAT=DYNAMIC;\n\n-- insert into tig_max_ids (max_uid, max_nid) values (1, 1);\n\n-- Get top nodes for the user: user1@hostname\n--\n-- select nid, node from nodes, users\n-- where ('user1@hostname' = user_id)\n-- AND (nodes.uid = users.uid)\n-- AND (parent_nid is null);\n\n-- Get all subnodes of the node: /privacy/default for user: user1@hostname\n--\n-- select nid, node from nodes,\n-- (\n-- select nid as dnid from nodes,\n-- (\n-- select nid as pnid from nodes, users\n-- where ('user1@hostname' = user_id)\n-- AND (nodes.uid = users.uid)\n-- AND (parent_nid is null)\n-- AND (node = 'privacy')\n-- ) ptab where (parent_nid = pnid)\n-- AND (node = 'default')\n-- ) dtab where (parent_nid = dnid);\n\n-- Get all keys (pairs) for the node: /privacy/default/24 for user: user1@hostname\n--\n-- select pkey, pval from pairs,\n-- (\n-- select nid, node from nodes,\n-- (\n-- select nid as dnid from nodes,\n-- (\n-- select nid as pnid from nodes, users\n-- where ('user1@hostname' = user_id)\n-- AND (nodes.uid = users.uid)\n-- \t AND (parent_nid is null)\n-- \t AND (node = 'privacy')\n-- ) ptab where (parent_nid = pnid)\n-- AND (node = 'default')\n-- ) dtab where (parent_nid = dnid)\n-- ) ntab where (pairs.nid = ntab.nid) AND (node = '24');\n"
},
{
"path": "tigase-server 7.1.0/database/mysql-schema-4-props.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- QUERY START:\n-- This is a dummy user who keeps all the database-properties\ncall TigAddUserPlainPw('db-properties', NULL);\n-- QUERY END:\n\nselect NOW(), ' - Setting schema version to 4.0';\n\n-- QUERY START:\ncall TigPutDBProperty('schema-version', '4.0');\n-- QUERY END:\n"
},
{
"path": "tigase-server 7.1.0/database/mysql-schema-4-schema.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- To load schema to MySQL database execute following commands:\n--\n-- mysqladmin -u root -pdbpass create tigase\n-- mysql -u root -pdbpass tigase < database/mysql-schema-4.sql\n-- echo \"GRANT ALL ON tigase.* TO tigase_user@'%' \\\n-- IDENTIFIED BY 'tigase_passwd'; \\\n-- FLUSH PRIVILEGES;\" | mysql -u root -pdbpass mysql\n-- echo \"GRANT ALL ON tigase.* TO tigase_user@'localhost' \\\n-- IDENTIFIED BY 'tigase_passwd'; \\\n-- FLUSH PRIVILEGES;\" | mysql -u root -pdbpass mysql\n-- echo \"GRANT ALL ON tigase.* TO tigase_user \\\n-- IDENTIFIED BY 'tigase_passwd'; \\\n-- FLUSH PRIVILEGES;\" | mysql -u root -pdbpass mysql\n\n-- QUERY START:\n\ncreate table if not exists tig_users (\n\tuid bigint unsigned NOT NULL auto_increment,\n\n\t-- Jabber User ID\n\tuser_id varchar(2049) NOT NULL,\n\t-- UserID SHA1 hash to prevent duplicate user_ids\n\tsha1_user_id char(128) NOT NULL,\n\t-- User password encrypted or not\n\tuser_pw varchar(255) default NULL,\n\t-- Time the account has been created\n\tacc_create_time timestamp DEFAULT CURRENT_TIMESTAMP,\n\t-- Time of the last user login\n\tlast_login timestamp DEFAULT 0,\n\t-- Time of the last user logout\n\tlast_logout timestamp DEFAULT 0,\n\t-- User online status, if > 0 then user is online, the value\n\t-- indicates the number of user connections.\n\t-- It is incremented on each user login and decremented on each\n\t-- user logout.\n\tonline_status int default 0,\n\t-- Number of failed login attempts\n\tfailed_logins int default 0,\n\t-- User status, whether the account is active or disabled\n\t-- >0 - account active, 0 - account disabled\n\taccount_status int default 1,\n\n\tprimary key (uid),\n\tunique key sha1_user_id (sha1_user_id),\n\tkey user_pw (user_pw),\n--\tkey user_id (user_id(765)),\n\tkey last_login (last_login),\n\tkey last_logout (last_logout),\n\tkey account_status (account_status),\n\tkey online_status (online_status)\n)\nENGINE=InnoDB default character set utf8 ROW_FORMAT=COMPRESSED KEY_BLOCK_SIZE=8;\n\n-- QUERY END:\n\n-- QUERY START:\n\nCREATE INDEX part_of_user_id ON tig_users (user_id(255));\n\n-- QUERY END:\n\n-- QUERY START:\n\ncreate table if not exists tig_nodes (\n nid bigint unsigned NOT NULL auto_increment,\n parent_nid bigint unsigned,\n uid bigint unsigned NOT NULL,\n\n node varchar(255) NOT NULL,\n\n primary key (nid),\n unique key tnode (parent_nid, uid, node),\n key node (node),\n\t\t\t key uid (uid),\n\t\t\t key parent_nid (parent_nid),\n\t\t\t constraint tig_nodes_constr foreign key (uid) references tig_users (uid)\n)\nENGINE=InnoDB default character set utf8 ROW_FORMAT=DYNAMIC;\n\n-- QUERY END:\n\n-- QUERY START:\n\ncreate table if not exists tig_pairs (\n nid bigint unsigned,\n uid bigint unsigned NOT NULL,\n\n pkey varchar(255) NOT NULL,\n pval mediumtext,\n\n key pkey (pkey),\n\t\t\t key uid (uid),\n\t\t\t key nid (nid),\n\t\t\t constraint tig_pairs_constr_1 foreign key (uid) references tig_users (uid),\n\t\t\t constraint tig_pairs_constr_2 foreign key (nid) references tig_nodes (nid)\n)\nENGINE=InnoDB default character set utf8 ROW_FORMAT=COMPRESSED KEY_BLOCK_SIZE=8;\n\n-- QUERY END:\n\n-- QUERY START:\n\ncreate table if not exists short_news (\n -- Automatic record ID\n snid bigint unsigned NOT NULL auto_increment,\n -- Automaticly generated timestamp and automaticly updated on change\n publishing_time timestamp,\n\t-- Optional news type: 'shorts', 'minis', 'techs', 'funs'....\n\tnews_type varchar(10),\n -- Author JID\n author varchar(128) NOT NULL,\n -- Short subject - this is short news, right?\n subject varchar(128) NOT NULL,\n -- Short news message - this is short news, right?\n body varchar(1024) NOT NULL,\n primary key(snid),\n key publishing_time (publishing_time),\n key author (author),\n key news_type (news_type)\n)\nENGINE=InnoDB default character set utf8 ROW_FORMAT=DYNAMIC;\n\n-- QUERY END:\n\n-- QUERY START:\n\ncreate table if not exists xmpp_stanza (\n\t\t\t id bigint unsigned NOT NULL auto_increment,\n\t\t\t stanza text NOT NULL,\n\n\t\t\t primary key (id)\n)\nENGINE=InnoDB default character set utf8 ROW_FORMAT=DYNAMIC;\n\n-- QUERY END:"
},
{
"path": "tigase-server 7.1.0/database/mysql-schema-4-sp.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- Database stored procedures and functions for Tigase schema version 4.0.0\n\n-- QUERY START:\ndrop procedure if exists TigInitdb;\n-- QUERY END:\n-- QUERY START:\ndrop procedure if exists TigAddUser;\n-- QUERY END:\n-- QUERY START:\ndrop procedure if exists TigAddUserPlainPw;\n-- QUERY END:\n-- QUERY START:\ndrop procedure if exists TigGetUserDBUid;\n-- QUERY END:\n-- QUERY START:\ndrop procedure if exists TigRemoveUser;\n-- QUERY END:\n-- QUERY START:\ndrop procedure if exists TigUpdatePassword;\n-- QUERY END:\n-- QUERY START:\ndrop procedure if exists TigUpdatePasswordPlainPw;\n-- QUERY END:\n-- QUERY START:\ndrop procedure if exists TigUpdatePasswordPlainPwRev;\n-- QUERY END:\n-- QUERY START:\ndrop procedure if exists TigGetPassword;\n-- QUERY END:\n-- QUERY START:\ndrop procedure if exists TigUserLogin;\n-- QUERY END:\n-- QUERY START:\ndrop procedure if exists TigUserLoginPlainPw;\n-- QUERY END:\n-- QUERY START:\ndrop procedure if exists TigUserLogout;\n-- QUERY END:\n-- QUERY START:\ndrop procedure if exists TigOnlineUsers;\n-- QUERY END:\n-- QUERY START:\ndrop procedure if exists TigOfflineUsers;\n-- QUERY END:\n-- QUERY START:\ndrop procedure if exists TigAllUsers;\n-- QUERY END:\n-- QUERY START:\ndrop procedure if exists TigAllUsersCount;\n-- QUERY END:\n-- QUERY START:\ndrop procedure if exists TigDisableAccount;\n-- QUERY END:\n-- QUERY START:\ndrop procedure if exists TigEnableAccount;\n-- QUERY END:\n-- QUERY START:\ndrop procedure if exists TigActiveAccounts;\n-- QUERY END:\n-- QUERY START:\ndrop procedure if exists TigDisabledAccounts;\n-- QUERY END:\n-- QUERY START:\ndrop procedure if exists TigAddNode;\n-- QUERY END:\n-- QUERY START:\ndrop procedure if exists TigTestAddUser;\n-- QUERY END:\n-- QUERY START:\ndrop procedure if exists TigUsers2Ver4Convert;\n-- QUERY END:\n-- QUERY START:\ndrop procedure if exists TigPutDBProperty;\n-- QUERY END:\n-- QUERY START:\ndrop function if exists TigGetDBProperty;\n-- QUERY END:\n-- QUERY START:\ndrop procedure if exists TigUpdatePairs;\n-- QUERY END:\n\ndelimiter //\n\n-- QUERY START:\n-- Database properties get - function\ncreate function TigGetDBProperty(_tkey varchar(255) CHARSET utf8) returns mediumtext CHARSET utf8\nREADS SQL DATA\nbegin\n\tdeclare _result mediumtext CHARSET utf8;\n\n\tselect pval into _result from tig_pairs, tig_users\n\t\twhere (pkey = _tkey) AND (sha1_user_id = sha1(lower('db-properties')))\n\t\t\t\t\tAND (tig_pairs.uid = tig_users.uid);\n\n\treturn (_result);\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- Database properties set - procedure\ncreate procedure TigPutDBProperty(_tkey varchar(255) CHARSET utf8, _tval mediumtext CHARSET utf8)\nbegin\n if exists( select 1 from tig_pairs, tig_users where\n (sha1_user_id = sha1(lower('db-properties'))) AND (tig_users.uid = tig_pairs.uid)\n AND (pkey = _tkey))\n then\n update tig_pairs, tig_users set pval = _tval\n where (sha1_user_id = sha1(lower('db-properties'))) AND (tig_users.uid = tig_pairs.uid)\n AND (pkey = _tkey);\n else\n insert into tig_pairs (pkey, pval, uid)\n select _tkey, _tval, uid from tig_users\n where (sha1_user_id = sha1(lower('db-properties')));\n end if;\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- The initialization of the database.\n-- The procedure should be called manually somehow before starting the\n-- server. In theory the server could call the procedure automatically\n-- at the startup time but I don't know yet how to solve the problem\n-- with multiple cluster nodes starting at later time when the server\n-- is already running.\ncreate procedure TigInitdb()\nbegin\n update tig_users set online_status = 0;\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- Add a new user to the database assuming the user password is already\n-- encoded properly according to the database settings.\n-- If password is not encoded TigAddUserPlainPw should be used instead.\ncreate procedure TigAddUser(_user_id varchar(2049) CHARSET utf8, _user_pw varchar(255) CHARSET utf8)\nbegin\n\tdeclare res_uid bigint unsigned;\n\n\tinsert into tig_users (user_id, sha1_user_id, user_pw)\n\t\tvalues (_user_id, sha1(lower(_user_id)), _user_pw);\n\n\tselect LAST_INSERT_ID() into res_uid;\n\n\tinsert into tig_nodes (parent_nid, uid, node)\n\t\tvalues (NULL, res_uid, 'root');\n\n\tif _user_pw is NULL then\n\t\tupdate tig_users set account_status = -1 where uid = res_uid;\n\tend if;\n\n\tselect res_uid as uid;\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- Takes plain text user password and converts it to internal representation\n-- and creates a new user account.\ncreate procedure TigAddUserPlainPw(_user_id varchar(2049) CHARSET utf8, _user_pw varchar(255) CHARSET utf8)\nbegin\n\tcase TigGetDBProperty('password-encoding')\n\t\twhen 'MD5-PASSWORD' then\n\t\t\tcall TigAddUser(_user_id, MD5(_user_pw));\n\t\twhen 'MD5-USERID-PASSWORD' then\n\t\t\tcall TigAddUser(_user_id, MD5(CONCAT(_user_id, _user_pw)));\n\t\twhen 'MD5-USERNAME-PASSWORD' then\n\t\t\tcall TigAddUser(_user_id, MD5(CONCAT(substring_index(_user_id, '@', 1), _user_pw)));\n\t\telse\n\t\t\tcall TigAddUser(_user_id, _user_pw);\n\t\tend case;\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- Low level database user id as big number. Used only for performance reasons\n-- and save database space. Besides JID is too large to server as UID\ncreate procedure TigGetUserDBUid(_user_id varchar(2049) CHARSET utf8)\nbegin\n\tselect uid from tig_users where sha1_user_id = sha1(lower(_user_id));\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- Removes a user from the database\ncreate procedure TigRemoveUser(_user_id varchar(2049) CHARSET utf8)\nbegin\n\tdeclare res_uid bigint unsigned;\n\n\tselect uid into res_uid from tig_users where sha1_user_id = sha1(lower(_user_id));\n\n\tdelete from tig_pairs where uid = res_uid;\n\tdelete from tig_nodes where uid = res_uid;\n\tdelete from tig_users where uid = res_uid;\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- Returns user's password from the database\ncreate procedure TigGetPassword(_user_id varchar(2049) CHARSET utf8)\nbegin\n\tselect user_pw from tig_users where sha1_user_id = sha1(lower(_user_id));\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- Takes plain text user password and converts it to internal representation\ncreate procedure TigUpdatePasswordPlainPw(_user_id varchar(2049) CHARSET utf8, _user_pw varchar(255) CHARSET utf8)\nbegin\n\tcase TigGetDBProperty('password-encoding')\n\t\twhen 'MD5-PASSWORD' then\n\t\t\tcall TigUpdatePassword(_user_id, MD5(_user_pw));\n\t\twhen 'MD5-USERID-PASSWORD' then\n\t\t\tcall TigUpdatePassword(_user_id, MD5(CONCAT(_user_id, _user_pw)));\n\t\twhen 'MD5-USERNAME-PASSWORD' then\n\t\t\tcall TigUpdatePassword(_user_id, MD5(CONCAT(substring_index(_user_id, '@', 1), _user_pw)));\n\t\telse\n\t\t\tcall TigUpdatePassword(_user_id, _user_pw);\n\t\tend case;\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- Variant of TigUpdatePasswordPlainPw SP with parameters in reverse order.\n-- Some implementations require the parameters to be in the same order as\n-- the update query.\ncreate procedure TigUpdatePasswordPlainPwRev(_user_pw varchar(255) CHARSET utf8, _user_id varchar(2049) CHARSET utf8)\nbegin\n\tcall TigUpdatePasswordPlainPw(_user_id, _user_pw);\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- Update user password\ncreate procedure TigUpdatePassword(_user_id varchar(2049) CHARSET utf8, _user_pw varchar(255) CHARSET utf8)\nbegin\n\tupdate tig_users set user_pw = _user_pw where sha1_user_id = sha1(lower(_user_id));\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- List all online users\ncreate procedure TigOnlineUsers()\nbegin\n\tselect user_id, last_login, last_logout, online_status, failed_logins, account_status\n\t\tfrom tig_users where online_status > 0;\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- List all offline users\ncreate procedure TigOfflineUsers()\nbegin\n\tselect user_id, last_login, last_logout, online_status, failed_logins, account_status\n\t\tfrom tig_users where online_status = 0;\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- List of all users in database\ncreate procedure TigAllUsers()\nbegin\n\tselect user_id, last_login, last_logout, online_status, failed_logins, account_status\n\t\tfrom tig_users;\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- All users count\ncreate procedure TigAllUsersCount()\nbegin\n\tselect count(*) from tig_users;\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- Performs user login for a plain text password, converting it to an internal\n-- representation if necessary\ncreate procedure TigUserLoginPlainPw(_user_id varchar(2049) CHARSET utf8, _user_pw varchar(255) CHARSET utf8)\nbegin\n\tcase TigGetDBProperty('password-encoding')\n\t\twhen 'MD5-PASSWORD' then\n\t\t\tcall TigUserLogin(_user_id, MD5(_user_pw));\n\t\twhen 'MD5-USERID-PASSWORD' then\n\t\t\tcall TigUserLogin(_user_id, MD5(CONCAT(_user_id, _user_pw)));\n\t\twhen 'MD5-USERNAME-PASSWORD' then\n\t\t\tcall TigUserLogin(_user_id, MD5(CONCAT(substring_index(_user_id, '@', 1), _user_pw)));\n\t\telse\n\t\t\tcall TigUserLogin(_user_id, _user_pw);\n\t\tend case;\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- Perforrm user login. It returns user_id uppon success and NULL\n-- on failure.\n-- If the login is successful it also increases online_status and sets\n-- last_login time to the current timestamp\ncreate procedure TigUserLogin(_user_id varchar(2049) CHARSET utf8, _user_pw varchar(255) CHARSET utf8)\nbegin\n\tif exists(select 1 from tig_users\n\t\twhere (account_status > 0) AND (sha1_user_id = sha1(lower(_user_id))) AND (user_pw = _user_pw) AND (user_id = _user_id))\n\tthen\n\t\tupdate tig_users\n\t\t\tset online_status = online_status + 1, last_login = CURRENT_TIMESTAMP\n\t\t\twhere sha1_user_id = sha1(lower(_user_id));\n\t\tselect _user_id as user_id;\n\telse\n\t\tupdate tig_users set failed_logins = failed_logins + 1 where sha1_user_id = sha1(lower(_user_id));\n\t\tselect NULL as user_id;\n\tend if;\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- It decreases online_status and sets last_logout time to the current timestamp\ncreate procedure TigUserLogout(_user_id varchar(2049) CHARSET utf8)\nbegin\n\tupdate tig_users\n\t\tset online_status = greatest(online_status - 1, 0),\n\t\t\tlast_logout = CURRENT_TIMESTAMP\n\t\twhere user_id = _user_id;\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- Disable user account\ncreate procedure TigDisableAccount(_user_id varchar(2049) CHARSET utf8)\nbegin\n\tupdate tig_users set account_status = 0 where sha1_user_id = sha1(lower(_user_id));\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- Enable user account\ncreate procedure TigEnableAccount(_user_id varchar(2049) CHARSET utf8)\nbegin\n\tupdate tig_users set account_status = 1 where sha1_user_id = sha1(lower(_user_id));\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- Get list of all active user accounts\ncreate procedure TigActiveAccounts()\nbegin\n\tselect user_id, last_login, last_logout, online_status, failed_logins, account_status\n\t\tfrom tig_users where account_status > 0;\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- Get list of all disabled user accounts\ncreate procedure TigDisabledAccounts()\nbegin\n\tselect user_id, last_login, last_logout, online_status, failed_logins, account_status\n\t\tfrom tig_users where account_status = 0;\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- Helper procedure for adding a new node\ncreate procedure TigAddNode(_parent_nid bigint, _uid bigint, _node varchar(255) CHARSET utf8)\nbegin\n\tinsert into tig_nodes (parent_nid, uid, node)\n\t\tvalues (_parent_nid, _uid, _node);\n\tselect LAST_INSERT_ID() as nid;\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- Procedure to efficiently and safely update data in tig_pairs table\ncreate procedure TigUpdatePairs(_nid bigint, _uid bigint, _tkey varchar(255) CHARSET utf8, _tval mediumtext CHARSET utf8)\nbegin\n if exists(SELECT 1 FROM tig_pairs WHERE nid = _nid AND uid = _uid AND pkey = _tkey)\n then\n UPDATE tig_pairs SET pval = _tval WHERE nid = _nid AND uid = _uid AND pkey = _tkey;\n ELSE\n INSERT INTO tig_pairs (nid, uid, pkey, pval) VALUES (_nid, _uid, _tkey, _tval);\n END IF;\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- For testing only:\ncreate procedure TigTestAddUser(_user_id varchar(2049) CHARSET utf8, _user_passwd varchar(255) CHARSET utf8,\n\t\t\t success_text text CHARSET utf8, failure_text text CHARSET utf8)\nbegin\n\tdeclare insert_status int default 0;\n\tDECLARE CONTINUE HANDLER FOR 1062 SET insert_status=1;\n\tcall TigAddUserPLainPw(_user_id, _user_passwd);\n\tif insert_status = 0 then\n\t\t select success_text;\n \telse\n\t\t select failure_text;\n\tend if;\nend //\n-- QUERY END:\n\n-- QUERY START:\ncreate procedure TigUsers2Ver4Convert()\nbegin\n\n\tdeclare _user_id varchar(2049) CHARSET utf8;\n\tdeclare _password varchar(255) CHARSET utf8;\n\tdeclare _parent_nid bigint;\n\tdeclare _uid bigint;\n\tdeclare _node varchar(255) CHARSET utf8;\n\tdeclare l_last_row_fetched int default 0;\n\n\tDECLARE cursor_users CURSOR FOR\n\t\tselect user_id, pval as password\n\t\t\tfrom tig_users, tig_pairs\n\t\t\twhere tig_users.uid = tig_pairs.uid and pkey = 'password';\n\tDECLARE CONTINUE HANDLER FOR NOT FOUND SET l_last_row_fetched=1;\n\n\tSTART TRANSACTION;\n\n\t\tSET l_last_row_fetched=0;\n\n\t\tOPEN cursor_users;\n\t\t\tcursor_loop:LOOP\n\t\t\t\tFETCH cursor_users INTO _user_id, _password;\n \t\tIF l_last_row_fetched=1 THEN\n \t\tLEAVE cursor_loop;\n \t\tEND IF;\n\t\t\t\tcall TigUpdatePasswordPlainPw(_user_id, _password);\n\t\t\tEND LOOP cursor_loop;\n\t\tCLOSE cursor_users;\n\n\t\tSET l_last_row_fetched=0;\n\n\tCOMMIT;\n\nend //\n-- QUERY END:\n\ndelimiter ;\n\n"
},
{
"path": "tigase-server 7.1.0/database/mysql-schema-4-test.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\nselect 'Initializing database..';\ncall TigInitdb();\n\n-- Possible encodings are:\n-- - 'MD5-USERID-PASSWORD'\n-- - 'MD5-PASSWORD'\n-- - 'PLAIN'\n-- More can be added if needed.\ncall TigPutDBProperty('password-encoding', 'PLAIN');\ncall TigPutDBProperty('schema-version', '4.0');\n\nselect 'Adding new user with PlainPw: ', 'test_user', 'test_password';\ncall TigTestAddUser('test_user', 'test_passwd', 'SUCCESS - adding new user',\n\t\t 'ERROR - adding new user');\n\ncall TigUserLogin('test_user', 'wrong_passwd', @res_user_id);\nselect @res_user_id as user_id\\g\nselect if(@res_user_id is NULL,\n 'SUCCESS - User login failed as expected, used UserLogin',\n\t\t\t \t 'ERROR - User login succeeded as NOT expected');\n\ncall TigUserLoginPlainPw('test_user', 'wrong_passwd', @res_user_id);\nselect if(@res_user_id is NULL,\n\t\t\t 'SUCCESS - User login failed as expected, used wrong password',\n\t\t\t \t 'ERROR - User login succeeded as NOT expected');\n\ncall TigUserLoginPlainPw('test_user', 'test_passwd', @res_user_id);\nselect if(@res_user_id is not NULL,\n\t\t\t 'SUCCESS - User login OK as expected, used UserLoginPlainPw',\n\t\t\t \t 'ERROR - User login failed as NOT expected');\n\ncall TigUserLogout('test_user');\ncall TigUserLogout('test_user');\nselect online_status into @res_online_status from tig_users\n where user_id = 'test_user';\nselect if(@res_online_status = 0,\n\t\t\t 'SUCCESS - online status OK after 2 logouts',\n\t\t\t \t 'ERROR - online status incorrect after 2 logouts');\n\nselect 'Changing password using UpdatePassword';\ncall TigUpdatePassword('test_user', 'new_password');\ncall TigUserLoginPlainPw('test_user', 'new_password', @res_user_id);\nselect if(@res_user_id is NULL,\n\t\t\t 'SUCCESS - User login failed as expected, password incorrectly changed',\n\t\t\t \t 'ERROR - User login succeeded as NOT expected');\n\nselect 'Changing password using UpdatePasswordPlainPw';\ncall TigUpdatePasswordPlainPw('test_user', 'new_password');\ncall TigUserLoginPlainPw('test_user', 'new_password', @res_user_id);\nselect if(@res_user_id is not NULL,\n\t\t\t 'SUCCESS - User login OK as expected, password updated with PlainPw',\n\t\t\t \t 'ERROR - User login failed as NOT expected');\n\ncall TigUserLogout('test_user');\nselect 'Disabling user account';\ncall TigDisableAccount('test_user');\ncall TigUserLoginPlainPw('test_user', 'new_password', @res_user_id);\nselect if(@res_user_id is NULL,\n\t\t\t 'SUCCESS - User login failed as expected, account disabled',\n\t\t\t \t 'ERROR - User login succeeded as NOT expected');\n\nselect 'Enabling user account';\ncall TigEnableAccount('test_user');\ncall TigUserLoginPlainPw('test_user', 'new_password', @res_user_id);\nselect if(@res_user_id is not NULL,\n\t\t\t 'SUCCESS - User login OK as expected, account enabled',\n\t\t\t \t 'ERROR - User login failed as NOT expected');\n\ncall TigUserLogout('test_user');\n\nselect 'Adding new user with PlainPw: ', 'test_user_2', 'test_password_2';\ncall TigTestAddUser('test_user_2', 'test_passwd_2', 'SUCCESS - adding new user',\n\t\t 'ERROR - adding new user');\n\nselect 'Adding a user with the same user_id: ', 'test_user', 'test_password_2';\ncall TigTestAddUser('test_user', 'test_password_2', 'ERROR, that was duplicate entry insertion and it should fail.', 'SUCCESS - user adding failure as expected as that was duplicate entry insertion attempt');\n\ncall TigRemoveUser('test_user');\ncall TigRemoveUser('test_user_2');\ncall TigOnlineUsers();\ncall TigOfflineUsers();\n\n"
},
{
"path": "tigase-server 7.1.0/database/mysql-schema-4.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\nsource database/mysql-schema-4-schema.sql;\n\nsource database/mysql-schema-4-sp.sql;\n\nsource database/mysql-schema-4-props.sql;\n\n-- LOAD FILE: database/mysql-schema-4-schema.sql\n\n-- LOAD FILE: database/mysql-schema-4-sp.sql\n\n-- LOAD FILE: database/mysql-schema-4-props.sql\n\n"
},
{
"path": "tigase-server 7.1.0/database/mysql-schema-5-1-props.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- QUERY START:\n-- This is a dummy user who keeps all the database-properties\ncall TigAddUserPlainPw('db-properties', NULL);\n-- QUERY END:\n\nselect NOW(), ' - Setting schema version to 5.1';\n\n-- QUERY START:\ncall TigPutDBProperty('schema-version', '5.1');\n-- QUERY END:\n"
},
{
"path": "tigase-server 7.1.0/database/mysql-schema-5-1-schema.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- Database stored procedures and functions for Tigase schema version 5.1\n\nsource database/mysql-schema-4-schema.sql;\n\n-- LOAD FILE: database/mysql-schema-4-schema.sql\n"
},
{
"path": "tigase-server 7.1.0/database/mysql-schema-5-1-sp.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- Database stored procedures and functions for Tigase schema version 5.1\n\nsource database/mysql-schema-4-sp.sql;\n\n-- LOAD FILE: database/mysql-schema-4-sp.sql\n\n-- QUERY START:\ndrop procedure if exists TigUpdatePairs;\n-- QUERY END:\n \ndelimiter //\n\n-- QUERY START:\n-- Procedure to efficiently and safely update data in tig_pairs table\ncreate procedure TigUpdatePairs(_nid bigint, _uid bigint, _tkey varchar(255) CHARSET utf8, _tval mediumtext CHARSET utf8)\nbegin\n if exists(SELECT 1 FROM tig_pairs WHERE nid = _nid AND uid = _uid AND pkey = _tkey)\n then\n UPDATE tig_pairs SET pval = _tval WHERE nid = _nid AND uid = _uid AND pkey = _tkey;\n ELSE\n INSERT INTO tig_pairs (nid, uid, pkey, pval) VALUES (_nid, _uid, _tkey, _tval);\n END IF;\nend //\n-- QUERY END:\n\n\ndelimiter ;\n"
},
{
"path": "tigase-server 7.1.0/database/mysql-schema-5-1.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\nsource database/mysql-schema-4-schema.sql;\n\nsource database/mysql-schema-5-1-sp.sql;\n\nsource database/mysql-schema-5-1-props.sql;\n\n-- LOAD FILE: database/mysql-schema-4-schema.sql;\n\n-- LOAD FILE: database/mysql-schema-5-1-sp.sql;\n\n-- LOAD FILE: database/mysql-schema-5-1-props.sql;\n "
},
{
"path": "tigase-server 7.1.0/database/mysql-schema-5.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\nsource database/mysql-schema-4-schema.sql;\n\nsource database/mysql-schema-4-sp.sql;\n\nsource database/mysql-schema-4-props.sql;\n\n-- LOAD FILE: database/mysql-schema-4-schema.sql;\n\n-- LOAD FILE: database/mysql-schema-4-sp.sql;\n\n-- LOAD FILE: database/mysql-schema-4-props.sql;\n\n"
},
{
"path": "tigase-server 7.1.0/database/mysql-schema-7-1-props.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2016 \"Tigase, Inc.\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n--\n\n-- QUERY START:\n-- This is a dummy user who keeps all the database-properties\ncall TigAddUserPlainPw('db-properties', NULL);\n-- QUERY END:\n\nselect NOW(), ' - Setting schema version to 7.1';\n\n-- QUERY START:\ncall TigPutDBProperty('schema-version', '7.1');\n-- QUERY END:\n"
},
{
"path": "tigase-server 7.1.0/database/mysql-schema-7-1-schema.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2016 \"Tigase, Inc.\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n--\n\n-- Database stored procedures and functions for Tigase schema version 5.1\n\nsource database/mysql-schema-5-1-schema.sql;\n\n-- LOAD FILE: database/mysql-schema-5-1-schema.sql\n\n\n-- QUERY START:\nALTER TABLE tig_pairs ADD `pid` INT NOT NULL AUTO_INCREMENT PRIMARY KEY\n-- QUERY END:\n"
},
{
"path": "tigase-server 7.1.0/database/mysql-schema-7-1-sp.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2016 \"Tigase, Inc.\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n--\n\n-- Database stored procedures and functions for Tigase schema version 5.1\n\nsource database/mysql-schema-5-1-sp.sql;\n\n-- LOAD FILE: database/mysql-schema-5-1-sp.sql\n\n-- QUERY START:\ndrop procedure if exists TigAddNode;\n-- QUERY END:\n\n-- QUERY START:\ndrop procedure if exists TigPutDBProperty;\n-- QUERY END:\n\n-- QUERY START:\ndrop procedure if exists TigUserLogout;\n-- QUERY END:\n \n \ndelimiter //\n\n-- QUERY START:\n-- Helper procedure for adding a new node\ncreate procedure TigAddNode(_parent_nid bigint, _uid bigint, _node varchar(255) CHARSET utf8)\nbegin\n if exists(SELECT 1 FROM tig_nodes WHERE parent_nid = _parent_nid AND uid = _uid AND node = _node) then\n SELECT nid FROM tig_nodes WHERE parent_nid = _parent_nid AND uid = _uid AND node = _node;\n ELSEIF exists(SELECT 1 FROM tig_nodes WHERE _parent_nid is null AND uid = _uid AND 'root' = _node) then\n SELECT nid FROM tig_nodes WHERE uid = _uid AND node = _node;\n ELSE\n\tinsert into tig_nodes (parent_nid, uid, node) values (_parent_nid, _uid, _node);\n\tselect LAST_INSERT_ID() as nid;\n END IF;\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- Database properties set - procedure\ncreate procedure TigPutDBProperty(_tkey varchar(255) CHARSET utf8, _tval mediumtext CHARSET utf8)\nbegin\n if exists( select 1 from tig_pairs, tig_users where\n (sha1_user_id = sha1(lower('db-properties'))) AND (tig_users.uid = tig_pairs.uid)\n AND (pkey = _tkey))\n then\n update tig_pairs tp, tig_users tu, tig_nodes tn set pval = _tval\n where (tu.sha1_user_id = sha1(lower('db-properties'))) AND (tu.uid = tp.uid)\n AND (tp.pkey = _tkey) AND (tn.node = \"root\");\n else\n insert into tig_pairs (pkey, pval, uid, nid)\n select _tkey, _tval, tu.uid, tn.nid from tig_users tu left join tig_nodes tn on tn.uid=tu.uid\n where (tu.sha1_user_id = sha1(lower('db-properties')) and tn.node=\"root\");\n end if;\nend //\n-- QUERY END:\n\n\n-- QUERY START:\n-- It decreases online_status and sets last_logout time to the current timestamp\ncreate procedure TigUserLogout(_user_id varchar(2049) CHARSET utf8)\nbegin\n\tupdate tig_users\n\t\tset online_status = greatest(online_status - 1, 0),\n\t\t\tlast_logout = CURRENT_TIMESTAMP\n\t\twhere sha1_user_id = sha1(lower(_user_id));\nend //\n-- QUERY END:\n\ndelimiter ;\n\n\n\n"
},
{
"path": "tigase-server 7.1.0/database/mysql-schema-7-1.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2016 \"Tigase, Inc.\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n--\n\nsource database/mysql-schema-7-1-schema.sql;\n\nsource database/mysql-schema-7-1-sp.sql;\n\nsource database/mysql-schema-7-1-props.sql;\n\n-- LOAD FILE: database/mysql-schema-7-1-schema.sql;\n\n-- LOAD FILE: database/mysql-schema-7-1-sp.sql;\n\n-- LOAD FILE: database/mysql-schema-7-1-props.sql;\n "
},
{
"path": "tigase-server 7.1.0/database/mysql-schema-upgrade-to-4.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- Database schema upgrade for Tigase version 4.0.0\n\nselect NOW(), ' - Dropping foreign indexes';\n-- QUERY START:\nalter table tig_nodes DROP FOREIGN KEY tig_nodes_constr;\n-- QUERY END:\n-- QUERY START:\nalter table tig_pairs DROP FOREIGN KEY tig_pairs_constr_1;\n-- QUERY END:\n-- QUERY START:\nalter table tig_pairs DROP FOREIGN KEY tig_pairs_constr_2;\n-- QUERY END:\n\nselect NOW(), ' - Renaming old tig_pairs table for later convertion';\n-- QUERY START:\nalter table tig_pairs rename to tig_pairs_old;\n-- QUERY END:\nselect NOW(), ' - Renaming old tig_nodes table for later convertion';\n-- QUERY START:\nalter table tig_nodes rename to tig_nodes_old;\n-- QUERY END:\n-- QUERY START:\nalter table tig_nodes_old add index parent_nid (parent_nid);\n-- QUERY END:\n-- QUERY START:\nalter table tig_nodes_old add index uid (uid);\n-- QUERY END:\nselect NOW(), ' - Renaming old tig_users table for later convertion';\n-- QUERY START:\nalter table tig_users rename to tig_users_old;\n-- QUERY END:\n\nselect NOW(), ' - Loading new database schema 4.0';\n-- LOAD SCHEMA:\nsource database/mysql-schema-4-schema.sql;\n\nselect NOW(), ' - Setting passwords encoding in the database';\n-- Possible encodings are:\n-- - 'MD5-USERID-PASSWORD'\n-- - 'MD5-PASSWORD'\n-- - 'PLAIN'\n-- More can be added if needed.\n-- QUERY START:\ncall TigPutDBProperty('password-encoding', 'PLAIN');\n-- QUERY END:\n\nselect NOW(), ' - Temporarly adding old_uid column to tig_users table';\n-- QUERY START:\nalter table tig_users add column old_uid bigint;\n-- QUERY END:\n-- QUERY START:\nalter table tig_users add index old_uid (old_uid);\n-- QUERY END:\nselect NOW(), ' - Temporarly adding old_nid column to tig_nodes table';\n-- QUERY START:\nalter table tig_nodes add column old_nid bigint;\n-- QUERY END:\n-- QUERY START:\nalter table tig_nodes add index old_nid (old_nid);\n-- QUERY END:\n\nselect NOW(), ' - Copying tig_users data to a new table';\n-- QUERY START:\ninsert into tig_users (user_id, sha1_user_id, old_uid)\n\tselect user_id, sha1(user_id), uid from tig_users_old;\n-- QUERY END:\n\nselect NOW(), ' - Copying tig_nodes data to a new table';\n-- QUERY START:\ninsert into tig_nodes (uid, old_nid, node)\n\tselect tig_users.uid, nid, node from tig_users, tig_nodes_old\n\t\twhere (tig_nodes_old.uid = tig_users.old_uid);\n-- QUERY END:\n\nselect NOW(), ' - Updating parent_nids in the new tig_nodes table';\n-- QUERY START:\ncreate temporary table temp_nodes\n\tselect tig_nodes.uid as new_uid, tig_nodes.nid as new_nid,\n\t\t\ttig_nodes_old.nid as old_nid, tig_nodes_old.parent_nid as old_parent_nid\n\t\tfrom tig_nodes, tig_nodes_old where tig_nodes.old_nid = tig_nodes_old.nid;\n-- QUERY END:\n-- QUERY START:\n\nalter table temp_nodes add index new_nid (new_nid);\n-- QUERY END:\n-- QUERY START:\nalter table temp_nodes add index old_nid (old_nid);\n-- QUERY END:\n-- QUERY START:\n\nupdate tig_nodes, tig_nodes_old, temp_nodes\n\tset tig_nodes.parent_nid = temp_nodes.new_nid\n\twhere (tig_nodes.old_nid = tig_nodes_old.nid)\n\t\tAND (tig_nodes_old.parent_nid = temp_nodes.old_nid);\n-- QUERY END:\n\nselect NOW(), ' - Loading tig_pairs table from old one with new uids and nids';\n-- QUERY START:\ninsert into tig_pairs (nid, uid, pkey, pval)\n\tselect tig_nodes.nid, tig_users.uid, pkey, pval\n\t\tfrom tig_pairs_old, tig_users, tig_nodes\n\t\twhere (tig_pairs_old.uid = tig_users.old_uid)\n\t\t\tAND (tig_pairs_old.nid = tig_nodes.old_nid);\n-- QUERY END:\n\nselect NOW(), ' - Droping temporarly columns';\n-- QUERY START:\nalter table tig_users drop index old_uid;\n-- QUERY END:\n-- QUERY START:\nalter table tig_users drop column old_uid;\n-- QUERY END:\n-- QUERY START:\nalter table tig_nodes drop index old_nid;\n-- QUERY END:\n-- QUERY START:\nalter table tig_nodes drop column old_nid;\n-- QUERY END:\n\nselect NOW(), ' - Converting user passwords to a new format';\n-- QUERY START:\ncall TigUsers2Ver4Convert();\n-- QUERY END:\n\nselect NOW(), ' - All done, database ready to use!';\n"
},
{
"path": "tigase-server 7.1.0/database/mysql-schema-upgrade-to-5-1.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\nselect NOW(), ' - Installing missing stored procedures';\n\n-- QUERY START:\ndrop procedure if exists TigUpdatePairs;\n-- QUERY END:\n \ndelimiter //\n\n-- QUERY START:\n-- Procedure to efficiently and safely update data in tig_pairs table\ncreate procedure TigUpdatePairs(_nid bigint, _uid bigint, _tkey varchar(255) CHARSET utf8, _tval mediumtext CHARSET utf8)\nbegin\n if exists(SELECT 1 FROM tig_pairs WHERE nid = _nid AND uid = _uid AND pkey = _tkey)\n then\n UPDATE tig_pairs SET pval = _tval WHERE nid = _nid AND uid = _uid AND pkey = _tkey;\n ELSE\n INSERT INTO tig_pairs (nid, uid, pkey, pval) VALUES (_nid, _uid, _tkey, _tval);\n END IF;\nend //\n-- QUERY END:\n\ndelimiter ;\n\n\n-- QUERY START:\ncall TigPutDBProperty('schema-version', '5.1');\n-- QUERY END:\n\nselect NOW(), ' - All done, database ver 5.1 ready to use!';"
},
{
"path": "tigase-server 7.1.0/database/mysql-schema-upgrade-to-7-1.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2016 \"Tigase, Inc.\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n\nselect NOW(), ' - Upgrading schema to version 7.1';\n\nselect NOW(), 'modifying stored procedures';\n\n-- QUERY START:\ndrop procedure if exists TigUserLogout;\n-- QUERY END:\n\n-- QUERY START:\ndrop procedure if exists TigAddNode;\n-- QUERY END:\n\n-- QUERY START:\ndrop procedure if exists TigPutDBProperty;\n-- QUERY END:\n \ndelimiter //\n\n-- QUERY START:\n-- It decreases online_status and sets last_logout time to the current timestamp\ncreate procedure TigUserLogout(_user_id varchar(2049) CHARSET utf8)\nbegin\n\tupdate tig_users\n\t\tset online_status = greatest(online_status - 1, 0),\n\t\t\tlast_logout = CURRENT_TIMESTAMP\n\t\twhere sha1_user_id = sha1(lower(_user_id));\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- Helper procedure for adding a new node\ncreate procedure TigAddNode(_parent_nid bigint, _uid bigint, _node varchar(255) CHARSET utf8)\nbegin\n if exists(SELECT 1 FROM tig_nodes WHERE parent_nid = _parent_nid AND uid = _uid AND node = _node) then\n SELECT nid FROM tig_nodes WHERE parent_nid = _parent_nid AND uid = _uid AND node = _node;\n ELSEIF exists(SELECT 1 FROM tig_nodes WHERE _parent_nid is null AND uid = _uid AND 'root' = _node) then\n SELECT nid FROM tig_nodes WHERE uid = _uid AND node = _node;\n ELSE\n\tinsert into tig_nodes (parent_nid, uid, node) values (_parent_nid, _uid, _node);\n\tselect LAST_INSERT_ID() as nid;\n END IF;\nend //\n-- QUERY END:\n\n-- QUERY START:\n-- Database properties set - procedure\ncreate procedure TigPutDBProperty(_tkey varchar(255) CHARSET utf8, _tval mediumtext CHARSET utf8)\nbegin\n if exists( select 1 from tig_pairs, tig_users where\n (sha1_user_id = sha1(lower('db-properties'))) AND (tig_users.uid = tig_pairs.uid)\n AND (pkey = _tkey))\n then\n update tig_pairs tp, tig_users tu, tig_nodes tn set pval = _tval\n where (tu.sha1_user_id = sha1(lower('db-properties'))) AND (tu.uid = tp.uid)\n AND (tp.pkey = _tkey) AND (tn.node = \"root\");\n else\n insert into tig_pairs (pkey, pval, uid, nid)\n select _tkey, _tval, tu.uid, tn.nid from tig_users tu left join tig_nodes tn on tn.uid=tu.uid\n where (tu.sha1_user_id = sha1(lower('db-properties')) and tn.node=\"root\");\n end if;\nend //\n-- QUERY END:\n\ndelimiter ;\n\n-- QUERY START:\nselect NOW(), 'adding root node for db-properties';\n-- QUERY END:\n\n-- QUERY START:\ncall TigAddNode(null,(select uid from tig_users where user_id=\"db-properties\"),\"root\");\n-- QUERY END:\n\n-- QUERY START:\nupdate tig_pairs set nid = (select nid from tig_nodes where uid=(select uid from tig_users where user_id=\"db-properties\") and node=\"root\") where uid=(select uid from tig_users where user_id=\"db-properties\");\n-- QUERY END:\n\n-- QUERY START:\nselect NOW(), 'altering tig_pairs table to add missing indexes';\n-- QUERY END:\n\n-- QUERY START:\nALTER TABLE tig_pairs ADD `pid` INT NOT NULL AUTO_INCREMENT PRIMARY KEY\n-- QUERY END:\n\n\n-- QUERY START:\ncall TigPutDBProperty('schema-version', '7.1');\n-- QUERY END:\n\n-- QUERY START:\nselect NOW(), ' - All done, database ver 7.1 ready to use!';\n-- QUERY END:\n\n\n\n"
},
{
"path": "tigase-server 7.1.0/database/postgresql-installer-create-db.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- QUERY START: create database\ncreate database ${dbName};\n-- QUERY END: create database\n\n-- QUERY START: add user\ncreate user ${dbUser} with password '${dbPass}';\n-- QUERY END: add user\n\n-- QUERY START: GRANT ALL\nGRANT ALL ON database ${dbName} TO ${dbUser};\n-- QUERY END: GRANT ALL\n\n-- QUERY START: ALTER DATABASE\nALTER DATABASE ${dbName} OWNER TO ${dbUser};\n-- QUERY END: ALTER DATABASE\n\n\n\n"
},
{
"path": "tigase-server 7.1.0/database/postgresql-installer-post.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- Permissions fix\n\n-- QUERY START: ALTER SCHEMA\nALTER SCHEMA public OWNER TO ${dbUser};\n-- QUERY END: ALTER SCHEMA\n\n-- QUERY START: GRANT ALL ON ALL TABLES\nGRANT ALL ON ALL TABLES IN SCHEMA public TO ${dbUser};\n-- QUERY END: GRANT ALL ON ALL TABLES\n\n-- QUERY START: GRANT ALL ON ALL FUNCTIONS\nGRANT ALL ON ALL FUNCTIONS IN SCHEMA public TO ${dbUser};\n-- QUERY END: GRANT ALL ON ALL FUNCTIONS\n\n-- QUERY START: GRANT ALL ON ALL SEQUENCES\nGRANT ALL ON ALL SEQUENCES IN SCHEMA public TO ${dbUser};\n-- QUERY END: GRANT ALL ON ALL SEQUENCES\n\n\n"
},
{
"path": "tigase-server 7.1.0/database/postgresql-schema-3.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- To load schema to PostgreSQL database execute following commands:\n--\n-- createuser tigase\n-- createdb -U tigase tigase\n-- psql -q -U tigase -d tigase -f postgresql-schema.sql\n\n\ncreate table short_news (\n -- Automatic record ID\n snid serial,\n -- Automaticly generated timestamp and automaticly updated on change\n publishing_time timestamp default now(),\n\t-- Optional news type: 'shorts', 'minis', 'techs', 'funs'....\n\tnews_type\t\t\t\tvarchar(10),\n -- Author JID\n author varchar(128) NOT NULL,\n -- Short subject - this is short news, right?\n subject varchar(128) NOT NULL,\n -- Short news message - this is short news, right?\n body varchar(1024) NOT NULL,\n primary key(snid)\n);\ncreate index publishing_time on short_news (publishing_time);\ncreate index author on short_news (author);\ncreate index news_type on short_news (news_type);\n\ncreate table xmpp_stanza (\n\t\t\t id serial,\n\t\t\t stanza text NOT NULL\n);\n\ncreate table tig_users (\n uid bigint NOT NULL,\n\n user_id varchar(128) NOT NULL,\n\n primary key (uid)\n);\ncreate unique index user_id on tig_users ( user_id );\n\ncreate table tig_nodes (\n nid bigint NOT NULL,\n parent_nid bigint,\n uid bigint NOT NULL references tig_users(uid),\n\n node varchar(64) NOT NULL,\n\n primary key (nid)\n);\ncreate unique index tnode on tig_nodes ( parent_nid, uid, node );\ncreate index node on tig_nodes ( node );\n\ncreate table tig_pairs (\n nid bigint references tig_nodes(nid),\n uid bigint NOT NULL references tig_users(uid),\n\n pkey varchar(128) NOT NULL,\n pval varchar(65535)\n);\ncreate index pkey on tig_pairs ( pkey );\n\ncreate table tig_max_ids (\n max_uid bigint,\n max_nid bigint\n);\n\n\ninsert into tig_max_ids (max_uid, max_nid) values (1, 1);\n\n-- Get top nodes for the user: user1@hostname\n--\n-- select nid, node from nodes, users\n-- where ('user1@hostname' = user_id)\n-- AND (nodes.uid = users.uid)\n-- AND (parent_nid is null);\n\n-- Get all subnodes of the node: /privacy/default for user: user1@hostname\n--\n-- select nid, node from nodes,\n-- (\n-- select nid as dnid from nodes,\n-- (\n-- select nid as pnid from nodes, users\n-- where ('user1@hostname' = user_id)\n-- AND (nodes.uid = users.uid)\n-- AND (parent_nid is null)\n-- AND (node = 'privacy')\n-- ) ptab where (parent_nid = pnid)\n-- AND (node = 'default')\n-- ) dtab where (parent_nid = dnid);\n\n-- Get all keys (pairs) for the node: /privacy/default/24 for user: user1@hostname\n--\n-- select pkey, pval from pairs,\n-- (\n-- select nid, node from nodes,\n-- (\n-- select nid as dnid from nodes,\n-- (\n-- select nid as pnid from nodes, users\n-- where ('user1@hostname' = user_id)\n-- AND (nodes.uid = users.uid)\n-- \t AND (parent_nid is null)\n-- \t AND (node = 'privacy')\n-- ) ptab where (parent_nid = pnid)\n-- AND (node = 'default')\n-- ) dtab where (parent_nid = dnid)\n-- ) ntab where (pairs.nid = ntab.nid) AND (node = '24');\n"
},
{
"path": "tigase-server 7.1.0/database/postgresql-schema-4-props.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- QUERY START:\n-- This is a dummy user who keeps all the database-properties\nselect TigAddUserPlainPw('db-properties', NULL);\n-- QUERY END:\n\nselect now(), ' - Setting schema version to 4.0';\n\n-- QUERY START:\nselect TigPutDBProperty('schema-version', '4.0');\n-- QUERY END:\n\n"
},
{
"path": "tigase-server 7.1.0/database/postgresql-schema-4-schema.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- QUERY START:\ncreate table tig_users (\n\tuid bigserial,\n\n\t-- Jabber User ID\n\tuser_id varchar(2049) NOT NULL,\n\t-- User password encrypted or not\n\tuser_pw varchar(255) default NULL,\n\t-- Time the account has been created\n\tacc_create_time TIMESTAMP DEFAULT CURRENT_TIMESTAMP,\n\t-- Time of the last user login\n\tlast_login timestamp,\n\t-- Time of the last user logout\n\tlast_logout timestamp,\n\t-- User online status, if > 0 then user is online, the value\n\t-- indicates the number of user connections.\n\t-- It is incremented on each user login and decremented on each\n\t-- user logout.\n\tonline_status int default 0,\n\t-- Number of failed login attempts\n\tfailed_logins int default 0,\n\t-- User status, whether the account is active or disabled\n\t-- >0 - account active, 0 - account disabled\n\taccount_status int default 1,\n\n\tprimary key (uid)\n);\n-- QUERY END:\n-- QUERY START:\ncreate unique index user_id on tig_users ( lower(user_id) );\n-- QUERY END:\n-- QUERY START:\ncreate index user_pw on tig_users (user_pw);\n-- QUERY END:\n-- QUERY START:\ncreate index last_login on tig_users (last_login);\n-- QUERY END:\n-- QUERY START:\ncreate index last_logout on tig_users (last_logout);\n-- QUERY END:\n-- QUERY START:\ncreate index account_status on tig_users (account_status);\n-- QUERY END:\n-- QUERY START:\ncreate index online_status on tig_users (online_status);\n-- QUERY END:\n\n-- QUERY START:\ncreate table tig_nodes (\n nid bigserial,\n parent_nid bigint,\n uid bigint NOT NULL references tig_users(uid),\n\n node varchar(255) NOT NULL,\n\n primary key (nid)\n);\n-- QUERY END:\n-- QUERY START:\ncreate unique index tnode on tig_nodes ( parent_nid, uid, node );\n-- QUERY END:\n-- QUERY START:\ncreate index node on tig_nodes ( node );\n-- QUERY END:\n-- QUERY START:\ncreate index nuid on tig_nodes (uid);\n-- QUERY END:\n-- QUERY START:\ncreate index parent_nid on tig_nodes (parent_nid);\n-- QUERY END:\n\n-- QUERY START:\ncreate table tig_pairs (\n nid bigint references tig_nodes(nid),\n uid bigint NOT NULL references tig_users(uid),\n\n pkey varchar(255) NOT NULL,\n pval text\n);\n-- QUERY END:\n-- QUERY START:\ncreate index pkey on tig_pairs ( pkey );\n-- QUERY END:\n-- QUERY START:\ncreate index puid on tig_pairs (uid);\n-- QUERY END:\n-- QUERY START:\ncreate index pnid on tig_pairs (nid);\n-- QUERY END:\n\n-- QUERY START:\ncreate table short_news (\n -- Automatic record ID\n snid bigserial,\n -- Automaticly generated timestamp and automaticly updated on change\n publishing_time timestamp default now(),\n\t-- Optional news type: 'shorts', 'minis', 'techs', 'funs'....\n\tnews_type\t\t\t\tvarchar(10),\n -- Author JID\n author varchar(128) NOT NULL,\n -- Short subject - this is short news, right?\n subject varchar(128) NOT NULL,\n -- Short news message - this is short news, right?\n body varchar(1024) NOT NULL,\n primary key(snid)\n);\n-- QUERY END:\n-- QUERY START:\ncreate index publishing_time on short_news (publishing_time);\n-- QUERY END:\n-- QUERY START:\ncreate index author on short_news (author);\n-- QUERY END:\n-- QUERY START:\ncreate index news_type on short_news (news_type);\n-- QUERY END:\n\n-- QUERY START:\ncreate table xmpp_stanza (\n\t\t\t id bigserial,\n\t\t\t stanza text NOT NULL\n);\n-- QUERY END:\n"
},
{
"path": "tigase-server 7.1.0/database/postgresql-schema-4-sp.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n\n-- Database stored procedures and fucntions for Tigase schema version 4.0.0\n\n-- QUERY START:\nCREATE OR REPLACE FUNCTION public.create_plpgsql_language ()\n RETURNS TEXT\n AS $$\n CREATE LANGUAGE plpgsql;\n SELECT 'language plpgsql created'::TEXT;\n $$\nLANGUAGE 'sql';\n\nSELECT CASE WHEN\n (SELECT true::BOOLEAN\n FROM pg_language\n WHERE lanname='plpgsql')\n THEN\n (SELECT 'language already installed'::TEXT)\n ELSE\n (SELECT public.create_plpgsql_language())\n END;\n\nDROP FUNCTION public.create_plpgsql_language ();\n-- QUERY END:\n\n-- QUERY START:\n-- Database properties get - function\ncreate or replace function TigGetDBProperty(varchar(255)) returns text as '\ndeclare\n _result text;\n _tkey alias for $1;\nbegin\n\n\tselect pval into _result from tig_pairs, tig_users\n\t\twhere (pkey = _tkey) AND (lower(user_id) = lower(''db-properties''))\n\t\t\t\t\tAND (tig_pairs.uid = tig_users.uid);\n\n\treturn _result;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:\n\n-- QUERY START:\n-- Database properties set - procedure\ncreate or replace function TigPutDBProperty(varchar(255), text) returns void as '\ndeclare\n _tkey alias for $1;\n _tval alias for $2;\nbegin\n if exists( select pval from tig_pairs, tig_users where\n\t\t(lower(user_id) = lower(''db-properties'')) AND (tig_users.uid = tig_pairs.uid)\n\t\tAND (pkey = _tkey))\n then\n\t update tig_pairs set pval = _tval from tig_users\n where (lower(tig_users.user_id) = lower(''db-properties''))\n AND (tig_users.uid = tig_pairs.uid)\n AND (pkey = _tkey);\n else\n insert into tig_pairs (pkey, pval, uid)\n\t\t select _tkey, _tval, uid from tig_users\n\t\t\t where (lower(user_id) = lower(''db-properties''));\n end if;\n return;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:\n\n-- QUERY START:\n-- The initialization of the database.\n-- The procedure should be called manually somehow before starting the\n-- server. In theory the server could call the procedure automatically\n-- at the startup time but I don't know yet how to solve the problem\n-- with multiple cluster nodes starting at later time when the server\n-- is already running.\ncreate or replace function TigInitdb() returns void as '\nbegin\n\tupdate tig_users set online_status = 0;\n return;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:\n\n-- QUERY START:\n-- Add a new user to the database assuming the user password is already\n-- encoded properly according to the database settings.\n-- If password is not encoded TigAddUserPlainPw should be used instead.\ncreate or replace function TigAddUser(varchar(2049), varchar(255))\n returns bigint as '\ndeclare\n _user_id alias for $1;\n _user_pw alias for $2;\n _res_uid bigint;\nbegin\n\tif exists( select uid from tig_users where\n\t\t(lower(user_id) = lower(_user_id)) AND (user_pw = _user_pw) )\n\tthen\n\t\treturn null;\n\telse\n\t\tinsert into tig_users (user_id, user_pw)\n\t\t\tvalues (_user_id, _user_pw);\n\t\tselect currval(''tig_users_uid_seq'') into _res_uid;\n\n\t\tinsert into tig_nodes (parent_nid, uid, node)\n\t\tvalues (NULL, _res_uid, ''root'');\n\n\t\treturn _res_uid as uid;\n\tend if;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:\n\n-- QUERY START:\n-- Takes plain text user password and converts it to internal representation\n-- and creates a new user account.\ncreate or replace function TigAddUserPlainPw(varchar(2049), varchar(255))\n returns bigint as '\ndeclare\n _user_id alias for $1;\n _user_pw alias for $2;\n _enc text;\n _res_uid bigint;\nbegin\n\tselect TigGetDBProperty(''password-encoding'') into _enc;\n select\n case _enc\n \t\twhen ''MD5-PASSWORD'' then TigAddUser(_user_id, MD5(_user_pw))\n\t when ''MD5-USERID-PASSWORD'' then TigAddUser(_user_id, MD5(_user_id || _user_pw))\n\t when ''MD5-USERNAME-PASSWORD'' then\n TigAddUser(_user_id, MD5(split_part(_user_id, ''@'', 1) || _user_pw))\n\t else TigAddUser(_user_id, _user_pw)\n\t end into _res_uid;\n\treturn _res_uid as uid;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:\n\n-- QUERY START:\n-- Low level database user id as big number. Used only for performance reasons\n-- and save database space. Besides JID is too large to server as UID\ncreate or replace function TigGetUserDBUid(varchar(2049)) returns bigint as '\ndeclare\n _user_id alias for $1;\n res_uid bigint;\nbegin\n\tselect uid into res_uid from tig_users where lower(user_id) = lower(_user_id);\n return res_uid;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:\n\n-- QUERY START:\n-- Removes a user from the database\ncreate or replace function TigRemoveUser(varchar(2049)) returns void as '\ndeclare\n _user_id alias for $1;\n res_uid bigint;\nbegin\n\tselect uid into res_uid from tig_users where lower(user_id) = lower(_user_id);\n\n\tdelete from tig_pairs where uid = res_uid;\n\tdelete from tig_nodes where uid = res_uid;\n\tdelete from tig_users where uid = res_uid;\n return;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:\n\n-- QUERY START:\n-- Returns user's password from the database\ncreate or replace function TigGetPassword(varchar(2049)) returns varchar(255) as '\ndeclare\n _user_id alias for $1;\n res_pw varchar(255);\nbegin\n\tselect user_pw into res_pw from tig_users where lower(user_id) = lower(_user_id);\n return res_pw;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:\n\n-- QUERY START:\n-- Takes plain text user password and converts it to internal representation\ncreate or replace function TigUpdatePasswordPlainPw(varchar(2049), varchar(255))\n returns void as '\ndeclare\n _user_id alias for $1;\n _user_pw alias for $2;\n _enc text;\nbegin\n\tselect TigGetDBProperty(''password-encoding'') into _enc;\n perform\n case _enc\n\t\twhen ''MD5-PASSWORD'' then TigUpdatePassword(_user_id, MD5(_user_pw))\n\t\twhen ''MD5-USERID-PASSWORD'' then\n TigUpdatePassword(_user_id, MD5(_user_id || _user_pw))\n\t when ''MD5-USERNAME-PASSWORD'' then\n TigUpdatePassword(_user_id, MD5(split_part(_user_id, ''@'', 1) || _user_pw))\n\t\telse TigUpdatePassword(_user_id, _user_pw)\n\t\tend;\n return;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:\n\n-- QUERY START:\n-- Variant of TigUpdatePasswordPlainPw SP with parameters in reverse order.\n-- Some implementations require the parameters to be in the same order as\n-- the update query.\ncreate or replace function TigUpdatePasswordPlainPwRev(varchar(255), varchar(2049))\n returns void as '\ndeclare\n _user_pw alias for $1;\n _user_id alias for $2;\nbegin\n perform TigUpdatePasswordPlainPw(_user_id, _user_pw);\n return;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:\n\n-- QUERY START:\n-- Update user password\ncreate or replace function TigUpdatePassword(varchar(2049), varchar(255))\n returns void as '\ndeclare\n _user_id alias for $1;\n _user_pw alias for $2;\nbegin\n\tupdate tig_users set user_pw = _user_pw where lower(user_id) = lower(_user_id);\n return;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:\n\n-- QUERY START:\n-- List all online users\ncreate or replace function TigOnlineUsers() returns void as '\nbegin\n return;\n\tselect user_id, last_login, last_logout, online_status, failed_logins, account_status\n\t\tfrom tig_users where online_status > 0;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:\n\n-- QUERY START:\n-- List all offline users\ncreate or replace function TigOfflineUsers() returns void as '\nbegin\n return;\n\tselect user_id, last_login, last_logout, online_status, failed_logins, account_status\n\t\tfrom tig_users where online_status = 0;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:\n\n-- QUERY START:\n-- List of all users in database\ncreate or replace function TigAllUsers() returns setof varchar(2049) as\n\t'select user_id from tig_users;'\nLANGUAGE 'sql';\n-- create or replace function TigAllUsers() returns void as '\n-- begin\n-- return;\n--\tselect user_id, last_login, last_logout, online_status, failed_logins, account_status\n--\t\tfrom tig_users;\n-- end;\n-- ' LANGUAGE 'plpgsql';\n-- QUERY END:\n\n-- QUERY START:\n-- All users count\ncreate or replace function TigAllUsersCount() returns bigint as '\ndeclare\n res_cnt bigint;\nbegin\n\tselect count(*) into res_cnt from tig_users;\n return res_cnt;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:\n\n-- QUERY START:\n-- Performs user login for a plain text password, converting it to an internal\n-- representation if necessary\ncreate or replace function TigUserLoginPlainPw(varchar(2049), varchar(255))\n\t\t\t \t\t\t\t\t returns varchar(2049) as '\ndeclare\n _user_id alias for $1;\n _user_pw alias for $2;\n res_user_id varchar(2049);\n _enc text;\nbegin\n\tselect TigGetDBProperty(''password-encoding'') into _enc;\n select\n case _enc\n\t\twhen ''MD5-PASSWORD'' then TigUserLogin(_user_id, MD5(_user_pw))\n\t\twhen ''MD5-USERID-PASSWORD'' then\n TigUserLogin(_user_id, MD5(_user_id || _user_pw))\n\t when ''MD5-USERNAME-PASSWORD'' then\n TigUserLogin(_user_id, MD5(split_part(_user_id, ''@'', 1) || _user_pw))\n\t\telse TigUserLogin(_user_id, _user_pw)\n\t\tend into res_user_id;\n return res_user_id;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:\n\n-- QUERY START:\n-- Perforrm user login. It returns user_id uppon success and NULL\n-- on failure.\n-- If the login is successful it also increases online_status and sets\n-- last_login time to the current timestamp\ncreate or replace function TigUserLogin(varchar(2049), varchar(255))\n\t\t\t \t\t\t\t\t returns varchar(2049) as '\ndeclare\n _user_id alias for $1;\n _user_pw alias for $2;\n res_user_id varchar(2049);\nbegin\n\tif exists(select user_id from tig_users\n\t\twhere (account_status > 0) AND (lower(user_id) = lower(_user_id)) AND (user_pw = _user_pw))\n\tthen\n\t\tupdate tig_users\n\t\t\tset online_status = online_status + 1, last_login = now()\n\t\t\twhere lower(user_id) = lower(_user_id);\n select _user_id into res_user_id;\n\telse\n\t\tupdate tig_users set failed_logins = failed_logins + 1 where lower(user_id) = lower(_user_id);\n select NULL into res_user_id;\n\tend if;\n return res_user_id;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:\n\n-- QUERY START:\n-- It decreases online_status and sets last_logout time to the current timestamp\ncreate or replace function TigUserLogout(varchar(2049)) returns void as '\ndeclare\n _user_id alias for $1;\nbegin\n\tupdate tig_users\n\t\tset online_status = greatest(online_status - 1, 0),\n\t\t\tlast_logout = now()\n\t\twhere lower(user_id) = lower(_user_id);\n return;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:\n\n-- QUERY START:\n-- Disable user account\ncreate or replace function TigDisableAccount(varchar(2049)) returns void as '\ndeclare\n _user_id alias for $1;\nbegin\n\tupdate tig_users set account_status = 0 where lower(user_id) = lower(_user_id);\n return;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:\n\n-- QUERY START:\n-- Enable user account\ncreate or replace function TigEnableAccount(varchar(2049)) returns void as '\ndeclare\n _user_id alias for $1;\nbegin\n\tupdate tig_users set account_status = 1 where lower(user_id) = lower(_user_id);\n return;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:\n\n-- QUERY START:\n-- Get list of all active user accounts\ncreate or replace function TigActiveAccounts() returns void as '\nbegin\n return;\n\tselect user_id, last_login, last_logout, online_status, failed_logins, account_status\n\t\tfrom tig_users where account_status > 0;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:\n\n-- QUERY START:\n-- Get list of all disabled user accounts\ncreate or replace function TigDisabledAccounts() returns table(user_id varchar(2049), last_login timestamp, last_logout timestamp, online_status int, failed_logins int, account_status int) as '\n\tselect user_id, last_login, last_logout, online_status, failed_logins, account_status\n\t\tfrom tig_users where account_status = 0;\n' LANGUAGE 'sql';\n-- QUERY END:\n\n-- QUERY START:\n-- Helper procedure for adding a new node\ncreate or replace function TigAddNode(bigint, bigint, varchar(255))\n returns bigint as '\ndeclare\n _parent_nid alias for $1;\n _uid alias for $2;\n _node alias for $3;\n res_nid bigint;\nbegin\n\tinsert into tig_nodes (parent_nid, uid, node)\n\t\tvalues (_parent_nid, _uid, _node);\n select currval(''tig_nodes_nid_seq'') into res_nid;\n return res_nid;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:\n\n-- QUERY START:\ncreate or replace function TigUsers2Ver4Convert() returns void as '\ndeclare\n user_row RECORD;\nbegin\n\n for user_row in\n\t\tselect user_id, pval as password\n\t\t\tfrom tig_users, tig_pairs\n\t\t\twhere tig_users.uid = tig_pairs.uid and pkey = ''password'' loop\n\t\tperform TigUpdatePasswordPlainPw(user_row.user_id, user_row.password);\n\tEND LOOP;\n return;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:\n\n-- QUERY START:\ncreate or replace function TigUpdatePairs(bigint, bigint, varchar(255), text) returns void as '\ndeclare\n _nid alias for $1;\n _uid alias for $2;\n _tkey alias for $3;\n _tval alias for $4;\nbegin\n if exists(select 1 from tig_pairs where nid = _nid and uid = _uid and pkey = _tkey)\n then\n update tig_pairs set pval = _tval where nid = _nid and uid = _uid and pkey = _tkey;\n else\n insert into tig_pairs (nid, uid, pkey, pval) values (_nid, _uid, _tkey, _tval);\n end if;\n return;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:\n"
},
{
"path": "tigase-server 7.1.0/database/postgresql-schema-4.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- To load schema to PostgreSQL database execute following commands:\n--\n-- createuser tigase\n-- createdb -U tigase tigase\n-- psql -q -U tigase -d tigase -f postgresql-schema.sql\n\n\\i database/postgresql-schema-4-schema.sql\n\n\\i database/postgresql-schema-4-sp.sql\n\n\\i database/postgresql-schema-4-props.sql\n\n-- LOAD FILE: database/postgresql-schema-4-schema.sql\n\n-- LOAD FILE: database/postgresql-schema-4-sp.sql\n\n-- LOAD FILE: database/postgresql-schema-4-props.sql\n\n"
},
{
"path": "tigase-server 7.1.0/database/postgresql-schema-5-1-props.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n\n-- QUERY START:\n-- This is a dummy user who keeps all the database-properties\nselect TigAddUserPlainPw('db-properties', NULL);\n-- QUERY END:\n\nselect now(), ' - Setting schema version to 5.1';\n\n-- QUERY START:\nselect TigPutDBProperty('schema-version', '5.1');\n-- QUERY END:\n\n"
},
{
"path": "tigase-server 7.1.0/database/postgresql-schema-5-1-schema.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n\n-- Database stored procedures and fucntions for Tigase schema version 5.1\n\n\\i database/postgresql-schema-4-schema.sql\n\n-- LOAD FILE: database/postgresql-schema-4-schema.sql\n"
},
{
"path": "tigase-server 7.1.0/database/postgresql-schema-5-1-sp.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n\n-- Database stored procedures and fucntions for Tigase schema version 5.1\n\n\\i database/postgresql-schema-4-sp.sql\n\n-- LOAD FILE: database/postgresql-schema-4-sp.sql\n\n-- QUERY START:\ncreate or replace function TigUpdatePairs(bigint, bigint, varchar(255), text) returns void as '\ndeclare\n _nid alias for $1;\n _uid alias for $2;\n _tkey alias for $3;\n _tval alias for $4;\nbegin\n if exists(select 1 from tig_pairs where nid = _nid and uid = _uid and pkey = _tkey)\n then\n update tig_pairs set pval = _tval where nid = _nid and uid = _uid and pkey = _tkey;\n else\n insert into tig_pairs (nid, uid, pkey, pval) values (_nid, _uid, _tkey, _tval);\n end if;\n return;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:"
},
{
"path": "tigase-server 7.1.0/database/postgresql-schema-5-1.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- To load schema to PostgreSQL database execute following commands:\n--\n-- createuser tigase\n-- createdb -U tigase tigase\n-- psql -q -U tigase -d tigase -f postgresql-schema.sql\n\n\\i database/postgresql-schema-4-schema.sql\n\n\\i database/postgresql-schema-5-1-sp.sql\n\n\\i database/postgresql-schema-5-1-props.sql\n\n-- LOAD FILE: database/postgresql-schema-4-schema.sql\n\n-- LOAD FILE: database/postgresql-schema-5-1-sp.sql\n\n-- LOAD FILE: database/postgresql-schema-5-1-props.sql\n"
},
{
"path": "tigase-server 7.1.0/database/postgresql-schema-5.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- To load schema to PostgreSQL database execute following commands:\n--\n-- createuser tigase\n-- createdb -U tigase tigase\n-- psql -q -U tigase -d tigase -f postgresql-schema.sql\n\n\\i database/postgresql-schema-4-schema.sql\n\n\\i database/postgresql-schema-4-sp.sql\n\n\\i database/postgresql-schema-4-props.sql\n\n-- LOAD FILE: database/postgresql-schema-4-schema.sql\n\n-- LOAD FILE: database/postgresql-schema-4-sp.sql\n\n-- LOAD FILE: database/postgresql-schema-4-props.sql\n"
},
{
"path": "tigase-server 7.1.0/database/postgresql-schema-7-1-props.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n\n-- QUERY START:\n-- This is a dummy user who keeps all the database-properties\nselect TigAddUserPlainPw('db-properties', NULL);\n-- QUERY END:\n\nselect now(), ' - Setting schema version to 7.1';\n\n-- QUERY START:\nselect TigPutDBProperty('schema-version', '7.1');\n-- QUERY END:\n\n"
},
{
"path": "tigase-server 7.1.0/database/postgresql-schema-7-1-schema.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2016 \"Tigase, Inc.\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n\n-- Database stored procedures and fucntions for Tigase schema version 5.1\n\n\\i database/postgresql-schema-5-1-schema.sql\n\n-- LOAD FILE: database/postgresql-schema-5-1-schema.sql\n\n-- QUERY START:\nALTER TABLE tig_pairs ADD COLUMN pid BIGSERIAL PRIMARY KEY;\n-- QUERY END:\n"
},
{
"path": "tigase-server 7.1.0/database/postgresql-schema-7-1-sp.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2016 \"Tigase, Inc.\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n\n-- Database stored procedures and fucntions for Tigase schema version 5.1\n\n\\i database/postgresql-schema-5-1-sp.sql\n\n-- LOAD FILE: database/postgresql-schema-5-1-sp.sql\n\n\n-- QUERY START:\n-- Database properties set - procedure\ncreate or replace function TigPutDBProperty(varchar(255), text) returns void as '\ndeclare\n _tkey alias for $1;\n _tval alias for $2;\nbegin\n if exists( select pval from tig_pairs, tig_users where\n\t\t(lower(user_id) = lower(''db-properties'')) AND (tig_users.uid = tig_pairs.uid)\n\t\tAND (pkey = _tkey))\n then\n\t update tig_pairs set pval = _tval from tig_users\n where (lower(tig_users.user_id) = lower(''db-properties''))\n AND (tig_users.uid = tig_pairs.uid)\n AND (pkey = _tkey);\n else\n insert into tig_pairs (pkey, pval, uid, nid)\n\t\t select _tkey, _tval, tu.uid, tn.nid from tig_users tu left join tig_nodes tn on tn.uid=tu.uid\n\t\t\t where (lower(user_id) = lower(''db-properties'') and tn.node=''root'' );\n end if;\n return;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:"
},
{
"path": "tigase-server 7.1.0/database/postgresql-schema-7-1.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- To load schema to PostgreSQL database execute following commands:\n--\n-- createuser tigase\n-- createdb -U tigase tigase\n-- psql -q -U tigase -d tigase -f postgresql-schema.sql\n\n\\i database/postgresql-schema-4-schema.sql\n\n\\i database/postgresql-schema-5-1-sp.sql\n\n\\i database/postgresql-schema-5-1-props.sql\n\n-- LOAD FILE: database/postgresql-schema-4-schema.sql\n\n-- LOAD FILE: database/postgresql-schema-5-1-sp.sql\n\n-- LOAD FILE: database/postgresql-schema-5-1-props.sql\n"
},
{
"path": "tigase-server 7.1.0/database/postgresql-schema-upgrade-to-4.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- Database schema upgrade for Tigase version 4.0.0\n\nselect NOW(), ' - Dropping foreign indexes';\nalter table tig_nodes DROP constraint tig_nodes_uid_fkey;\nalter table tig_pairs DROP constraint tig_pairs_uid_fkey;\nalter table tig_pairs DROP constraint tig_pairs_nid_fkey;\nalter table tig_users DROP constraint tig_users_pkey;\nalter table tig_nodes DROP constraint tig_nodes_pkey;\ndrop index user_id;\ndrop index tnode;\ndrop index node;\ndrop index pkey;\n\nselect NOW(), ' - Renaming old tig_pairs table for later convertion';\nalter table tig_pairs rename to tig_pairs_old;\ncreate index pkey_old on tig_pairs_old (pkey);\ncreate index puid_old on tig_pairs_old (uid);\ncreate index pnid_old on tig_pairs_old (nid);\n\nselect NOW(), ' - Renaming old tig_nodes table for later convertion';\nalter table tig_nodes rename to tig_nodes_old;\ncreate index nnid_old on tig_nodes_old (nid);\ncreate index parent_nid_old on tig_nodes_old (parent_nid);\ncreate index nuid_old on tig_nodes_old (uid);\ncreate index node_old on tig_nodes_old (node);\n\nselect NOW(), ' - Renaming old tig_users table for later convertion';\nalter table tig_users rename to tig_users_old;\ncreate index uuid_old on tig_users_old (uid);\ncreate index user_id_old on tig_users_old (user_id);\n\nselect NOW(), ' - Loading new database schema 4.0';\n\\i database/postgresql-schema-4.sql;\n\nselect NOW(), ' - Setting passwords encoding in the database';\n-- Possible encodings are:\n-- - 'MD5-USERID-PASSWORD'\n-- - 'MD5-PASSWORD'\n-- - 'PLAIN'\n-- More can be added if needed.\nselect TigPutDBProperty('password-encoding', 'PLAIN');\n\nselect NOW(), ' - Temporarly adding old_uid column to tig_users table';\nalter table tig_users add column old_uid bigint;\ncreate index old_uid on tig_users (old_uid);\nselect NOW(), ' - Temporarly adding old_nid column to tig_nodes table';\nalter table tig_nodes add column old_nid bigint;\ncreate index old_nid on tig_nodes (old_nid);\n\nselect NOW(), ' - Copying tig_users data to a new table';\ninsert into tig_users (user_id, old_uid)\n\tselect user_id, uid from tig_users_old;\n\nselect NOW(), ' - Copying tig_nodes data to a new table';\ninsert into tig_nodes (uid, old_nid, node)\n\tselect tig_users.uid, nid, node from tig_users, tig_nodes_old\n\t\twhere (tig_nodes_old.uid = tig_users.old_uid);\n\nselect NOW(), ' - Updating parent_nids in the new tig_nodes table';\ncreate temporary table temp_nodes as\n\tselect tig_nodes.uid as new_uid, tig_nodes.nid as new_nid,\n\t\t\ttig_nodes_old.nid as old_nid, tig_nodes_old.parent_nid as old_parent_nid\n\t\tfrom tig_nodes, tig_nodes_old where tig_nodes.old_nid = tig_nodes_old.nid;\n\ncreate index new_nid on temp_nodes (new_nid);\ncreate index old_nid on temp_nodes (old_nid);\n\nupdate tig_nodes\n\tset parent_nid = temp_nodes.new_nid from tig_nodes_old, temp_nodes\n\twhere (tig_nodes.old_nid = tig_nodes_old.nid)\n\t\tAND (tig_nodes_old.parent_nid = temp_nodes.old_nid);\n\nselect NOW(), ' - Loading tig_pairs table from old one with new uids and nids';\ninsert into tig_pairs (nid, uid, pkey, pval)\n\tselect tig_nodes.nid, tig_users.uid, pkey, pval\n\t\tfrom tig_pairs_old, tig_users, tig_nodes\n\t\twhere (tig_pairs_old.uid = tig_users.old_uid)\n\t\t\tAND (tig_pairs_old.nid = tig_nodes.old_nid);\n\nselect NOW(), ' - Droping temporarly columns';\ndrop index old_uid;\nalter table tig_users drop column old_uid;\ndrop index old_nid;\nalter table tig_nodes drop column old_nid;\n\nselect NOW(), ' - Converting user passwords to a new format';\nselect TigUsers2Ver4Convert();\n\nselect NOW(), ' - All done, database ready to use!';\n"
},
{
"path": "tigase-server 7.1.0/database/postgresql-schema-upgrade-to-5-1.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n\n\nselect NOW(), ' - Installing missing stored procedures';\n\n-- QUERY START:\ncreate or replace function TigUpdatePairs(bigint, bigint, varchar(255), text) returns void as '\ndeclare\n _nid alias for $1;\n _uid alias for $2;\n _tkey alias for $3;\n _tval alias for $4;\nbegin\n if exists(select 1 from tig_pairs where nid = _nid and uid = _uid and pkey = _tkey)\n then\n update tig_pairs set pval = _tval where nid = _nid and uid = _uid and pkey = _tkey;\n else\n insert into tig_pairs (nid, uid, pkey, pval) values (_nid, _uid, _tkey, _tval);\n end if;\n return;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:\n\n\n-- QUERY START:\nselect TigPutDBProperty('schema-version', '5.1');\n-- QUERY END:\n\nselect NOW(), ' - All done, database ver 5.1 ready to use!';"
},
{
"path": "tigase-server 7.1.0/database/postgresql-schema-upgrade-to-7-1.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2016 \"Tigase, Inc.\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n\n\nselect NOW(), ' - Updating database version';\n\n\n-- QUERY START:\n-- Database properties set - procedure\ncreate or replace function TigPutDBProperty(varchar(255), text) returns void as '\ndeclare\n _tkey alias for $1;\n _tval alias for $2;\nbegin\n if exists( select pval from tig_pairs, tig_users where\n\t\t(lower(user_id) = lower(''db-properties'')) AND (tig_users.uid = tig_pairs.uid)\n\t\tAND (pkey = _tkey))\n then\n\t update tig_pairs set pval = _tval from tig_users\n where (lower(tig_users.user_id) = lower(''db-properties''))\n AND (tig_users.uid = tig_pairs.uid)\n AND (pkey = _tkey);\n else\n insert into tig_pairs (pkey, pval, uid, nid)\n\t\t select _tkey, _tval, tu.uid, tn.nid from tig_users tu left join tig_nodes tn on tn.uid=tu.uid\n\t\t\t where (lower(user_id) = lower(''db-properties'') and tn.node=''root'' );\n end if;\n return;\nend;\n' LANGUAGE 'plpgsql';\n-- QUERY END:\n\n\n-- QUERY START:\nALTER TABLE tig_pairs ADD COLUMN pid BIGSERIAL PRIMARY KEY;\n-- QUERY END:\n\n-- QUERY START:\nupdate tig_pairs set nid = (select nid from tig_nodes where uid=(select uid from tig_users where user_id='db-properties') and node='root') where uid=(select uid from tig_users where user_id='db-properties');\n-- QUERY END:\n\n-- QUERY START:\nselect TigPutDBProperty('schema-version', '7.1');\n-- QUERY END:\n\nselect NOW(), ' - All done, database ver 7.1 ready to use!';"
},
{
"path": "tigase-server 7.1.0/database/sqlserver-installer-create-db.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- QUERY START: USE database\nUSE [master]\n-- QUERY END: USE database\nGO\n\n-- QUERY START: create database\nCREATE DATABASE ${dbName};\n-- QUERY END: create database\nGO\n\n-- QUERY START: add user\nCREATE LOGIN [${dbUser}] WITH PASSWORD=N'${dbPass}', DEFAULT_DATABASE=[${dbName}]\n-- QUERY END: add user\nGO\n\n-- QUERY START: ALTER DATABASE\nIF NOT EXISTS (SELECT name FROM sys.filegroups WHERE is_default=1 AND name = N'PRIMARY') ALTER DATABASE [${dbName}] MODIFY FILEGROUP [PRIMARY] DEFAULT\n-- QUERY END: ALTER DATABASE\nGO\n\n-- QUERY START: USE DATABASE\nUSE [${dbName}]\n-- QUERY END: USE DATABASE\nGO\n\n-- QUERY START: GRANT ALL\nCREATE USER [${dbUser}] FOR LOGIN [${dbUser}]\n-- QUERY END: GRANT ALL\nGO\n\n-- QUERY START: ALTER DATABASE\nALTER USER [${dbUser}] WITH DEFAULT_SCHEMA=[dbo]\n-- QUERY END: ALTER DATABASE\nGO\n\n-- QUERY START: ALTER DATABASE\nALTER ROLE [db_owner] ADD MEMBER [${dbUser}]\n-- QUERY END: ALTER DATABASE\nGO\n"
},
{
"path": "tigase-server 7.1.0/database/sqlserver-installer-post.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- QUERY START: USE DATABASE\nUSE [${dbName}]\n-- QUERY END: USE DATABASE\nGO\n\n-- QUERY START: ALTER DATABASE\nALTER ROLE [db_owner] ADD MEMBER [${dbUser}]\n-- QUERY END: ALTER DATABASE\nGO\n"
},
{
"path": "tigase-server 7.1.0/database/sqlserver-schema-4.sql",
"content": "SET ANSI_NULLS ON\nGO\nSET QUOTED_IDENTIFIER ON\nGO\nCREATE TABLE [dbo].[tig_max_ids](\n\t[max_uid] [bigint] NULL,\n\t[max_nid] [bigint] NULL\n) ON [PRIMARY]\n\nGO\nSET ANSI_NULLS ON\nGO\nSET QUOTED_IDENTIFIER ON\nGO\nCREATE TABLE [dbo].[tig_users](\n\t[uid] [bigint] NOT NULL,\n\t[user_id] [varchar](256) NOT NULL\n) ON [PRIMARY]\n\nGO\n\nCREATE UNIQUE NONCLUSTERED INDEX [IX_tig_users] ON [dbo].[tig_users] \n(\n\t[user_id] ASC\n) ON [PRIMARY]\nGO\n\nCREATE UNIQUE NONCLUSTERED INDEX [IX_tig_users_1] ON [dbo].[tig_users] \n(\n\t[uid] ASC\n) ON [PRIMARY]\nGO\nSET ANSI_NULLS ON\nGO\nSET QUOTED_IDENTIFIER ON\nGO\nCREATE TABLE [dbo].[short_news](\n\t[snid] [bigint] IDENTITY(1,1) NOT NULL,\n\t[publishing_time] [datetime] NOT NULL CONSTRAINT [DF_short_news_publishing_time] DEFAULT (getdate()),\n\t[news_type] [varchar](50) NULL,\n\t[author] [varchar](128) NOT NULL,\n\t[subject] [varchar](128) NOT NULL,\n\t[body] [varchar](1024) NOT NULL,\n CONSTRAINT [PK_short_news] PRIMARY KEY CLUSTERED \n(\n\t[snid] ASC\n) ON [PRIMARY]\n) ON [PRIMARY]\n\nGO\n\nCREATE NONCLUSTERED INDEX [IX_short_news] ON [dbo].[short_news] \n(\n\t[publishing_time] ASC\n) ON [PRIMARY]\nGO\n\nCREATE NONCLUSTERED INDEX [IX_short_news_1] ON [dbo].[short_news] \n(\n\t[author] ASC\n) ON [PRIMARY]\nGO\n\nCREATE NONCLUSTERED INDEX [IX_short_news_2] ON [dbo].[short_news] \n(\n\t[news_type] ASC\n) ON [PRIMARY]\nGO\nSET ANSI_NULLS ON\nGO\nSET QUOTED_IDENTIFIER ON\nGO\nCREATE TABLE [dbo].[xmpp_stanza](\n\t[id] [bigint] IDENTITY(1,1) NOT NULL,\n\t[stanza] [text] NOT NULL\n) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]\n\nGO\nSET ANSI_NULLS ON\nGO\nSET QUOTED_IDENTIFIER ON\nGO\nCREATE TABLE [dbo].[tig_nodes](\n\t[nid] [bigint] NOT NULL,\n\t[parent_nid] [bigint] NULL,\n\t[uid] [bigint] NOT NULL,\n\t[node] [varchar](128) NOT NULL\n) ON [PRIMARY]\n\nGO\n\nCREATE UNIQUE NONCLUSTERED INDEX [IX_tig_nodes] ON [dbo].[tig_nodes] \n(\n\t[parent_nid] ASC,\n\t[node] ASC,\n\t[uid] ASC\n) ON [PRIMARY]\nGO\n\nCREATE NONCLUSTERED INDEX [IX_tig_nodes_1] ON [dbo].[tig_nodes] \n(\n\t[node] ASC\n) ON [PRIMARY]\nGO\n\nCREATE UNIQUE NONCLUSTERED INDEX [IX_tig_nodes_2] ON [dbo].[tig_nodes] \n(\n\t[nid] ASC\n) ON [PRIMARY]\nGO\nSET ANSI_NULLS ON\nGO\nSET QUOTED_IDENTIFIER ON\nGO\nCREATE TABLE [dbo].[tig_pairs](\n\t[nid] [bigint] NOT NULL,\n\t[uid] [bigint] NOT NULL,\n\t[pkey] [varchar](128) NOT NULL,\n\t[pval] [text] NULL\n) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]\n\nGO\n\nCREATE NONCLUSTERED INDEX [IX_tig_pairs] ON [dbo].[tig_pairs] \n(\n\t[pkey] ASC\n) ON [PRIMARY]\nGO\nALTER TABLE [dbo].[tig_nodes] WITH CHECK ADD CONSTRAINT [FK_tig_nodes_tig_users] FOREIGN KEY([uid])\nREFERENCES [dbo].[tig_users] ([uid])\nGO\nALTER TABLE [dbo].[tig_nodes] CHECK CONSTRAINT [FK_tig_nodes_tig_users]\nGO\nALTER TABLE [dbo].[tig_pairs] WITH CHECK ADD CONSTRAINT [FK_tig_pairs_tig_nodes] FOREIGN KEY([nid])\nREFERENCES [dbo].[tig_nodes] ([nid])\nGO\nALTER TABLE [dbo].[tig_pairs] CHECK CONSTRAINT [FK_tig_pairs_tig_nodes]\nGO\nALTER TABLE [dbo].[tig_pairs] WITH CHECK ADD CONSTRAINT [FK_tig_pairs_tig_users] FOREIGN KEY([uid])\nREFERENCES [dbo].[tig_users] ([uid])\nGO\nALTER TABLE [dbo].[tig_pairs] CHECK CONSTRAINT [FK_tig_pairs_tig_users]\n"
},
{
"path": "tigase-server 7.1.0/database/sqlserver-schema-5-1-props.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- QUERY START:\nSET QUOTED_IDENTIFIER ON\n-- QUERY END:\nGO\n\n-- QUERY START:\n-- This is a dummy user who keeps all the database-properties\nexec dbo.TigAddUserPlainPw 'db-properties', NULL;\n-- QUERY END:\nGO\n\nselect GETDATE(), ' - Setting schema version to 5.1';\n\n-- QUERY START:\nexec dbo.TigPutDBProperty 'schema-version', '5.1';\n-- QUERY END:\nGO"
},
{
"path": "tigase-server 7.1.0/database/sqlserver-schema-5-1-schema.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n\n-- To load schema to execute following commands:\n--\n\n-- QUERY START:\nSET QUOTED_IDENTIFIER ON\n-- QUERY END:\nGO\n\n-- QUERY START:\nCREATE TABLE [dbo].[tig_users](\n\t[uid] [bigint] IDENTITY(1,1) NOT NULL,\n\n\t-- Jabber User ID\n\t[user_id] [nvarchar](2049) NOT NULL,\n\t\n\t-- UserID SHA1 hash to prevent duplicate user_ids\n\t[sha1_user_id] [varbinary](32) NOT NULL,\n\t-- User password encrypted or not\n\t[user_pw] [nvarchar](255) NULL,\n\t-- Time the account has been created\n\t[acc_create_time] [datetime] DEFAULT getdate(),\n\t-- Time of the last user login\n\t[last_login] [datetime] default 0,\n\t-- Time of the last user logout\n\t[last_logout] [datetime] default 0,\n\t-- User online status, if > 0 then user is online, the value\n\t-- indicates the number of user connections.\n\t-- It is incremented on each user login and decremented on each\n\t-- user logout.\n\t[online_status] [int] default 0,\n\t-- Number of failed login attempts\n\t[failed_logins] [int] default 0,\n\t-- User status, whether the account is active or disabled\n\t-- >0 - account active, 0 - account disabled\n\t[account_status] [int] default 1,\n\t-- helper column for indexing due to limitation of SQL server \n\tuser_id_fragment AS LEFT (user_id, 256), \n\n\tCONSTRAINT [PK_tig_users] PRIMARY KEY CLUSTERED ( [uid] ASC ) ON [PRIMARY],\n\tCONSTRAINT [IX_tig_users_sha1_user_id] UNIQUE NONCLUSTERED ( [sha1_user_id] ASC ) ON [PRIMARY]\n) ON [PRIMARY]\n-- QUERY END:\n\n-- QUERY START:\nCREATE NONCLUSTERED INDEX [IX_tig_users_account_status] ON [dbo].[tig_users] ([account_status] ASC) ON [PRIMARY]\n-- QUERY END:\nGO\n\n-- QUERY START:\nCREATE NONCLUSTERED INDEX [IX_tig_users_last_login] ON [dbo].[tig_users] ([last_login] ASC) ON [PRIMARY]\n-- QUERY END:\nGO\n\n-- QUERY START:\nCREATE NONCLUSTERED INDEX [IX_tig_users_last_logout] ON [dbo].[tig_users] ( [last_logout] ASC) ON [PRIMARY]\n-- QUERY END:\nGO\n\n-- QUERY START:\nCREATE NONCLUSTERED INDEX [IX_tig_users_online_status] ON [dbo].[tig_users] ([online_status] ASC) ON [PRIMARY]\n-- QUERY END:\nGO\n\n-- QUERY START:\nCREATE NONCLUSTERED INDEX [IX_tig_users_user_id_fragment] ON [dbo].[tig_users] ( [user_id_fragment] ASC) ON [PRIMARY]\n-- QUERY END:\nGO\n\n-- QUERY START:\nCREATE NONCLUSTERED INDEX [IX_tig_users_user_pw] ON [dbo].[tig_users] ([user_pw] ASC) ON [PRIMARY]\n-- QUERY END:\nGO\n\n\n\n-- QUERY START:\nCREATE TABLE [dbo].[tig_nodes](\n\t[nid] [bigint] IDENTITY(1,1) NOT NULL,\n\t[parent_nid] [bigint] NULL,\n\t[uid] [bigint] NOT NULL,\n\t[node] [nvarchar](255) NOT NULL,\n CONSTRAINT [PK_tig_nodes_nid] PRIMARY KEY CLUSTERED ( [nid] ASC ) ON [PRIMARY],\n CONSTRAINT [IX_tnode] UNIQUE NONCLUSTERED ( [parent_nid] ASC, [uid] ASC, [node] ASC ) ON [PRIMARY]\n) ON [PRIMARY]\n-- QUERY END:\nGO\n\n-- QUERY START:\nCREATE NONCLUSTERED INDEX [IX_tig_nodes_node] ON [dbo].[tig_nodes] ( [node] ASC) ON [PRIMARY]\n-- QUERY END:\nGO\n\n-- QUERY START:\nCREATE NONCLUSTERED INDEX [IX_tig_nodes_parent_nid] ON [dbo].[tig_nodes] ( [parent_nid] ASC ) ON [PRIMARY]\n-- QUERY END:\nGO\n\n-- QUERY START:\nCREATE NONCLUSTERED INDEX [IX_tig_nodes_uid] ON [dbo].[tig_nodes] ( [uid] ASC ) ON [PRIMARY]\n-- QUERY END:\nGO\n\n-- QUERY START:\nALTER TABLE [dbo].[tig_nodes] WITH CHECK ADD CONSTRAINT [FK_tig_nodes_tig_users] FOREIGN KEY([uid])\nREFERENCES [dbo].[tig_users] ([uid])\n-- QUERY END:\nGO\n\n-- QUERY START:\nALTER TABLE [dbo].[tig_nodes] CHECK CONSTRAINT [FK_tig_nodes_tig_users]\n-- QUERY END:\nGO\n\n\n-- QUERY START:\nCREATE TABLE [dbo].[tig_pairs](\n\t[nid] [bigint] NULL,\n\t[uid] [bigint] NOT NULL,\n\t[pkey] [nvarchar](255) NOT NULL,\n\t[pval] [ntext] NULL\n) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]\n-- QUERY END:\nGO\n\n-- QUERY START:\nCREATE NONCLUSTERED INDEX [IX_tig_pairs_nid] ON [dbo].[tig_pairs] ( [nid] ASC ) ON [PRIMARY]\n-- QUERY END:\nGO\n\n-- QUERY START:\nCREATE NONCLUSTERED INDEX [IX_tig_pairs_pkey] ON [dbo].[tig_pairs] ( [pkey] ASC ) ON [PRIMARY]\n-- QUERY END:\nGO\n\n-- QUERY START:\nCREATE NONCLUSTERED INDEX [IX_tig_pairs_uid] ON [dbo].[tig_pairs] ( [uid] ASC ) ON [PRIMARY]\n-- QUERY END:\nGO\n\n-- QUERY START:\nALTER TABLE [dbo].[tig_pairs] WITH CHECK ADD CONSTRAINT [FK_tig_pairs_tig_nodes] FOREIGN KEY([nid])\nREFERENCES [dbo].[tig_nodes] ([nid])\n-- QUERY END:\nGO\n\n-- QUERY START:\nALTER TABLE [dbo].[tig_pairs] CHECK CONSTRAINT [FK_tig_pairs_tig_nodes]\n-- QUERY END:\nGO\n\n-- QUERY START:\nALTER TABLE [dbo].[tig_pairs] WITH CHECK ADD CONSTRAINT [FK_tig_pairs_tig_users] FOREIGN KEY([uid])\nREFERENCES [dbo].[tig_users] ([uid])\n-- QUERY END:\nGO\n\n-- QUERY START:\nALTER TABLE [dbo].[tig_pairs] CHECK CONSTRAINT [FK_tig_pairs_tig_users]\n-- QUERY END:\nGO\n\n\n-- QUERY START:\nCREATE TABLE [dbo].[xmpp_stanza](\n\t[id] [bigint] IDENTITY(1,1) NOT NULL,\n\t[stanza] [ntext] NOT NULL,\n CONSTRAINT [PK_xmpp_stanza] PRIMARY KEY CLUSTERED ( [id] ASC ) ON [PRIMARY]\n) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]\n-- QUERY END:\nGO\n\n\n-- QUERY START:\nCREATE TABLE [dbo].[short_news](\n\t[snid] [bigint] IDENTITY(1,1) NOT NULL,\n\t[publishing_time] [datetime] NOT NULL,\n\t[news_type] [varchar](50) NULL,\n\t[author] [nvarchar](128) NOT NULL,\n\t[subject] [nvarchar](128) NOT NULL,\n\t[body] [nvarchar](1024) NOT NULL,\n CONSTRAINT [PK_short_news_snid] PRIMARY KEY CLUSTERED ( [snid] ASC ) ON [PRIMARY]\n) ON [PRIMARY]\n-- QUERY END:\nGO\n\n-- QUERY START:\nCREATE NONCLUSTERED INDEX [IX_short_news_author] ON [dbo].[short_news] ( [author] ASC ) ON [PRIMARY]\n-- QUERY END:\nGO\n\n-- QUERY START:\nCREATE NONCLUSTERED INDEX [IX_short_news_news_type] ON [dbo].[short_news] ( [news_type] ASC ) ON [PRIMARY]\n-- QUERY END:\nGO\n\n-- QUERY START:\nCREATE NONCLUSTERED INDEX [IX_short_news_publishing_time] ON [dbo].[short_news] ( [publishing_time] ASC ) ON [PRIMARY]\n-- QUERY END:\nGO\n\n-- QUERY START:\nALTER TABLE [dbo].[short_news] ADD CONSTRAINT [DF_short_news_publishing_time] DEFAULT (getdate()) FOR [publishing_time]\n-- QUERY END:\nGO\n\n"
},
{
"path": "tigase-server 7.1.0/database/sqlserver-schema-5-1-sp.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- Database stored procedures and functions for Tigase schema version 5.2.0\n\n-- QUERY START:\nSET QUOTED_IDENTIFIER ON\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigInitdb')\nDROP PROCEDURE TigInitdb\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigAddUserPlainPw')\nDROP PROCEDURE TigAddUserPlainPw\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigAddUser')\nDROP PROCEDURE TigAddUser\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigGetUserDBUid')\nDROP PROCEDURE TigGetUserDBUid\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigRemoveUser')\nDROP PROCEDURE TigRemoveUser\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigUpdatePasswordPlainPw')\nDROP PROCEDURE TigUpdatePasswordPlainPw\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigUpdatePassword')\nDROP PROCEDURE TigUpdatePassword\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigUpdatePasswordPlainPwRev')\nDROP PROCEDURE TigUpdatePasswordPlainPwRev\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigGetPassword')\nDROP PROCEDURE TigGetPassword\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigUserLoginPlainPw')\nDROP PROCEDURE TigUserLoginPlainPw\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigUserLogin')\nDROP PROCEDURE TigUserLogin\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigUserLogout')\nDROP PROCEDURE TigUserLogout\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigOnlineUsers')\nDROP PROCEDURE TigOnlineUsers\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigOfflineUsers')\nDROP PROCEDURE TigOfflineUsers\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigAllUsers')\nDROP PROCEDURE TigAllUsers\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigAllUsersCount')\nDROP PROCEDURE TigAllUsersCount\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigDisableAccount')\nDROP PROCEDURE TigDisableAccount\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigEnableAccount')\nDROP PROCEDURE TigEnableAccount\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigActiveAccounts')\nDROP PROCEDURE TigActiveAccounts\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigDisabledAccounts')\nDROP PROCEDURE TigDisabledAccounts\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigAddNode')\nDROP PROCEDURE TigAddNode\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigTestAddUser')\nDROP PROCEDURE TigTestAddUser\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigUsers2Ver4Convert')\nDROP PROCEDURE TigUsers2Ver4Convert\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigPutDBProperty')\nDROP PROCEDURE TigPutDBProperty\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'FN' AND name = 'TigGetDBProperty')\nDROP FUNCTION TigGetDBProperty\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigUpdatePairs')\nDROP PROCEDURE TigUpdatePairs\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'FN' AND name = 'InlineMax')\nDROP FUNCTION InlineMax\n-- QUERY END:\nGO\n\n\n\n\n-- QUERY START:\n-- The initialization of the database.\n-- The procedure should be called manually somehow before starting the\n-- server. In theory the server could call the procedure automatically\n-- at the startup time but I don't know yet how to solve the problem\n-- with multiple cluster nodes starting at later time when the server\n-- is already running.\ncreate procedure dbo.TigInitdb\nAS\nbegin\n update dbo.tig_users set online_status = 0;\nend\n-- QUERY END:\nGO\n\n-- QUERY START:\n-- Database properties get - function\ncreate function TigGetDBProperty(@_tkey nvarchar(255)) returns nvarchar(MAX)\nAS\nbegin\n--Declare @_result nvarchar(MAX);\nreturn (select pval from dbo.tig_pairs AS p, dbo.tig_users AS u\n\t\twhere (pkey = @_tkey) AND (sha1_user_id = HASHBYTES('SHA1', LOWER(N'db-properties')))\n\t\t\t\t\tAND (p.uid = u.uid));\n\nend\n-- QUERY END:\nGO\n\n\n-- QUERY START:\n-- Database properties set - procedure\ncreate procedure dbo.TigPutDBProperty\n\t@_tkey nvarchar(255),\n\t@_tval ntext\n\tAS\n\tbegin\n\t\tDeclare @_nid int;\n\t\tDeclare @_uid int;\n\t\tDeclare @_count int;\n\t\tif exists (select 1 from dbo.tig_pairs, dbo.tig_users\n\t\t\t\t\twhere (sha1_user_id = HASHBYTES('SHA1', LOWER(N'db-properties')))\n\t\t\t\t\t\tAND (dbo.tig_users.uid = dbo.tig_pairs.uid) AND (pkey = @_tkey))\n\t\t\tbegin\n\t\t\t\tselect @_nid = dbo.tig_pairs.nid, @_uid = dbo.tig_pairs.uid from dbo.tig_pairs, dbo.tig_users\n\t\t\t\t\twhere (sha1_user_id = HASHBYTES('SHA1', LOWER(N'db-properties')))\n\t\t\t\t\t\tAND (dbo.tig_users.uid = dbo.tig_pairs.uid) AND (pkey = @_tkey);\n\t\t\t\tupdate dbo.tig_pairs set pval = @_tval\n\t\t\t\t\twhere (@_uid = uid) AND (pkey = @_tkey) ;\n\t\t\tend\n\t\telse\n\t\t\tbegin\n\t\t\t\tselect @_nid = dbo.tig_pairs.nid, @_uid = dbo.tig_pairs.uid from dbo.tig_pairs, dbo.tig_users\n\t\t\t\t\twhere (sha1_user_id = HASHBYTES('SHA1', LOWER(N'db-properties')))\n\t\t\t\t\t\tAND (dbo.tig_users.uid = dbo.tig_pairs.uid) AND (pkey = @_tkey);\n\t\t\t\tinsert into dbo.tig_pairs (pkey, pval, uid)\n\t\t\t\t\tselect @_tkey, @_tval, uid from dbo.tig_users\n\t\t\t\t\t\twhere (sha1_user_id = HASHBYTES('SHA1', LOWER(N'db-properties')));\n\t\t\tend\n\tend\n-- QUERY END:\nGO\n\n\n-- QUERY START:\n-- Add a new user to the database assuming the user password is already\n-- encoded properly according to the database settings.\n-- If password is not encoded TigAddUserPlainPw should be used instead.\ncreate procedure dbo.TigAddUser\n\t@_user_id nvarchar(2049),\n\t@_user_pw nvarchar(255)\nAS\n\tbegin\n\t\tSET NOCOUNT ON;\n\t\t\n\t\tdeclare @res_uid bigint;\n\n\t\tinsert into dbo.tig_users (user_id, sha1_user_id, user_pw)\n\t\t\tvalues (@_user_id, HASHBYTES('SHA1', LOWER(@_user_id)) , @_user_pw);\n\n\t\tset @res_uid = (select SCOPE_IDENTITY());\n\n\t\tif (@res_uid is not NULL)\n\t\t\tinsert into dbo.tig_nodes (parent_nid, uid, node)\n\t\t\t\tvalues (NULL, @res_uid, N'root');\n\n\t\tif (@_user_pw is NULL) \n\t\t\tupdate dbo.tig_users set account_status = -1 where uid = @res_uid;\n\n\t\tselect @res_uid as uid;\n\tend;\n-- QUERY END:\nGO\n\n-- QUERY START:\n-- Takes plain text user password and converts it to internal representation\n-- and creates a new user account.\ncreate procedure dbo.TigAddUserPlainPw\n\t@_user_id nvarchar(2049),\n\t@_user_pw nvarchar(255)\nAS\nbegin\n\tdeclare @_encoding nvarchar(512)\n\tdeclare @_hashed_pass varbinary(32)\n\tset @_encoding = dbo.TigGetDBProperty(N'password-encoding')\n\tif @_encoding = N'MD5-PASSWORD'\n\t\tbegin\n\t\t\tset @_hashed_pass = HASHBYTES('MD5', @_user_pw);\n\t\t\texec TigAddUser @_user_id, @_hashed_pass;\n\t\tend\n\tif @_encoding = N'MD5-USERID-PASSWORD' \n\t\tbegin\n\t\t\tset @_hashed_pass = HASHBYTES('MD5', @_user_id + @_user_pw);\n\t\t\texec TigAddUser @_user_id, @_hashed_pass\n\t\tend\n\tif @_encoding = N'MD5-USERNAME-PASSWORD'\n\t\tbegin\n\t\t\tset @_hashed_pass = HASHBYTES('MD5', (LEFT (@_user_id, CHARINDEX(N'@',@_user_id)-1)) + @_user_pw);\n\t\t\texec TigAddUser @_user_id, @_hashed_pass;\n\t\tend\n\telse\n\t\texec TigAddUser @_user_id, @_user_pw ;\n\tend\n-- QUERY END:\nGO\n\n-- QUERY START:\n-- Low level database user id as big number. Used only for performance reasons\n-- and save database space. Besides JID is too large to server as UID\ncreate procedure dbo.TigGetUserDBUid\n\t@_user_id nvarchar(2049)\nAS\t\nbegin\n\tselect uid from dbo.tig_users where sha1_user_id = hashbytes('SHA1', lower(@_user_id));\nend\n-- QUERY END:\nGO\n\n-- QUERY START:\n-- Removes a user from the database\ncreate procedure dbo.TigRemoveUser\n\t@_user_id nvarchar(2049)\nAS\nbegin\n\tdeclare @res_uid bigint;\n\n\tset @res_uid = (select uid from dbo.tig_users where sha1_user_id = hashbytes('SHA1', lower(@_user_id)));\n\n\tdelete from dbo.tig_pairs where uid = @res_uid;\n\tdelete from dbo.tig_nodes where uid = @res_uid;\n\tdelete from dbo.tig_users where uid = @res_uid;\nend\n-- QUERY END:\nGO\n\n-- QUERY START:\n-- Returns user's password from the database\ncreate procedure dbo.TigGetPassword\n\t@_user_id nvarchar(2049)\nAS\nbegin\n\tselect user_pw from dbo.tig_users where sha1_user_id = hashbytes('SHA1', lower(@_user_id));\nend\n-- QUERY END:\nGO\n\n-- QUERY START:\n-- Update user password\ncreate procedure dbo.TigUpdatePassword\n\t@_user_id nvarchar(2049),\n\t@_user_pw nvarchar(255)\nAS\nbegin\n\tupdate dbo.tig_users set user_pw = @_user_pw where sha1_user_id = hashbytes('SHA1', lower(@_user_id));\nend\n-- QUERY END:\nGO\n\n-- QUERY START:\n-- Takes plain text user password and converts it to internal representation\ncreate procedure dbo.TigUpdatePasswordPlainPw\n\t@_user_id nvarchar(2049),\n\t@_user_pw nvarchar(255)\nAS\nbegin\n\tdeclare @_encoding nvarchar(512)\n\tdeclare @_hashed_pass varbinary(32)\n\tset @_encoding = dbo.TigGetDBProperty(N'password-encoding')\n\tif @_encoding = N'MD5-PASSWORD'\n\t\tbegin\n\t\t\tset @_hashed_pass = HASHBYTES('MD5', @_user_pw);\n\t\t\texec TigUpdatePassword @_user_id, @_hashed_pass;\n\t\tend\n\tif @_encoding = N'MD5-USERID-PASSWORD' \n\t\tbegin\n\t\t\tset @_hashed_pass = HASHBYTES('MD5', @_user_id + @_user_pw);\n\t\t\texec TigUpdatePassword @_user_id, @_hashed_pass\n\t\tend\n\tif @_encoding = N'MD5-USERNAME-PASSWORD'\n\t\tbegin\n\t\t\tset @_hashed_pass = HASHBYTES('MD5', (LEFT (@_user_id, CHARINDEX(N'@',@_user_id)-1)) + @_user_pw);\n\t\t\texec TigUpdatePassword @_user_id, @_hashed_pass;\n\t\tend\n\telse\n\t\texec TigUpdatePassword @_user_id, @_user_pw ;\nend\n-- QUERY END:\nGO\n\n-- QUERY START:\n-- Variant of TigUpdatePasswordPlainPw SP with parameters in reverse order.\n-- Some implementations require the parameters to be in the same order as\n-- the update query.\ncreate procedure dbo.TigUpdatePasswordPlainPwRev\n\t@_user_pw nvarchar(255),\n\t@_user_id nvarchar(2049)\nAS\nbegin\n\texec TigUpdatePasswordPlainPw @_user_id, @_user_pw;\nend\n-- QUERY END:\nGO\n\n-- QUERY START:\n-- List all online users\ncreate procedure dbo.TigOnlineUsers\nAS\nbegin\n\tselect user_id, last_login, last_logout, online_status, failed_logins, account_status\n\t\tfrom dbo.tig_users where online_status > 0;\nend\n-- QUERY END:\nGO\n\n-- QUERY START:\n-- List all offline users\ncreate procedure dbo.TigOfflineUsers\nAS\nbegin\n\tselect user_id, last_login, last_logout, online_status, failed_logins, account_status\n\t\tfrom dbo.tig_users where online_status = 0;\nend\n-- QUERY END:\nGO\n\n-- QUERY START:\n-- List of all users in database\ncreate procedure dbo.TigAllUsers\nAS\nbegin\n\tselect user_id, last_login, last_logout, online_status, failed_logins, account_status\n\t\tfrom dbo.tig_users;\nend\n-- QUERY END:\nGO\n\n-- QUERY START:\n-- All users count\ncreate procedure dbo.TigAllUsersCount\nAS\nbegin\n\tselect count(*) from dbo.tig_users;\nend\n-- QUERY END:\nGO\n\n-- QUERY START:\n-- Perforrm user login. It returns user_id uppon success and NULL\n-- on failure.\n-- If the login is successful it also increases online_status and sets\n-- last_login time to the current timestamp\ncreate procedure dbo.TigUserLogin\n\t@_user_id nvarchar(2049),\n\t@_user_pw nvarchar(255)\nAS\nbegin\n\tif exists(select 1 from dbo.tig_users\n\t\twhere (account_status > 0) AND (sha1_user_id = hashbytes('SHA1', lower(@_user_id)))\n\t\t\tAND (user_pw = @_user_pw) AND (user_id = @_user_id))\n\t\tbegin\n\t\tupdate dbo.tig_users\n\t\t\tset online_status = online_status + 1, last_login = CURRENT_TIMESTAMP\n\t\t\t\twhere sha1_user_id = hashbytes('SHA1', lower(@_user_id));\n\t\t\tselect @_user_id as user_id;\n\t\tend\n\telse\n\t\tbegin\n\t\t\tupdate dbo.tig_users set failed_logins = failed_logins + 1 where sha1_user_id = hashbytes('SHA1', lower(@_user_id));\n\t\t\tselect NULL as user_id;\n\t\tend\n\tend\n-- QUERY END:\nGO\n\n-- QUERY START:\n-- Performs user login for a plain text password, converting it to an internal\n-- representation if necessary\ncreate procedure dbo.TigUserLoginPlainPw\n\t@_user_id nvarchar(2049),\n\t@_user_pw nvarchar(255)\nAS\nbegin\n\tdeclare @_encoding nvarchar(512)\n\tdeclare @_hashed_pass varbinary(32)\n\tset @_encoding = dbo.TigGetDBProperty(N'password-encoding')\n\tif @_encoding = 'MD5-PASSWORD'\n\t\tbegin\n\t\t\tset @_hashed_pass = HASHBYTES('MD5', @_user_pw);\n\t\t\texec TigUserLogin @_user_id, @_hashed_pass;\n\t\tend\n\tif @_encoding = N'MD5-USERID-PASSWORD' \n\t\tbegin\n\t\t\tset @_hashed_pass = HASHBYTES('MD5', @_user_id + @_user_pw);\n\t\t\texec TigUserLogin @_user_id, @_hashed_pass\n\t\tend\n\tif @_encoding = N'MD5-USERNAME-PASSWORD'\n\t\tbegin\n\t\t\tset @_hashed_pass = HASHBYTES('MD5', (LEFT (@_user_id, CHARINDEX(N'@',@_user_id)-1)) + @_user_pw);\n\t\t\texec TigUserLogin @_user_id, @_hashed_pass;\n\t\tend\n\telse\n\t\texec TigUserLogin @_user_id, @_user_pw ;\n\tend\n-- QUERY END:\nGO\n\n-- QUERY START:\n-- helper function\ncreate function dbo.InlineMax(@val1 int, @val2 int)\nreturns int\nas\nbegin\n if @val1 > @val2\n return @val1\n return isnull(@val2,@val1)\nend\n-- QUERY END:\nGO\n\n-- QUERY START:\n-- It decreases online_status and sets last_logout time to the current timestamp\ncreate procedure dbo.TigUserLogout\n\t@_user_id nvarchar(2049)\nAS\nbegin\n\tupdate dbo.tig_users\n\t\tset online_status = dbo.InlineMax(online_status - 1, 0),\n\t\t\tlast_logout = CURRENT_TIMESTAMP\n\t\twhere user_id = @_user_id;\nend\n-- QUERY END:\nGO\n\n-- QUERY START:\n-- Disable user account\ncreate procedure dbo.TigDisableAccount\n\t@_user_id nvarchar(2049)\nAS\nbegin\n\tupdate dbo.tig_users set account_status = 0 where sha1_user_id = hashbytes('SHA1', lower(@_user_id));\nend\n-- QUERY END:\nGO\n\n-- QUERY START:\n-- Enable user account\ncreate procedure dbo.TigEnableAccount\n\t@_user_id nvarchar(2049)\nAS\nbegin\n\tupdate dbo.tig_users set account_status = 1 where sha1_user_id = hashbytes('SHA1', lower(@_user_id));\nend\n-- QUERY END:\nGO\n\n-- QUERY START:\n-- Get list of all active user accounts\ncreate procedure dbo.TigActiveAccounts\nAS\nbegin\n\tselect user_id, last_login, last_logout, online_status, failed_logins, account_status\n\t\tfrom dbo.tig_users where account_status > 0;\nend\n-- QUERY END:\nGO\n\n-- QUERY START:\n-- Get list of all disabled user accounts\ncreate procedure dbo.TigDisabledAccounts\nAS\nbegin\n\tselect user_id, last_login, last_logout, online_status, failed_logins, account_status\n\t\tfrom dbo.tig_users where account_status = 0;\nend\n-- QUERY END:\nGO\n\n-- QUERY START:\n-- Helper procedure for adding a new node\ncreate procedure dbo.TigAddNode\n@_parent_nid bigint,\n@_uid bigint,\n@_node nvarchar(255)\nAS\nbegin\n\tSET NOCOUNT ON;\n\t\n\tinsert into dbo.tig_nodes (parent_nid, uid, node)\n\t\tvalues (@_parent_nid, @_uid, @_node);\n\tselect SCOPE_IDENTITY() as nid;\nend\n-- QUERY END:\nGO\n\n-- QUERY START:\n-- Procedure to efficiently and safely update data in tig_pairs table\ncreate procedure dbo.TigUpdatePairs\n@_nid bigint,\n@_uid bigint,\n@_tkey nvarchar(255),\n@_tval ntext\nAS\nbegin\n if exists(SELECT 1 FROM dbo.tig_pairs WHERE nid = @_nid AND uid = @_uid AND pkey = @_tkey)\n UPDATE dbo.tig_pairs SET pval = @_tval WHERE nid = @_nid AND uid = @_uid AND pkey = @_tkey;\n ELSE\n INSERT INTO dbo.tig_pairs (nid, uid, pkey, pval) VALUES (@_nid, @_uid, @_tkey, @_tval);\nEND\n-- QUERY END:\nGO\n\n\n"
},
{
"path": "tigase-server 7.1.0/database/sqlserver-schema-5-1.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2012 \"Artur Hefczyc\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- $Rev: $\n-- Last modified by $Author: $\n-- $Date: $\n--\n\n-- To load schema to PostgreSQL database execute following commands:\n--\n-- createuser tigase\n-- createdb -U tigase tigase\n-- psql -q -U tigase -d tigase -f postgresql-schema.sql\n\n-- LOAD FILE: database/sqlserver-schema-5-1-schema.sql\n\n-- LOAD FILE: database/sqlserver-schema-5-1-sp.sql\n\n-- LOAD FILE: database/sqlserver-schema-5-1-props.sql\n"
},
{
"path": "tigase-server 7.1.0/database/sqlserver-schema-7-1-props.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2016 \"Tigase, Inc.\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n--\n\n-- QUERY START:\nSET QUOTED_IDENTIFIER ON\n-- QUERY END:\nGO\n\n-- QUERY START:\n-- This is a dummy user who keeps all the database-properties\nexec dbo.TigAddUserPlainPw 'db-properties', NULL;\n-- QUERY END:\nGO\n\nselect GETDATE(), ' - Setting schema version to 7.1';\n\n-- QUERY START:\nexec dbo.TigPutDBProperty 'schema-version', '7.1';\n-- QUERY END:\nGO"
},
{
"path": "tigase-server 7.1.0/database/sqlserver-schema-7-1-schema.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2016 \"Tigase, Inc.\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n\n-- To load schema to execute following commands:\n--\n\n-- QUERY START:\nSET QUOTED_IDENTIFIER ON\n-- QUERY END:\nGO\n\n-- LOAD FILE: database/sqlserver-schema-5-1-schema.sql\n\n-- QUERY START:\nIF EXISTS(SELECT * FROM sys.indexes WHERE object_id = object_id('dbo.tig_pairs') AND NAME ='IX_clustered_tig_pairs_nid_uid_pkey')\n DROP INDEX IX_clustered_tig_pairs_nid_uid_pkey ON dbo.tig_pairs;\n-- QUERY END:\nGO\n\n-- QUERY START:\nALTER TABLE [dbo].[tig_pairs]\n ADD [pid] [bigint] IDENTITY(1,1) NOT NULL,\n CONSTRAINT [PK_tig_pairs] PRIMARY KEY CLUSTERED ( [pid] ASC ) ON [PRIMARY]\n-- QUERY END:\nGO\n\n"
},
{
"path": "tigase-server 7.1.0/database/sqlserver-schema-7-1-sp.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2016 \"Tigase, Inc.\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n-- Database stored procedures and functions for Tigase schema version 7.1.0\n\n-- QUERY START:\nSET QUOTED_IDENTIFIER ON\n-- QUERY END:\nGO\n\n-- LOAD FILE: database/sqlserver-schema-5-1-sp.sql\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigPutDBProperty')\nDROP PROCEDURE TigPutDBProperty\n-- QUERY END:\nGO\n\n\n-- QUERY START:\n-- Database properties set - procedure\ncreate procedure dbo.TigPutDBProperty\n\t@_tkey nvarchar(255),\n\t@_tval ntext\n\tAS\n\tbegin\n\t\tDeclare @_nid int;\n\t\tDeclare @_uid int;\n\t\tDeclare @_count int;\n\t\tif exists (select 1 from dbo.tig_pairs, dbo.tig_users\n\t\t\t\t\twhere (sha1_user_id = HASHBYTES('SHA1', LOWER(N'db-properties')))\n\t\t\t\t\t\tAND (dbo.tig_users.uid = dbo.tig_pairs.uid) AND (pkey = @_tkey))\n\t\t\tbegin\n\t\t\t\tselect @_nid = dbo.tig_pairs.nid, @_uid = dbo.tig_pairs.uid from dbo.tig_pairs, dbo.tig_users\n\t\t\t\t\twhere (sha1_user_id = HASHBYTES('SHA1', LOWER(N'db-properties')))\n\t\t\t\t\t\tAND (dbo.tig_users.uid = dbo.tig_pairs.uid) AND (pkey = @_tkey);\n\t\t\t\tupdate dbo.tig_pairs set pval = @_tval\n\t\t\t\t\twhere (@_uid = uid) AND (pkey = @_tkey) ;\n\t\t\tend\n\t\telse\n\t\t\tbegin\n\t\t\t\tselect @_nid = dbo.tig_pairs.nid, @_uid = dbo.tig_pairs.uid from dbo.tig_pairs, dbo.tig_users\n\t\t\t\t\twhere (sha1_user_id = HASHBYTES('SHA1', LOWER(N'db-properties')))\n\t\t\t\t\t\tAND (dbo.tig_users.uid = dbo.tig_pairs.uid) AND (pkey = @_tkey);\n\t\t\t\tinsert into dbo.tig_pairs (pkey, pval, uid, nid)\n\t\t\t\t\tselect @_tkey, @_tval, tu.uid, tn.nid from dbo.tig_users tu left join tig_nodes tn on tn.uid=tu.uid\n\t\t\t\t\t\twhere (sha1_user_id = HASHBYTES('SHA1', LOWER(N'db-properties')) and tn.node='root');\n\t\t\t\t\t\t\n\t\t\tend\n\tend\n-- QUERY END:\nGO\n\n"
},
{
"path": "tigase-server 7.1.0/database/sqlserver-schema-7-1.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2016 \"Tigase, Inc.\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n--\n\n-- To load schema to PostgreSQL database execute following commands:\n--\n-- createuser tigase\n-- createdb -U tigase tigase\n-- psql -q -U tigase -d tigase -f postgresql-schema.sql\n\n-- LOAD FILE: database/sqlserver-schema-7-1-schema.sql\n\n-- LOAD FILE: database/sqlserver-schema-7-1-sp.sql\n\n-- LOAD FILE: database/sqlserver-schema-7-1-props.sql\n"
},
{
"path": "tigase-server 7.1.0/database/sqlserver-schema-upgrade-to-7-1.sql",
"content": "--\n-- Tigase Jabber/XMPP Server\n-- Copyright (C) 2004-2016 \"Tigase, Inc.\" \n--\n-- This program is free software: you can redistribute it and/or modify\n-- it under the terms of the GNU Affero General Public License as published by\n-- the Free Software Foundation, either version 3 of the License.\n--\n-- This program is distributed in the hope that it will be useful,\n-- but WITHOUT ANY WARRANTY; without even the implied warranty of\n-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n-- GNU Affero General Public License for more details.\n--\n-- You should have received a copy of the GNU Affero General Public License\n-- along with this program. Look for COPYING file in the top folder.\n-- If not, see http://www.gnu.org/licenses/.\n--\n--\n\n-- QUERY START:\nSET QUOTED_IDENTIFIER ON\n-- QUERY END:\nGO\n\n\n-- QUERY START:\nIF EXISTS (SELECT * FROM sys.objects WHERE type = 'P' AND name = 'TigPutDBProperty')\nDROP PROCEDURE TigPutDBProperty\n-- QUERY END:\nGO\n\n-- QUERY START:\nIF EXISTS(SELECT * FROM sys.indexes WHERE object_id = object_id('dbo.tig_pairs') AND NAME ='IX_clustered_tig_pairs_nid_uid_pkey')\n DROP INDEX IX_clustered_tig_pairs_nid_uid_pkey ON dbo.tig_pairs;\n-- QUERY END:\nGO\n\n\n\n-- QUERY START:\n-- Database properties set - procedure\ncreate procedure dbo.TigPutDBProperty\n\t@_tkey nvarchar(255),\n\t@_tval ntext\n\tAS\n\tbegin\n\t\tDeclare @_nid int;\n\t\tDeclare @_uid int;\n\t\tDeclare @_count int;\n\t\tif exists (select 1 from dbo.tig_pairs, dbo.tig_users\n\t\t\t\t\twhere (sha1_user_id = HASHBYTES('SHA1', LOWER(N'db-properties')))\n\t\t\t\t\t\tAND (dbo.tig_users.uid = dbo.tig_pairs.uid) AND (pkey = @_tkey))\n\t\t\tbegin\n\t\t\t\tselect @_nid = dbo.tig_pairs.nid, @_uid = dbo.tig_pairs.uid from dbo.tig_pairs, dbo.tig_users\n\t\t\t\t\twhere (sha1_user_id = HASHBYTES('SHA1', LOWER(N'db-properties')))\n\t\t\t\t\t\tAND (dbo.tig_users.uid = dbo.tig_pairs.uid) AND (pkey = @_tkey);\n\t\t\t\tupdate dbo.tig_pairs set pval = @_tval\n\t\t\t\t\twhere (@_uid = uid) AND (pkey = @_tkey) ;\n\t\t\tend\n\t\telse\n\t\t\tbegin\n\t\t\t\tselect @_nid = dbo.tig_pairs.nid, @_uid = dbo.tig_pairs.uid from dbo.tig_pairs, dbo.tig_users\n\t\t\t\t\twhere (sha1_user_id = HASHBYTES('SHA1', LOWER(N'db-properties')))\n\t\t\t\t\t\tAND (dbo.tig_users.uid = dbo.tig_pairs.uid) AND (pkey = @_tkey);\n\t\t\t\tinsert into dbo.tig_pairs (pkey, pval, uid, nid)\n\t\t\t\t\tselect @_tkey, @_tval, tu.uid, tn.nid from dbo.tig_users tu left join tig_nodes tn on tn.uid=tu.uid\n\t\t\t\t\t\twhere (sha1_user_id = HASHBYTES('SHA1', LOWER(N'db-properties')) and tn.node='root');\n\t\t\t\t\t\t\n\t\t\tend\n\tend\n-- QUERY END:\nGO\n\n\n\n-- QUERY START:\nALTER TABLE [dbo].[tig_pairs]\n ADD [pid] [bigint] IDENTITY(1,1) NOT NULL,\n CONSTRAINT [PK_tig_pairs] PRIMARY KEY CLUSTERED ( [pid] ASC ) ON [PRIMARY]\n-- QUERY END:\nGO\n\n\n-- QUERY START:\nupdate tig_pairs set nid = (select nid from tig_nodes where uid=(select uid from tig_users where user_id='db-properties') and node='root') where uid=(select uid from tig_users where user_id='db-properties');\n-- QUERY END:\nGO\n\n\nselect GETDATE(), ' - Setting schema version to 7.1';\n\n-- QUERY START:\nexec dbo.TigPutDBProperty 'schema-version', '7.1';\n-- QUERY END:\nGO"
},
{
"path": "tigase-server 7.1.0/database/sqlserver-schema.sql",
"content": "SET ANSI_NULLS ON\nGO\nSET QUOTED_IDENTIFIER ON\nGO\nCREATE TABLE [dbo].[tig_max_ids](\n\t[max_uid] [bigint] NULL,\n\t[max_nid] [bigint] NULL\n) ON [PRIMARY]\n\nGO\nSET ANSI_NULLS ON\nGO\nSET QUOTED_IDENTIFIER ON\nGO\nCREATE TABLE [dbo].[tig_users](\n\t[uid] [bigint] NOT NULL,\n\t[user_id] [nvarchar](128) NOT NULL\n) ON [PRIMARY]\n\nGO\n\nCREATE UNIQUE NONCLUSTERED INDEX [IX_tig_users] ON [dbo].[tig_users] \n(\n\t[user_id] ASC\n) ON [PRIMARY]\nGO\n\nCREATE UNIQUE NONCLUSTERED INDEX [IX_tig_users_1] ON [dbo].[tig_users] \n(\n\t[uid] ASC\n) ON [PRIMARY]\nGO\nSET ANSI_NULLS ON\nGO\nSET QUOTED_IDENTIFIER ON\nGO\nCREATE TABLE [dbo].[short_news](\n\t[snid] [bigint] IDENTITY(1,1) NOT NULL,\n\t[publishing_time] [datetime] NOT NULL CONSTRAINT [DF_short_news_publishing_time] DEFAULT (getdate()),\n\t[news_type] [nvarchar](50) NULL,\n\t[author] [nvarchar](128) NOT NULL,\n\t[subject] [nvarchar](128) NOT NULL,\n\t[body] [nvarchar](1024) NOT NULL,\n CONSTRAINT [PK_short_news] PRIMARY KEY CLUSTERED \n(\n\t[snid] ASC\n) ON [PRIMARY]\n) ON [PRIMARY]\n\nGO\n\nCREATE NONCLUSTERED INDEX [IX_short_news] ON [dbo].[short_news] \n(\n\t[publishing_time] ASC\n) ON [PRIMARY]\nGO\n\nCREATE NONCLUSTERED INDEX [IX_short_news_1] ON [dbo].[short_news] \n(\n\t[author] ASC\n) ON [PRIMARY]\nGO\n\nCREATE NONCLUSTERED INDEX [IX_short_news_2] ON [dbo].[short_news] \n(\n\t[news_type] ASC\n) ON [PRIMARY]\nGO\nSET ANSI_NULLS ON\nGO\nSET QUOTED_IDENTIFIER ON\nGO\nCREATE TABLE [dbo].[xmpp_stanza](\n\t[id] [bigint] IDENTITY(1,1) NOT NULL,\n\t[stanza] [text] NOT NULL\n) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]\n\nGO\nSET ANSI_NULLS ON\nGO\nSET QUOTED_IDENTIFIER ON\nGO\nCREATE TABLE [dbo].[tig_nodes](\n\t[nid] [bigint] NOT NULL,\n\t[parent_nid] [bigint] NULL,\n\t[uid] [bigint] NOT NULL,\n\t[node] [nvarchar](64) NOT NULL\n) ON [PRIMARY]\n\nGO\n\nCREATE UNIQUE NONCLUSTERED INDEX [IX_tig_nodes] ON [dbo].[tig_nodes] \n(\n\t[parent_nid] ASC,\n\t[node] ASC,\n\t[uid] ASC\n) ON [PRIMARY]\nGO\n\nCREATE NONCLUSTERED INDEX [IX_tig_nodes_1] ON [dbo].[tig_nodes] \n(\n\t[node] ASC\n) ON [PRIMARY]\nGO\n\nCREATE UNIQUE NONCLUSTERED INDEX [IX_tig_nodes_2] ON [dbo].[tig_nodes] \n(\n\t[nid] ASC\n) ON [PRIMARY]\nGO\nSET ANSI_NULLS ON\nGO\nSET QUOTED_IDENTIFIER ON\nGO\nCREATE TABLE [dbo].[tig_pairs](\n\t[nid] [bigint] NOT NULL,\n\t[uid] [bigint] NOT NULL,\n\t[pkey] [nvarchar](128) NOT NULL,\n\t[pval] [text] NULL\n) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]\n\nGO\n\nCREATE NONCLUSTERED INDEX [IX_tig_pairs] ON [dbo].[tig_pairs] \n(\n\t[pkey] ASC\n) ON [PRIMARY]\nGO\nALTER TABLE [dbo].[tig_nodes] WITH CHECK ADD CONSTRAINT [FK_tig_nodes_tig_users] FOREIGN KEY([uid])\nREFERENCES [dbo].[tig_users] ([uid])\nGO\nALTER TABLE [dbo].[tig_nodes] CHECK CONSTRAINT [FK_tig_nodes_tig_users]\nGO\nALTER TABLE [dbo].[tig_pairs] WITH CHECK ADD CONSTRAINT [FK_tig_pairs_tig_nodes] FOREIGN KEY([nid])\nREFERENCES [dbo].[tig_nodes] ([nid])\nGO\nALTER TABLE [dbo].[tig_pairs] CHECK CONSTRAINT [FK_tig_pairs_tig_nodes]\nGO\nALTER TABLE [dbo].[tig_pairs] WITH CHECK ADD CONSTRAINT [FK_tig_pairs_tig_users] FOREIGN KEY([uid])\nREFERENCES [dbo].[tig_users] ([uid])\nGO\nALTER TABLE [dbo].[tig_pairs] CHECK CONSTRAINT [FK_tig_pairs_tig_users]\n"
},
{
"path": "tigase-server 7.1.0/debian/README.Debian",
"content": "Tigase for Debian\n-----------------\n\nTigase Jabber/XMPP Server is Open Source and Free (GPLv3) Java based server.\n\n -- Tomasz Sterna , Thu Mar 13 10:40:12 CET 2009\n"
},
{
"path": "tigase-server 7.1.0/debian/changelog",
"content": "tigase-server (4.1.5-b1686-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1686: Changed SQL scripts to server-database\n\n -- Tomasz Sterna Mon, 25 May 2009 14:29:23 +0000\n\ntigase-server (4.1.5-b1685-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1685: Proper paths to derby jars in scripts\n\n -- Tomasz Sterna Mon, 25 May 2009 14:24:26 +0000\n\ntigase-server (4.1.5-b1684-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1684: Added derbytools jar to CLASSPATH\n during postinst\n\n -- Tomasz Sterna Mon, 25 May 2009 14:16:10 +0000\n\ntigase-server (4.1.5-b1683-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1683: Added statistics displaying number of\n data buffers waiting in the I/O component. Attempt to make data\n writing more efficient by writing as much data as possible in a\n single method call. Added method returning number of buffers waiting\n to send in the I/O. Switching to Sun Java implementation during\n postinstall Added derby jar to CLASSPATH during postinst\n\n -- Tomasz Sterna Mon, 25 May 2009 14:10:17 +0000\n\ntigase-server (4.1.5-b1678-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1678: Attempt to make data reading more\n efficient, reading as much characters from the network socket as\n possible in a single method run.\n\n -- Tomasz Sterna Mon, 25 May 2009 12:11:09 +0000\n\ntigase-server (4.1.5-b1677-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1677: Added check for JRE version to init\n script\n\n -- Tomasz Sterna Mon, 25 May 2009 10:11:08 +0000\n\ntigase-server (4.1.5-b1676-xk2) hardy; urgency=low\n\n * Checking JRE version during init.d startup script.\n\n -- Tomasz Sterna Mon, 25 May 2009 08:52:49 +0000\n\ntigase-server (4.1.5-b1676-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1676: Presence optimizations switched off\n temporarily. Fixed problem with excessive CPU usage by tigase.net\n\n -- Tomasz Sterna Sun, 24 May 2009 00:11:09 +0000\n\ntigase-server (4.1.5-b1674-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1674: Fixed a bug with SM initialization and\n now the cluster sends broadcast to all cluster nodes about new user\n connection after initial presence.\n\n -- Tomasz Sterna Sat, 23 May 2009 20:11:09 +0000\n\ntigase-server (4.1.5-b1673-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1673: Typo fixes. Typo fixes. Typo fixes.\n\n -- Tomasz Sterna Sat, 23 May 2009 18:11:09 +0000\n\ntigase-server (4.1.5-b1670-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1670: Broadcasted presence are always sent\n to bare user jid now. Added msg and check to block user installing\n over existing Tigase dir Broadcasted presence are always sent to\n bare user jid now. Added new connection status: REMOTE for user\n connections established to different cluster nodes. Fixed a bug with\n token authentication which used getUserId() which couldn't work as\n user id is only available after successful authentication. Now it\n takes user id as a parameter. Minor code adjustments. Added method\n returning number of user connections with a given connection status\n and fixed a bug in removing invalid user connections from the list.\n Added callback: handleResourceBind(), now special actions can be\n performed on the user resource bind. Major code fixes and\n improvements related to the new clustering implementation. Minor\n code adjustments. Added local domain name to the statistics list to\n make it easier to find out from which cluster node statistics come.\n Logic bug fixed. Code changes related to a possible bug in detecting\n empty read calls, tests don't show any improvements though. Minor\n code adjustements. Minor code adjustements. Minor code adjustements.\n Minor code adjustements. A few fixes related to possible conflicts\n in the cluster mode. Added simple caching code for the connection\n pool. Added initRepository call for the connection pool to allow for\n the pool to initialize itself. For now it initializes internal\n cache. Clustering code reworked and new, simpler but more effective\n implementation created. No more connections hangs on resource bind\n in case of cluster communications problems. Fresh code needs more\n tests though.\n\n -- Tomasz Sterna Sat, 23 May 2009 12:11:10 +0000\n\ntigase-server (4.1.5-b1649-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1649: changed the code adding admin in the\n installer to use Tigase repo classes\n\n -- Tomasz Sterna Sat, 23 May 2009 10:11:08 +0000\n\ntigase-server (4.1.5-b1648-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1648: Fixed incorrect features providing, i\n hope.... Fixed incorrect features providing, i hope....\n\n -- Tomasz Sterna Thu, 21 May 2009 16:26:41 +0000\n\ntigase-server (4.1.5-b1646-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1646: Fixed incorrect features providing, i\n hope....\n\n -- Tomasz Sterna Wed, 20 May 2009 22:11:08 +0000\n\ntigase-server (4.1.5-b1645-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1645: fixed installer bug, where user\n selection of JDK path was overwrited by JAVA_HOME\n\n -- Tomasz Sterna Tue, 19 May 2009 08:11:09 +0000\n\ntigase-server (4.1.5-b1644-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1644: activated user adding task adding xmpp\n admin user from installer activated user adding task Added jmx files\n to the installation and a groovy script for user mgmt\n\n -- Tomasz Sterna Mon, 18 May 2009 16:11:08 +0000\n\ntigase-server (4.1.5-b1640-xk2) hardy; urgency=low\n\n * Updated to SVN revision 1640\n Merged r1637 to debian init script\n * Fixed bug in init script\n\n -- Tomasz Sterna Mon, 18 May 2009 13:50:04 +0000\n\ntigase-server (4.1.5-b1637-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1637:\\nPresence incorrect broadcast fixed\n for probe and initial presence. Code formatting update CLASSPATH\n generating now excludes wrapper libraries\n\n -- Tomasz Sterna Mon, 18 May 2009 13:33:22 +0000\n\ntigase-server (4.1.5-b1634-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1634:\\nAdded GC calls when memory is Low.\n\n -- Tomasz Sterna Sun, 17 May 2009 20:11:09 +0000\n\ntigase-server (4.1.5-b1633-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1633:\\nTypo fixes.\n\n -- Tomasz Sterna Sat, 16 May 2009 18:11:09 +0000\n\ntigase-server (4.1.5-b1632-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1632:\\nTypo fixes.\n\n -- Tomasz Sterna Sat, 16 May 2009 16:11:08 +0000\n\ntigase-server (4.1.5-b1631-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1631:\\navoid-stale-pid.patch was merged to\n SVN Added info about using discovered config file\n\n -- Tomasz Sterna Sat, 16 May 2009 12:11:08 +0000\n\ntigase-server (4.1.5-b1628-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1628:\\nAdded debian source directory\n\n -- Tomasz Sterna Thu, 14 May 2009 12:12:53 +0000\n\ntigase-server (4.1.5-b1627-xk2) hardy; urgency=low\n\n * Added tigase.extras.io.PEMSSLContextContainer as default\n tigase.io.SSLContextContainer in init.properties\n * Added dependency: libbcprov-java. Required by PEMSSLContextContainer.\n\n -- Tomasz Sterna Tue, 12 May 2009 10:51:21 +0000\n\ntigase-server (4.1.5-b1627-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1627:\\nReverted to old and apparently\n correct behaviour with sending initial presence to all from and both\n contacts.\n\n -- Tomasz Sterna Mon, 11 May 2009 22:37:08 +0000\n\ntigase-server (4.1.5-b1626-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1626:\\nProbably fixed a bug with concurrent\n data reading from network socket. Each new server connection is\n opened in a separate thread to avoid DNS blocking.\n\n -- Tomasz Sterna Mon, 11 May 2009 18:11:33 +0000\n\ntigase-server (4.1.5-b1624-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1624:\\nadding xmpp admin user from installer\n unneeded file cleanup config file saving fix in console installer\n\n -- Tomasz Sterna Mon, 11 May 2009 12:11:09 +0000\n\ntigase-server (4.1.5-b1621-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1621:\\nMerge branch 'dbfix'\n\n -- Tomasz Sterna Sun, 10 May 2009 20:11:08 +0000\n\ntigase-server (4.1.5-b1620-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1620:\\nAdded db and config screens Fixed\n wrong Derby location selection in console mode Improved packs\n selection, ignoring packs for other systems\n\n -- Tomasz Sterna Sun, 10 May 2009 16:11:08 +0000\n\ntigase-server (4.1.5-b1616-xk3) hardy; urgency=low\n\n * Added Stored procedures for Digest Auth\n\n -- Tomasz Sterna Sun, 10 May 2009 00:56:21 +0000\n\ntigase-server (4.1.5-b1616-xk2) hardy; urgency=low\n\n * Added digest auth methods to TigaseAuth.\n\n -- Tomasz Sterna Sun, 10 May 2009 00:01:56 +0000\n\ntigase-server (4.1.5-b1616-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1616:\\nA few fixes and spelling corrections\n in scripts\n\n -- Tomasz Sterna Sat, 09 May 2009 16:11:08 +0000\n\ntigase-server (4.1.5-b1615-xk2) hardy; urgency=low\n\n * Fixed init script to properly include JDBC drivers\n\n -- Tomasz Sterna Fri, 08 May 2009 10:14:32 +0000\n\ntigase-server (4.1.5-b1615-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1615\n\n -- Tomasz Sterna Fri, 08 May 2009 09:01:07 +0000\n\ntigase-server (4.1.5-b1614-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1614\n\n -- Tomasz Sterna Fri, 08 May 2009 09:00:07 +0000\n\ntigase-server (4.1.5-b1613-xk1) hardy; urgency=low\n\n * Updated to SVN revision 1613\n * Separated packages:\n - tigase-xmltools\n - tigase-utils\n - tigase-extras\n - tigase-muc\n - tigase-pubsub\n * Using /usr/share/tigase for all Tigase shared data\n\n -- Tomasz Sterna Thu, 07 May 2009 13:46:50 +0000\n\ntigase-server (4.1.4-xk2) dapper; urgency=low\n\n * Moved Derby Database to /var/spool/tigase/tigase-derbydb\n\n -- Tomasz Sterna Fri, 17 Apr 2009 10:30:21 +0000\n\ntigase-server (4.1.4-xk1) unstable; urgency=low\n\n * Updated Tigase to version 4.1.4:\n * tigase-extras-0.3.0.jar\n * tigase-muc-1.0.2.jar\n * tigase-pubsub-1.0.1.jar\n * tigase-server-4.1.4.jar\n * tigase-utils-3.1.2.jar\n * tigase-xmltools-3.1.1.jar\n * Updated SQLDB connectors:\n * mysql-connector-java-5.1.7.tar.gz\n * postgresql-8.3-604.jdbc3.jar\n\n -- Tomasz Sterna Mon, 16 Mar 2009 09:40:18 +0000\n\ntigase-server (4.1.0-b1315-1) unstable; urgency=low\n\n * Initial Release.\n\n -- Tomasz Sterna Thu, 13 Mar 2009 10:42:12 +0200\n\n"
},
{
"path": "tigase-server 7.1.0/debian/compat",
"content": "4\n"
},
{
"path": "tigase-server 7.1.0/debian/control",
"content": "Source: tigase-server\nSection: net\nPriority: extra\nMaintainer: Tomasz Sterna \nBuild-Depends: cdbs, debhelper (>= 5), sun-java6-jdk, maven2\nStandards-Version: 3.8.0\n\nPackage: tigase-server\nArchitecture: all\nDepends: sun-java6-jre | sun-java6-jdk, sun-java6-javadb | libmysql-java | libpg-java,\n tigase-xmltools, tigase-utils, tigase-extras, libbcprov-java,\n adduser, ${misc:Depends}\nDescription: Open Source and Free (GPLv3) Java based Jabber/XMPP server\n The design and implementation goals of the Tigase Jabber/XMPP Server\n * Make the server robust and reliable.\n * Make the server secure communication platform.\n * Make flexible server which can be applied to different use cases.\n * Make extensible server which takes full advantage of XMPP protocol\n extensibility.\n * Make the server easy to setup and maintain.\n .\n See http://www.tigase.org/\nHomepage: http://www.tigase.org/\n"
},
{
"path": "tigase-server 7.1.0/debian/copyright",
"content": "This package was debianized by Tomasz Sterna \non Thu, 13 Mar 2009 10:46:12 +0200.\n\nIt was downloaded from https://svn.tigase.org/reps/tigase-server/trunk\n\nUpstream Author: Artur Hefczyc\n\nCopyright (C) 2004-2012 \"Artur Hefczyc\" \n\n This program is free software: you can redistribute it and/or modify\n it under the terms of the GNU Affero General Public License as published by\n the Free Software Foundation, version 3 of the License.\n\n This program is distributed in the hope that it will be useful,\n but WITHOUT ANY WARRANTY; without even the implied warranty of\n MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n GNU Affero General Public License for more details.\n\nYou should have received a copy of the GNU Affero General Public License with\nthe Debian GNU/Linux distribution in file /usr/share/common-licenses/GPL-3\nIf not, see .\n"
},
{
"path": "tigase-server 7.1.0/debian/init.properties",
"content": "--user-db=derby\n--user-db-uri=jdbc:derby:/var/spool/tigase/tigase-derbydb;create=true;logDevice=/var/log/tigase\n--ssl-container-class=tigase.extras.io.PEMSSLContextContainer\nbasic-conf/logging/java.util.logging.FileHandler.pattern = /var/log/tigase/tigase.log\ns2s/connections/tls/keys-store = /etc/tigase/certs/rsa-keystore\ns2s/connections/tls/trusts-store = /etc/tigase/certs/truststore\ns2s/connections/tls/server-certs-dir = /etc/tigase/certs\nc2s/connections/tls/keys-store = /etc/tigase/certs/rsa-keystore\nc2s/connections/tls/trusts-store = /etc/tigase/certs/truststore\nc2s/connections/tls/server-certs-dir = /etc/tigase/certs\nbosh/connections/tls/keys-store = /etc/tigase/certs/rsa-keystore\nbosh/connections/tls/trusts-store = /etc/tigase/certs/truststore\nbosh/connections/tls/server-certs-dir = /etc/tigase/certs\n"
},
{
"path": "tigase-server 7.1.0/debian/rules",
"content": "#!/usr/bin/make -f\n# debian/rules for Jetty (uses CDBS)\n\ninclude /usr/share/cdbs/1/rules/debhelper.mk\ninclude /usr/share/cdbs/1/rules/simple-patchsys.mk\n\nbuild:\n\tmvn package\n\nclean::\n\trm -rf target\n\nbinary-post-install/tigase-server::\n\tmv debian/tigase-server/usr/share/tigase/database debian/tigase-server/usr/share/tigase/server-database\n\tsed -i 's#jars/\\|libs/#lib/#g' debian/tigase-server/usr/share/tigase/scripts/*.sh\n\tsed -i 's#lib/tigase-server[^.]*.jar#lib/'`basename debian/tigase-server/usr/share/tigase/lib/tigase-server*.jar`'#g' debian/tigase-server/usr/share/tigase/scripts/*.sh\n\tsed -i 's#lib/derby#/usr/lib/jvm/java-6-sun/db/lib/derby#g' debian/tigase-server/usr/share/tigase/scripts/*.sh\n\tsed -i 's#database/#server-database/#g' debian/tigase-server/usr/share/tigase/scripts/*.sh\n\tchmod +x debian/tigase-server/usr/share/tigase/scripts/*.sh\n\tcat debian/init.properties >> debian/tigase-server/etc/tigase/init.properties\n\tfind debian/tigase-server -depth -type d -name .svn -exec rm -rf {} \\;\n"
},
{
"path": "tigase-server 7.1.0/debian/std-logger.sh",
"content": "#!/bin/sh\nLOG=$1\nshift\nexec $* >>$LOG 2>&1 &1 | grep -q 'java version[^0-9]\\+\\([2-9]\\|1\\.[6-9]\\)'; then\n\tif [ -z \"$JAVA_HOME\" ]; then\n\t\techo \"Could not start $DESC because no Java Runtime Environment (JRE) was found.\"\n\telse\n\t\techo \"$DESC needs Sun Java(TM) SE Runtime Environment at least version 1.6.\"\n\tfi\n\techo \"Please download and install JRE 1.6 or higher and set\"\n\techo \"JAVA_HOME in /etc/default/tigase-server to the JRE's installation directory.\"\n\texit 0\nfi\n\n# Put all jars in classpath\nCLASSPATH=\"$TIGASE_JAR\"\n\nCLASSPATH=\"`ls -d $TIGASE_HOME/lib/*.jar 2>/dev/null | grep -v wrapper | tr '\\n' :`$CLASSPATH\"\nfor lib in /usr/lib/jvm/java-6-sun/db/lib/derby.jar \\\n /usr/share/java/postgresql.jar \\\n /usr/share/java/mysql.jar \\\n /usr/share/java/bcprov.jar ; do\n if [ -r $lib ]; then CLASSPATH=\"$CLASSPATH:$lib\"; fi\ndone\n\nARGUMENTS=\"$JAVA_OPTIONS $TIGASE_DBDRV -cp $CLASSPATH $TIGASE_RUN -c $TIGASE_CONFIG $TIGASE_OPTIONS\"\n\n##################################################\n# Do the action\n##################################################\ncase \"$1\" in\n start)\n\tif start-stop-daemon --quiet --test --start --pidfile \"$PIDFILE\" \\\n\t\t\t --user \"$TIGASE_USER\" --exec \"$JAVA\" > /dev/null; then \n\n\t if [ -f $PIDFILE ]; then\n\t\techo \"$PIDFILE exists, but $NAME was not running. Ignoring $PIDFILE\"\n\t fi\n\n\t echo -n \"Starting $DESC: \"\n\t\ttouch $TIGASE_CONSOLE_LOG\n\t\tchown $TIGASE_USER:adm $TIGASE_CONSOLE_LOG\n\t\techo \"STARTED Tigase `date`\" >>$TIGASE_CONSOLE_LOG\n\t\tstart-stop-daemon --quiet --start --background --pidfile \"$PIDFILE\" --make-pidfile \\\n\t\t --chuid \"$TIGASE_USER\" --startas \"$TIGASE_HOME/scripts/std-logger.sh\" \\\n\t\t -- \"$TIGASE_CONSOLE_LOG\" \"$JAVA\" $ARGUMENTS\n\t\tsleep 1\n\t\tif [ -e \"$TIGASE_CONFIG\" ]; then\n\t\t\tchown $TIGASE_USER:adm $TIGASE_CONFIG\n\t\t\tchmod 0640 $TIGASE_CONFIG\n\t\tfi\n\t\techo \"$NAME.\"\n\telse\n\techo \"(already running).\"\n\t\texit 1\n\tfi\n\t;;\n\n stop)\n \techo -n \"Stopping $DESC: \"\n\n\tif start-stop-daemon --quiet --test --start --pidfile \"$PIDFILE\" \\\n\t\t--user \"$TIGASE_USER\" --exec \"$JAVA\" > /dev/null; then\n\t\tif [ -x \"$PIDFILE\" ]; then\n\t\t\techo \"(not running but $PIDFILE exists).\"\n\t\telse\n\t\t\techo \"(not running).\"\n\t\tfi\n\telse\n\t\tstart-stop-daemon --quiet --stop \\\n\t\t\t--pidfile \"$PIDFILE\" --user \"$TIGASE_USER\" --exec \"$JAVA\" > /dev/null\n\t\tsleep 1\n\t\twhile ! start-stop-daemon --quiet --test --start \\\n\t\t\t--pidfile \"$PIDFILE\" --user \"$TIGASE_USER\" \\\n\t\t\t--startas \"$JAVA\" > /dev/null; do \n\t\t\tsleep 1\n\t\t\techo -n \".\"\n\t\t\tstart-stop-daemon --oknodo --quiet --stop \\\n\t\t\t\t--pidfile \"$PIDFILE\" --user \"$TIGASE_USER\" --exec \"$JAVA\"\n\t\tdone\n\t\trm -f \"$PIDFILE\"\n\t\techo \"$NAME.\"\n\tfi\n\t;;\n\n restart|force-reload)\n\t$0 stop $*\n\tsleep 1\n\t$0 start $*\n\t;;\n\n check)\n\techo \"Checking arguments to Tigase: \"\n\techo\n\techo \"PIDFILE = $PIDFILE\"\n\techo \"JAVA_OPTIONS = $JAVA_OPTIONS\"\n\techo \"JAVA = $JAVA\"\n\techo \"TIGASE_USER = $TIGASE_USER\"\n\techo \"ARGUMENTS = $ARGUMENTS\"\n\techo \"TIGASE_HOME = $TIGASE_HOME\"\n\techo \"TIGASE_JAR = $TIGASE_JAR\"\n\techo \"TIGASE_CONFIG = $TIGASE_CONFIG\"\n\techo \"TIGASE_OPTIONS = $TIGASE_OPTIONS\"\n\techo \"CLASSPATH = $CLASSPATH\"\n\techo \"TIGASE_CONSOLE_LOG = $TIGASE_CONSOLE_LOG\"\n\t\n\tif [ -f $PIDFILE ] && kill -0 `cat $PIDFILE` 2>/dev/null\n\tthen\n\t\techo \"Tigase running pid=\"`cat $PIDFILE`\n\t\texit 0\n\tfi\n\texit 1\n\t;;\n\n zap)\n\trm -f $TIGASE_PID\n\t;;\n\n *)\n\techo \"Usage: /etc/init.d/tigase-server {start|stop|restart|force-reload|check}\" >&2\n\texit 1\n\t;;\nesac\n\nexit 0\n"
},
{
"path": "tigase-server 7.1.0/debian/tigase-server.install",
"content": "target/*.jar\tusr/share/tigase/lib\nscripts/*.sh\tusr/share/tigase/scripts\ndebian/*.sh\tusr/share/tigase/scripts\ndatabase\tusr/share/tigase\netc\t\tusr/share/tigase\netc/init.properties\tetc/tigase\ncerts\t\t\tetc/tigase\n*.html\t\tusr/share/doc/tigase-server\n"
},
{
"path": "tigase-server 7.1.0/debian/tigase-server.postinst",
"content": "#!/bin/sh -e\n\ncase \"$1\" in\n configure)\n\tif ! id tigase > /dev/null 2>&1 ; then\n\t adduser --system --home /usr/share/tigase --no-create-home \\\n\t\t--ingroup nogroup --disabled-password --shell /bin/false \\\n\t\ttigase\n\tfi\n\tchown tigase:adm /var/log/tigase\n\tchown tigase:root /etc/tigase /etc/tigase/certs \\\n\t\t/etc/tigase/certs/rsa-keystore /etc/tigase/certs/truststore \\\n\t\t/var/spool/tigase\n\tchmod 750 /var/log/tigase /var/spool/tigase \\\n\t\t/etc/tigase /etc/tigase/certs\n\tsed -i 's/$HOST_NAME/'`hostname --fqdn`'/g' /etc/tigase/init.properties*\n\n\tif grep -q 'db=derby$' /etc/tigase/init.properties\n\t\tDERBYDB=`sed -n 's/.*user-db-uri.*jdbc:derby://;s/;.*//p' /etc/tigase/init.properties`\n\tthen\n\t\tif [ -n \"$DERBYDB\" ] && [ ! -d \"$DERBYDB\" ] && [ -r /usr/lib/jvm/java-6-sun/db/lib/derby.jar ]\n\t\tthen\n\t\t\techo \"Creating Derby database for Tigase in \\`$DERBYDB' ...\"\n\t\t\tOLDCWD=`pwd`\n\t\t\tcd /usr/share/tigase\n\t\t\tscripts/derby-db-create.sh \"$DERBYDB\" >/dev/null\n\t\t\t[ -e derby.log ] && rm *.log\n\t\t\tchown -R tigase \"$DERBYDB\"\n\t\t\tcd $OLDCWD\n\t\tfi\n\tfi\n ;;\n\n abort-upgrade|abort-remove|abort-deconfigure)\n ;;\n\n *)\n\techo \"$0 called with unknown argument \\`$1'\" >&2\n\texit 1\n ;;\nesac\n\n#DEBHELPER#\n"
},
{
"path": "tigase-server 7.1.0/debian/tigase-server.postrm",
"content": "#!/bin/sh -e\n\n#DEBHELPER#\n\ncase \"$1\" in\n purge)\n\tuserdel tigase || true\n rm -rf /var/log/tigase /var/spool/tigase\n ;;\n\n remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)\n # Nothing to do here\n ;;\n\n *)\n echo \"$0 called with unknown argument \\`$1'\" >&2\n exit 1\n ;;\nesac\n"
},
{
"path": "tigase-server 7.1.0/debian/watch",
"content": "version=3\nhttp://www.tigase.org/files/downloads/tigase-server/tigase-server-(.*)\\.tar\\.gz debian uupdate\n"
},
{
"path": "tigase-server 7.1.0/etc/APNs_HTMessage_Dev.pem",
"content": "Bag Attributes\n friendlyName: Apple Development IOS Push Services: com.fanxinmsg.htmssage\n localKeyID: 5B 6C 87 73 6E 92 50 34 49 52 51 A2 6A 41 DB 96 8A 60 E4 66 \nsubject=/UID=com.fanxinmsg.htmssage/CN=Apple Development IOS Push Services: com.fanxinmsg.htmssage/OU=TQHAZ76T65/C=US\nissuer=/C=US/O=Apple Inc./OU=Apple Worldwide Developer Relations/CN=Apple Worldwide Developer Relations Certification Authority\n-----BEGIN CERTIFICATE-----\nMIIFkTCCBHmgAwIBAgIIcVR8mKzwXSAwDQYJKoZIhvcNAQEFBQAwgZYxCzAJBgNV\nBAYTAlVTMRMwEQYDVQQKDApBcHBsZSBJbmMuMSwwKgYDVQQLDCNBcHBsZSBXb3Js\nZHdpZGUgRGV2ZWxvcGVyIFJlbGF0aW9uczFEMEIGA1UEAww7QXBwbGUgV29ybGR3\naWRlIERldmVsb3BlciBSZWxhdGlvbnMgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkw\nHhcNMTcwMTAzMDU1MDQyWhcNMTgwMTAzMDU1MDQyWjCBkDEmMCQGCgmSJomT8ixk\nAQEMFmNvbS5mYW54aW5tc2cuaHRtc3NhZ2UxRDBCBgNVBAMMO0FwcGxlIERldmVs\nb3BtZW50IElPUyBQdXNoIFNlcnZpY2VzOiBjb20uZmFueGlubXNnLmh0bXNzYWdl\nMRMwEQYDVQQLDApUUUhBWjc2VDY1MQswCQYDVQQGEwJVUzCCASIwDQYJKoZIhvcN\nAQEBBQADggEPADCCAQoCggEBAPnjSNyC3DM3quWeZym8dgfIGeHl/b1/hfSbW6tx\nWn6tAfwGxjvytmRNp86lXk1nZNLzl4AteoPhqzYztsuKeaxsD8tQ8DfyZU12LGEn\nMcz5ZGadK6gLKhSzgMtNW8taWIuOEqz8VLesK+Rxdeq7O/LX6Vc1Cr7cnGufDWwu\nZyT4xpmI44GkfjG4OjTp4EP+BG7pH8XHN5MzSqFs9406RTCW3v9ixKjRKz5Iemr8\nQ1zXWA8ra5jHBwOLYxLy3SzQ2pgoiCLs3lO1MmfeShbYZANLY3DJwuAv/rBlWrPF\ngrPOsZIDTRHJeYOl/bmmOYkXG4dNr9HjOLnB52jIacqyO50CAwEAAaOCAeUwggHh\nMB0GA1UdDgQWBBRbbIdzbpJQNElSUaJqQduWimDkZjAJBgNVHRMEAjAAMB8GA1Ud\nIwQYMBaAFIgnFwmpthhgi+zruvZHWcVSVKO3MIIBDwYDVR0gBIIBBjCCAQIwgf8G\nCSqGSIb3Y2QFATCB8TCBwwYIKwYBBQUHAgIwgbYMgbNSZWxpYW5jZSBvbiB0aGlz\nIGNlcnRpZmljYXRlIGJ5IGFueSBwYXJ0eSBhc3N1bWVzIGFjY2VwdGFuY2Ugb2Yg\ndGhlIHRoZW4gYXBwbGljYWJsZSBzdGFuZGFyZCB0ZXJtcyBhbmQgY29uZGl0aW9u\ncyBvZiB1c2UsIGNlcnRpZmljYXRlIHBvbGljeSBhbmQgY2VydGlmaWNhdGlvbiBw\ncmFjdGljZSBzdGF0ZW1lbnRzLjApBggrBgEFBQcCARYdaHR0cDovL3d3dy5hcHBs\nZS5jb20vYXBwbGVjYS8wTQYDVR0fBEYwRDBCoECgPoY8aHR0cDovL2RldmVsb3Bl\nci5hcHBsZS5jb20vY2VydGlmaWNhdGlvbmF1dGhvcml0eS93d2RyY2EuY3JsMAsG\nA1UdDwQEAwIHgDATBgNVHSUEDDAKBggrBgEFBQcDAjAQBgoqhkiG92NkBgMBBAIF\nADANBgkqhkiG9w0BAQUFAAOCAQEAPDZc18IZn5e+5PGNgnH8y0yTNALeDqKbbgPs\n4+oci/zDGXwU1dyHPG1/2a5Q+YlRAQHhIHeXlRjtft+LDR1GhOWWrrI79WHaw2q0\n9CdTxnvRlXz9XrbUjo9DVyIpvidJuNXiG+KYhYHDCRFaMqPBC3gNd6Pj6073OKCX\nLTbGmuJo2/H5cO1/7B4+/AUNHqJG2DEH/YDwTSVcvHDm2APesPcNyvU94S111REO\n+3lDMYYCi7PpwhdWOPxBpyK6mlAmeHBkjlzk5dBrlePCqxjdERGhQflS1W1wqxz7\nRie3yW7WQxjYOUiAGx7C6Tpr9TFt2KN7OPsEGBJtYlXPDV8Btw==\n-----END CERTIFICATE-----\nBag Attributes\n friendlyName: apple\n localKeyID: 5B 6C 87 73 6E 92 50 34 49 52 51 A2 6A 41 DB 96 8A 60 E4 66 \nKey Attributes: \n-----BEGIN RSA PRIVATE KEY-----\nMIIEpAIBAAKCAQEA+eNI3ILcMzeq5Z5nKbx2B8gZ4eX9vX+F9Jtbq3Fafq0B/AbG\nO/K2ZE2nzqVeTWdk0vOXgC16g+GrNjO2y4p5rGwPy1DwN/JlTXYsYScxzPlkZp0r\nqAsqFLOAy01by1pYi44SrPxUt6wr5HF16rs78tfpVzUKvtyca58NbC5nJPjGmYjj\ngaR+Mbg6NOngQ/4Ebukfxcc3kzNKoWz3jTpFMJbe/2LEqNErPkh6avxDXNdYDytr\nmMcHA4tjEvLdLNDamCiIIuzeU7UyZ95KFthkA0tjcMnC4C/+sGVas8WCs86xkgNN\nEcl5g6X9uaY5iRcbh02v0eM4ucHnaMhpyrI7nQIDAQABAoIBAQCDH217MDuFsJ8/\nT+hIMTkqCijyrXGA/yp2WRM4GgnnULcq3Q8mI8zrQwhb2dBrA2cXfnSv8K1KCJ+D\nmI1Brs7719RN1pHGea4IgIr3C88JBJBXe/+NdRZGuI5Ln7McOLMfv5QzK1D09CYw\nAA1k94yUeBFcDlwuHKsDmfk8G/lJnyt6YdFB9vkJQO7nxmD+ro1q67RH9dIyIyAx\nkyWi9AFg/vn/X2Kmn+2HGR9wwAkPI8b4LPYnOivqPDJkeqzTJrZCoT/+vUc8goeB\nnqq4FKyfKN+i0ZaxQMuI/oNId0ZCPWyoM2OXh2DuqilXrOVuqIixd+2COHQnaDxv\npU4zpFxBAoGBAP/xH743M0cnia4FqREKYd++WpLiCWd/hqHw2F9uYfgYu21MUYCq\n6FnbR0BusAXckUbe+Ma8sra0xe6uPbpRWeqFKDWaYsqk1CJYs2ChpqTen8A1q9M5\nnzdQkUcO4pprjKGunifRvb0M+wAPP9B1mxlcm6RKd7oiMYiIF0f2UbNxAoGBAPnx\nzwmk/gXWzzFxA3LEYaNm6uE4cPb5K6mlFYErTUM43MEeltZh/Ep5fS8aXncUulw6\nAJ3BqEY9dIYNtMqdUtKdZLIlszx8kLWgIMcekBFBJBgq15d5i+0+qBJfDDt9erLY\ncbw6OYPMM5mfqeYuDZuVyolo9VYzXI9TYTv3etztAoGASrFd6C9H4b4iKg0w1+5F\nvfxZhoA86l2HNv+IxeD66mKdYDpjlr9J699Yne8vo6ZJJ3uu8qDjLvr2wL9M+HEB\nYrXVlD8oEaek2Rk10D+c2IS37mo7aPtqAcSbgTdQ3mwAsLa7JTfKvb9qCQxqPTX1\nO6ORMJMi+ck813GQCcpS8aECgYEA9ZyyWAbjfLdvGWW1/sSOMfVDoJhHIdsPFgDc\nlfcIUKODAt9dWEQnmMOzyWK/K4OZ8mEpE90m0Ac6BzVW0LgymDcEqa80Z5780Q4O\nx7z304zQvFL1UqulXjhxDsSKD7epqC/b7BzHQgWbOz5TxZbB1n8m7UrPs6p7LXjB\nFx2Fha0CgYA2+Yy/9itc+vrV0YotNpFirFXMFb7ihqHO1rQr0CEiPESHHpFZXN7/\nKDYAkdiysNNKuprsk2db6jpNFSfTtJY6t3XuwkDJoDdVQvDzSeJaQzH170v8AUUP\no5OzXAzOAwG5srWRgJVcvxjXMycFntiZSZT+xzT7VAuUTtFu9bVC9A==\n-----END RSA PRIVATE KEY-----\n"
},
{
"path": "tigase-server 7.1.0/etc/HTMessage_Dev_APNs.pem",
"content": "Bag Attributes\n friendlyName: Apple Development IOS Push Services: com.fanxinmsg.htmssage\n localKeyID: 5B 6C 87 73 6E 92 50 34 49 52 51 A2 6A 41 DB 96 8A 60 E4 66 \nsubject=/UID=com.fanxinmsg.htmssage/CN=Apple Development IOS Push Services: com.fanxinmsg.htmssage/OU=TQHAZ76T65/C=US\nissuer=/C=US/O=Apple Inc./OU=Apple Worldwide Developer Relations/CN=Apple Worldwide Developer Relations Certification Authority\n-----BEGIN CERTIFICATE-----\nMIIFkTCCBHmgAwIBAgIIcVR8mKzwXSAwDQYJKoZIhvcNAQEFBQAwgZYxCzAJBgNV\nBAYTAlVTMRMwEQYDVQQKDApBcHBsZSBJbmMuMSwwKgYDVQQLDCNBcHBsZSBXb3Js\nZHdpZGUgRGV2ZWxvcGVyIFJlbGF0aW9uczFEMEIGA1UEAww7QXBwbGUgV29ybGR3\naWRlIERldmVsb3BlciBSZWxhdGlvbnMgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkw\nHhcNMTcwMTAzMDU1MDQyWhcNMTgwMTAzMDU1MDQyWjCBkDEmMCQGCgmSJomT8ixk\nAQEMFmNvbS5mYW54aW5tc2cuaHRtc3NhZ2UxRDBCBgNVBAMMO0FwcGxlIERldmVs\nb3BtZW50IElPUyBQdXNoIFNlcnZpY2VzOiBjb20uZmFueGlubXNnLmh0bXNzYWdl\nMRMwEQYDVQQLDApUUUhBWjc2VDY1MQswCQYDVQQGEwJVUzCCASIwDQYJKoZIhvcN\nAQEBBQADggEPADCCAQoCggEBAPnjSNyC3DM3quWeZym8dgfIGeHl/b1/hfSbW6tx\nWn6tAfwGxjvytmRNp86lXk1nZNLzl4AteoPhqzYztsuKeaxsD8tQ8DfyZU12LGEn\nMcz5ZGadK6gLKhSzgMtNW8taWIuOEqz8VLesK+Rxdeq7O/LX6Vc1Cr7cnGufDWwu\nZyT4xpmI44GkfjG4OjTp4EP+BG7pH8XHN5MzSqFs9406RTCW3v9ixKjRKz5Iemr8\nQ1zXWA8ra5jHBwOLYxLy3SzQ2pgoiCLs3lO1MmfeShbYZANLY3DJwuAv/rBlWrPF\ngrPOsZIDTRHJeYOl/bmmOYkXG4dNr9HjOLnB52jIacqyO50CAwEAAaOCAeUwggHh\nMB0GA1UdDgQWBBRbbIdzbpJQNElSUaJqQduWimDkZjAJBgNVHRMEAjAAMB8GA1Ud\nIwQYMBaAFIgnFwmpthhgi+zruvZHWcVSVKO3MIIBDwYDVR0gBIIBBjCCAQIwgf8G\nCSqGSIb3Y2QFATCB8TCBwwYIKwYBBQUHAgIwgbYMgbNSZWxpYW5jZSBvbiB0aGlz\nIGNlcnRpZmljYXRlIGJ5IGFueSBwYXJ0eSBhc3N1bWVzIGFjY2VwdGFuY2Ugb2Yg\ndGhlIHRoZW4gYXBwbGljYWJsZSBzdGFuZGFyZCB0ZXJtcyBhbmQgY29uZGl0aW9u\ncyBvZiB1c2UsIGNlcnRpZmljYXRlIHBvbGljeSBhbmQgY2VydGlmaWNhdGlvbiBw\ncmFjdGljZSBzdGF0ZW1lbnRzLjApBggrBgEFBQcCARYdaHR0cDovL3d3dy5hcHBs\nZS5jb20vYXBwbGVjYS8wTQYDVR0fBEYwRDBCoECgPoY8aHR0cDovL2RldmVsb3Bl\nci5hcHBsZS5jb20vY2VydGlmaWNhdGlvbmF1dGhvcml0eS93d2RyY2EuY3JsMAsG\nA1UdDwQEAwIHgDATBgNVHSUEDDAKBggrBgEFBQcDAjAQBgoqhkiG92NkBgMBBAIF\nADANBgkqhkiG9w0BAQUFAAOCAQEAPDZc18IZn5e+5PGNgnH8y0yTNALeDqKbbgPs\n4+oci/zDGXwU1dyHPG1/2a5Q+YlRAQHhIHeXlRjtft+LDR1GhOWWrrI79WHaw2q0\n9CdTxnvRlXz9XrbUjo9DVyIpvidJuNXiG+KYhYHDCRFaMqPBC3gNd6Pj6073OKCX\nLTbGmuJo2/H5cO1/7B4+/AUNHqJG2DEH/YDwTSVcvHDm2APesPcNyvU94S111REO\n+3lDMYYCi7PpwhdWOPxBpyK6mlAmeHBkjlzk5dBrlePCqxjdERGhQflS1W1wqxz7\nRie3yW7WQxjYOUiAGx7C6Tpr9TFt2KN7OPsEGBJtYlXPDV8Btw==\n-----END CERTIFICATE-----\nBag Attributes\n friendlyName: apple\n localKeyID: 5B 6C 87 73 6E 92 50 34 49 52 51 A2 6A 41 DB 96 8A 60 E4 66 \nKey Attributes: \n-----BEGIN RSA PRIVATE KEY-----\nMIIEpAIBAAKCAQEA+eNI3ILcMzeq5Z5nKbx2B8gZ4eX9vX+F9Jtbq3Fafq0B/AbG\nO/K2ZE2nzqVeTWdk0vOXgC16g+GrNjO2y4p5rGwPy1DwN/JlTXYsYScxzPlkZp0r\nqAsqFLOAy01by1pYi44SrPxUt6wr5HF16rs78tfpVzUKvtyca58NbC5nJPjGmYjj\ngaR+Mbg6NOngQ/4Ebukfxcc3kzNKoWz3jTpFMJbe/2LEqNErPkh6avxDXNdYDytr\nmMcHA4tjEvLdLNDamCiIIuzeU7UyZ95KFthkA0tjcMnC4C/+sGVas8WCs86xkgNN\nEcl5g6X9uaY5iRcbh02v0eM4ucHnaMhpyrI7nQIDAQABAoIBAQCDH217MDuFsJ8/\nT+hIMTkqCijyrXGA/yp2WRM4GgnnULcq3Q8mI8zrQwhb2dBrA2cXfnSv8K1KCJ+D\nmI1Brs7719RN1pHGea4IgIr3C88JBJBXe/+NdRZGuI5Ln7McOLMfv5QzK1D09CYw\nAA1k94yUeBFcDlwuHKsDmfk8G/lJnyt6YdFB9vkJQO7nxmD+ro1q67RH9dIyIyAx\nkyWi9AFg/vn/X2Kmn+2HGR9wwAkPI8b4LPYnOivqPDJkeqzTJrZCoT/+vUc8goeB\nnqq4FKyfKN+i0ZaxQMuI/oNId0ZCPWyoM2OXh2DuqilXrOVuqIixd+2COHQnaDxv\npU4zpFxBAoGBAP/xH743M0cnia4FqREKYd++WpLiCWd/hqHw2F9uYfgYu21MUYCq\n6FnbR0BusAXckUbe+Ma8sra0xe6uPbpRWeqFKDWaYsqk1CJYs2ChpqTen8A1q9M5\nnzdQkUcO4pprjKGunifRvb0M+wAPP9B1mxlcm6RKd7oiMYiIF0f2UbNxAoGBAPnx\nzwmk/gXWzzFxA3LEYaNm6uE4cPb5K6mlFYErTUM43MEeltZh/Ep5fS8aXncUulw6\nAJ3BqEY9dIYNtMqdUtKdZLIlszx8kLWgIMcekBFBJBgq15d5i+0+qBJfDDt9erLY\ncbw6OYPMM5mfqeYuDZuVyolo9VYzXI9TYTv3etztAoGASrFd6C9H4b4iKg0w1+5F\nvfxZhoA86l2HNv+IxeD66mKdYDpjlr9J699Yne8vo6ZJJ3uu8qDjLvr2wL9M+HEB\nYrXVlD8oEaek2Rk10D+c2IS37mo7aPtqAcSbgTdQ3mwAsLa7JTfKvb9qCQxqPTX1\nO6ORMJMi+ck813GQCcpS8aECgYEA9ZyyWAbjfLdvGWW1/sSOMfVDoJhHIdsPFgDc\nlfcIUKODAt9dWEQnmMOzyWK/K4OZ8mEpE90m0Ac6BzVW0LgymDcEqa80Z5780Q4O\nx7z304zQvFL1UqulXjhxDsSKD7epqC/b7BzHQgWbOz5TxZbB1n8m7UrPs6p7LXjB\nFx2Fha0CgYA2+Yy/9itc+vrV0YotNpFirFXMFb7ihqHO1rQr0CEiPESHHpFZXN7/\nKDYAkdiysNNKuprsk2db6jpNFSfTtJY6t3XuwkDJoDdVQvDzSeJaQzH170v8AUUP\no5OzXAzOAwG5srWRgJVcvxjXMycFntiZSZT+xzT7VAuUTtFu9bVC9A==\n-----END RSA PRIVATE KEY-----\n"
},
{
"path": "tigase-server 7.1.0/etc/bosh-extra-headers.txt",
"content": "Access-Control-Allow-Origin: *\nAccess-Control-Allow-Methods: GET, POST, OPTIONS\nAccess-Control-Allow-Headers: Content-Type\nAccess-Control-Max-Age: 86400\n"
},
{
"path": "tigase-server 7.1.0/etc/client-access-policy.xml",
"content": "\n\n \n \n \n \n \n \n \n \n \n \n"
},
{
"path": "tigase-server 7.1.0/etc/config-dump.properties",
"content": "sess-man/plugins-conf/message-archive-xep-0136/required-store-method[S]=message\nsess-man/plugins-conf/urn:ietf:params:xml:ns:xmpp-bind/apns-token-db-uri[S]=jdbc:mysql://127.0.0.1:3306/tigase?user=tigase&password=123456&useUnicode=true&characterEncoding=UTF8\nsess-man/plugins-conf/enabled-mechanisms[S]=ANONYMOUS,PLAIN\nsess-man/component-id[S]=sess-man@izwz98w1n1tjfj7xt5ljyqz\nsess-man/def-hostname[S]=izwz98w1n1tjfj7xt5ljyqz\nsess-man/admins[s]=admin@app.im\nsess-man/scripts-dir[S]=scripts/admin\nsess-man/command/ALL[S]=ADMIN\nsess-man/max-queue-size[I]=5060\nsess-man/scheduler-threads[I]=1\nsess-man/incoming-filters[S]=tigase.server.filters.PacketCounter\nsess-man/outgoing-filters[S]=tigase.server.filters.PacketCounter\nsess-man/admin-scripts-dir[S]=scripts/admin/\nsess-man/plugins[s]=session-close, session-open, default-handler, jabber:iq:register, jabber:iq:auth, urn:ietf:params:xml:ns:xmpp-sasl, urn:ietf:params:xml:ns:xmpp-bind, urn:ietf:params:xml:ns:xmpp-session, jabber:iq:roster, jabber:iq:privacy, jabber:iq:version, http://jabber.org/protocol/stats, starttls, vcard-temp, http://jabber.org/protocol/commands, jabber:iq:private, urn:xmpp:ping, presence-state, presence-subscription, disco, domain-filter, zlib, amp, message-carbons, vcard-xep-0292, urn:xmpp:time, urn:xmpp:csi:0, urn:xmpp:receipts, message-push, message-archive-xep-0136\nsess-man/plugins-concurrency[S]=\nsess-man/skip-privacy[B]=false\nsess-man/offline-user-autocreate[S]=false\nsess-man/sm-threads-pool[S]=default\nsess-man/force-detail-stale-connection-check[B]=true\nsess-man/stale-connection-closer-queue-size[I]=1000\nsess-man/auth-timeout[L]=120\nsess-man/sm-threads-factor[I]=1\nbasic-conf/logging/tigase.http.level[S]=FINEST\nbasic-conf/logging/tigase.xmpp.impl.level[S]=FINE\nbasic-conf/logging/tigase.muc.level[S]=FINE\nbasic-conf/logging/tigase.apns.level[S]=FINE\nbasic-conf/logging/tigase.db.jdbc.level[S]=FINER\nbasic-conf/component-id[S]=basic-conf@izwz98w1n1tjfj7xt5ljyqz\nbasic-conf/def-hostname[S]=izwz98w1n1tjfj7xt5ljyqz\nbasic-conf/admins[s]=admin@app.im\nbasic-conf/scripts-dir[S]=scripts/admin\nbasic-conf/command/ALL[S]=ADMIN\nbasic-conf/logging/.level[S]=CONFIG\nbasic-conf/logging/handlers[S]=java.util.logging.ConsoleHandler java.util.logging.FileHandler\nbasic-conf/logging/java.util.logging.ConsoleHandler.formatter[S]=tigase.util.LogFormatter\nbasic-conf/logging/java.util.logging.ConsoleHandler.level[S]=WARNING\nbasic-conf/logging/java.util.logging.FileHandler.append[S]=true\nbasic-conf/logging/java.util.logging.FileHandler.count[S]=5\nbasic-conf/logging/java.util.logging.FileHandler.formatter[S]=tigase.util.LogFormatter\nbasic-conf/logging/java.util.logging.FileHandler.limit[S]=10000000\nbasic-conf/logging/java.util.logging.FileHandler.pattern[S]=logs/tigase.log\nbasic-conf/logging/tigase.useParentHandlers[S]=true\nbasic-conf/logging/java.util.logging.FileHandler.level[S]=ALL\nbasic-conf/user-domain-repo-pool[S]=tigase.db.UserRepositoryMDImpl\nbasic-conf/auth-domain-repo-pool[S]=tigase.db.AuthRepositoryMDImpl\nbasic-conf/user-repo-pool-size[I]=10\nbasic-conf/data-repo-pool-size[I]=10\nbasic-conf/user-repo-class[S]=mysql\nbasic-conf/user-repo-url[S]=jdbc:mysql://127.0.0.1:3306/tigase?user=tigase&password=123456&useUnicode=true&characterEncoding=UTF-8&zeroDateTimeBehavior=convertToNull\nbasic-conf/auth-repo-class[S]=tigase.db.jdbc.TigaseCustomAuth\nbasic-conf/auth-repo-url[S]=jdbc:mysql://127.0.0.1:3306/tigase?user=tigase&password=123456&useUnicode=true&characterEncoding=UTF-8&zeroDateTimeBehavior=convertToNull\nbasic-conf/ssl-container-class[S]=tigase.io.jdk18.SNISSLContextContainer\nbasic-conf/ssl-certs-location[S]=certs/\nbasic-conf/ssl-def-cert-domain[S]=default\nbasic-conf/config-dump-file[S]=etc/config-dump.properties\nhttp/http/ports[i]=19080, 19081\nhttp/api-keys[s]=open_access\nhttp/component-id[S]=http@izwz98w1n1tjfj7xt5ljyqz\nhttp/def-hostname[S]=izwz98w1n1tjfj7xt5ljyqz\nhttp/admins[s]=admin@app.im\nhttp/scripts-dir[S]=scripts/admin\nhttp/command/ALL[S]=ADMIN\nhttp/max-queue-size[I]=506\nhttp/scheduler-threads[I]=1\nhttp/incoming-filters[S]=tigase.server.filters.PacketCounter\nhttp/outgoing-filters[S]=tigase.server.filters.PacketCounter\nhttp/http/server-class[S]=tigase.http.java.JavaStandaloneHttpServer\nmessage-archive/auto[S]=true\nmessage-archive/component-id[S]=message-archive@izwz98w1n1tjfj7xt5ljyqz\nmessage-archive/def-hostname[S]=izwz98w1n1tjfj7xt5ljyqz\nmessage-archive/admins[s]=admin@app.im\nmessage-archive/scripts-dir[S]=scripts/admin\nmessage-archive/command/ALL[S]=ADMIN\nmessage-archive/max-queue-size[I]=506\nmessage-archive/scheduler-threads[I]=1\nmessage-archive/incoming-filters[S]=tigase.server.filters.PacketCounter\nmessage-archive/outgoing-filters[S]=tigase.server.filters.PacketCounter\nmessage-archive/tags-support[B]=false\nmessage-archive/archive-repo-uri[S]=jdbc:mysql://127.0.0.1:3306/tigase?user=tigase&password=123456&useUnicode=true&characterEncoding=UTF-8&zeroDateTimeBehavior=convertToNull\nmessage-archive/remove-expired-messages-delay[S]=PT1H\nmessage-archive/remove-expired-messages-period[S]=P1D\nmessage-archive/remove-expired-messages[B]=false\namp/store-limit[L]=10000\namp/component-id[S]=amp@izwz98w1n1tjfj7xt5ljyqz\namp/def-hostname[S]=izwz98w1n1tjfj7xt5ljyqz\namp/admins[s]=admin@app.im\namp/scripts-dir[S]=scripts/admin\namp/command/ALL[S]=ADMIN\namp/max-queue-size[I]=506\namp/scheduler-threads[I]=1\namp/incoming-filters[S]=tigase.server.filters.PacketCounter\namp/outgoing-filters[S]=tigase.server.filters.PacketCounter\namp/security-level[S]=STRICT\namp/amp-repo-uri[S]=jdbc:mysql://127.0.0.1:3306/tigase?user=tigase&password=123456&useUnicode=true&characterEncoding=UTF-8&zeroDateTimeBehavior=convertToNull\nmessage-router/component-id[S]=message-router@izwz98w1n1tjfj7xt5ljyqz\nmessage-router/def-hostname[S]=izwz98w1n1tjfj7xt5ljyqz\nmessage-router/admins[s]=admin@app.im\nmessage-router/scripts-dir[S]=scripts/admin\nmessage-router/command/ALL[S]=ADMIN\nmessage-router/max-queue-size[I]=5060\nmessage-router/scheduler-threads[I]=1\nmessage-router/incoming-filters[S]=tigase.server.filters.PacketCounter\nmessage-router/outgoing-filters[S]=tigase.server.filters.PacketCounter\nmessage-router/components/msg-receivers/message-archive.class[S]=tigase.archive.MessageArchiveComponent\nmessage-router/components/msg-receivers/message-archive.active[B]=true\nmessage-router/components/msg-receivers/http.class[S]=tigase.http.HttpMessageReceiver\nmessage-router/components/msg-receivers/http.active[B]=true\nmessage-router/components/msg-receivers/id-names[s]=amp, bosh, c2s, eventbus, http, message-archive, monitor, s2s, sess-man, ws2s\nmessage-router/components/msg-receivers/amp.class[S]=tigase.server.amp.AmpComponent\nmessage-router/components/msg-receivers/amp.active[B]=true\nmessage-router/components/msg-receivers/bosh.class[S]=tigase.server.bosh.BoshConnectionManager\nmessage-router/components/msg-receivers/bosh.active[B]=true\nmessage-router/components/msg-receivers/c2s.class[S]=tigase.server.xmppclient.ClientConnectionManager\nmessage-router/components/msg-receivers/c2s.active[B]=true\nmessage-router/components/msg-receivers/eventbus.class[S]=tigase.disteventbus.component.EventBusComponent\nmessage-router/components/msg-receivers/eventbus.active[B]=true\nmessage-router/components/msg-receivers/monitor.class[S]=tigase.monitor.MonitorComponent\nmessage-router/components/msg-receivers/monitor.active[B]=true\nmessage-router/components/msg-receivers/s2s.class[S]=tigase.server.xmppserver.S2SConnectionManager\nmessage-router/components/msg-receivers/s2s.active[B]=true\nmessage-router/components/msg-receivers/sess-man.class[S]=tigase.server.xmppsession.SessionManager\nmessage-router/components/msg-receivers/sess-man.active[B]=true\nmessage-router/components/msg-receivers/ws2s.class[S]=tigase.server.websocket.WebSocketClientConnectionManager\nmessage-router/components/msg-receivers/ws2s.active[B]=true\nmessage-router/components/registrators/id-names[s]=vhost-man, stats\nmessage-router/components/registrators/vhost-man.class[S]=tigase.vhosts.VHostManager\nmessage-router/components/registrators/vhost-man.active[B]=true\nmessage-router/components/registrators/stats.class[S]=tigase.stats.StatisticsCollector\nmessage-router/components/registrators/stats.active[B]=true\nmessage-router/hostnames[s]=app.im\nmessage-router/disco-name[S]=Tigase\nmessage-router/disco-show-version[B]=true\nmessage-router/updates-checking[B]=true\nmessage-router/updates-checking-interval[L]=7\nvhost-man/component-id[S]=vhost-man@izwz98w1n1tjfj7xt5ljyqz\nvhost-man/def-hostname[S]=izwz98w1n1tjfj7xt5ljyqz\nvhost-man/admins[s]=admin@app.im\nvhost-man/scripts-dir[S]=scripts/admin\nvhost-man/command/ALL[S]=ADMIN\nvhost-man/repository-class[S]=tigase.vhosts.VHostJDBCRepository\nvhost-man/hostnames[s]=app.im\nvhost-man/dns-srv-def-addr[S]=izwz98w1n1tjfj7xt5ljyqz\nvhost-man/dns-def-ip[S]=10.30.210.67\nvhost-man/domains-per-user-limit[I]=25\nstats/component-id[S]=stats@izwz98w1n1tjfj7xt5ljyqz\nstats/def-hostname[S]=izwz98w1n1tjfj7xt5ljyqz\nstats/admins[s]=admin@app.im\nstats/scripts-dir[S]=scripts/admin\nstats/command/ALL[S]=ADMIN\nstats/stats-history-size[I]=0\nstats/stats-update-interval[L]=10\nbosh/component-id[S]=bosh@izwz98w1n1tjfj7xt5ljyqz\nbosh/def-hostname[S]=izwz98w1n1tjfj7xt5ljyqz\nbosh/admins[s]=admin@app.im\nbosh/scripts-dir[S]=scripts/admin\nbosh/command/ALL[S]=ADMIN\nbosh/max-queue-size[I]=5060\nbosh/scheduler-threads[I]=1\nbosh/incoming-filters[S]=tigase.server.filters.PacketCounter\nbosh/outgoing-filters[S]=tigase.server.filters.PacketCounter\nbosh/connections/tls/use[B]=true\nbosh/net-buffer[I]=2048\nbosh/traffic-throttling[S]=xmpp:2500:0:disc,bin:20m:0:disc\nbosh/net-buffer-limit[I]=2097152\nbosh/elements-number-limit[I]=1000\nbosh/watchdog_delay[L]=600000\nbosh/watchdog_timeout[L]=1740000\nbosh/watchdog_ping_type[S]=WHITESPACE\nbosh/connections/5280/type[S]=accept\nbosh/connections/5280/socket[S]=plain\nbosh/connections/5280/ifc[s]=*\nbosh/connections/5280/remote-host[S]=localhost\nbosh/connections/5280/connections/tls/required[B]=false\nbosh/connections/ports[i]=5280\nbosh/white-char-ack[B]=false\nbosh/xmpp-ack[B]=false\nbosh/max-inactivity-time[L]=600\nbosh/cm-see-other-host[S]=\nbosh/routings/multi-mode[B]=true\nbosh/routings/.+[S]=sess-man@izwz98w1n1tjfj7xt5ljyqz\nbosh/socket-close-wait[L]=1\nbosh/tls-want-client-auth-enabled[B]=false\nbosh/max-wait[L]=30\nbosh/min-polling[L]=10\nbosh/max-inactivity[L]=10\nbosh/concurrent-requests[I]=2\nbosh/hold-requests[I]=1\nbosh/max-batch-size[I]=15\nbosh/batch-queue-timeout[L]=100\nbosh/max-session-waiting-packets[I]=100\nbosh/send-node-hostname[B]=true\nbosh/sid-logger-level[S]=OFF\nc2s/component-id[S]=c2s@izwz98w1n1tjfj7xt5ljyqz\nc2s/def-hostname[S]=izwz98w1n1tjfj7xt5ljyqz\nc2s/admins[s]=admin@app.im\nc2s/scripts-dir[S]=scripts/admin\nc2s/command/ALL[S]=ADMIN\nc2s/max-queue-size[I]=5060\nc2s/scheduler-threads[I]=1\nc2s/incoming-filters[S]=tigase.server.filters.PacketCounter\nc2s/outgoing-filters[S]=tigase.server.filters.PacketCounter\nc2s/connections/tls/use[B]=true\nc2s/net-buffer[I]=2048\nc2s/traffic-throttling[S]=xmpp:2500:0:disc,bin:20m:0:disc\nc2s/net-buffer-limit[I]=2097152\nc2s/elements-number-limit[I]=1000\nc2s/watchdog_delay[L]=600000\nc2s/watchdog_timeout[L]=1740000\nc2s/watchdog_ping_type[S]=WHITESPACE\nc2s/connections/5222/type[S]=accept\nc2s/connections/5222/socket[S]=plain\nc2s/connections/5222/ifc[s]=*\nc2s/connections/5222/remote-host[S]=localhost\nc2s/connections/5222/connections/tls/required[B]=false\nc2s/connections/5223/type[S]=accept\nc2s/connections/5223/socket[S]=ssl\nc2s/connections/5223/ifc[s]=*\nc2s/connections/5223/remote-host[S]=localhost\nc2s/connections/5223/connections/tls/required[B]=false\nc2s/connections/ports[i]=5222, 5223\nc2s/white-char-ack[B]=false\nc2s/xmpp-ack[B]=false\nc2s/max-inactivity-time[L]=86400\nc2s/cm-see-other-host[S]=\nc2s/routings/multi-mode[B]=true\nc2s/routings/.+[S]=sess-man@izwz98w1n1tjfj7xt5ljyqz\nc2s/socket-close-wait[L]=1\nc2s/tls-want-client-auth-enabled[B]=false\neventbus/component-id[S]=eventbus@izwz98w1n1tjfj7xt5ljyqz\neventbus/def-hostname[S]=izwz98w1n1tjfj7xt5ljyqz\neventbus/admins[s]=admin@app.im\neventbus/scripts-dir[S]=scripts/admin\neventbus/command/ALL[S]=ADMIN\neventbus/max-queue-size[I]=506\neventbus/scheduler-threads[I]=1\neventbus/incoming-filters[S]=tigase.server.filters.PacketCounter\neventbus/outgoing-filters[S]=tigase.server.filters.PacketCounter\neventbus/modules/jabber:iq:version[S]=tigase.component.modules.impl.JabberVersionModule\neventbus/modules/receiver[S]=tigase.disteventbus.component.EventReceiverModule\neventbus/modules/subscribe[S]=tigase.disteventbus.component.SubscribeModule\neventbus/modules/unsubscribe[S]=tigase.disteventbus.component.UnsubscribeModule\neventbus/modules/urn:xmpp:ping[S]=tigase.component.modules.impl.XmppPingModule\neventbus/modules/disco[S]=tigase.component.modules.impl.DiscoveryModule\neventbus/modules/publisher[S]=tigase.disteventbus.component.EventPublisherModule\neventbus/modules/commands[S]=tigase.component.modules.impl.AdHocCommandModule\nmonitor/component-id[S]=monitor@izwz98w1n1tjfj7xt5ljyqz\nmonitor/def-hostname[S]=izwz98w1n1tjfj7xt5ljyqz\nmonitor/admins[s]=admin@app.im\nmonitor/scripts-dir[S]=scripts/admin\nmonitor/command/ALL[S]=ADMIN\nmonitor/max-queue-size[I]=506\nmonitor/scheduler-threads[I]=1\nmonitor/incoming-filters[S]=tigase.server.filters.PacketCounter\nmonitor/outgoing-filters[S]=tigase.server.filters.PacketCounter\nmonitor/modules/jabber:iq:version[S]=tigase.component.modules.impl.JabberVersionModule\nmonitor/modules/urn:xmpp:ping[S]=tigase.component.modules.impl.XmppPingModule\nmonitor/modules/disco[S]=tigase.monitor.modules.DiscoveryMonitorModule\nmonitor/modules/commands[S]=tigase.monitor.modules.AdHocCommandMonitorModule\ns2s/component-id[S]=s2s@izwz98w1n1tjfj7xt5ljyqz\ns2s/def-hostname[S]=izwz98w1n1tjfj7xt5ljyqz\ns2s/admins[s]=admin@app.im\ns2s/scripts-dir[S]=scripts/admin\ns2s/command/ALL[S]=ADMIN\ns2s/max-queue-size[I]=506\ns2s/scheduler-threads[I]=1\ns2s/incoming-filters[S]=tigase.server.filters.PacketCounter\ns2s/outgoing-filters[S]=tigase.server.filters.PacketCounter\ns2s/connections/tls/use[B]=true\ns2s/net-buffer[I]=65536\ns2s/traffic-throttling[S]=xmpp:15k:0:disc,bin:120m:0:disc\ns2s/net-buffer-limit[I]=20971520\ns2s/elements-number-limit[I]=1000\ns2s/watchdog_delay[L]=600000\ns2s/watchdog_timeout[L]=1740000\ns2s/watchdog_ping_type[S]=WHITESPACE\ns2s/connections/5269/type[S]=accept\ns2s/connections/5269/socket[S]=plain\ns2s/connections/5269/ifc[s]=*\ns2s/connections/5269/remote-host[S]=localhost\ns2s/connections/5269/connections/tls/required[B]=false\ns2s/connections/ports[i]=5269\ns2s/white-char-ack[B]=false\ns2s/xmpp-ack[B]=false\ns2s/max-inactivity-time[L]=900\ns2s/max-packet-waiting-time[L]=420\ns2s/max-in-conns[I]=4\ns2s/max-out-total-conns[I]=1\ns2s/max-out-per-ip-conns[I]=1\ns2s/s2s-conn-selector[S]=tigase.server.xmppserver.S2SRandomSelector\ns2s/cid-connections-tasks-threads[I]=1\ns2s/s2s-domain-mapping[S]=\nws2s/component-id[S]=ws2s@izwz98w1n1tjfj7xt5ljyqz\nws2s/def-hostname[S]=izwz98w1n1tjfj7xt5ljyqz\nws2s/admins[s]=admin@app.im\nws2s/scripts-dir[S]=scripts/admin\nws2s/command/ALL[S]=ADMIN\nws2s/max-queue-size[I]=5060\nws2s/scheduler-threads[I]=1\nws2s/incoming-filters[S]=tigase.server.filters.PacketCounter\nws2s/outgoing-filters[S]=tigase.server.filters.PacketCounter\nws2s/connections/tls/use[B]=true\nws2s/net-buffer[I]=2048\nws2s/traffic-throttling[S]=xmpp:2500:0:disc,bin:20m:0:disc\nws2s/net-buffer-limit[I]=2097152\nws2s/elements-number-limit[I]=1000\nws2s/watchdog_delay[L]=600000\nws2s/watchdog_timeout[L]=1740000\nws2s/watchdog_ping_type[S]=WHITESPACE\nws2s/connections/5290/type[S]=accept\nws2s/connections/5290/socket[S]=plain\nws2s/connections/5290/ifc[s]=*\nws2s/connections/5290/remote-host[S]=localhost\nws2s/connections/5290/connections/tls/required[B]=false\nws2s/connections/ports[i]=5290\nws2s/white-char-ack[B]=false\nws2s/xmpp-ack[B]=false\nws2s/max-inactivity-time[L]=86400\nws2s/cm-see-other-host[S]=\nws2s/routings/multi-mode[B]=true\nws2s/routings/.+[S]=sess-man@izwz98w1n1tjfj7xt5ljyqz\nws2s/socket-close-wait[L]=1\nws2s/tls-want-client-auth-enabled[B]=false\nws2s/protocol-versions[s]=hybi\n"
},
{
"path": "tigase-server 7.1.0/etc/cross-domain-policy.xml",
"content": "\n\n \n \n\n"
},
{
"path": "tigase-server 7.1.0/etc/htmessage_production_APNs.pem",
"content": "Bag Attributes\n friendlyName: Apple Push Services: com.fanxinmsg.htmssage\n localKeyID: 3F 5E 98 55 0A 59 11 29 B1 39 40 8F FD B6 39 16 69 DB 1D 01 \nsubject=/UID=com.fanxinmsg.htmssage/CN=Apple Push Services: com.fanxinmsg.htmssage/OU=TQHAZ76T65/O=Hefei Palm Peak Technology Co., Ltd./C=US\nissuer=/C=US/O=Apple Inc./OU=Apple Worldwide Developer Relations/CN=Apple Worldwide Developer Relations Certification Authority\n-----BEGIN CERTIFICATE-----\nMIIGRDCCBSygAwIBAgIIC5vm99Uw+38wDQYJKoZIhvcNAQELBQAwgZYxCzAJBgNV\nBAYTAlVTMRMwEQYDVQQKDApBcHBsZSBJbmMuMSwwKgYDVQQLDCNBcHBsZSBXb3Js\nZHdpZGUgRGV2ZWxvcGVyIFJlbGF0aW9uczFEMEIGA1UEAww7QXBwbGUgV29ybGR3\naWRlIERldmVsb3BlciBSZWxhdGlvbnMgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkw\nHhcNMTcwMzA5MDIxNDM1WhcNMTgwNDA4MDIxNDM1WjCBrzEmMCQGCgmSJomT8ixk\nAQEMFmNvbS5mYW54aW5tc2cuaHRtc3NhZ2UxNDAyBgNVBAMMK0FwcGxlIFB1c2gg\nU2VydmljZXM6IGNvbS5mYW54aW5tc2cuaHRtc3NhZ2UxEzARBgNVBAsMClRRSEFa\nNzZUNjUxLTArBgNVBAoMJEhlZmVpIFBhbG0gUGVhayBUZWNobm9sb2d5IENvLiwg\nTHRkLjELMAkGA1UEBhMCVVMwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB\nAQDHNLE+jn2wrPq0N701D7mfd68sfn8FpgYxkntI+fSICrBDoTQNAai6deKLTX33\nKAO6+uxNyjsibEfJ9NtJ2YMO/kk7gN1KhfJtIrWKmjpjJ+F4G/TagQuEavVfR26+\nQoXNShycnSAF8D6/FSpuZGZ50mzpuBDHElZ+f8kk74zvpKB9oeR3TnjQHzSd9P0V\n/bcdtdBLYsEAWoX2V1v5K1gImD8OXzn735MhiqZx+4oxuiQ7fXfolnwU1AOabfEc\nnLvybtxxhWSe4p1Pe3ZXYtPpwWin9W/QZZ+ZufGjmAvWYQrZq8nZAQNX1ci4AVRU\nKziNoNsNOhTsV1txdUM0H0BNAgMBAAGjggJ5MIICdTAdBgNVHQ4EFgQUP16YVQpZ\nESmxOUCP/bY5FmnbHQEwDAYDVR0TAQH/BAIwADAfBgNVHSMEGDAWgBSIJxcJqbYY\nYIvs67r2R1nFUlSjtzCCARwGA1UdIASCARMwggEPMIIBCwYJKoZIhvdjZAUBMIH9\nMIHDBggrBgEFBQcCAjCBtgyBs1JlbGlhbmNlIG9uIHRoaXMgY2VydGlmaWNhdGUg\nYnkgYW55IHBhcnR5IGFzc3VtZXMgYWNjZXB0YW5jZSBvZiB0aGUgdGhlbiBhcHBs\naWNhYmxlIHN0YW5kYXJkIHRlcm1zIGFuZCBjb25kaXRpb25zIG9mIHVzZSwgY2Vy\ndGlmaWNhdGUgcG9saWN5IGFuZCBjZXJ0aWZpY2F0aW9uIHByYWN0aWNlIHN0YXRl\nbWVudHMuMDUGCCsGAQUFBwIBFilodHRwOi8vd3d3LmFwcGxlLmNvbS9jZXJ0aWZp\nY2F0ZWF1dGhvcml0eTAwBgNVHR8EKTAnMCWgI6Ahhh9odHRwOi8vY3JsLmFwcGxl\nLmNvbS93d2RyY2EuY3JsMA4GA1UdDwEB/wQEAwIHgDATBgNVHSUEDDAKBggrBgEF\nBQcDAjAQBgoqhkiG92NkBgMBBAIFADAQBgoqhkiG92NkBgMCBAIFADCBiQYKKoZI\nhvdjZAYDBgR7MHkMFmNvbS5mYW54aW5tc2cuaHRtc3NhZ2UwBQwDYXBwDBtjb20u\nZmFueGlubXNnLmh0bXNzYWdlLnZvaXAwBgwEdm9pcAwjY29tLmZhbnhpbm1zZy5o\ndG1zc2FnZS5jb21wbGljYXRpb24wDgwMY29tcGxpY2F0aW9uMA0GCSqGSIb3DQEB\nCwUAA4IBAQAFS4u12Ob5s/dvhwO9+ZREo5Jm/MlBthxEN/7gM0oxkMTh+LiPOWwK\n44UFFlFWTOnUP5jl/xjurozS9n4oKA/BS2QDN1sQVR/bidaIAQUn5ZfEz68RDfHW\nrO9Dqzf/Q9gcCU+kY0NC62C1wJ1o0i5qmN04+cgUBvm0B8x26fFDS4TiCrfWyM2P\nSzXmoshivHRMIgtiJVdpizw3qtQTOjiWb26pQfXxTodremlEFZOOL0B9+rnySR8w\nSw79xoug+2M0QRDZ4fA0itsE2tEliVQRBmXLF2f1JoyyYClL/yf8yKRf6RQDFT3X\nZyrQy8ctl8L1FOg676DqsmVZhsgbwQcX\n-----END CERTIFICATE-----\nBag Attributes\n friendlyName: apple\n localKeyID: 3F 5E 98 55 0A 59 11 29 B1 39 40 8F FD B6 39 16 69 DB 1D 01 \nKey Attributes: \n-----BEGIN RSA PRIVATE KEY-----\nMIIEogIBAAKCAQEAxzSxPo59sKz6tDe9NQ+5n3evLH5/BaYGMZJ7SPn0iAqwQ6E0\nDQGounXii0199ygDuvrsTco7ImxHyfTbSdmDDv5JO4DdSoXybSK1ipo6YyfheBv0\n2oELhGr1X0duvkKFzUocnJ0gBfA+vxUqbmRmedJs6bgQxxJWfn/JJO+M76SgfaHk\nd0540B80nfT9Ff23HbXQS2LBAFqF9ldb+StYCJg/Dl85+9+TIYqmcfuKMbokO313\n6JZ8FNQDmm3xHJy78m7ccYVknuKdT3t2V2LT6cFop/Vv0GWfmbnxo5gL1mEK2avJ\n2QEDV9XIuAFUVCs4jaDbDToU7FdbcXVDNB9ATQIDAQABAoIBAF8vU13z0iUgkm6Y\nj6USDX0gQCi/jMxTJ3R6bMRTA0AZ811tYqSwXUIzX/t2HLGDgjzO9yi4cAcjvC3I\n/RtNfq0kXjO7gIHCfTMeuaYvyaRlgvvUR+w8axdr0DElvcnVmX+dYQyIm6uavzCo\n2WyENt8Q6A/JbuLgZUnun1sxx6Mdq+2JHlRWmp1oZqJavxkuxPfOgvJGsQ7Jyau6\n/1qmljlR91LydJzlVfZ8gIbVdrroVSIpAi52eOYwUVpimHoQDb8gg5Z4CXf05pr2\n6ZfxyE2kvplVaY5NtmjxOq63BcnjzoQB0KvB9JbTrC9RlTy4EcTX5LgCScgUBOAE\nZjDzDUECgYEA40AQ5TbqRuGMwaffOtKlM3XJf9QTEZKziEeZ0VuG+9HBLzsrBGfR\nx+7VwEDnNVtJdHUvJOCZWVrUwe7IU88lXFnCSUOtIo6xRIIDp7s+HUTFmWc9DREy\nfnBa8qfSwmfrQdL92dZQEsJM22jmfVbQ2G8Ufuc49yR+4TbQFKElmpECgYEA4Gha\nnCRu9j8Fppi3GuOHGBvyaB45Hpq20nk2loNmmWFbT8daHLcd6n5QOVhT4ROhJ+Tc\n6Op4w1402wT97AGOn+pwNHSeZ3SrKoRSc3GMcab2KrbKqGJBiUXjbxy34ke0rBR3\nzBOkGBI1qAi+mt5HAUHkPI+iKEQjz3gvMtz3D/0CgYBFJGT/mKnHTzDoaw88coLZ\nGWlpfzkeC6icOkzOqi5zx+ojWLlJ6dymHEDk8dpnHZNH36+sZLnDuiMprmE9PrV7\nV8QJTpILBadh1L0P96R6e0Yz2nl01FqspbrGQdGaXMvzhyK9eLt8OanwyAX49MUu\nVP3Dbs6iQ3RnSaod3Ln4QQKBgCOAXtVU7jkGv14bytv2Iuktgqv2HBM7ZrDlfD1T\njGe3fzqfzyG71n/Ce+6Wiq6Q7G3jRw+SCIjf3nzHzWQI2wdxj069JFI5otqXFHQv\nAoj4YPlg8a6x3Kxa4iAx6uVhcrPGiS0/7jXgq5xpxb26bIFGa1UpY/36ya+I0+64\nBl4BAoGARY09HjFavAwlKGnMNRBXqXhRjBXSfKjKbJz57pYezyYQ1xHuF/GItrgB\nxI/OJeEdVFpo/ApH7/0krIM6AtLLjuEwYSDsUKAHYMhf+Ymb55z4GfhuWP/iDh/+\n/FjEojlv36ykWcKSFXQbKVK7XqNCJ9BHQn8fQxuD8mdFnfZ/O2o=\n-----END RSA PRIVATE KEY-----\n"
},
{
"path": "tigase-server 7.1.0/etc/init-apns.properties",
"content": "cert_file=APNs_HTMessage_Dev.p12\n#cert_file=htmessage_production_APNs.p12\n#cert_file=HTMessage_Dev_APNs.p12\npwd=123456\nexecutor_size=20\nmaxConnections=20\n"
},
{
"path": "tigase-server 7.1.0/etc/init.properties",
"content": "config-type=--gen-config-def\n--admins=admin@app.im\n--virt-hosts = app.im\n\n--user-db=mysql\n--user-db-uri=jdbc:mysql://127.0.0.1:3306/tigase?user=tigase&password=123456&useUnicode=true&characterEncoding=UTF-8&zeroDateTimeBehavior=convertToNull\n\nsess-man/plugins-conf/urn\\:ietf\\:params\\:xml\\:ns\\:\\xmpp-bind/apns-token-db-uri=jdbc:mysql://127.0.0.1:3306/tigase?user=tigase&password=123456&useUnicode=true&characterEncoding=UTF8\n\n\nsess-man/plugins-conf/enabled-mechanisms=ANONYMOUS,PLAIN\n\nbasic-conf/logging/tigase.http.level=FINEST\nbasic-conf/logging/tigase.db.jdbc.level=FINER\nbasic-conf/logging/tigase.xmpp.impl.level=FINE\nbasic-conf/logging/tigase.muc.level=FINE\nbasic-conf/logging/tigase.apns.level=FINE\n\n#sess-man/plugins-conf/amp/user-store-limit-enable[B]=false\n#sess-man/plugins-conf//user-store-limit-enable[B]=false\namp/store-limit[L]=10000\n\n--sm-plugins=+urn:xmpp:receipts,+message-push,+message-archive-xep-0136\n\n--comp-name-1=http\n--comp-class-1=tigase.http.HttpMessageReceiver\nhttp/api-keys[s]=open_access\nhttp/http/ports[i]=19080,19081\n\n\n--comp-name-2=message-archive\n--comp-class-2=tigase.archive.MessageArchiveComponent\nmessage-archive/auto=true\nsess-man/plugins-conf/message-archive-xep-0136/required-store-method=message\n"
},
{
"path": "tigase-server 7.1.0/etc/jmx.access",
"content": "######################################################################\n# Default Access Control File for Remote JMX(TM) Monitoring\n######################################################################\n#\n# Access control file for Remote JMX API access to monitoring.\n# This file defines the allowed access for different roles. The\n# password file (jmxremote.password by default) defines the roles and their\n# passwords. To be functional, a role must have an entry in\n# both the password and the access files.\n#\n# Default location of this file is $JRE/lib/management/jmxremote.access\n# You can specify an alternate location by specifying a property in \n# the management config file $JRE/lib/management/management.properties\n# (See that file for details)\n#\n# The file format for password and access files is syntactically the same\n# as the Properties file format. The syntax is described in the Javadoc\n# for java.util.Properties.load.\n# Typical access file has multiple lines, where each line is blank,\n# a comment (like this one), or an access control entry.\n#\n# An access control entry consists of a role name, and an\n# associated access level. The role name is any string that does not\n# itself contain spaces or tabs. It corresponds to an entry in the\n# password file (jmxremote.password). The access level is one of the\n# following:\n# \"readonly\" grants access to read attributes of MBeans.\n# For monitoring, this means that a remote client in this\n# role can read measurements but cannot perform any action\n# that changes the environment of the running program.\n# \"readwrite\" grants access to read and write attributes of MBeans,\n# to invoke operations on them, and to create or remove them.\n#\t\t This access should be granted to only trusted clients, \n# since they can potentially interfere with the smooth\n#\t\t operation of a running program \n#\n# A given role should have at most one entry in this file. If a role\n# has no entry, it has no access.\n# If multiple entries are found for the same role name, then the last\n# access entry is used.\n#\n#\n# Default access control entries:\n# o The \"monitorRole\" role has readonly access. \n# o The \"controlRole\" role has readwrite access.\n\nmonitor readonly\nadmin readwrite\n"
},
{
"path": "tigase-server 7.1.0/etc/jmx.password",
"content": "# ----------------------------------------------------------------------\n# Template for jmxremote.password\n#\n# o Copy this template to jmxremote.password\n# o Set the user/password entries in jmxremote.password\n# o Change the permission of jmxremote.password to read-only\n# by the owner.\n#\n# See below for the location of jmxremote.password file.\n# ----------------------------------------------------------------------\n\n##############################################################\n# Password File for Remote JMX Monitoring\n##############################################################\n#\n# Password file for Remote JMX API access to monitoring. This\n# file defines the different roles and their passwords. The access\n# control file (jmxremote.access by default) defines the allowed\n# access for each role. To be functional, a role must have an entry\n# in both the password and the access files.\n#\n# Default location of this file is $JRE/lib/management/jmxremote.password\n# You can specify an alternate location by specifying a property in \n# the management config file $JRE/lib/management/management.properties\n# or by specifying a system property (See that file for details).\n\n\n##############################################################\n# File permissions of the jmxremote.password file\n##############################################################\n# Since there are cleartext passwords stored in this file,\n# this file must be readable by ONLY the owner,\n# otherwise the program will exit with an error. \n#\n# The file format for password and access files is syntactically the same\n# as the Properties file format. The syntax is described in the Javadoc\n# for java.util.Properties.load.\n# Typical password file has multiple lines, where each line is blank,\n# a comment (like this one), or a password entry.\n#\n#\n# A password entry consists of a role name and an associated\n# password. The role name is any string that does not itself contain\n# spaces or tabs. The password is again any string that does not\n# contain spaces or tabs. Note that passwords appear in the clear in\n# this file, so it is a good idea not to use valuable passwords.\n#\n# A given role should have at most one entry in this file. If a role\n# has no entry, it has no access.\n# If multiple entries are found for the same role name, then the last one\n# is used.\n#\n# In a typical installation, this file can be read by anybody on the\n# local machine, and possibly by people on other machines.\n# For # security, you should either restrict the access to this file,\n# or specify another, less accessible file in the management config file\n# as described above.\n#\n# Following are two commented-out entries. The \"measureRole\" role has\n# password \"QED\". The \"controlRole\" role has password \"R&D\".\n#\n# monitorRole QED\n# controlRole R&D\n\nadmin admin_pass\nmonitor monitor_pass"
},
{
"path": "tigase-server 7.1.0/etc/logback.xml",
"content": "\n \n logs/tigase.log\n true\n \n %date [%thread] %-5level %logger{35} - %msg%n\n \n \n\n \n \n \n \n \n\n\t\t\n \n\t\t\n \n \n \n\n\n"
},
{
"path": "tigase-server 7.1.0/etc/snmp.acl",
"content": "# ----------------------------------------------------------------------\n# Template for SNMP Access Control List File\n#\n# o Copy this template to snmp.acl\n# o Set access control for SNMP support\n# o Change the permission of snmp.acl to be read-only\n# by the owner.\n#\n# See below for the location of snmp.acl file.\n# ----------------------------------------------------------------------\n\n############################################################\n# SNMP Access Control List File \n############################################################\n#\n# Default location of this file is $JRE/lib/management/snmp.acl.\n# You can specify an alternate location by specifying a property in \n# the management config file $JRE/lib/management/management.properties\n# or by specifying a system property (See that file for details).\n#\n\n\n##############################################################\n# File permissions of the snmp.acl file\n##############################################################\n# \n# Since there are cleartext community strings stored in this file,\n# this ACL file must be readable by ONLY the owner,\n# otherwise the program will exit with an error. \n#\n##############################################################\n#\t\tFormat of the acl group\n##############################################################\n#\n# communities: a list of SNMP community strings to which the\n# access control applies separated by commas.\n#\n# access: either \"read-only\" or \"read-write\".\n#\n# managers: a list of hosts to be granted the access rights.\n# Each can be expressed as any one of the following:\n# - hostname: hubble\n# - ip v4 and v6 addresses: 123.456.789.12 , fe80::a00:20ff:fe9b:ea82\n# - ip v4 and v6 netmask prefix notation: 123.456.789.0/24, \n# fe80::a00:20ff:fe9b:ea82/64 \n# see RFC 2373 (http://www.ietf.org/rfc/rfc2373.txt)\n#\n# An example of two community groups for multiple hosts:\n# acl = {\n# {\n# communities = public, private\n# access = read-only\n# managers = hubble, snowbell, nanak\n# }\n# {\n# communities = jerry\n# access = read-write\n# managers = hubble, telescope\n# }\n# }\n# \n##############################################################\n# Format of the trap group\n##############################################################\n#\n# trap-community: a single SNMP community string that will be included\n# in the traps sent to the hosts.\n#\n# hosts: a list of hosts to which the SNMP agent will send traps.\n#\n# An example of two trap community definitions for multiple hosts:\n# trap = {\n# {\n# trap-community = public\n# hosts = hubble, snowbell\n# }\n# {\n# trap-community = private\n# hosts = telescope\n# }\n# }\n#\n############################################################\n#\n# Update the community strings (public and private) below\n# before copying this template file\n# \t\n# Common SNMP ACL Example\n# ------------------------\n#\n# o Only localhost can connect, and access rights\n# are limited to read-only\n# o Traps are sent to localhost only\n#\n#\nacl = {\n {\n communities = public, private\n access = read-write\n managers = localhost, devel.tigase.org\n }\n}\n# \n# \n# trap = {\n# {\n# trap-community = public\n# hosts = localhost \n# }\n# }\n"
},
{
"path": "tigase-server 7.1.0/etc/tigase-http-context.xml",
"content": "\n\n\n\n"
},
{
"path": "tigase-server 7.1.0/etc/tigase.conf",
"content": "#osgiEnabled=(true|false)\n#osgiEnabled=false\nOSGI=${osgiEnabled}\nENC=\"-Dfile.encoding=UTF-8 -Dsun.jnu.encoding=UTF-8\"\nDRV=\"-Djdbc.drivers=com.mysql.jdbc.Driver:org.postgresql.Driver:org.apache.derby.jdbc.EmbeddedDriver\"\n#GC=\"-XX:+UseBiasedLocking -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:ParallelCMSThreads=2 -XX:-ReduceInitialCardMarks\"\n#EX=\"-XX:+OptimizeStringConcat -XX:+DoEscapeAnalysis -XX:+UseNUMA\"\n#JMX_REMOTE_IP=\"-Djava.rmi.server.hostname=0.0.0.0\"\n\nJAVA_HOME=\"${JAVA_HOME}\"\nCLASSPATH=\"${CLASSPATH}\"\n\nJAVA_OPTIONS=\"${GC} ${EX} ${ENC} ${DRV} ${JMX_REMOTE_IP} -server -Xms100M -Xmx200M -XX:PermSize=32m -XX:MaxPermSize=1024m -XX:MaxDirectMemorySize=128m \"\nTIGASE_CONFIG=\"etc/tigase.xml\"\nTIGASE_OPTIONS=\" --property-file etc/init.properties \"\n"
},
{
"path": "tigase-server 7.1.0/logs/server-info.html",
"content": "\n\nServer informations\n\n\n
Tigase XMPP Server
\n
Server informations
\n\n"
},
{
"path": "tigase-server 7.1.0/modules/distribution/pom.xml",
"content": "\n\n\t\n\t\tpom\n\t\t../..\n\t\n\t4.0.0\n\n\ttigase\n\ttigase-server-dist\n\tTigase XMPP Server Distribution builder\n\n\t${packaging.type}\n\n\t\n\t\ttigase\n\t\ttigase-server-master\n\t\t7.1.0-SNAPSHOT\n\t\t../master\n\t\n\t\n\t\n\t\t\n\t\t\t\n\t\t\t\t\n\t\t\t\t\t!windows\n\t\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\texec-maven-plugin\n\t\t\t\t\t\torg.codehaus.mojo\n\t\t\t\t\t\t1.2.1\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\tChangeLog generation\n\t\t\t\t\t\t\t\tvalidate\n\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\texec\n\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t${project.basedir}/scripts/genChangeLog.sh\n\t\t\t\t\t\t\t\t\t${project.basedir}\n\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\tmaven-antrun-plugin\n\t\t\t\t\t\t1.7\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\tvalidate\n\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t]*>//g\"/>\n\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t]*>//g\"/>\n\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\n\n\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\trun\n\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\t\t\t\n\t\n\t\n\t\t\n\n\t\t\t\n\t\t\t\tmaven-assembly-plugin\n\t\t\t\t2.4\n\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\tdist\n\t\t\t\t\t\tpackage\n\t\t\t\t\t\t\n\t\t\t\t\t\t\tsingle\n\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\tsrc/main/assembly/dist.xml\n\t\t\t\t\t\t\t\tsrc/main/assembly/dist-max.xml\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\tgnu\n\t\t\t\t\t\t\ttigase-server-${project.version}-b${gitVersion}\n\t\t\t\t\t\t\t../../pack\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\n\t\t\t\n\n\t\t\t\n\t\t\t\tmaven-clean-plugin\n\t\t\t\t2.6.1\n\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\tdefault-clean\n\t\t\t\t\t\tclean\n\t\t\t\t\t\t\n\t\t\t\t\t\t\tclean\n\t\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\tclean-deps\n\t\t\t\t\t\tclean\n\t\t\t\t\t\t\n\t\t\t\t\t\t\tclean\n\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t${project.basedir}/../../jars\n\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t**/*.jar\n\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\tfalse\n\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\torg.apache.maven.plugins\n\t\t\t\tmaven-dependency-plugin\n\t\t\t\t2.8\n\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\tcopy-dependencies\n\t\t\t\t\t\tvalidate\n\t\t\t\t\t\t\n\t\t\t\t\t\t\tcopy-dependencies\n\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t${project.basedir}/../../jars\n\t\t\t\t\t\t\ttrue\n\t\t\t\t\t\t\ttrue\n\t\t\t\t\t\t\ttrue\n\t\t\t\t\t\t\ttrue>\n\t\t\t\t\t\t\ttrue\n\t\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\tcopy-old-pubsub\n\t\t\t\t\t\tvalidate\n\t\t\t\t\t\t\n\t\t\t\t\t\t\tcopy\n\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\ttigase\n\t\t\t\t\t\t\t\t\ttigase-pubsub\n\t\t\t\t\t\t\t\t\t2.2.0\n\t\t\t\t\t\t\t\t\ttigase-pubsub-2.2.0.jar.old\n\t\t\t\t\t\t\t\t\tjar\n\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t${project.basedir}/../../jars\n\t\t\t\t\t\t\tfalse\n\t\t\t\t\t\t\ttrue\n\t\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\ttigase-resources\n\t\t\t\t\t\tvalidate\n\t\t\t\t\t\t\n\t\t\t\t\t\t\tunpack\n\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\ttigase\n\t\t\t\t\t\t\t\t\ttigase-http-api\n\t\t\t\t\t\t\t\t\t1.2.0-SNAPSHOT\n\t\t\t\t\t\t\t\t\tjar\n\t\t\t\t\t\t\t\t\tfalse\n\t\t\t\t\t\t\t\t\t${project.basedir}/../..\n\t\t\t\t\t\t\t\t\t*.xml\n\t\t\t\t\t\t\t\t\n\n\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\ttigase\n\t\t\t\t\t\t\t\t\ttigase-http-api\n\t\t\t\t\t\t\t\t\t1.2.0-SNAPSHOT\n\t\t\t\t\t\t\t\t\tjar\n\t\t\t\t\t\t\t\t\tfalse\n\t\t\t\t\t\t\t\t\t${project.basedir}/../..\n\t\t\t\t\t\t\t\t\t**/*.groovy, **/*.html\n\t\t\t\t\t\t\t\t\n\n\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\ttigase\n\t\t\t\t\t\t\t\t\ttigase-http-api-jetty\n\t\t\t\t\t\t\t\t\t1.1.0-SNAPSHOT\n\t\t\t\t\t\t\t\t\tjar\n\t\t\t\t\t\t\t\t\tfalse\n\t\t\t\t\t\t\t\t\t${project.basedir}/../..\n\t\t\t\t\t\t\t\t\t*.xml\n\t\t\t\t\t\t\t\t\n\n\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\ttigase\n\t\t\t\t\t\t\t\t\ttigase-http-api-jetty\n\t\t\t\t\t\t\t\t\t1.1.0-SNAPSHOT\n\t\t\t\t\t\t\t\t\tjar\n\t\t\t\t\t\t\t\t\tfalse\n\t\t\t\t\t\t\t\t\t${project.basedir}/../..\n\t\t\t\t\t\t\t\t\t**/*.groovy\n\t\t\t\t\t\t\t\t\n\n\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\ttigase\n\t\t\t\t\t\t\t\t\ttigase-muc\n\t\t\t\t\t\t\t\t\t2.4.0-SNAPSHOT\n\t\t\t\t\t\t\t\t\tjar\n\t\t\t\t\t\t\t\t\tfalse\n\t\t\t\t\t\t\t\t\t${project.basedir}/../../scripts\n\t\t\t\t\t\t\t\t\t**/*.groovy\n\t\t\t\t\t\t\t\t\n\n\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\ttigase\n\t\t\t\t\t\t\t\t\ttigase-socks5\n\t\t\t\t\t\t\t\t\t1.2.0-SNAPSHOT\n\t\t\t\t\t\t\t\t\tjar\n\t\t\t\t\t\t\t\t\tfalse\n\t\t\t\t\t\t\t\t\t${project.basedir}/../../database\n\t\t\t\t\t\t\t\t\t**/*.sql\n\t\t\t\t\t\t\t\t\n\n\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\ttigase\n\t\t\t\t\t\t\t\t\ttigase-pubsub\n\t\t\t\t\t\t\t\t\t3.2.0-SNAPSHOT\n\t\t\t\t\t\t\t\t\tjar\n\t\t\t\t\t\t\t\t\tfalse\n\t\t\t\t\t\t\t\t\t${project.basedir}/../..\n\t\t\t\t\t\t\t\t\t**/*.sql,**/*.sh,**/*.cmd,**/*.txt\n\t\t\t\t\t\t\t\t\n\n\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\ttigase\n\t\t\t\t\t\t\t\t\ttigase-pubsub\n\t\t\t\t\t\t\t\t\t3.2.0-SNAPSHOT\n\t\t\t\t\t\t\t\t\tjar\n\t\t\t\t\t\t\t\t\tfalse\n\t\t\t\t\t\t\t\t\t${project.basedir}/../..\n\t\t\t\t\t\t\t\t\t**/*.groovy\n\t\t\t\t\t\t\t\t\n\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\torg.apache.maven.plugins\n\t\t\t\tmaven-jarsigner-plugin\n\t\t\t\t1.4\n\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\tsign\n\t\t\t\t\t\tvalidate\n\t\t\t\t\t\t\n\t\t\t\t\t\t\tsign\n\t\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\t${project.basedir}/../..\n\t\t\t\t\t\n\t\t\t\t\t\ttarget/tigase*.?ar\n\t\t\t\t\t\tjars/tigase*.?ar\n\t\t\t\t\t\tjars/licence-lib.jar\n\t\t\t\t\t\n\t\t\t\t\tfalse\n\t\t\t\t\tfalse\n\t\t\t\t\thttp://timestamp.comodoca.com/rfc3161\n\t\t\t\t\t${sign-skip}\n\t\t\t\t\ttrue\n\n\t\t\t\t\t${sign-keystore}\n\t\t\t\t\t${sign-alias}\n\t\t\t\t\t${sign-storepass}\n\t\t\t\t\t${sign-keypass}\n\t\t\t\t\t${verbose-log}\n\t\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\torg.apache.maven.plugins\n\t\t\t\tmaven-deploy-plugin\n\t\t\t\t2.8.2\n\t\t\t\t\n\t\t\t\t\ttrue\n\t\t\t\t\n\t\t\t\n\t\t\n\t\n\n\t\n\n\t\t\n\t\t\n\t\t\ttigase\n\t\t\ttigase-server\n\t\t\t7.1.0-SNAPSHOT\n\t\t\n\t\t\n\t\t\ttigase\n\t\t\ttigase-ext-mailer\n\t\t\t1.0.0-SNAPSHOT\n\t\t\truntime\n\t\t\t\n\t\t\t\t\n\t\t\t\t\torg.apache.felix\n\t\t\t\t\torg.osgi.core\n\t\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\ttigase\n\t\t\ttigase-muc\n\t\t\t2.4.0-SNAPSHOT\n\t\t\truntime\n\t\t\n\t\t\n\t\t\ttigase\n\t\t\ttigase-pubsub\n\t\t\t3.2.0-SNAPSHOT\n\t\t\truntime\n\t\t\n\t\t\n\t\t\ttigase\n\t\t\ttigase-extras\n\t\t\t1.1.2-SNAPSHOT\n\t\t\truntime\n\t\t\n\t\t\n\t\t\ttigase\n\t\t\tlicence-lib\n\t\t\t1.2.0-SNAPSHOT\n\t\t\truntime\n\t\t\n\t\t\n\t\t\ttigase\n\t\t\ttigase-stats-collector-library\n\t\t\t1.2.0-SNAPSHOT\n\t\t\truntime\n\t\t\n\t\t\n\t\t\ttigase\n\t\t\ttigase-stats-collector-provider\n\t\t\t1.2.0-SNAPSHOT\n\t\t\truntime\n\t\t\n\t\t\n\t\t\ttigase\n\t\t\ttigase-http-api\n\t\t\t1.2.0-SNAPSHOT\n\t\t\truntime\n\t\t\n\t\t\n\t\t\ttigase.sure.web\n\t\t\ttigase-web-ui\n\t\t\t2.1-SNAPSHOT\n\t\t\twar\n\t\t\n\t\t\n\t\t\ttigase\n\t\t\ttigase-http-api-jetty\n\t\t\t1.1.0-SNAPSHOT\n\t\t\truntime\n\t\t\t\t\n\t\t\n\t\t\ttigase\n\t\t\ttigase-message-archiving\n\t\t\t1.2.0-SNAPSHOT\n\t\t\truntime\n\t\t\n\t\t\n\t\t\ttigase\n\t\t\ttigase-unified-archive\n\t\t\t1.0.0-SNAPSHOT\n\t\t\truntime\n\t\t\n\t\t\n\t\t\ttigase\n\t\t\ttigase-socks5\n\t\t\t1.2.0-SNAPSHOT\n\t\t\truntime\n\t\t\n\t\t\n\t\t\ttigase\n\t\t\ttigase-stun\n\t\t\t1.1.2-SNAPSHOT\n\t\t\truntime\n\t\t\n\t\t\n\t\t\ttigase\n\t\t\ttigase-acs\n\t\t\t2.3.0-SNAPSHOT\n\t\t\truntime\n\t\t\n\t\t\n\t\t\ttigase\n\t\t\ttigase-acs-muc\n\t\t\t1.2.0-SNAPSHOT\n\t\t\truntime\n\t\t\n\t\t\n\t\t\ttigase\n\t\t\ttigase-acs-pubsub\n\t\t\t1.2.0-SNAPSHOT\n\t\t\truntime\n\t\t\n\n\t\t\n\t\t\ttigase\n\t\t\ttigase-mongodb\n\t\t\t1.1.0-SNAPSHOT\n\t\t\truntime\n\t\t\n\n\n\n\t\t\n\t\t\n\t\t\torg.apache.derby\n\t\t\tderby\n\t\t\t10.12.1.1\n\t\t\truntime\n\t\t\n\t\t\n\t\t\torg.apache.derby\n\t\t\tderbytools\n\t\t\t10.12.1.1\n\t\t\truntime\n\t\t\n\t\t\n\t\t\tmysql\n\t\t\tmysql-connector-java\n\t\t\t5.1.11\n\t\t\truntime\n\t\t\n\t\t\n\t\t\torg.postgresql\n\t\t\tpostgresql\n\t\t\t9.4.1207\n\t\t\truntime\n\t\t\n\t\t\n\t\t\tnet.sourceforge.jtds\n\t\t\tjtds\n\t\t\t1.3.1\n\t\t\truntime\n\t\t\n\t\t\n\t\t\torg.mongodb\n\t\t\tmongo-java-driver\n\t\t\t2.14.1\n\t\t\truntime\n\t\t\n\n\n\t\t\n\t\t\n\t\t\torg.codehaus.groovy\n\t\t\tgroovy-all\n\t\t\t2.4.3\n\t\t\truntime\n\t\t\n\t\t\n\t\t\torg.hamcrest\n\t\t\thamcrest-core\n\t\t\t1.3\n\t\t\truntime\n\t\t\n\t\t\n\t\t\torg.slf4j\n\t\t\tslf4j-api\n\t\t\t${slf4j.version}\n\t\t\truntime\n\t\t\ttrue\n\t\t\n\t\t\n\t\t\torg.slf4j\n\t\t\tjul-to-slf4j\n\t\t\t${slf4j.version}\n\t\t\truntime\n\t\t\ttrue\n\t\t\n\t\t\n\t\t\tde.javawi\n\t\t\tjstun\n\t\t\t0.7.3\n\t\t\n\n\t\t\n\t\t\n\t\t\torg.apache.felix\n\t\t\torg.osgi.core\n\t\t\t1.4.0\n\t\t\truntime\n\t\t\n\t\t\n\t\t\torg.apache.felix\n\t\t\torg.apache.felix.bundlerepository\n\t\t\t1.6.6\n\t\t\truntime\n\t\t\n\t\t\n\t\t\torg.apache.felix\n\t\t\torg.apache.felix.http.bundle\n\t\t\t2.2.1\n\t\t\truntime\n\t\t\t\n\t\t\t\t\n\t\t\t\t\torg.apache.felix\n\t\t\t\t\torg.apache.felix.http.bridge\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\torg.apache.felix\n\t\t\t\t\torg.apache.felix.http.cometd\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\torg.apache.felix\n\t\t\t\t\torg.apache.felix.http.jetty\n\t\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\torg.apache.felix\n\t\t\torg.apache.felix.configadmin\n\t\t\t1.6.0\n\t\t\truntime\n\t\t\n\t\t\n\t\t\torg.apache.felix\n\t\t\torg.apache.felix.main\n\t\t\t4.4.0\n\t\t\truntime\n\t\t\n\t\t\n\t\t\torg.apache.felix\n\t\t\torg.apache.felix.shell\n\t\t\t1.4.2\n\t\t\truntime\n\t\t\n\t\t\n\t\t\torg.apache.felix\n\t\t\torg.apache.felix.shell.remote\n\t\t\t1.0.4\n\t\t\truntime\n\t\t\t\n\t\t\t\t\n\t\t\t\t\torg.apache.felix\n\t\t\t\t\torg.osgi.core\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\torg.apache.felix\n\t\t\t\t\torg.osgi.compendium\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\torg.apache.felix\n\t\t\t\t\torg.apache.felix.shell\n\t\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\tch.qos.logback\n\t\t\tlogback-classic\n\t\t\t1.0.0\n\t\t\n\t\t\n\t\t\tch.qos.logback\n\t\t\tlogback-core\n\t\t\t1.0.0\n\t\t\n\t\t\n\t\t\tjunit\n\t\t\tjunit\n\t\t\t4.11\n\t\t\ttest\n\t\t\n\t\n\n\n"
},
{
"path": "tigase-server 7.1.0/modules/distribution/scripts/genChangeLog.sh",
"content": "#!/bin/bash\n\ngit log --pretty --numstat --summary tigase-server-5.1.0..master | scripts/git2cl > ChangeLog\n"
},
{
"path": "tigase-server 7.1.0/modules/distribution/scripts/git2cl",
"content": "#!/usr/bin/perl\n\n# Copyright (C) 2007, 2008 Simon Josefsson \n# Copyright (C) 2007 Luis Mondesi \n# * calls git directly. To use it just: \n# cd ~/Project/my_git_repo; git2cl > ChangeLog\n# * implements strptime()\n# * fixes bugs in $comment parsing\n# - copy input before we remove leading spaces\n# - skip \"merge branch\" statements as they don't\n# have information about files (i.e. we never\n# go into $state 2)\n# - behaves like a pipe/filter if input is given from the CLI\n# else it calls git log by itself\n#\n# The functions mywrap, last_line_len, wrap_log_entry are derived from\n# the cvs2cl tool, see :\n# Copyright (C) 2001,2002,2003,2004 Martyn J. Pearce \n# Copyright (C) 1999 Karl Fogel \n#\n# git2cl is free software; you can redistribute it and/or modify it\n# under the terms of the GNU General Public License as published by\n# the Free Software Foundation; either version 2, or (at your option)\n# any later version.\n#\n# git2cl is distributed in the hope that it will be useful, but\n# WITHOUT ANY WARRANTY; without even the implied warranty of\n# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU\n# General Public License for more details.\n#\n# You should have received a copy of the GNU General Public License\n# along with git2cl; see the file COPYING. If not, write to the Free\n# Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA\n# 02110-1301 USA.\n\n=head1 NAME\n\ngit2cl - tool to convert git logs to GNU ChangeLog\n\n=head1 SYNOPSIS\n\ngit2cl > ChangeLog\n\nIf you don't want git2cl to invoke git log internally, you can use it\nas a pipe.\nIt needs a git log generated with --pretty --numstat and --summary.\nYou can use it as follows:\n\n git log --pretty --numstat --summary | git2cl > ChangeLog\n\n=head1 DESCRIPTION\n\nThis is a quick'n'dirty tool to convert git logs to GNU ChangeLog\nformat.\n\nThe tool invokes `git log` internally unless you pipe a log to it.\nThus, typically you would use it as follows:\n\n=head1 SEE ALSO\n\nOutput format specification:\n \n\n=head1 AUTHORS\n\ngit2cl is developed by Simon Josefsson \n and Luis Mondesi \n\n=cut\n\nuse strict;\nuse POSIX qw(strftime);\nuse Text::Wrap qw(wrap);\nuse FileHandle;\n\nuse constant EMPTY_LOG_MESSAGE => '*** empty log message ***';\n\n# this is a helper hash for stptime.\n# Assumes you are calling 'git log ...' with LC_ALL=C\nmy %month = (\n 'Jan'=>0,\n 'Feb'=>1,\n 'Mar'=>2,\n 'Apr'=>3,\n 'May'=>4,\n 'Jun'=>5,\n 'Jul'=>6,\n 'Aug'=>7,\n 'Sep'=>8,\n 'Oct'=>9,\n 'Nov'=>10,\n 'Dec'=>11,\n);\n\nmy $fh = new FileHandle;\n\nsub key_ready\n{\n my ($rin, $nfd);\n vec($rin, fileno(STDIN), 1) = 1;\n return $nfd = select($rin, undef, undef, 0);\n}\n\nsub strptime {\n my $str = shift;\n return undef if not defined $str;\n\n # we are parsing this format\n # Fri Oct 26 00:42:56 2007 -0400\n # to these fields\n # sec, min, hour, mday, mon, year, wday = -1, yday = -1, isdst = -1\n # Luis Mondesi \n my @date;\n if ($str =~ /([[:alpha:]]{3})\\s+([[:alpha:]]{3})\\s+([[:digit:]]{1,2})\\s+([[:digit:]]{1,2}):([[:digit:]]{1,2}):([[:digit:]]{1,2})\\s+([[:digit:]]{4})/){\n push(@date,$6,$5,$4,$3,$month{$2},($7 - 1900),-1,-1,-1);\n } else {\n die (\"Cannot parse date '$str'\\n'\");\n }\n return @date;\n}\n\nsub mywrap {\n my ($indent1, $indent2, @text) = @_;\n # If incoming text looks preformatted, don't get clever\n my $text = Text::Wrap::wrap($indent1, $indent2, @text);\n if ( grep /^\\s+/m, @text ) {\n\treturn $text;\n }\n my @lines = split /\\n/, $text;\n $indent2 =~ s!^((?: {8})+)!\"\\t\" x (length($1)/8)!e;\n $lines[0] =~ s/^$indent1\\s+/$indent1/;\n s/^$indent2\\s+/$indent2/\n\tfor @lines[1..$#lines];\n my $newtext = join \"\\n\", @lines;\n $newtext .= \"\\n\"\n\tif substr($text, -1) eq \"\\n\";\n return $newtext;\n}\n\nsub last_line_len {\n my $files_list = shift;\n my @lines = split (/\\n/, $files_list);\n my $last_line = pop (@lines);\n return length ($last_line);\n}\n\n# A custom wrap function, sensitive to some common constructs used in\n# log entries.\nsub wrap_log_entry {\n my $text = shift; # The text to wrap.\n my $left_pad_str = shift; # String to pad with on the left.\n\n # These do NOT take left_pad_str into account:\n my $length_remaining = shift; # Amount left on current line.\n my $max_line_length = shift; # Amount left for a blank line.\n\n my $wrapped_text = ''; # The accumulating wrapped entry.\n my $user_indent = ''; # Inherited user_indent from prev line.\n\n my $first_time = 1; # First iteration of the loop?\n my $suppress_line_start_match = 0; # Set to disable line start checks.\n\n my @lines = split (/\\n/, $text);\n while (@lines) # Don't use `foreach' here, it won't work.\n {\n\tmy $this_line = shift (@lines);\n\tchomp $this_line;\n\n\tif ($this_line =~ /^(\\s+)/) {\n\t $user_indent = $1;\n\t}\n\telse {\n\t $user_indent = '';\n\t}\n\n\t# If it matches any of the line-start regexps, print a newline now...\n\tif ($suppress_line_start_match)\n\t{\n\t $suppress_line_start_match = 0;\n\t}\n\telsif (($this_line =~ /^(\\s*)\\*\\s+[a-zA-Z0-9]/)\n\t || ($this_line =~ /^(\\s*)\\* [a-zA-Z0-9_\\.\\/\\+-]+/)\n\t || ($this_line =~ /^(\\s*)\\([a-zA-Z0-9_\\.\\/\\+-]+(\\)|,\\s*)/)\n\t || ($this_line =~ /^(\\s+)(\\S+)/)\n\t || ($this_line =~ /^(\\s*)- +/)\n\t || ($this_line =~ /^()\\s*$/)\n\t || ($this_line =~ /^(\\s*)\\*\\) +/)\n\t || ($this_line =~ /^(\\s*)[a-zA-Z0-9](\\)|\\.|\\:) +/))\n\t{\n\t $length_remaining = $max_line_length - (length ($user_indent));\n\t}\n\n\t# Now that any user_indent has been preserved, strip off leading\n\t# whitespace, so up-folding has no ugly side-effects.\n\t$this_line =~ s/^\\s*//;\n\n\t# Accumulate the line, and adjust parameters for next line.\n\tmy $this_len = length ($this_line);\n\tif ($this_len == 0)\n\t{\n\t # Blank lines should cancel any user_indent level.\n\t $user_indent = '';\n\t $length_remaining = $max_line_length;\n\t}\n\telsif ($this_len >= $length_remaining) # Line too long, try breaking it.\n\t{\n\t # Walk backwards from the end. At first acceptable spot, break\n\t # a new line.\n\t my $idx = $length_remaining - 1;\n\t if ($idx < 0) { $idx = 0 };\n\t while ($idx > 0)\n\t {\n\t\tif (substr ($this_line, $idx, 1) =~ /\\s/)\n\t\t{\n\t\t my $line_now = substr ($this_line, 0, $idx);\n\t\t my $next_line = substr ($this_line, $idx);\n\t\t $this_line = $line_now;\n\n\t\t # Clean whitespace off the end.\n\t\t chomp $this_line;\n\n\t\t # The current line is ready to be printed.\n\t\t $this_line .= \"\\n${left_pad_str}\";\n\n\t\t # Make sure the next line is allowed full room.\n\t\t $length_remaining = $max_line_length - (length ($user_indent));\n\n\t\t # Strip next_line, but then preserve any user_indent.\n\t\t $next_line =~ s/^\\s*//;\n\n\t\t # Sneak a peek at the user_indent of the upcoming line, so\n\t\t # $next_line (which will now precede it) can inherit that\n\t\t # indent level. Otherwise, use whatever user_indent level\n\t\t # we currently have, which might be none.\n\t\t my $next_next_line = shift (@lines);\n\t\t if ((defined ($next_next_line)) && ($next_next_line =~ /^(\\s+)/)) {\n\t\t\t$next_line = $1 . $next_line if (defined ($1));\n\t\t\t# $length_remaining = $max_line_length - (length ($1));\n\t\t\t$next_next_line =~ s/^\\s*//;\n\t\t }\n\t\t else {\n\t\t\t$next_line = $user_indent . $next_line;\n\t\t }\n\t\t if (defined ($next_next_line)) {\n\t\t\tunshift (@lines, $next_next_line);\n\t\t }\n\t\t unshift (@lines, $next_line);\n\n\t\t # Our new next line might, coincidentally, begin with one of\n\t\t # the line-start regexps, so we temporarily turn off\n\t\t # sensitivity to that until we're past the line.\n\t\t $suppress_line_start_match = 1;\n\n\t\t last;\n\t\t}\n\t\telse\n\t\t{\n\t\t $idx--;\n\t\t}\n\t }\n\n\t if ($idx == 0)\n\t {\n\t\t# We bottomed out because the line is longer than the\n\t\t# available space. But that could be because the space is\n\t\t# small, or because the line is longer than even the maximum\n\t\t# possible space. Handle both cases below.\n\n\t\tif ($length_remaining == ($max_line_length - (length ($user_indent))))\n\t\t{\n\t\t # The line is simply too long -- there is no hope of ever\n\t\t # breaking it nicely, so just insert it verbatim, with\n\t\t # appropriate padding.\n\t\t $this_line = \"\\n${left_pad_str}${this_line}\";\n\t\t}\n\t\telse\n\t\t{\n\t\t # Can't break it here, but may be able to on the next round...\n\t\t unshift (@lines, $this_line);\n\t\t $length_remaining = $max_line_length - (length ($user_indent));\n\t\t $this_line = \"\\n${left_pad_str}\";\n\t\t}\n\t }\n\t}\n\telse # $this_len < $length_remaining, so tack on what we can.\n\t{\n\t # Leave a note for the next iteration.\n\t $length_remaining = $length_remaining - $this_len;\n\n\t if ($this_line =~ /\\.$/)\n\t {\n\t\t$this_line .= \" \";\n\t\t$length_remaining -= 2;\n\t }\n\t else # not a sentence end\n\t {\n\t\t$this_line .= \" \";\n\t\t$length_remaining -= 1;\n\t }\n\t}\n\n\t# Unconditionally indicate that loop has run at least once.\n\t$first_time = 0;\n\n\t$wrapped_text .= \"${user_indent}${this_line}\";\n }\n\n # One last bit of padding.\n $wrapped_text .= \"\\n\";\n\n return $wrapped_text;\n}\n\n# main\n\nmy @date;\nmy $author;\nmy @files;\nmy $comment;\n\nmy $state; # 0-header 1-comment 2-files\nmy $done = 0;\n\n$state = 0;\n\n# if reading from STDIN, we assume that we are\n# getting git log as input\nif (key_ready())\n{\n\n #my $dummyfh; # don't care about writing\n #($fh,$dummyfh) = FileHandle::pipe;\n $fh->fdopen(*STDIN, 'r');\n}\nelse\n{\n $fh->open(\"LC_ALL=C git log --pretty --numstat --summary|\")\n\tor die(\"Cannot execute git log...$!\\n\");\n}\n\nwhile (my $_l = <$fh>) {\n #print STDERR \"debug ($state, \" . (@date ? (strftime \"%Y-%m-%d\", @date) : \"\") . \"): `$_'\\n\";\n if ($state == 0) {\n\tif ($_l =~ m,^Author: (.*),) {\n\t $author = $1;\n\t}\n\tif ($_l =~ m,^Date: (.*),) {\n\t @date = strptime($1);\n\t}\n\t$state = 1 if ($_l =~ m,^$, and $author and (@date+0>0));\n } elsif ($state == 1) {\n # * modifying our input text is a bad choice\n # let's make a copy of it first, then we remove spaces \n # * if we meet a \"merge branch\" statement, we need to start\n # over and find a real entry\n # Luis Mondesi \n my $_s = $_l;\n\t$_s =~ s/^ //g;\n if ($_s =~ m/^Merge branch/)\n {\n $state=0;\n next;\n }\n\t$comment = $comment . $_s;\n\t$state = 2 if ($_l =~ m,^$,);\n } elsif ($state == 2) {\n\tif ($_l =~ m,^([0-9]+)\\t([0-9]+)\\t(.*)$,) {\n\t push @files, $3;\n\t}\n\t$done = 1 if ($_l =~ m,^$,);\n }\n\n if ($done) {\n\tprint (strftime \"%Y-%m-%d $author\\n\\n\", @date);\n\n\tmy $files = join (\", \", @files);\n\t$files = mywrap (\"\\t\", \"\\t\", \"* $files\"), \": \";\n\n\tif (index($comment, EMPTY_LOG_MESSAGE) > -1 ) {\n\t $comment = \"[no log message]\\n\";\n\t}\n\n\tmy $files_last_line_len = 0;\n\t$files_last_line_len = last_line_len($files) + 1;\n\tmy $msg = wrap_log_entry($comment, \"\\t\", 69-$files_last_line_len, 69);\n\n\t$msg =~ s/[ \\t]+\\n/\\n/g;\n\n\tprint \"$files: $msg\\n\";\n\n\t@date = ();\n\t$author = \"\";\n\t@files = ();\n\t$comment = \"\";\n\n\t$state = 0;\n\t$done = 0;\n }\n}\n\nif (@date + 0)\n{\n print (strftime \"%Y-%m-%d $author\\n\\n\", @date);\n my $msg = wrap_log_entry($comment, \"\\t\", 69, 69);\n $msg =~ s/[ \\t]+\\n/\\n/g;\n print \"\\t* $msg\\n\";\n}\n"
},
{
"path": "tigase-server 7.1.0/modules/distribution/src/main/assembly/dist-max.xml",
"content": "\n\n\tdist-max\n\t\n\t\tzip\n\t\ttar.gz\n\t\n\n\t\n\t\t\n\t\t\t./\n\t\t\t./\n\t\t\t\n\t\t\t\tREADME\n\t\t\t\tChangeLog\n\t\t\t\tLicense.html\n\t\t\t\tpackage.html\n\t\t\t\n\t\t\n\t\t\n\t\t\t../../certs\n\t\t\tcerts\n\t\t\t\n\t\t\t\tdummy.cer\n\t\t\t\trsa-keystore\n\t\t\t\ttruststore\n\t\t\t\n\t\t\n\t\t\n\t\t\t../../database\n\t\t\tdatabase\n\t\t\t\n\t\t\t\t*\n\t\t\t\n\t\t\n\t\t\n\t\t\t../../docs\n\t\t\tdocs\n\t\t\t\n\t\t\t\tAdministration_Guide/html_chunk/**/*\n\t\t\t\tAdministration_Guide/pdf/**/*\n\t\t\t\tDevelopment_Guide/html_chunk/**/*\n\t\t\t\tDevelopment_Guide/pdf/**/*\n\t\t\t\tProperties_Guide/html_chunk/**/*\n\t\t\t\tProperties_Guide/pdf/**/*\n\t\t\t\tUser_Guide/html_chunk/**/*\n\t\t\t\tUser_Guide/pdf/**/*\n\t\t\t\tjavadoc/**/*\n\t\t\t\n\t\t\n\t\t\n\t\t\t../../win-stuff\n\t\t\twin-stuff\n\t\t\t\n\t\t\t\t*/**\n\t\t\t\n\t\t\n\t\t\n\t\t\t../../etc\n\t\t\tetc\n\t\t\t\n\t\t\t\tbosh-extra-headers.txt\n\t\t\t\tcross-domain-policy.xml\n\t\t\t\tclient-access-policy.xml\n\t\t\t\tinit.properties\n\t\t\t\ttigase.conf\n\t\t\t\tjmx.access\n\t\t\t\tjmx.password\n\t\t\t\tlogback.xml\n\t\t\t\tsnmp.acl\n\t\t\t\ttigase-http-context.xml\n\t\t\t\n\t\t\n\t\t\n\t\t\n\t\t\t../../conf\n\t\t\tconf\n\t\t\t\n\t\t\t\tconfig.properties\n\t\t\t\n\t\t\n\t\t\n\t\t\t../../src/main/groovy/tigase/admin\n\t\t\tscripts/admin\n\t\t\t\n\t\t\t\t**/*\n\t\t\t\n\t\t\n\t\t\n\t\t\t../../jars\n\t\t\tjars\n\t\t\t\n\t\t\t\t**/*.old\n\t\t\t\n\t\t\n\t\t\n\t\t\t../../scripts\n\t\t\tscripts\n\t\t\t\n\t\t\t\t**/*\n\t\t\t\n\t\t\t0744\n\t\t\t0744\n\t\t\n\t\t\n\t\t\t./\n\t\t\t/logs\n\t\t\t\n\t\t\t\t*/**\n\t\t\t\n\t\t\t0744\n\t\t\t0754\n\t\t\n\t\n\n\t\n\t\t\n\t\t\tjars\n\t\t\tfalse\n\t\t\t${artifact.artifactId}.${artifact.extension}\n\t\t\tfalse\n\t\t\truntime\n\t\t\t\n\t\t\t\n\t\t\t\t\n\t\t\t\ttigase:tigase-server\n\t\t\t\t\n\t\t\t\t\n\t\t\t\ttigase:tigase-acs\n\t\t\t\ttigase:tigase-acs-muc\n\t\t\t\ttigase:tigase-acs-pubsub\n\t\t\t\ttigase:tigase-muc\n\t\t\t\ttigase:tigase-pubsub\n\t\t\t\ttigase:tigase-extras\n\t\t\t\ttigase:licence-lib\n\t\t\t\ttigase:tigase-stats-collector-library\n\t\t\t\ttigase:tigase-stats-collector-provider\n\t\t\t\ttigase:tigase-http-api\n\t\t\t\ttigase:tigase-http-api-jetty\n\t\t\t\ttigase.sure.web:tigase-web-ui\n\t\t\t\ttigase:tigase-message-archiving\n\t\t\t\ttigase:tigase-unified-archive\n\t\t\t\ttigase:tigase-socks5\n\t\t\t\ttigase:tigase-stun\n\t\t\t\ttigase:tigase-mongodb\n\t\t\t\ttigase:tigase-ext-mailer\n\n\t\t\t\t\n\t\t\t\torg.apache.derby:derby\n\t\t\t\torg.apache.derby:derbytools\n\t\t\t\tmysql:mysql-connector-java\n\t\t\t\torg.postgresql:postgresql\n\t\t\t\tnet.sourceforge.jtds:jtds\n\t\t\t\torg.mongodb:mongo-java-driver\n\t\t\t\t\n\t\t\t\t\n\t\t\t\torg.codehaus.groovy:groovy-all\n\t\t\t\topenDMK:jdmkrt\n\t\t\t\torg.hamcrest:hamcrest-core\n\t\t\t\torg.slf4j:slf4j-api\n\t\t\t\torg.slf4j:jul-to-slf4j\n\t\t\t\tde.javawi:jstun\n\n\t\t\t\t\n\t\t\t\tjavax.servlet:javax.servlet-api\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\n\t\t\t\torg.eclipse.jetty:jetty-http\n\t\t\t\torg.eclipse.jetty:jetty-io\n\t\t\t\torg.eclipse.jetty:jetty-security\n\t\t\t\torg.eclipse.jetty:jetty-server\n\t\t\t\torg.eclipse.jetty:jetty-servlet\n\t\t\t\torg.eclipse.jetty:jetty-util\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\n\n\t\t\t\t\n\t\t\t\torg.osgi:org.osgi.core\n\t\t\t\torg.apache.felix:org.apache.felix.bundlerepository\n\t\t\t\torg.apache.felix:org.apache.felix.configadmin\n\t\t\t\torg.apache.felix:org.apache.felix.main\n\t\t\t\torg.apache.felix:org.apache.felix.shell\n\t\t\t\torg.apache.felix:org.apache.felix.shell.remote\n\t\t\t\tch.qos.logback:logback-classic\n\t\t\t\tch.qos.logback:logback-core\n\n\t\t\t\t\n\t\t\t\tjavax.activation:activation\n\t\t\t\tcom.sun.mail:javax.mail\n\t\t\t\tcom.sun.mail:smtp\n\n\t\t\t\n\t\t\n\t\n\n"
},
{
"path": "tigase-server 7.1.0/modules/distribution/src/main/assembly/dist.xml",
"content": "\n\n\tdist\n\t\n\t\tzip\n\t\ttar.gz\n\t\n\n\t\n\t\t\n\t\t\t./\n\t\t\t./\n\t\t\t\n\t\t\t\tREADME\n\t\t\t\tChangeLog\n\t\t\t\tLicense.html\n\t\t\t\tpackage.html\n\t\t\t\n\t\t\n\t\t\n\t\t\t../../certs\n\t\t\tcerts\n\t\t\t\n\t\t\t\tdummy.cer\n\t\t\t\trsa-keystore\n\t\t\t\ttruststore\n\t\t\t\n\t\t\n\t\t\n\t\t\t../../database\n\t\t\tdatabase\n\t\t\t\n\t\t\t\t*\n\t\t\t\n\t\t\n\t\t\n\t\t\t../../docs\n\t\t\tdocs\n\t\t\t\n\t\t\t\tAdministration_Guide/html_chunk/**/*\n\t\t\t\tAdministration_Guide/pdf/**/*\n\t\t\t\tDevelopment_Guide/html_chunk/**/*\n\t\t\t\tDevelopment_Guide/pdf/**/*\n\t\t\t\tProperties_Guide/html_chunk/**/*\n\t\t\t\tProperties_Guide/pdf/**/*\n\t\t\t\tUser_Guide/html_chunk/**/*\n\t\t\t\tUser_Guide/pdf/**/*\n\t\t\t\tjavadoc/**/*\n\t\t\t\n\t\t\n\t\t\n\t\t\t../../win-stuff\n\t\t\twin-stuff\n\t\t\t\n\t\t\t\t*/**\n\t\t\t\n\t\t\n\t\t\n\t\t\t../../etc\n\t\t\tetc\n\t\t\t\n\t\t\t\tbosh-extra-headers.txt\n\t\t\t\tcross-domain-policy.xml\n\t\t\t\tclient-access-policy.xml\n\t\t\t\tinit.properties\n\t\t\t\ttigase.conf\n\t\t\t\tjmx.access\n\t\t\t\tjmx.password\n\t\t\t\tlogback.xml\n\t\t\t\tsnmp.acl\n\t\t\t\ttigase-http-context.xml\n\t\t\t\n\t\t\n\t\t\n\t\t\t../../src/main/groovy/tigase/admin\n\t\t\tscripts/admin\n\t\t\t\n\t\t\t\t**/*\n\t\t\t\n\t\t\n\t\t\n\t\t\t../../scripts\n\t\t\tscripts\n\t\t\t\n\t\t\t\t**/*\n\t\t\t\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\t0744\n\t\t\t0744\n\t\t\n\t\t\n\t\t\t./\n\t\t\t/logs\n\t\t\t\n\t\t\t\t*/**\n\t\t\t\n\t\t\t0644\n\t\t\t0754\n\t\t\n\t\n\t\n\t\t\n\t\t\tfalse\n\t\t\tjars\n\t\t\t${artifact.artifactId}.${artifact.extension}\n\t\t\tfalse\n\t\t\t\n\t\t\t\n\t\t\t\t\n\t\t\t\ttigase:tigase-server\n\t\t\t\ttigase:tigase-http-api\n\t\t\t\ttigase.sure.web:tigase-web-ui\n\t\t\t\tjavax.servlet:javax.servlet-api\n\n\t\t\t\t\n\t\t\t\torg.apache.derby:derby\n\t\t\t\torg.apache.derby:derbytools\n\t\t\t\tmysql:mysql-connector-java\n\t\t\t\torg.postgresql:postgresql\n\t\t\t\t\n\t\t\t\torg.codehaus.groovy:groovy-all\n\t\t\t\topenDMK:jdmkrt\n\t\t\t\tnet.sourceforge.jtds:jtds\n\n\t\t\t\n\t\t\n\t\n\n"
},
{
"path": "tigase-server 7.1.0/modules/distribution/src/main/resources/META-INF/java.security.Provider",
"content": "# our security providers\ntigase.auth.TigaseSaslProvider"
},
{
"path": "tigase-server 7.1.0/modules/documentation/.gitignore",
"content": ".html\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/css/docbook-xsl.css",
"content": "/*\n CSS stylesheet for XHTML produced by DocBook XSL stylesheets.\n*/\n\nbody {\n font-family: Georgia,serif;\n}\n\ncode, pre {\n font-family: \"Courier New\", Courier, monospace;\n}\n\nspan.strong {\n font-weight: bold;\n}\n\nbody blockquote {\n margin-top: .75em;\n line-height: 1.5;\n margin-bottom: .75em;\n}\n\nhtml body {\n margin: 1em 5% 1em 5%;\n line-height: 1.2;\n}\n\nbody div {\n margin: 0;\n}\n\nh1, h2, h3, h4, h5, h6\n{\n color: #527bbd;\n font-family: Arial,Helvetica,sans-serif;\n}\n\ndiv.toc p:first-child,\ndiv.list-of-figures p:first-child,\ndiv.list-of-tables p:first-child,\ndiv.list-of-examples p:first-child,\ndiv.example p.title,\ndiv.sidebar p.title\n{\n font-weight: bold;\n color: #527bbd;\n font-family: Arial,Helvetica,sans-serif;\n margin-bottom: 0.2em;\n}\n\nbody h1 {\n margin: .0em 0 0 -4%;\n line-height: 1.3;\n border-bottom: 2px solid silver;\n}\n\nbody h2 {\n margin: 0.5em 0 0 -4%;\n line-height: 1.3;\n border-bottom: 2px solid silver;\n}\n\nbody h3 {\n margin: .8em 0 0 -3%;\n line-height: 1.3;\n}\n\nbody h4 {\n margin: .8em 0 0 -3%;\n line-height: 1.3;\n}\n\nbody h5 {\n margin: .8em 0 0 -2%;\n line-height: 1.3;\n}\n\nbody h6 {\n margin: .8em 0 0 -1%;\n line-height: 1.3;\n}\n\nbody hr {\n border: none; /* Broken on IE6 */\n}\ndiv.footnotes hr {\n border: 1px solid silver;\n}\n\ndiv.navheader th, div.navheader td, div.navfooter td {\n font-family: Arial,Helvetica,sans-serif;\n font-size: 0.9em;\n font-weight: bold;\n color: #527bbd;\n}\ndiv.navheader img, div.navfooter img {\n border-style: none;\n}\ndiv.navheader a, div.navfooter a {\n font-weight: normal;\n}\ndiv.navfooter hr {\n border: 1px solid silver;\n}\n\nbody td {\n line-height: 1.2\n}\n\nbody th {\n line-height: 1.2;\n}\n\nol {\n line-height: 1.2;\n}\n\nul, body dir, body menu {\n line-height: 1.2;\n}\n\nhtml {\n margin: 0; \n padding: 0;\n}\n\nbody h1, body h2, body h3, body h4, body h5, body h6 {\n margin-left: 0\n} \n\nbody pre {\n margin: 0.5em 10% 0.5em 1em;\n line-height: 1.0;\n color: navy;\n}\n\ntt.literal, code.literal {\n color: navy;\n}\n\n.programlisting, .screen {\n border: 1px solid silver;\n background: #f4f4f4;\n margin: 0.5em 10% 0.5em 0;\n padding: 0.5em 1em;\n}\n\ndiv.sidebar {\n background: #ffffee;\n margin: 1.0em 10% 0.5em 0;\n padding: 0.5em 1em;\n border: 1px solid silver;\n}\ndiv.sidebar * { padding: 0; }\ndiv.sidebar div { margin: 0; }\ndiv.sidebar p.title {\n margin-top: 0.5em;\n margin-bottom: 0.2em;\n}\n\ndiv.bibliomixed {\n margin: 0.5em 5% 0.5em 1em;\n}\n\ndiv.glossary dt {\n font-weight: bold;\n}\ndiv.glossary dd p {\n margin-top: 0.2em;\n}\n\ndl {\n margin: .8em 0;\n line-height: 1.2;\n}\n\ndt {\n margin-top: 0.5em;\n}\n\ndt span.term {\n font-style: normal;\n color: navy;\n}\n\ndiv.variablelist dd p {\n margin-top: 0;\n}\n\ndiv.itemizedlist li, div.orderedlist li {\n margin-left: -0.8em;\n margin-top: 0.5em;\n}\n\nul, ol {\n list-style-position: outside;\n}\n\ndiv.sidebar ul, div.sidebar ol {\n margin-left: 2.8em;\n}\n\ndiv.itemizedlist p.title,\ndiv.orderedlist p.title,\ndiv.variablelist p.title\n{\n margin-bottom: -0.8em;\n}\n\ndiv.revhistory table {\n border-collapse: collapse;\n border: none;\n}\ndiv.revhistory th {\n border: none;\n color: #527bbd;\n font-family: Arial,Helvetica,sans-serif;\n}\ndiv.revhistory td {\n border: 1px solid silver;\n}\n\n/* Keep TOC and index lines close together. */\ndiv.toc dl, div.toc dt,\ndiv.list-of-figures dl, div.list-of-figures dt,\ndiv.list-of-tables dl, div.list-of-tables dt,\ndiv.indexdiv dl, div.indexdiv dt\n{\n line-height: normal;\n margin-top: 0;\n margin-bottom: 0;\n}\n\n/*\n Table styling does not work because of overriding attributes in\n generated HTML.\n*/\ndiv.table table,\ndiv.informaltable table\n{\n margin-left: 0;\n margin-right: 5%;\n margin-bottom: 0.8em;\n}\ndiv.informaltable table\n{\n margin-top: 0.4em\n}\ndiv.table thead,\ndiv.table tfoot,\ndiv.table tbody,\ndiv.informaltable thead,\ndiv.informaltable tfoot,\ndiv.informaltable tbody\n{\n /* No effect in IE6. */\n border-top: 3px solid #527bbd;\n border-bottom: 3px solid #527bbd;\n}\ndiv.table thead, div.table tfoot,\ndiv.informaltable thead, div.informaltable tfoot\n{\n font-weight: bold;\n}\n\ndiv.mediaobject img {\n margin-bottom: 0.8em;\n}\ndiv.figure p.title,\ndiv.table p.title\n{\n margin-top: 1em;\n margin-bottom: 0.4em;\n}\n\ndiv.calloutlist p\n{\n margin-top: 0em;\n margin-bottom: 0.4em;\n}\n\na img {\n border-style: none;\n}\n\n@media print {\n div.navheader, div.navfooter { display: none; }\n}\n\nspan.aqua { color: aqua; }\nspan.black { color: black; }\nspan.blue { color: blue; }\nspan.fuchsia { color: fuchsia; }\nspan.gray { color: gray; }\nspan.green { color: green; }\nspan.lime { color: lime; }\nspan.maroon { color: maroon; }\nspan.navy { color: navy; }\nspan.olive { color: olive; }\nspan.purple { color: purple; }\nspan.red { color: red; }\nspan.silver { color: silver; }\nspan.teal { color: teal; }\nspan.white { color: white; }\nspan.yellow { color: yellow; }\n\nspan.aqua-background { background: aqua; }\nspan.black-background { background: black; }\nspan.blue-background { background: blue; }\nspan.fuchsia-background { background: fuchsia; }\nspan.gray-background { background: gray; }\nspan.green-background { background: green; }\nspan.lime-background { background: lime; }\nspan.maroon-background { background: maroon; }\nspan.navy-background { background: navy; }\nspan.olive-background { background: olive; }\nspan.purple-background { background: purple; }\nspan.red-background { background: red; }\nspan.silver-background { background: silver; }\nspan.teal-background { background: teal; }\nspan.white-background { background: white; }\nspan.yellow-background { background: yellow; }\n\nspan.big { font-size: 2em; }\nspan.small { font-size: 0.6em; }\n\nspan.underline { text-decoration: underline; }\nspan.overline { text-decoration: overline; }\nspan.line-through { text-decoration: line-through; }\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/files/StatsDumper.groovy",
"content": "//CLASSPATH=/home/tigase/tigase-server/jars/tigase-server.jar\nimport tigase.stats.JavaJMXProxy\nimport tigase.stats.JMXProxyListener\nimport tigase.stats.StatisticsProviderMBean\n\nif (args.size() > 0) {\n if (args[0] == \"-h\") {\n println (\"Parameters are: [hostname] [username] [password] [dir] [port] [delay(ms)] [interval(ms)] [loadhistory(bool)]\")\n System.exit(0)\n }\n}\n\n\ndef hostname = args.size() > 0 ? args[0] : \"0.0.0.0\"\ndef username = args.size() > 1 ? args[1] : \"admin\"\ndef password = args.size() > 2 ? args[2] : \"pass\"\ndef dir = args.size() > 3 ? args[3] : \"stats\"\ndef port = args.size() > 4 ? args[4].toInteger() : 9050\ndef delay = args.size() > 5 ? args[5].toLong() : 10000\ndef interval = args.size() > 6 ? args[6].toLong() : 10000\ndef loadHistory = args.size() > 7 ? args[7].toBoolean() : false\n\nif (!new File(dir).exists()) {\n new File(dir).mkdir()\n}\n\ndef proxy = new JavaJMXProxy(hostname, hostname, port, username, password, delay, interval, loadHistory)\nproxy.start()\n\nsleep delay\n\nwhile (true) {\n try {\n def allStats = proxy.getAllStats(0)\n if (allStats != null) {\n def timeToken = (int) System.currentTimeMillis() / 1000.toInteger() / 60.toInteger()\n def file1 = new File(\"${dir}/stats_${new Date().format('yyyy-MM-dd_hh:mm:ss')}.txt\")\n println \"Saving stats to the file ${file1.path}\"\n allStats.each { key, value -> file1 << key + \" \" + value + \"\\n\" }\n }\n } catch(all) {\n println(\"An exception: \" + all)\n }\n sleep interval\n}\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/index.asciidoc",
"content": "= Tigase Administration Guide\nTigase Team \nv7.1.0\n:numbered:\n:website: http://tigase.net\n:Date: 2014-07-10\n\n\nWelcome to the Tigase Administration Guide.\n\n:leveloffset: 1\n\ninclude::text/Tigase_v7.1.0.asciidoc[]\n\ninclude::text/Admin_Guide_01_-_About_Tigase_Jabber_XMPP_Server.asciidoc[]\n\ninclude::text/Admin_Guide_02_-_Quick_Start.asciidoc[]\n\n\n:leveloffset: 2\n\ninclude::text/Admin_Guide_03_-_Quick_Start_-_A_-_Installation_Using_GUI_Installer.asciidoc[]\n\ninclude::text/Admin_Guide_04_-_Quick_Start_-_B_-_Installation_Using_Web_Installer.asciidoc[]\n\ninclude::text/Admin_Guide_05_-_Quick_Start_-_C_-_Installing_Using_Console_Installer.asciidoc[]\n\ninclude::text/Admin_Guide_06_-_Quick_Start_-_D_-_Manual_Installation_in_Console_Mode.asciidoc[]\n\ninclude::text/Admin_Guide_07_-_Quick_Start_-_E_-_Windows_Installation.asciidoc[]\n\ninclude::text/Admin_Guide_07_-_Quick_Start_-_F_-_Setting_Up_Server.asciidoc[]\n\n:leveloffset: 1\n\ninclude::text/Admin_Guide_08_-_Latest_and_Nightly_Builds.asciidoc[]\n\ninclude::text/Admin_Guide_09_-_Configuration.asciidoc[]\n\n:leveloffset: 2\n\ninclude::text/Admin_Guide_10_-_Configuration_-_A_-_Tigase_XMPP_Server_init.properties_Configuration.asciidoc[]\n\ninclude::text/Admin_Guide_11_-_Configuration_-_B_-_Startup_Files_tigase.sh_and_tigase.asciidoc[]\n\ninclude::text/Admin_Guide_12_-_Configuration_-_C_-_Linux_Settings_for_High_Load_Systems.asciidoc[]\n\ninclude::text/Admin_Guide_13_-_Configuration_-_D_-_Configuration_Storage_Options.asciidoc[]\n\ninclude::text/Admin_Guide_13_-_Configuration_-_E_-_JVM_settings.asciidoc[]\n\ninclude::text/Admin_Guide_105_-_Configuration_-_F_-_Sess-man.asciidoc[]\n\n:leveloffset: 1\n\ninclude::text/Admin_Guide_14_-_Security.asciidoc[]\n\n:leveloffset: 2\n\ninclude::text/Admin_Guide_15_-_Security_-_A_-_Server_Certificates.asciidoc[]\n\n:leveloffset: 3\n\ninclude::text/Admin_Guide_16_-_Security_-_A_-_Server_Certificates_-_1_-_Creating_and_Loading_the_Server_Certificate_in_PEM_Files.asciidoc[]\n\ninclude::text/Admin_Guide_17_-_Security_-_A_-_Server_Certificates_-_2_-_Installing_StartCom_Certificate_in_your_Linux_System.asciidoc[]\n\n//include::text/Admin_Guide_18_-_Security_-_A_-_Server_Certificates_-_3_-_Server_Certificate_Using_Keytool_and_Keystore.asciidoc[]\n\n:leveloffset: 2\n\ninclude::text/Admin_Guide_19_-_Security_-_B_-_Authentication_Connectors.asciidoc[]\n\n:leveloffset: 3\n\ninclude::text/Admin_Guide_20_-_Security_-_B_-_Authentication_Connectors_-_1_-_Tigase_Auth_Connector.asciidoc[]\n\ninclude::text/Admin_Guide_21_-_Security_-_B_-_Authentication_Connectors_-_2_-_Tigase_Custom_Auth_Connector.asciidoc[]\n\ninclude::text/Admin_Guide_22_-_Security_-_B_-_Authentication_Connectors_-_3_-_Drupal_Authentication_Added.asciidoc[]\n\ninclude::text/Admin_Guide_23_-_Security_-_B_-_Authentication_Connectors_-_4_-_LDAP_Authentication_Connector.asciidoc[]\n\ninclude::text/Admin_Guide_24_-_Security_-_B_-_Authentication_Connectors_-_5_-_Configuration_of_SASL_EXTERNAL.asciidoc[]\n\n:leveloffset: 2\n\ninclude::text/Admin_Guide_25_-_Security_-_C_-_Packet_Filtering.asciidoc[]\n\n:leveloffset: 3\n\ninclude::text/Admin_Guide_26_-_Security_-_C_-_Packet_Filtering_-_1_-_Domain_Based_Packet_Filtering.asciidoc[]\n\n:leveloffset: 2\n\ninclude::text/Admin_Guide_27_-_Security_-_D_-_Access_Control_List.asciidoc[]\n\n:leveloffset: 1\n\ninclude::text/Admin_Guide_28_-_Database_Management.asciidoc[]\n\n:leveloffset: 2\n\ninclude::text/Admin_Guide_29_-_Database_Management_-_A_-_Database_Preparation.asciidoc[]\n\n:leveloffset: 3\n\ninclude::text/Admin_Guide_29_-_Database_Management_-_A_-_Database_Preperation_-_1_-_DbSchemaLoader.asciidoc[]\n\ninclude::text/Admin_Guide_30_-_Database_Management_-_A_-_Database_Preparation_-_1_-_Prepare_the_MySQL_Database_for_Tigase_Server.asciidoc[]\n\ninclude::text/Admin_Guide_31_-_Database_Management_-_A_-_Database_Preparation_-_2_-_Prepare_the_Derby_Database_for_Tigase_Server.asciidoc[]\n\ninclude::text/Admin_Guide_32_-_Database_Management_-_A_-_Database_Preparation_-_3_-_Prepare_the_MS_SQL_Server_Database_for_Tigase_Server.asciidoc[]\n\ninclude::text/Admin_Guide_33_-_Database_Management_-_A_-_Database_Preparation_-_4_-_Prepare_the_PostgreSQL_Database_for_Tigase_Server.asciidoc[]\n\ninclude::text/Admin_Guide_34_-_Database_Management_-_A_-_Database_Preperation_-_5_-_Prepare_Tigase_for_MongoDB.asciidoc[]\n\n:leveloffset: 2\n\ninclude::text/Admin_Guide_35_-_Database_Management_-_B_-_Hashed_User_Passwords_in_Database.asciidoc[]\n\ninclude::text/Admin_Guide_36_-_Database_Management_-_C_-_Tigase_Server_and_Multiple_Databases.asciidoc[]\n\ninclude::text/Admin_Guide_37_-_Database_Management_-_D_-_Importing_User_Data.asciidoc[]\n\ninclude::text/Admin_Guide_38_-_Database_Management_-_E_-_Integrating_Existing_Databases.asciidoc[]\n\n:leveloffset: 3\n\ninclude::text/Admin_Guide_39_-_Database_Management_-_E_-_Integrating_Existing_Databases_-_1_-_Connecting_Tigase_Server_to_MySQL_Database.asciidoc[]\n\ninclude::text/Admin_Guide_40_-_Database_Management_-_E_-_Integrating_Existing_Databases_-_2_-_Integrating_Tigase_Server_with_Drupal.asciidoc[]\n\ninclude::text/Admin_Guide_41_-_Database_Management_-_E_-_Integrating_Existing_Databases_-_3_-_Integrating_Tigase_Server_with_LibreSource.asciidoc[]\n\ninclude::text/Admin_Guide_42_-_Database_Management_-_E_-_Integrating_Existing_Databases_-_4_-_MySQL_Database_Use.asciidoc[]\n\ninclude::text/Admin_Guide_43_-_Database_Management_-_E_-_Integrating_Existing_Databases_-_5_-_PostgreSQL_Database.asciidoc[]\n\n:leveloffset: 2\n\ninclude::text/Admin_Guide_44_-_Database_Management_-_F_-_Schema_Updates.asciidoc[]\n\n:leveloffset: 3\n\ninclude::text/Admin_Guide_45_-_Database_Managament_-_F_-_Schema_Updates_-_A_-_Tigase_Server_7.1.asciidoc[]\n\ninclude::text/Admin_Guide_46_-_Database_Management_-_F_-_Schema_Updates_-_B_-_Tigase_Server_Version_5.x.asciidoc[]\n\ninclude::text/Admin_Guide_47_-_Database_Management_-_F_-_Schema_Updates_-_B_-_Tigase_Server_Version_5.x_-_1_-_Derby.asciidoc[]\n\ninclude::text/Admin_Guide_48_-_Database_Management_-_F_-_Schema_Updates_-_B_-_Tigase_Server_Version_5.x_-_2_-_MySQL_Database_Schema_Upgrade_for_Tigase_5.1.asciidoc[]\n\ninclude::text/Admin_Guide_49_-_Database_Management_-_F_-_Schema_Updates_-_B_-_Tigase_Server_Version_5.x_-_3_-_PostgreSQL_Database_Schema_Upgrade_for_Tigase_5.1.asciidoc[]\n\ninclude::text/Admin_Guide_50_-_Database_Management_-_F_-_Schema_Updates_-_B_-_Tigase_Server_Version_5.x_-_4_-_Tigase_Database_Minor_but_Useful_Schema_Change_in_Version_5.1.asciidoc[]\n\ninclude::text/Admin_Guide_51_-_Database_Management_-_F_-_Schema_Updates_-_C_-_Tigase_Server_Version_4.x.asciidoc[]\n\ninclude::text/Admin_Guide_52_-_Database_Management_-_F_-_Schema_Updates_-_C_-_Tigase_Server_Version_4.x_-_1_-_MySQL_Database_Schema_Upgrade_for_Tigase_4.0.asciidoc[]\n\n:leveloffset: 1\n\ninclude::text/Admin_Guide_53_-_Components.asciidoc[]\n\n:leveloffset: 2\n\ninclude::text/Admin_Guide_54_-_Components_-_A_-_StanzaSender.asciidoc[]\n\ninclude::text/Admin_Guide_55_-_Components_-_B_-_Tigase_HTTP_API.asciidoc[]\n\n:leveloffset: 3\n\ninclude::text/Admin_Guide_56_-_Components_-_B_-_Tigase_HTTP_API_-_1_-_REST_API_Guide.asciidoc[]\n\ninclude::text/Admin_Guide_57_-_Components_-_B_-_Tigase_HTTP_API_-_2_-_Admin_UI.asciidoc[]\n\ninclude::text/Admin_Guide_58_-_Components_-_B_-_Tigase_HTTP_API_-_3_-_Web_Client.asciidoc[]\n\n:leveloffset: 2\n\ninclude::text/Admin_Guide_59_-_Components_-_C_-_Message_Archiving.asciidoc[]\n\ninclude::text/Admin_Guide_60_-_Components_-_D_-_Advanced_Message_Processing_-_AMP_XEP-0079.asciidoc[]\n\ninclude::text/Admin_Guide_61_-_Components_-_E_-_PubSub.asciidoc[]\n\n:leveloffset: 3\n\ninclude::text/Admin_Guide_62_-_Components_-_E_-_PubSub_-_1_-_Offline_Message_Sink.asciidoc[]\n\ninclude::text/Admin_Guide_63_-_Components_-_E_-_PubSub_-_2_-_PubSub_Schema_Changes.asciidoc[]\n\n:leveloffset: 2\n\ninclude::text/Admin_Guide_64_-_Components_-_F_-_Server_Monitoring.asciidoc[]\n\n:leveloffset: 3\n\ninclude::text/Admin_Guide_65_-_Components_-_F_-_Server_Monitoring_-_1_-_Setting_up_Remote_Monitoring_in_the_Server.asciidoc[]\n\ninclude::text/Admin_Guide_66_-_Components_-_F_-_Server_Monitoring_-_2_-_Retrieving_statistics.asciidoc[]\n\ninclude::text/Admin_Guide_102_-_Statistics_Descriptions.asciidoc[]\n\n:leveloffset: 2\n\ninclude::text/Admin_Guide_67_-_Components_-_F_-_Server_Monitoring_-_3_-_EventBus.asciidoc[]\n\n:leveloffset: 2\n\ninclude::text/Admin_Guide_68_-_Components_-_G_-_Server_to_Server_Protocol.asciidoc[]\n\ninclude::text/Admin_Guide_69_-_Components_-_H_-_MUC.asciidoc[]\n\ninclude::text/Admin_Guide_70_-_Components_-_I_-_Tigase_Load_Balancing.asciidoc[]\n\ninclude::text/Admin_Guide_71_-_Components_-_J_-_External_Component_Configuration.asciidoc[]\n\n:leveloffset: 3\n\ninclude::text/Admin_Guide_72_-_Components_-_J_-_External_Component_Configuration_-_1_-_Basic_Configuration_Options_(external_component).asciidoc[]\n\ninclude::text/Admin_Guide_73_-_Components_-_J_-_External_Component_Configuration_-_2_-_Tigase_as_External_Component.asciidoc[]\n\ninclude::text/Admin_Guide_74_-_Components_-_J_-_External_Component_Configuration_-_3_-_Load_Balancing_External_Components_in_Cluster_Mode.asciidoc[]\n\n:leveloffset: 2\n\ninclude::text/Admin_Guide_103_-_Components_-_K_-_C2S.asciidoc[]\n\ninclude::text/Admin_Guide_106_-_Components_-_L_-_Socks5.asciidoc[]\n\ninclude::text/Admin_Guide_75_-_Virtual_Hosts_in_the_Tigase_Server.asciidoc[]\n\n:leveloffset: 3\n\ninclude::text/Admin_Guide_76_-_Virtual_Hosts_in_the_Tigase_Server_-_A_-_Specification_for_ad-hoc_Commands_Used_to_Manage_Virtual_Domains.asciidoc[]\n\ninclude::text/Admin_Guide_77_-_Virtual_Hosts_in_the_Tigase_Server_-_B_-_Virtual_Components_for_Cluster_Mode.asciidoc[]\n\n:leveloffset: 1\n\ninclude::text/Admin_Guide_78_-_Using_Tigase.asciidoc[]\n\n:leveloffset: 2\n\ninclude::text/Admin_Guide_79_-_Using_Tigase_-_A_-_Log_Guide.asciidoc[]\n\ninclude::text/Admin_Guide_80_-_Using_Tigase_-_B_-_Debugging_Tigase.asciidoc[]\n\ninclude::text/Admin_Guide_81_-_Using_Tigase_-_C_-_Basic_System_Checks.asciidoc[]\n\ninclude::text/Admin_Guide_82_-_Using_Tigase_-_D_-_Add_and_Manage_Virtual_Domains.asciidoc[]\n\ninclude::text/Admin_Guide_83_-_Using_Tigase_-_E_-_Presence_Forwarding.asciidoc[]\n\ninclude::text/Admin_Guide_84_-_Using_Tigase_-_F_-_Register_Own_XMPP_Domain.asciidoc[]\n\ninclude::text/Admin_Guide_85_-_Using_Tigase_-_G_-_Tigase_and_PyMSN-t_Transport.asciidoc[]\n\ninclude::text/Admin_Guide_86_-_Using_Tigase_-_H_-_Two_or_more_SessionManagers.asciidoc[]\n\ninclude::text/Admin_Guide_87_-_Using_Tigase_-_I_-_Watchdog.asciidoc[]\n\ninclude::text/Admin_Guide_88_-_Using_Tigase_-_J_-_Tips_and_Tricks.asciidoc[]\n\n:leveloffset: 3\n\ninclude::text/Admin_Guide_89_-_Using_Tigase_-_J_-_Tips_and_Tricks_-_1_-_Tigase_Tip_Checking_the_Runtime_Environment.asciidoc[]\n\ninclude::text/Admin_Guide_91_-_Using_Tigase_-_J_-_Tips_and_Tricks_-_3_-_Best_Practices_for_Connecting_From_Web_Browser_to_Tigase_XMPP_Server.asciidoc[]\n\n:leveloffset: 2\n\ninclude::text/Admin_Guide_92_-_Using_Tigase_-_K_-_Command_Line_Tools.asciidoc[]\n\n:leveloffset: 3\n\ninclude::text/Admin_Guide_93_-_Using_Tigase_-_K_-_Command_Line_Tools_-_1_-_Configuration_Managament_Tool.asciidoc[]\n\n:leveloffset: 2\n\ninclude::text/Admin_Guide_94_-_Using_Tigase_-_L_-_Scripting_Support_in_Tigase.asciidoc[]\n\n:leveloffset: 3\n\ninclude::text/Admin_Guide_95_-_Using_Tigase_-_L_-_Scripting_Support_in_Tigase_-_1_-_Scripting_Introduction_-_Hello_World.asciidoc[]\n\ninclude::text/Admin_Guide_96_-_Using_Tigase_-_L_-_Scripting_Support_in_Tigase_-_2_-_Tigase_Scripting_Version_4.4.x_Update_for_Administrators.asciidoc[]\n\ninclude::text/Admin_Guide_97_-_Using_Tigase_-_L_-_Scripting_Support_in_Tigase_-_3_-_Tigase_and_Python.asciidoc[]\n\n:leveloffset: 2\n\ninclude::text/Admin_Guide_98_-_Using_Tigase_-_M_-_Configuration_Wizards.asciidoc[]\n\ninclude::text/Admin_Guide_99_-_Using_Tigase_-_N_-_Offline_Messages.asciidoc[]\n\ninclude::text/Admin_Guide_100_-_Using_Tigase_-_O_-_Licensing.asciidoc[]\n\ninclude::text/Admin_Guide_101_-_Using_Tigase_-_P_-_Advanced_Options.asciidoc[]\n\ninclude::text/Admin_Guide_104_-_Using_Tigase_-_Q_-_Clustering.asciidoc[]\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_01_-_About_Tigase_Jabber_XMPP_Server.asciidoc",
"content": "[[about]]\n= About Tigase XMPP Server\n\n:Author: Artur Hefczyc \n:Version: v2.0, June 2014: reformatted for AsciiDoc\n:Date: 2010-04-06 16:18\n:Revision: 2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\n*Tigase XMPP Server* is an *Open Source and Free (AGPLv3)* Java based server. The goals behind its design and implementation of the server are:\n\n. Make the server robust and reliable.\n. Make the server a secure communication platform.\n. Make a flexible server which can be applied to different use cases.\n. Make an extensible server which takes full advantage of XMPP protocol extensibility.\n. Make the server easy to setup and maintain.\n\n== Robust and reliable\n\nThis means that the server can handle many concurrent requests/connections and can run for a long time reliably. The server is designed and implemented to handle millions of simultaneous connections.\n\nIt is not enough however to design and implement a high load server and hope it will run well. The main focus of the project is put in into testing. Tests are taken so seriously that a dedicated testing framework has been implemented. All server functions are considered as implemented only when they pass a rigorous testing cycle. The testing cycle consists of 3 fundamental tests:\n\n. *Functional tests* - Checking whether the function works at all.\n. *Performance tests* - Checking whether the function performs well enough.\n. *Stability tests* - Checking whether the function behaves well in long term run. It must handle hundreds of requests a second in a several hour server run.\n\n== Security\n\nThere are a few elements of the security related to XMPP servers: secure data transmissions which is met by the implementation of *SSL* or *TLS* protocol, secure user authorization which is met by the implementation of *DIGEST* or *SASL* user authorization and secure deployment which is met by component architecture.\n\n*Secure deployment* Tigase software installation does not impact network security. Companies usually have their networks divided into 2 parts: *DMZ* which is partially open to the outside world and the *Private network* which is closed to the outside world.\n\nIf the XMPP server is to provide an effective way of communication between company employees regardless if they are in a secure company office or outside (perhaps at a customer site), it needs to accept both internal and external connections. So the natural location for the server deployment is the *DMZ*. However, this solution has some considerations: each company has normally established network users base and integrated authorization mechanisms. However, that information should be stored outside the DMZ to protect internal security, so how to maintain ease of installation and system security?\n\n*Tigase server* offers a solution for such a case. With it's component structure, Tigase can be easily deployed on any number machines and from the user's point of view it is seen as a one logical XMPP server. In this case we can install a Session Manager module in the *private* network, and a Client Connection Manager with Server Connection Manager in the *DMZ*.\n\nSession Manager connects to *DMZ* and receives all packets from external users. Thus is can securely realize users authorization based on company authorization mechanisms.\n\n== Flexibility\n\nThere are many different XMPP server implementations. The most prevolant are:\n\n- Used as a business communication platform in small and medium companies where the server is not under a heavy load. For such deployments security is a key feature.\n- For huge community websites or internet portal servers is, on the other hand, usually under very heavy load and has to support thousands or millions of simultaneous connections. For such a deployment we need a different level of security as most of the service is open to the public.\n- For very small community deployments or for small home networks the key factor is ease to deploy and maintain.\n\nArchitecture based on components provides the ability to run selected modules on separate machines so the server can be easily applied in any scenario.\n\nFor simple installation the server generates a config file which can be used straight away with very few modifications or none at all. For complex deployments though, you can tweak configurations to your needs and setup XMPP server on as many physical machines as you need.\n\n== Extensibility\n\nThe world changes all the time as does user's needs. The XMPP protocol has been designed to be extensible to make it easy to add new features and apply it to those different user's needs. As a result, XMPP is a very effective platform not only for sending messages to other users, it can also be extended for sending instant notifications about events, a useful platform for on-line customer service, voice communication, and other cases where sending information instantly to other people is needed.\n\n*Tigase server* has been designed to be extensible using a modular architecture. You can easily replace components which do not fulfill your requirements with others better fitting your needs. But that is not all, another factor of extensibility is how easy is to replace or add new extensions. A great deal of focus has been put into the server design API to make it easy for other software developers to create extensions and implement new features.\n\n== Ease of Use\n\nComplex computer networks consisting of many servers with different services are hard to maintain. This requires employing professional staff to operate and maintain the network.\n\nNot all networks are so complex however, most small companies have just a few servers for their needs with services like e-mail and a HTTP server. They might want to add an XMPP server to the collection of their services and don't want to dedicate resources on setup and maintenance. For such users our default configuration is exactly what they need. If the operating system on the server is well configured, then Tigase should automatically pickup the correct hostname and be ready to operate immediately.\n\nTigase server is designed and implemented to allow dynamic reconfiguration during runtime so there is no need to restart the server each time you want to change configuration settings.\n\nThere are also interfaces and handlers available to make it easy to implement a web user interface for server monitoring and configuring.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_02_-_Quick_Start.asciidoc",
"content": "[[QuickStart]]\n= Quick Start Guide\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 21:18\n:revision: 2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\n== Minimum Requirements\n\nBefore you begin installing Tigase server onto your system, please make sure the minimum requirements are installed first: +\n- *Java Development Kit v8 or later* - We recommend Oracle JDK. OpenJDK may work, but some features might cause errors. +\n\n- *Administrator access* - We recommend that you install Tigase Server from a user login with administrator access. +\n\n== Contents\n\nThis is a set of documents allowing you to quickly start with our software. Every document provides an introduction to a single topic allowing you to start using/developing or just working on the subject. Please have a look at the documents list below to find a topic you are looking for. If you don't find a document for the topic you need please link:http://www.tigase.net/contact[let us know].\n\n- xref:guiinstall[Installation using GUI installer]\n- xref:consoleinstall[Installing using console installer]\n- xref:manualinstall[Manual installation in console mode]\n- xref:webinstall[Installation Using Web Installer]\n- xref:TSBupdates[Tigase server binary updates]\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_03_-_Quick_Start_-_A_-_Installation_Using_GUI_Installer.asciidoc",
"content": "[[guiinstall]]\n= Installation Using GUI Installer\n\n:author: Mateusz Fiolka\n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 21:18\n:revision: 2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nIf you don't want to install Tigase using a manual method, you can use the GUI installer. It not only copies server files to preferred place, but also assists with configuration of the most important parameters and database setup. Therefore we recommend this as the way to install Tigase.\n\n== Prerequisites\n\nBefore you can start the GUI installer you will need to have working Java environment. Although installer only requires *JRE* (Java Runtime Environment), server needs the *JDK* (Java Development Kit). Please do note that *currently minimal JDK version Tigase is capable to run on is 1.6*. If you don't have JDK installed it is the right moment to do it. Visit the link:http://java.sun.com/javase/downloads/index.jsp[Java downloads site] From the list of available packages select newest JDK version (if you don't have a specific need to use J2EE then choose a package without it). After configuring JDK you can download the Tigase GUI installer and start the server installation process. It is also important to set the +JAVA_HOME+ environment correctly.\n\n== Download the Installer\n\nYou can always find the newest Tigase packages in the link:https://projects.tigase.org/projects/tigase-server/files[download section]. When you enter the page, you will be presented a list of files to choose from. You may be confused at the beginning as there are lot of choices, but all Tigase binary packages have conventional names, which help to differentiate them easily. They are of form *tigase-server-x.y.z-bv.ext* where 'x', 'y', 'z' and 'v' are version numbers and they change from a release to release. Ext is the file extension which in the case of our GUI installation program is *.jar*. We recommend you to download the latest version (highest version number) of the server as it contains latest functions and improvements\n\n== Run the jar File\n\nOn most systems installing JRE or JDK creates a default association which allows to run the *.jar* file by just double clicking on it. However if nothing happens when you do it there is a way to do it manually. Perform the steps in the following order:\n\n. If you are on *Windows* system you can use the command prompt to run the installer directly using the java command.\n .. Click on the *Start* menu and choose *Run...* (You can also use the *Win+R* shortcut).\n .. You will be presented with a dialog box where you can enter a command. Type \"*cmd*\" (or \"*command*\" in the case of windows version older then 2000) and submit the window.\nIf you are on a *Linux* system, you can use a terminal. It should be easily discoverable as it is a standard tool on this platform. Find and run it.\n. Command prompt / terminal will appear. You will be able to check a whether your *Java* environment is working. To do it type the\n+\n[source,bash]\n-----\njava -version\n-----\n+\ncommand and press Enter. If the message says that the command is not recognized then your *Java* installation may be corrupt or not configured properly. For correctly setting up *JRE/JDK* including setting the *JAVA_HOME* environmental variable please check documentation provided on the JDK download site. Also when the command succeeds please check if the printed version number fulfills Tigase requirements. When many versions of *JDK/JRE* are installed on one machine *java* command will need to be invoked with the full path it is placed on.\n+\n. When you have no doubt that you can run the correct Java launcher, you may start the installer i.e. for the file *tigase-server-4.1.0-b1315.jar* downloaded to the *c:\\download* directory type the following command:\n+\n[source,bash]\n-----\njava -jar c:\\download\\tigase-server-4.1.0-b1315.jar\n-----\n+\nThis command should start the installer or print an error message explaining what is the cause of problem.\n\n== Starting the Installation\n\nPlease note that this tutorial covers only the basic installation mode. Some screens have been omitted because they contain advanced options which are not shown in simple installation mode. Others such as progress of copying files and summary info on the other hand are self explanatory and will also not described.\n\n\n== JDK Selection\n\nimage:images/winInstall2.gif[]\n\nThis screen is only shown when JDK has not been selected automatically. When your JAVA_HOME path is properly set, it will be auto-detected saving you some configuration time. If you are reading this step and still don't have JDK installed, then go back to the xref:prerequisites[prerequisites] section where you can find some info on how to prepare your system for Tigase installation. Sometimes your system will be configured in a way that prevents detection of JDK path. This often happens when you install JRE after installing JDK. You will have to find JDK directory yourself. It is by default installed in the *Program Files\\Java* directory of your system drive.\n\n== Installation Type Selection\n\nimage:images/winInstall3.gif[]\n\nRecommended practice is to choose both installation and configuration of the server as manual configuration is more complicated, time consuming and error-prone.\n\n== Introduction To the Server\n\nimage:images/winInstall4.gif[]\n\nThis screen shows some information about Tigase which may help you understand what it is and how it can help to take advantage of the *XMPP* protocol. It is important that you read all information's appearing on the installer screens, as they contain valuable hints and most recent information.\n\n== Choice of Base Directory\n\nimage:images/winInstall6.gif[]\n\nThis is the point where you choose where do you want you server to be installed. Recommended path should not contain spaces, as it may be reason of some strange path problems. In the case of installation on Windows it should be installed on a short path because there is a limit of path lengths. Also note that on Windows Vista there may be some problems with making the server work while installed in the Program Files directory, related to the working of UAC mechanism, so better don't install it there. If you don't want are unsure about where to place the server, you can always leave the default selection.\n\n== Packages selection\n\nimage:images/winInstall7.gif[]\n\nNext important step is package selection. Note that some choices are grayed out and you cannot change them as they are essential. Packages consist of documentation, database drivers, sources of the server and some extras. When you select an item, you will be presented with a short description of it's content.\n\nWe recommend that you install documentation. It contains valuable resources which may be very helpful in administration and general use of the server.\n\nIf you have a working database platform that you want to use for storing all important user information in, just select appropriate db drivers. If you don't have a database engine, you can use the included derby database along with also included drivers.\n\nIf you are a developer and you want to be able to check how the server is working or if you want to help with the development, you can install also the included source codes.\n\n== Basic Server Configuration\n\nimage:images/winInstall13.gif[]\n\nOn this screen you will find most important basic configuration options. As this guide covers only non-advanced set up - disable the advanced configuration checkbox.\n\nFrom here you can select which components will be installed. For most installations the default selection will be most appropriate. You can expand the list to check if any of the other options will better suit your needs.\n\nIt is very important that you enter your domain name correctly here.\n\n- On *Linux* like system you can use the *hostname* command and extract the domain part from the output. If you use the *-f* parameter then you will get the fully qualified domain name.\n- On *Windows* use the standard *System* control panel applet. You will find your domain (computer name) in the *Computer name* tab.\n\nOn the other hand if you want to use Tigase virtual domain support and you have your *DNS* system configured properly, then you can put your virtual domains list here. Just separate them by comma characters. For example if your server is seen from the outside as *veloci.tigase.org,* *mammoth.tigase.org* and *tigase.org* then you can use Tigase instance as if it were three separate instances. In reality it will be one server, however *admin@veloci.tigase.org* will be a different user then *admin@tigase.org.* This feature allows to use one server to separate user groups, for example ones from different organizations.\n\nWhen you have your domain name just enter it in the domain text box. Next parameter will be the JID of server administrator. Standard practice is to use *admin*, however you may choose any name you like. For example for domain *tigase.org* the full admin name would be *admin@tigase.org.* Just stick your chosen name and domain together using the @ character as separator.\n\nUsing this information your XMPP admin will be automatically added to the database, so after installation you can just login into the server without registering admin first manually.\n\nYou should also select a database which will be used for storing user info. Default is the *Derby* database, if you don't need anything special just leave it as it is. Just select a new password as the default one is easy for a hacker to guess.\n\n*Important notice: Tigase installer does not contain the actual databases, only drivers allowing db access. The only exception is Derby database, which is included in JDK. It is automatically configured by installer, in case of other databases you will need to configure them by yourself.*\n\n== Verification of Database Connection and Performing DB Tasks\n\nimage:images/winInstall20.gif[]\n\nWhen you switch to this screen an automatic test of database configuration will be started. It consists of few steps which will be executed in order. After testing connection and configuring schema, admin users will be added.\n\nWhat to do if any of the tests will fail?\n\n- If you decided to use your own database, check if you entered correct password and whether your database is running.\n- If you use the embedded *Derby* database then probably your problem is more complicated. An error may indicate a bug in the installer. You may report it to one of Tigase developers.\n\nIf you cannot go beyond this step after trying to resolve database problems you may try xref:manualinstall[manual installation] mode.\n\n== Finishing Installation\n\nWhen you perform all those steps altogether with choosing Start Menu location and other basic actions you will be informed that installation process is complete. You can now use your Tigase server. There are some post installation actions you may want to perform. They are briefly presented below.\n\n== Running the Server\n\nPart of the installation process is the selection of Tigase base directory. This is where you can find all important server files. The installer will create some configurable shortcuts in the *Start Menu*. You can navigate to the menu and use it to start the server. To run the server manually:\n\n- On a *Linux* system you may start the server using the *tigase* file found in the *scripts* sub-directory of Tigase server base directory.\nYou will need to select the type of linux you have, debian, gentoo, mandirva, or redhat, and use the script located in the init.d folder.\nIn the root server directory type the following command:\n\n[source,bash]\n-----\n./scripts/{OS}/init.d/tigase start etc/tigase.conf\n-----\nOf course if you have a custom config file then change last command appropriately.\n\n- On a *Windows* platform you can use a *bat* file to run the server. There is a *run.bat* file in the Tigase root directory. Just double click it in *Explorer* or run it from command line to start the server. A window with server log output will pop-up.\n\nimage:images/winRun.gif[]\n\n== Installation as a Service\n\nOn *Windows* you can install Tigase as a service. To do it use the *InstallTigaseService.bat* batch file found also in server root directory.\n\nIn this mode service will be running in background and will be controllable from the *Services* management snapshot. To launch the tool right click on the *Computer* icon on the desktop. Choose the *Manage* action. It will run the *Computer management* graphical configuration program. On the left side choose the *Services* item. You will be shown with a list of services. Here you can find Tigase service when it will be installed.\n\nTo uninstall Tigase service use the *UninstallTigaseService.bat* file from Tigase server root directory.\n\n== How to Check if the Server is Running\n\nChecking if the server is running is quite easy. Just try to connect to it by using one of the many available *XMPP* clients.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_04_-_Quick_Start_-_B_-_Installation_Using_Web_Installer.asciidoc",
"content": "[[webinstall]]\n= Installation Using Web Installer\n:author: Eric Dziewa\n:version: v1.0, January 2015: New Web Installer!\n:Date: 2015-01-15\n:revision: v1.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nWhen Tigase XMPP Server starts up, it looks for the default configuration file: *etc/init.properties*. If this file has not been modified you can run the web installer. Which will step you through the process of configuring Tigase.\nIf you are installing Tigase in a Windows environment, please see the xref:winWebInstall[Windows Installation] section.\n\n== Download and Extract\n\nFirst download Tigase XMPP Server and extract it. You can download the link:https://projects.tigase.org/projects/tigase-server/files[official binaries], or the latest and greatest link:http://build.xmpp-test.net/nightlies/dists/[nightly builds].\n\n[source,bash]\n-----\n$ wget http://build.xmpp-test.net/nightlies/dists/2015-01-12/tigase-server-7.0.0-SNAPSHOT-b3752-dist-max.tar.gz\n$ tar -xf tigase-server-7.0.0-SNAPSHOT-b3752-dist-max.tar.gz\n$ cd tigase-server-7.0.0-SNAPSHOT-b3752\n-----\n\nPlease do not run as root.\n\n== Start the Server\n\n[source,bash]\n-----\nscripts/tigase.sh start\n-----\n\n== Verify Tigase is Running\n\nYou should see a list of listening ports.\n\n[source,bash]\n-----\n$ lsof -i -P\nCOMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME\njava 18387 tigase 141u IPv6 22185825 0t0 TCP *:8080 (LISTEN)\njava 18387 tigase 148u IPv6 22185834 0t0 TCP *:5222 (LISTEN)\njava 18387 tigase 149u IPv6 22185835 0t0 TCP *:5223 (LISTEN)\njava 18387 tigase 150u IPv6 22185836 0t0 TCP *:5290 (LISTEN)\njava 18387 tigase 151u IPv6 22185837 0t0 TCP *:5280 (LISTEN)\njava 18387 tigase 152u IPv6 22185838 0t0 TCP *:5269 (LISTEN)\n-----\n\n[[connecttoWebInstall]]\n== Connect to the Web Installer\n\nSome points before you can connect:\n\nThis setup page is restricted access, however for first setup there is a default account set to setup Tigase:\nUsername: admin\nPassword: tigase\n\nThis combination will only be valid once as it will be removed from init.properties file on compleation of setup process. After this point the setup page will only be accessable using the following:\n\n. JID accounts listed as administrators in --admins line in init.properties\n. Username and password combinations added to init.properties file manually, or at the last page in this process.\n\nPoint your browser to *http://localhost:8080/setup/* unless you are working remotely. Then you can use the domain name, or IP address. I used http://tpub.xmpp-test.net:8080/setup/ for this guide.\n\nEnter the username and password above to gain access.\n\n== Step Through the Installation Process\n\nYou will be greeted by the following \"About software\" page.\n\nimage:images/web-install-01.png[]\n\nRead it and then click \"Next\"\n\nimage:images/web-install-02.png[]\n\nHere is some information about our commercial products and licensing. Please read though the agreement, type your name or company and click \"Next\".\n\nimage:images/web-install-04.png[]\n\nThis page will look over your default configuration settings, these include the type, Domains you wish to use, and gives you a chance to specify an administrator for the domain. Also, you will be selecting what type of database Tigase server will be using.\n\nimage:images/web-install-05.png[]\n\nThe Advanced configuration page. Select what components and configurations you need.\n\nimage:images/web-install-06.png[]\n\nPlugins which will be loaded by the server, most plugins are enabled by default.\n\nimage:images/web-install-07.png[]\n\nThis is where the database schema is installed. *BE SURE TO SPECIFY SUPER USER ACCOUNT AND PASSWORD*\n\nimage:images/web-install-08.png[]\n\nYou should see a page like this after a successful database setup. This page will reveal any issues with your database setup such as invalid URIs, passwords, and schemas.\n\nimage:images/web-install-09.png[]\n\nNext a page asking if you'd like to provide an API Access Key to access HTTP REST commands. It is highly recommended that you either specify an API key or block access. Open API keys allow any REST command to be interpreted by the server.\n\nimage:images/web-install-10.png[]\n\nThe Setup Access Page will be locked from the admin/tigase user as specified above. This is your chance to have the setup pages add a specific user in addition to admin accounts to re-access this setup process later. If left blank, only JIDs listed in admin will be allowed to access.\n\nimage:images/web-install-11.png[]\n\nThe installation is complete and this is what the *init.properties* file will look like.\nIf you have a custom setup, or would like to put your own settings in, you may copy and past the contents here to edit the current init.properties file.\nClick \"Save\" to write the file to disk.\n\nimage:images/web-install-12.png[]\n\nYou have now finished the installation, proceed to the next step to restart the server.\n\n== Restart the Server\nIt is recommended at this point to stop the server manually and restart it using the proper script for your OS.\nFrom the Tigase base directory enter\n[source,bash]\n-----\n./scripts/tigase.sh stop\n\n./scripts/{OS}/init.d/tigase start etc/tigase.conf\n-----\nwhere {OS} is your type of Linux, gentoo, debian, mandriva, or redhat\n\nTo further fine tune the server you should edit etc/tigase.conf. Ensure *JAVA_HOME* path is correct, and increase memory if needed using *JAVA_OPTIONS* -Xmx (max), and -Xms (initial). You will need to direct Tigase to read settings from this file on startup as follows.\n\nEverything should be running smooth at this point. Check the logfiles in logs/ if you experience any problems.\n\n[[winWebInstall]]\n== Windows Instructions for using Web Installer\n\nThere are a few steps involved with setting up Tigase with the web installer in a Windows environment. Please follow this guide.\n\nFirst step is to extract the dist-max archive in it's entirety to the intended running directory. Once there, run the Setup.bat file inside the win-stuff folder. This will move the necessary files to the correct folders before Tigase begins operation.\n\nFrom here, you have a few options how to run Tigase; run.bat will operate Tigase using a java command, or run.bat which will start Tigase using the wrapper. You may also install Tigase and run it as a service.\n\nOne this setup is finished, web installer will continue the same from xref:connecttoWebInstall[here].\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_05_-_Quick_Start_-_C_-_Installing_Using_Console_Installer.asciidoc",
"content": "[[consoleinstall]]\n= Installing Using Console Installer\n:author: Mateusz Fiolka\n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 21:18\n:revision: 2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\n\n== Installation Using the text-mode Installer\n\nWhen you install Tigase server on a desktop machine or a server having a graphical user interface - you can use the xref:guiinstall[GUI Installer]. However servers are often administered using *SSH* text-mode connection because of low bandwidth requirements or user preferences. Due to popular demand, the Tigase development team has decided to implement a console installer for the server.\n\n*Note! The console installer is only available for Tigase server version 4.1.5 and later*.\n\n=== Requirements and Important Notice\n\nBefore trying the installer please keep in mind:\n\n- This is first - alpha rate version of the text-mode installation - meant to install the server and do some basic configuration. We will be very happy to see bug reports and overall feedback about this feature. Please send your remarks to mailto:artur.hefczyc@tigase.net[Artur Hefczyc] or Mateusz Fiolka.\n- You will still need to perform some additional steps before running the installer. The main requirement is to download and install *Java JDK v1.6 or newer*. This guide is aimed at advanced users - thus downloading and configuring JDK is left to the reader. You can find more info at the link:http://java.sun.com/javase/downloads/index.jsp[Java downloads site].\n\n== Download the Installer\n\nYou can always find the newest Tigase packages in the link:https://projects.tigase.org/projects/tigase-server/files/[download section]. When you enter the page, you will be presented a list of files to choose from. All Tigase binary packages have conventional names, which help to differentiate them easily. They are of form *tigase-server-x.y.z-bv.ext* where 'x', 'y', 'z' and 'v' are version numbers and they change from a release to release. Ext is the file extension which in the case of our console installation program is *.jar*. We recommend you download the latest version (highest version number) of the server as it contains latest functions and improvements.\n\n== Run the jar File\n\nIn terminal (SSH or Windows cmd prompt if you use on) type:\n[source,bash]\n-----\njava -jar nameOfTheDownloadedJarFile.jar -console\n-----\n\n== Installation Steps\n\nNow you are ready to to install the server.\n\nSome tips for working with the console installer:\n\n- Please remember to write down your JDK location because you will need to type it during the installation process.\n- Installer consists of number of screens which relate to different configuration aspects. Most of the panels end with a question whether you want to redisplay the panel or quit installer. When you make a mistake you will be probably asked later if you want re-enter the data again.\n- To quit the installer use standard termination key specific to your platform. For example on a *Linux* system it is the Ctrl+C key combination. Keep in mind that if you quit the installer after it copied some files - it may leave them in the place and you might have to remove them manually.\n- In current version the installer is of beta quality and using advanced configuration is not recommended. It might work, however it is not much tested and will be improved later.\n\n=== Initial Screen\n\nOn this screen you will find server version info which will be useful if you would to suggest something to Tigase developers.\n\n[source,bash]\n-----\nWelcome to the installation of Tigase XMPP (Jabber) Server X.Y.Z!\n\nThe homepage is at: http://www.tigase.org/\npress 1 to continue, 2 to quit, 3 to redisplay\n-----\n\n=== JDK Selection\n\nYour system may contain more then one JDK installation, thus you will have to make an explicit decision which one to use. Currently console mode installer doesn't contain any auto-detection code nor validation. You will have to enter the path correctly or you may have problems with running the server. For example on *Ubuntu Linux* you can find the JDK in the /lib/jvm/java-6-sun directory. For the current Tigase server JDK of version at least *1.6* is required.\n\n[source,bash]\n-----\nThe installed application needs a JDK. A java run-time\nenvironment (JRE) will be not sufficient.\n\nEnter path: /lib/jvm/java-6-sun\n-----\n\n=== Actions Selection\n\nChoose whether you want to configure the server in addition to install it.\n\n[source,bash]\n-----\n*** Select what you want to do next:\n\nOn this panel you can specify whether you want to install\nonly or configure already installed server or to do both. If\nyou are just installing a server on your machine it is a\ngood idea to do both steps.\n\n\n\nThe wizards you want to execute\nInstallation of the Tigase Server\n[on, off]\non\nConfiguration of the Tigase Server\n[on, off]\non\n-----\n\n=== Installer Info\n\nIntroduction to the installer.\n\n[source,bash]\n-----\nPlease note!\n\nWhile the Tigase server is quite stable and well tested\napplication the installer itself is a new addition. Take\nprecautions especially if you upgrade the server from\nearlier version. Backup old server files and the database.\n\nIf you notice any problems please report them to address:\nArtur Hefczyc\n\npress 1 to continue, 2 to quit, 3 to redisplay\n-----\n\n=== Server Info\n\nIf you don't know what exactly Tigase server is, you can find some basic introduction on this screen.\n\n[source,bash]\n-----\nTigase XMPP (Jabber) server ver 4.1.5-bDEV\n\n\nAbout\n\nCopyright (C) 2004 Tigase.org. \n\nTigase Jabber/XMPP Server is\nOpen Source and Free (AGPLv3)\nJava based server. The goals behind the design and\nimplementation of the server are:\n\n\nMake the server robust and reliable.\nMake the server secure communication platform.\nMake flexible server which can be applied to different use\ncases.\nMake extensible server which takes full advantage of XMPP\nprotocol extensibility.\n\n--- Press ENTER to continue ---\n\nMake the server easy to setup and maintain.\n\n\nInstallation, configuration and compilation\n\nThe most recent documentation on all these topics is always\navailable in the project website: www.tigase.org. Please\nrefer to the website for all the details and always up to\ndate guides.\n\nYou would probably want to start with Quick Start:\nhttp://www.tigase.org/content/quick-start documentation.\n\nThe website also contains lots of other useful information\nlike load tests results, user discussions and on-line support\nand help always available to you.\n\nThis is 4.1.5-bDEV release of the server. Please include the\nexact version number in all correspondence regarding the\nserver.\n\n\npress 1 to continue, 2 to quit, 3 to redisplay\n-----\n\n=== Server License\n\nThis is a license that you have to agree to use Tigase server. Please read it carefully. Take note, that in this manual only part is shown in order to decrease guide length.\n\n[source,bash]\n-----\nPlease read the following license agreement carefully:\n\n\n\nGNU General Public License - GNU Project - Free Software\nFoundation (FSF)\n\n\nGNU GENERAL PUBLIC LICENSE\nVersion 3, 29 June 2007\n\nCopyright (C) 2007 Free Software Foundation, Inc.\n Everyone is permitted to copy and distribute verbatim copies\n of this license document, but changing it is not allowed.\n\nPreamble\n\n...\n... Fragment cut out\n...\n\n\nYou should also get your employer (if you work as a\nprogrammer) or school, if any, to sign a \"copyright\ndisclaimer\" for the program, if necessary. For more\ninformation on this, and how to apply and follow the GNU\nGPL, see --- Press ENTER to continue ---\n\n.\n\nThe GNU General Public License does not permit incorporating\nyour program into proprietary programs. If your program is\na subroutine library, you may consider it more useful to\npermit linking proprietary applications with the library.\nIf this is what you want to do, use the GNU Lesser General\nPublic License instead of this License. But first, please\nread\n\n.\n\n1. I accept the terms of this license agreement.\n2. I do not accept the terms of this license agreement.\nChoose number (1-2):\n1\npress 1 to continue, 2 to quit, 3 to redisplay\n-----\n\n=== Server Location Selection\n\nEnter where you want the server to be installed. If you have administrator rights you can place it in a standard location where all your applications reside. If you don't have write permissions for this place, you can always install the server in your home directory.\n\n[source,bash]\n-----\nSelect target path\n[/home/user/tigase] /home/user/tigase-server\n\npress 1 to continue, 2 to quit, 3 to redisplay 1\n-----\n\n=== Selection of Packs to be Installed\n\nSome packs are optional and you can disable/enable them. In the following screen they have an [x] option before them. To switch their state enter item number and ENTER. When done press d and ENTER.\n\n[source,bash]\n-----\nSelect the packs you want to install:\n\n1 => Base, The base files\n2 => Unix Files, Files needed to run the server on Unix like systems\n3 => [x] Docs, The documentation\n4 => [x] Extras, Extras libraries, MUC, PubSub...\n5 => [x] Derby Database, Derby database and JDBC driver\n6 => [x] MySQL Database, MySQL JDBC driver (MySQL has to be\ninstalled separately)\n7 => [x] PostgreSQL Database, PostgreSQL JDBC driver\n(PostgreSQL has to be installed separately)\n8 => [x] SQL Server Database, SQL Server JDBC driver (SQL\nServer has to be installed separately)\n9 => [ ] Sources, The server source files, tools and\nlibraries sources are not included\nr => Redisplay menu\nd => Done\n\nChoose action: d\npress 1 to continue, 2 to quit, 3 to redisplay\n-----\n\n=== Installation\n\nDuring extracting and copying server files to their target you will be presented with the process progress.\n\n[source,bash]\n-----\n[ Starting to unpack ]\n[ Processing package: Base (1/9) ]\n[ Processing package: Unix Files (2/9) ]\n[ Processing package: Windows Files (3/9) ]\n[ Processing package: Docs (4/9) ]\n[ Processing package: Extras (5/9) ]\n[ Processing package: Derby Database (6/9) ]\n[ Processing package: MySQL Database (7/9) ]\n[ Processing package: PostgreSQL Database (8/9) ]\n[ Processing package: SQL Server Database (9/9) ]\n[ Unpacking finished ]\n-----\n\n=== Basic Configuration\n\nThis panel contains most important configuration options for the Tigase server. You can choose which components should be configured to be used when running server, add XMPP admin users and enter their password (many admins, comma separated, initially having the same password). Choose different password from the default one. Then select preferred database. If you don't have a standalone DB which you would like to use, you can choose the included Derby DB.\n\n*Important notice: Tigase installer doesn't contain the actual databases, only drivers allowing db access. One exception is Derby database, which is included in JDK. It is automatically configured by installer, in case of other databases you will need to configure them by yourself.*\n\n[source,bash]\n-----\n*** Basic Tigase server configuration\nOn this panel you can specify basic configuration settings\nfor the Tigase server.\n\nBased on your selection here more configuration options\nmight be presented later on. After the configuration is\ncomplete init.properties file will be created.\n\nYou can optionally restart the server at the end of the\nprocess if you like.\n\n\n\n0 [x] Default installation\n1 [ ] Default plus extra components\n2 [ ] Session Manager only\n3 [ ] Network connectivity only\ninput selection:\n0\nYour XMPP (Jabber) domains [my-laptop]\n\nServer administrators [admin@my-laptop]\n\nAdmin password [tigase]\n\n0 [x] Derby (built-in database)\n1 [ ] MySQL\n2 [ ] PostgreSQL\n3 [ ] SQLServer\n4 [ ] Other...\ninput selection:\n1\n-----\n\n=== Advanced Configuration\n\n*Please note: in this version advanced configuration is not supported. Although it may work it has not been tested and thus is not recommended. Please enter off to not use it.*\n\n[source,bash]\n-----\nAdvanced configuration options\n[on, off]\noff\npress 1 to continue, 2 to quit, 3 to redisplay\n-----\n\n=== Database Configuration\n\nDepending on which database you selected, you will be presented with related options to configure its connectivity options. As you will see, the parameters have default values.\n\n[source,bash]\n-----\n*** Database configuration:\n\nYou have selected MySQL database. This database needs\nadditional configuration parameters. Please enter all\nrequired information.\n\n\n\nMySQL super user account will be used only to create and\nconfigure database for the Tigase server. It will not be\nused by the Tigase server later on.\n\nSuper user account name: [root]\n\nWARNING: password will be visible while entering\nSuper user password: mysecretpassword\nWARNING: password will be visible while entering\nRetype password: mysecretpassword\n\n\n\nMySQL database details. It will be created automatically if\nit does not exist.\n\nDatabase account: [tigase]\n\nAccount password: [tigase12]\n\nDatabase name: [tigasedb]\n\nDatabase host or IP: [localhost]\n\nAdditional database parameters: []\n\npress 1 to continue, 2 to quit, 3 to redisplay\n-----\n\n=== Database Checking and Preparation\n\nAfter entering all database information an automatic test of connection and database setup is performed. If everything is ok the installer will try to convert database schema to required version and finally adds XMPP administrators to it.\n\n[source,bash]\n-----\nPerforming DB tasks\n\nChecking connection to the database\nConnection OK\nChecking if the database exists\nExists OK\nChecking the database schema\nNew schema loaded OK\nChecking whether the database needs conversion\nConversion not needed\nAdding XMPP admin accounts\nAdded admins OK\n-----\n\n=== Installation Complete\n\nNow you can run the server and use it!\n\n[source,bash]\n-----\nInstall was successful\napplication installed on /home/user/tigase-server\n[ Console installation done ]\n-----\n\n=== Running the Sever\n\nYou can start the server using the tigase file found in the scripts sub-directory of Tigase server base directory. There, select the type of linux you have, debian, gentoo, mendriva or redhat. In the root server directory type the following command:\n\n[source,bash]\n-----\n./scripts/{OS}/init.d/tigase start etc/tigase.conf\n-----\nWhere {OS} is your *nix operating system.\n\nOf course if you have a custom config file then change last command appropriately. On a Windows platform you can use a bat file to run the server. There is a run.bat file in the Tigase root directory. Just double click it in Explorer or run it from command line to start the server. A window with server log output will pop-up.\n\n=== How to Check if the Server is Running\n\nChecking to see if the server is running is quite easy. Just connect to it by using one of mnay available XMPP clients.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_06_-_Quick_Start_-_D_-_Manual_Installation_in_Console_Mode.asciidoc",
"content": "[[manualinstall]]\n= Manual Installation in Console Mode\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 21:18\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nOur preferred way to install the Tigase server is using xref:guiinstall[GUI installer] and configuration program which comes with one of the binary packages. Please pick up the latest version of the JAR file in our link:http://www.tigase.org/filebrowser/tigase-server[download section].\n\nIn many cases however this is not always possible to use the GUI installer. In many cases you have just an ssh access or even a direct access in console mode only. We are going to provide a text-only installer in one of the next releases but for the time being you can use our binary packages to install the server manually. Please continue reading to learn how to install and setup the server in a few easy steps...\n\nIf you have an old version of the Tigase server running and working and you intend to upgrade it please always backup the old version first.\n\n== Get the Binary Package\n\nHave a look at our link:http://www.tigase.org/filebrowser/tigase-server[download area]. Always pick the latest version of the package available. For manual installation either *zip* or *tar.gz* file is available. Pick one of files with filename looking like: *tigase-server-x.y.z-bv.tar.gz* or *tigase-server-x.y.z-bv.zip* where 'x', 'y', 'z' and 'v' are version numbers and they change from a release to release.\n\n== Unpack the Package\n\nUnpack the file using command for the tar.gz file:\n\n[source,sh]\n-----\n $ tar -xzvf tigase-server-x.y.z-bv.tar.gz\n-----\n\nor for the zip file:\n\n[source,sh]\n-----\n $ unzip tigase-server-x.y.z-bv.zip\n-----\n\nA new directory will be created: *tigase-server-x.y.z-bv/*.\n\nSometimes after unpacking package on unix system startup script doesn't have execution permissions. To fix the problem you have to run following command:\n\n[source,sh]\n-----\n $ chmod u+x ./scripts/tigase.sh\n-----\n\n== Prepare Configuration\n\nIf you look inside the new directory, it should like this output:\n\n[source,sh]\n-----\n $ ls -l\ntotal 316K\n-rw-r--r-- 1 265K 2008-12-15 22:24 ChangeLog\n-rw-r--r-- 1 37K 2008-12-15 22:24 License.html\n-rw-r--r-- 1 1.1K 2008-12-15 22:24 README\ndrwxr-xr-x 6 204 2009-02-03 13:25 certs/\ndrwxr-xr-x 22 748 2009-02-03 13:25 database/\ndrwxr-xr-x 3 102 2008-12-15 22:24 docs/\ndrwxr-xr-x 4 136 2009-02-03 13:25 etc/\ndrwxr-xr-x 3 102 2009-02-03 13:25 jars/\ndrwxr-xr-x 12 408 2009-02-03 13:25 libs/\ndrwxr-xr-x 2 68 2008-12-15 22:24 logs/\n-rw-r--r-- 1 1.5K 2008-12-15 22:24 package.html\ndrwxr-xr-x 7 238 2009-02-03 13:25 scripts/\n-----\n\nAt the moment the most important is the etc/ directory with 2 files:\n\n[source,sh]\n-----\n $ ls -l etc/\ntotal 8.0K\n-rw-r--r-- 1 97 2008-12-15 22:24 init.properties\n-rw-r--r-- 1 333 2008-12-15 22:24 tigase.conf\n-----\n\nA Small change in the tigase.conf file is needed. Find the line setting for *JAVA_HOME*:\n\n[source,sh]\n-----\nJAVA_HOME=\"${JDKPath}\"\n-----\n\nand replace *$\\{JDKPath}* with a path to Java installation on your system.\n\nYou need also to edit the init.properties file. It contains initial parameters normally set by the configuration program. As this is a manual installation, you will have to edit this document yourself. It contains already a few lines:\n\n[source,sh]\n-----\n $ cat etc/init.properties\nconfig-type=--gen-config-def\n--admins=admin@$HOST_NAME\n--virt-hosts = $HOST_NAME\n--debug=server\n-----\n\nYou have to replace *$HOST_NAME* with a domain name used for your XMPP installation. Let's say this is \\'*jabber.your-great.net*'. Your init.properties should look like this then:\n\n[source,sh]\n-----\n $ cat etc/init.properties\nconfig-type=--gen-config-def\n--admins=admin@jabber.your-great.net\n--virt-hosts = jabber.your-great.net\n--debug=server\n-----\n\nYou can also use multiple virtual domains if you want. Please have a look at the detailed description for *--virt-hosts* property in the init.properties guide and also more detailed information in the Virtual Hosts section of the Tigase Server guide.\n\nYou will also need to configure connection to the database. First you have to decide what database you want to use: *Derby*, *MySQL* or *PostgreSQL*. Then there are to more properties you have to add to the *init.properties:* *--user-db* and *--user-db-uri.* The first property specifies the database type you use and the second the database connection string. For simplicity let's assume you want to use *Derby* database with files located in directory */var/lib/tigase/derby*. 2 more lines need to be added to the *init.properties* file:\n\n[source,sh]\n-----\n $ cat etc/init.properties\nconfig-type=--gen-config-def\n--admins=admin@jabber.your-great.net\n--virt-hosts = jabber.your-great.net\n--debug=server\n--user-db=derby\n--user-db-uri=jdbc:derby:/var/lib/tigase/derby\n-----\n\nThis is enough basic configuration to have your Tigase server installation running.\n\n== Prepare Database\n\nNormally the database is prepared for you during the installation process. Now you are on your own. As in section above we prepare your first installation to run with the *Derby* database. Creating and preparing the Derby database is actually quite easy if you use a helper script: link:https://projects.tigase.org/projects/tigase-server/repository/revisions/master/entry/scripts/db-create-derby.sh[./scripts/db-create-derby.sh]. The file might not be in your *scripts/* directory if you have an earlier version of the package. Simply download it from the link provided if it is missing and put it in the *scripts/* directory and execute it with the database location as the parameter:\n\n[source,sh]\n-----\n $ ./scripts/db-create-derby.sh /var/lib/tigase/derby\n-----\n\nThere will be lots of output but if there is no error at the end of the output it means your database has been created and it is ready to use.\n\n*NOTE:* There might be filesystem access restrictions for the directory: */var/lib/* and you might want/need to select a different location.\n\n== Start the Server\n\nYou can start the server using the tigase file found in the scripts sub-directory of Tigase server base directory. There, select the type of linux you have, debian, gentoo, mendriva or redhat. In the root server directory type the following command:\n\n[source,bash]\n-----\n./scripts/{OS}/init.d/tigase start etc/tigase.conf\n-----\nWhere {OS} is your *nix operating system.\n\nand you should get the output like this:\n\n[source,sh]\n-----\nStarting Tigase:\nnohup: redirecting stderr to stdout\nTigase running pid=18103\n-----\n\n== Check if it is Working\n\nThe server is started already but how do you know if it is really working and there were no problems. Have a look in the *logs/* directory. There should be a few files in there:\n\n[source,sh]\n-----\n $ ls -l logs/\ntotal 40K\n-rw-r--r-- 1 20K 2009-02-03 21:48 tigase-console.log\n-rw-r--r-- 1 16K 2009-02-03 21:48 tigase.log.0\n-rw-r--r-- 1 0 2009-02-03 21:48 tigase.log.0.lck\n-rw-r--r-- 1 6 2009-02-03 21:48 tigase.pid\n-----\n\nThe first 2 files are the most interesting for us: *tigase-console.log* and *tigase.log.0*. The first one contains very limited information and only the most important entries. Have a look inside and check if there are any *WARNING* or *SEVERE* entries. If not everything should be fine.\n\nNow you can connect with an XMPP client of your choice. The first thing to do would be registering the first account - the admin account from your init.properties file: admin@jabber.your-great.net. Refer to your client documentation how to register a new account.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_07_-_Quick_Start_-_E_-_Windows_Installation.asciidoc",
"content": "[[windowsInstallation]]\n= Windows Installation\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 21:16\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nTigase server installation should be started with downloading the Tigase installer server from our link:https://projects.tigase.org/attachments/download/273/tigase-server-3.3.2-b889.exe[download area]. This guide describes installation procedure for the branch 3.x of the server so please pick up the latest version of the Tigase 3.x.\n\nThe Windows binary package is an executable file containing an installer. Run the file and the server will be installed and icons will be added to your Windows start menu. Locate the Tigase group in your menu and execute: \"Install Tigase service\" which will install the Tigase server as the system service and it will be automatically started whenever your system starts.\n\nIf you are going to use the Tigase server with MySQL database have a look now in the directory where the Tigase server is installed. There is a directory +etc/+. Have a look inside and find file called +init.properties+. Open the file with a text editor and make sure you added there 2 following lines:\n\n[source,bash]\n-----\n--user-db=mysql\n--user-db-uri=jdbc:mysql://localhost/tigasedb?user=tigase_user&password=mypass\n-----\n\nThe content of the file should look like the example screenshot below:\n\nimage:images/init_properties1.jpg[]\n\n== MySQL Database Installation\n\nThe section describes installation and configuration of the MySQL database to work with Tigase server.\n\nDownload the binary package from MySQL download area at link:http://dev.mysql.com/downloads/mysql/5.0.html#win32[mysql.com]. Make sure you select executable proper for your operating system.\n\nRun the installation program and follow default installation steps. When the installation is complete find the MySQL elements in the Windows Start menu and run the MySQL Configuration Wizard. Follow the wizard and make sure to check settings against the screenshots in the guide below.\n\nIn Welcome window just press 'Next'.(pic.1)\n\nimage:images/sql1.JPG[]\n\nIn the next window select option: 'Detailed Configuration' and press 'Next' (pic. 2)\n\nimage:images/sql2.JPG[]\n\nOn the next screen select option: 'Server Machine' and press 'Next' (pic. 3)\n\nimage:images/sql3.JPG[]\n\nOn the forth windows leave the default\" 'Multifunctional Database' and press 'Next' (pic. 4)\n\nimage:images/sql4.JPG[]\n\nOn the step number five just press 'Next' using defaults. (pic. 5)\n\nimage:images/sql5.JPG[]\n\nAgain, on window 6 select the default - 'Decision Support (DSS)/OLAP' and press 'Next' (pic.6)\n\nimage:images/sql6.JPG[]\n\nMake sure you switch OFF the 'Strict mode' and and press 'Next' (pic. 7)\n\nimage:images/sql7.JPG[]\n\nOn the character encoding page select: 'Manual Selected Default Character set/ Collation' and 'utf8', press 'Next' (pic.8)\n\nimage:images/sql8.JPG[]\n\nOn next window select 'Include Bin Directory in Windows PATH' and press 'Next' (pic.9)\n\nimage:images/sql9.JPG[]\n\nOn this window just enter the database super user password and make sure you remember it. When ready press 'Next' (pic. 10)\n\nimage:images/sql10.JPG[]\n\nThis is the last screen. Press 'Execute' to save the configuration parameters. (pic. 11)\n\nimage:images/sql11.JPG[]\n\nWhen the configuration is saved you can repeat all the steps and change settings at any time by running: *START => Programs => MYSQL=> MYSQL serwer machine=> MySQL Server Instance Config Wizard*\n\nNow we have to setup Tigase database. From the Start menu run the MySQL console and enter all commands below finishing them with **:\n\n. Create the database:\n+\n[source,sql]\n-----\nmysql>create database tigasedb;\n-----\n. Add database user:\n+\n[source,bash]\n-----\nmysql> GRANT ALL ON tigasedb.* TO tigase_user@'%' IDENTIFIED BY 'tigase_passwd';\nmysql> GRANT ALL ON tigasedb.* TO tigase_user@'localhost' IDENTIFIED BY 'tigase_passwd';\nmysql> GRANT ALL ON tigasedb.* TO tigase_user IDENTIFIED BY 'tigase_passwd';\nmysql> FLUSH PRIVILEGES;\n-----\n. Load Tigase database schema:\n+\n[source,bash]\n-----\nmysql> use tigasedb;\nmysql> source c:/Program Files/Tigase/database/mysql-schema.sql;\n-----\n\nThere is a small configuration bug in the installation of Tigase version 3.x. If you look in the *run.bat* file in the Tigase directory you have to replace string *inital.propereties* with *init.properties*.\n\nYou can now restart your machine and all services including the MySQL database and the Tigase server should be running. Alternatively if you don't want to restart your computer you can start both services manually if you know how to do it.\n\nWhen the system is up and running you can connect with any XMPP client (Psi for example) to your server to see if it is working.\n\nNow, you can tweak the server configuration further. Use the guide describing init.properties file for configuration details.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_07_-_Quick_Start_-_F_-_Setting_Up_Server.asciidoc",
"content": "[[setupTigaseServer]]\n= Tigase Server Network Instructions\n:author: Daniel Wisnewski \n:version: v1.0, May 2016: Reformatted for AsciiDoc.\n:date: 2016-05-13 10:30\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nOne you have installed Tigase XMPP Server on a machine, you're going to want to use it. If you are just using for local communications on a network behind a router, you're all set. Enjoy and use!\n\nHowever, if you want to have people from other computers outside your network connect to your server, you're going to have to go through a few more steps to show your server out to the public.\n\nNOTE: This guide is merely a recommendation of how to get a local server to be open to incoming communications. Any time you open ports, or take other security measures you risk compromising your network security. These are only recommendations, and may not be appropriate for all installations. Please consult your IT Security expert for securing your own installation.\n\nXMPP, being a decentralized communication method, relies on proper DNS records to figure out where and how an XMPP server is setup. Operating an XMPP Server will require you to properly setup DNS routing so not only can clients connect to you, but if you decide to run a federated server and enable server to server communication, you will need to do the same. If you already have a DNS server already, you should have little issue adding these records.\nIf you do not have a DNS setup pointing to your server, you may use a free dynamic name service such as dynu.com.\n\n== A Records\nYou will not be able to use an IP Address or a CNAME record to setup an XMPP Server. While it's not required, an A record can provide some other benefits such serving as a backup in case the SRV record is not configured right.\n\n== SRV Records\nYou will need to set SRV records both for client-to-server (c2s) communication and, if you plan to use it, server to server (s2s) communication. We recommend both records are entered for every server as some resources or clients will check for both records.\nFor this example we will use tigase.org is our domain, and xmpp as the xmpp server subdomain.\n\nSRV records have the following form:\n\n_service._protocol.name. TTL class SRV Priority weight port target.\n\nThe key is as follows:\n\n* *service*: is the symbolic name of the desired service, in this case it would be _xmpp-client_ or _xmpp-server_.\n* *protocol*: is the transport protocol, either TCP or UDP, XMPP traffic will take place over _TCP_.\n* *name*: the domain name where the server resides, in this case _tigase.org_.\n* *TTL*: a numeric value for DNS time to live in milliseconds, by default use _86400_.\n* *class*: DNS class field, this is always _IN_.\n* *priority*: the priority of the target host with lower numbers being higher priority. Since we are not setting up multiple SRV records, we can use _0_.\n* *weight*: the relative weight for records with the same priority. We can use _5_.\n* *port*: the specific TCP or UDP port where the service can be found. In this case it will be _5222_ or _5269_.\n* *target*: the hostname of the machine providing the service, here we will use _xmpp.tigase.org_.\n\nFor our example server, the SRV records will then look like this:\n\n*_xmpp-client._TCP.tigase.org 86400 IN SRV 0 5 5222 xmpp.tigase.org*\n\n*_xmpp-server._TCP.tigase.org 86400 IN SRV 0 5 5269 xmpp.tigase.org*\n\n=== Tigase and Vhosts\nIf you are running multiple vhosts or subdomains that you wish to separate, you will need another record. In this case an A record will be all you need if you are using default ports. If you are using custom ports, you will need to have a new SRV record for each subdomain.\n\n== Port Forwarding\nOnce your server is setup, you may need to open at least two ports. XMPP communication handling and SRV records occur on two ports; 5222 and 5269. SRV records may result in an error if these ports cannot be contacted by the SRV records service, and you will be unable to connect from outside your network.\nBoth ports should be setup to use TCP only. Remember, if you set custom ports for your servers communications, you may need to forward them as well.\n\n. If you are using TURN or STUN, you will need to forward 3478 under TCP and UDP.\n. If you are planning to use STUN or TURN over TLS, forward 5349 under TCP.\n\nIf you have a cell phone on a separate network with an XMPP client, you can now try to login to test the server. If that is not handy, you can use an online tool to check proper DNS records such as kingant's: link:https://kingant.net/check_xmpp_dns/[https://kingant.net/check_xmpp_dns/] and it will tell you if anything is missing.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_08_-_Latest_and_Nightly_Builds.asciidoc",
"content": "[[TSBupdates]]\n= Tigase Server Binary Updates\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 21:18\n:revision: 2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\n\nMost open source projects try to make sure that the nightly builds compile correctly so that these builds can be used. However, we at Tigase believe that these builds should be seperated until they are thoroughly tested and released. Although lots of installations out there we know of just run from our nightly builds, this puts an extra responsibility to make sure all code is functional and will constantly work. Therefore, our general approach is to run all basic functionality tests before each code commit to make sure it works correctly. This does not guarantee that there will never be a problem, but it is a precaution from preventing bad builds from arriving in the hands of our customers.\n\nSome users on the other hand, like to be on the bleeding edge and regularly use our nightly builds exploring new code changes and playing with new features before they are put to a full release. Others prefer to stick to stable and fully tested public releases. Others however, want something from the middle, the most recent features, but bug fixes, something like a beta or a release-candidate state.\n\nShould you choose to use the nighly builds, a few things you should consider:\n- Changes may be made to the code that can negatively affect performance.\n- Changes may be made to the code that can negatively affect security.\nWe *highly* recommend testing these builds in your environments before upgrading.\n\nWith these considerations in mind, we provide nightly builds at link:http://build.xmpp-test.net/nightlies/dists/[this link] which provides directories by date.\n\nStandard naming format is tigase-server-x.x.x-SNAPSHOT-byyyy.*\nx.x.x is the major version the builds are working towards, with yyyy being the specific build.\n*Note individual days may have the same builds as noted by the byyyy section of the file.*\n\nJust like the standard distributions, the builds are available with the following extensions:\n. .jar - Java installer version\n. .exe - Windows binary installer version\n. -javadoc.jar - Java installer for javadoc only\n. -dist.zip - Compressed binaries with no dependencies.\n. -dist.tar.gz - tarball compressed binaries with no dependencies.\n. -dist-max.zip - Compressed binaries with all dependencies.\n. -dist-max.tar.gz - tarball compressed binaries with all dependencies.\n\nWe also provide automated testing of each of our nightly builds for each supported databases. Tests are done with both functional and low memory parameters in mind, and are available link:http://build.xmpp-test.net/nightlies/tests/[at this link]. These tests can provide a quick examination of function before upgrading your current build.\n\nThe latest Cluster tests are available at link:http://graph.cluster-c.xmpp-test.net/latest/[this link] which shows performance and traffic use under strain using the latest available build of Tigase.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_09_-_Configuration.asciidoc",
"content": "[[configuration]]\n= Configuration\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 12:28\n:revision: 2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\n\nWhen the user tries to setup the client for the first time he comes across 2 configuration files: *tigase.conf* and *init.properties* in the /etc folder. Here is a brief explanation what all those files are about and in other sections you can learn all the details needed to configure the server.\n\n. xref:initPropertiesGuide[init.properties] file is a simple text file with server parameters in form: *key* = *value*. When the XML configuration file is missing the Tigase server reads *init.properties* file and uses parameters found there as defaults for generation of the XML file. Therefore if you change the *init.properties* file you normally have to stop the server, remove the XML file and start the server again. All the settings from the *init.properties* are read and applied to the XML configuration. The properties file is easy to read and very safe to modify. At the moment this is the recommended way change the server configuration.\n. xref:manualconfig[tigase.conf] is the Tigase server startup configuration. It is actually not used by the server itself. It rather contains operating system settings and environment parameters to correctly run the link:http://java.sun.com/[Java Virtual Machine]. It is only useful on the unix-like systems with Bash shell. If you run the server on MS Windows systems *tigase.bat* and *wrapper.conf* files are used instead. The *tigase.conf* file is read and loaded by the *scripts/tigase.sh* shell script which also scans the operating system environment for Java VM and other tools needed.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_100_-_Using_Tigase_-_O_-_Licensing.asciidoc",
"content": "[[licenseserver]]\n= Licensing\n:author: Daniel Wisnewski\n:version: v1.0, March 2016\n:date: 2016-03-15 11:00\n\n:numbered:\n:website: http://tigase.net\n:toc:\n\nFrom release of v7.1.0, users and commercial clients alike may now be able to register and request a license file from our servers on their own.\nThis process helps us maintain licenses, and can allow for client installations of new servers without the need to wait for a license file.\nUsers who do not wish to register will not be required to register. However, If you are using Tigase ACS or other commercial pieces of software, you will be required to register.\n\n*Again, Tigase XMPP Server will still be available free under AGPLv3, and free users will not need to register.*\n\n== Registering for a License\nTo obtain a license from our licensing servers, you will first need to register with us. This may be done in a few methods. The easiest method, and recommended is VIA use of our web portal.\n\n=== Web Portal\nPointing your browser to link:http://license.tigase.net:8080/rest/licence/register[license.tigase.net:8080/rest/licence/register] will give you the following page:\n\nimage::images/Licwebregform.png[Registation form]\n\nFill out the three required forms, your name, an E-mail where you will receive the license, and answer the math problem, to prove you are a human.\n\nOnce filled out, you will be greeted with the following screen:\n\nimage::images/Licwebregok.png[Confirmation page]\n\nYou will receive an E-mail shortly from tigase@tigase.net and will look like this:\n[source,bash]\n-----\nHi!\n\nWelcome User Name!\nYour CustomerID is 9s82stmw2tasc4h6q05n69azxs\n\nPlease add this line yo your init.properties:\n--customer-id=9s82stmw2tasc4h6q05n69azxs\n\n--\nTigase Team\n\n-----\n\nOnce you have this E-mail, proceed to xref:licenseconfig[License Configuration].\n\n=== AdHoc Commands\nThe new license server can now accept adHoc commands to be sent and received using XMPP stanzas. This is more complicated, but it may help you use scripts or automate the server registration process:\n\nThese Ad-Hoc commands may be used to manually start the following operations:\n\n==== +create-customer-id+\nCreates a new customer-id.\n\nReturns a blank form containing the following fields to be filled:\n- +name+ - full name of the user\n- +email+ - the email address user\n\n\n[source,xml]\n----\n\n \n\n----\n\nThe server sends in response:\n\nRegistration Form\n[source,xml]\n----\n\n\t\n \n\t\t\tCustomer Registration\n\t\t\tPlease fill all fields\n\t\t\t\n\t\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\t\n\t\t\t\t\n\t\t\t\n \n\t\n\n----\n\nThe user now sends the completed form:\n\nRegistration form response\n[source,xml]\n----\n\n\t\n\t\t\n\t\t\t\n\t\t\t\tBob Bobowsky\n\t\t\t\n\t\t\t\n\t\t\t\tbob@somewhere.gov\n\t\t\t\n\t\t\n\t\n\n----\n\nAfter sending the filled form, a new +customer-id+ will be generated and sent to the E-mail listed in the form.\nIf you are already registered, it will be sent to the following address existing +customer-id+\n\n==== +retrieve-license+\n\nTo obtain a license from the server must send a form containing a +customer-id+:\n\nStart-up Command +retrieve-license+\n[source,xml]\n----\n\n\t\n\n----\n\nIn response, the server will send a form asking for +customer-id+.\nIf the server's found his JabberID, it sent the form will automatically be filled in:\n\nAsking for +customer-id+\n[source,xml]\n----\n\n\t\n\t\t\n\t\t\tRetrieve licence\n\t\t\tPlease fill all fields\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\n\t\n\n----\n\nThe user sends the completed form:\n\nFilled Form license generation\n[source,xml]\n----\n\n\t\n\t\t\n\t\t\t\n\t\t\t\t6if49ogdd9qbenat2t1461f1kf\n\t\t\t\n\t\t\t\n\t\t\t\tacs\n\t\t\t\n\t\t\n\t\n\n----\n\nThe server sends a form containing the license.\n\nNOTE: Warning! The license may be in plain-text or Base64 encoded!\n\n.Generated license\n[source,xml]\n----\n\n\t\n\t\t\n\t\t\t\n\t\t\t\tmax-costam=9\n\t\t\t\tcomment=Licencja całkowicie domyślna\n\t\t\t\tlicence-nr=1\n\t\t\t\tlicence-id=de54488e-13d0-38a4-8614-1b624cc73ac0\n\t\t\t\tcustomer-name=Bob Bobowsky\n\t\t\t\tcustomer-jid=bob@coffeebean.local\n\t\t\t\ttemplate-id=fb9971738214b50c5700673956ade0fa0b8169d0\n\t\t\t\tvalid-since=2015-07-17\n\t\t\t\tvalid-until=2015-10-17\n\t\t\t\tsignature=2bca48ad20b63dd76be08b1a6…374dab308\n\t\t\t\n\t\t\n\t\n\n----\n\n[[licenseconfig]]\n== Configuring Tigase XMPP Server License Registration\nAs seen earlier, you will need to include your +customer-id+ into the init.properties file on your installation by adding the line:\n[source,properties]\n-----\n--customer-id=9s82stmw2tasc4h6q05n69azxs\n-----\nEverything should be automated from there.\n\n== Statistics Sent\nIf you are using Tigase without a customer ID, you will be given a warning that statistics will be sent to Tigase. Below is a breakdown of what is sent to the server.\n\nNOTE: The text below has been better formatted for readability, but does not reflect the actual text being sent to Tigase.\n\n[source,output]\n-----\n\n\txmppserver\n\t2016-06-23T17:16:24.777-0700\n\t\n vhost1.xmppserver.com\n \n\t308833\n\t\n 30924376\n 1426063360\n \n\t\n 1\n \n\t\n 0\n 0\n 1\n 0\n \n\t\n\t\t\n\t\t\t\n\t\t\t\tamp\n\t\t\t\tTigase XMPP Server\n\t\t\t\t7.1.0-SNAPSHOT-b4226/5e7210f6 (2016-06-01/23:15:52)\n\t\t\t\ttigase.cluster.AmpComponentClustered\n\t\t\t\n\n\t\t\t\n\t\t\t\tbosh\n\t\t\t\tTigase XMPP Server\n\t\t\t\t7.1.0-SNAPSHOT-b4226/5e7210f6 (2016-06-01/23:15:52)\n\t\t\t\ttigase.cluster.BoshConnectionClustered\n\t\t\t\n\n\t\t\t\n\t\t\t\tc2s\n\t\t\t\tTigase XMPP Server\n\t\t\t\t7.1.0-SNAPSHOT-b4226/5e7210f6 (2016-06-01/23:15:52)\n\t\t\t\ttigase.cluster.ClientConnectionClustered\n\t\t\t\n\n\t\t\t\n\t\t\t\tcl-comp\n\t\t\t\tTigase XMPP Server\n\t\t\t\t7.1.0-SNAPSHOT-b4226/5e7210f6 (2016-06-01/23:15:52)\n\t\t\t\ttigase.cluster.ClusterConnectionManager\n\t\t\t\n\n\t\t\t\n\t\t\t\teventbus\n\t\t\t\tTigase XMPP Server\n\t\t\t\t7.1.0-SNAPSHOT-b4226/5e7210f6 (2016-06-01/23:15:52)\n\t\t\t\ttigase.disteventbus.component.EventBusComponent\n\t\t\t\n\n\t\t\t\n\t\t\t\thttp\n\t\t\t\tTigase HTTP API component: Tigase HTTP API component\n\t\t\t\t1.2.0-SNAPSHOT-b135/27310f9b-7.1.0-SNAPSHOT-b4226/5e7210f6 (2016-06-01/23:15:52)\n\t\t\t\ttigase.http.HttpMessageReceiver\n\t\t\t\n\n\t\t\t\n\t\t\t\tmonitor\n\t\t\t\tTigase XMPP Server\n\t\t\t\t7.1.0-SNAPSHOT-b4226/5e7210f6 (2016-06-01/23:15:52)\n\t\t\t\ttigase.monitor.MonitorComponent\n\t\t\t\n\n\t\t\t\n\t\t\t\tmuc\n\t\t\t\tTigase ACS - MUC Component\n\t\t\t\t1.2.0-SNAPSHOT-b62/74afbb91-2.4.0-SNAPSHOT-b425/d2e26014\n\t\t\t\ttigase.muc.cluster.MUCComponentClustered\n\t\t\t\t\n\t\t\t\t\tclass tigase.muc.cluster.ShardingStrategy\n\t\t\t\t\n\t\t\t\n\n\t\t\t\n\t\t\t\tpubsub\n\t\t\t\tTigase ACS - PubSub Component\n\t\t\t\t1.2.0-SNAPSHOT-b65/1c802a4c-3.2.0-SNAPSHOT-b524/892f867f\n\t\t\t\ttigase.pubsub.cluster.PubSubComponentClustered\n\t\t\t\t\n\t\t\t\t\tclass tigase.pubsub.cluster.PartitionedStrategy\n\t\t\t\t\n\t\t\t\n\n\t\t\t\n\t\t\t\ts2s\n\t\t\t\tTigase XMPP Server\n\t\t\t\t7.1.0-SNAPSHOT-b4226/5e7210f6 (2016-06-01/23:15:52)\n\t\t\t\ttigase.server.xmppserver.S2SConnectionManager\n\t\t\t\n\n\t\t\t\n\t\t\t\tsess-man\n\t\t\t\tTigase XMPP Server\n\t\t\t\t7.1.0-SNAPSHOT-b4226/5e7210f6 (2016-06-01/23:15:52)\n\t\t\t\ttigase.cluster.SessionManagerClustered\n\t\t\t\t\n\t\t\t\t\tclass tigase.server.cluster.strategy.OnlineUsersCachingStrategy\n\t\t\t\t\n\t\t\t\n\n\t\t\t\n\t\t\t\tws2s\n\t\t\t\tTigase XMPP Server\n\t\t\t\t7.1.0-SNAPSHOT-b4226/5e7210f6 (2016-06-01/23:15:52)\n\t\t\t\ttigase.cluster.WebSocketClientConnectionClustered\n\t\t\t\n\n\t\t\t\n\t\t\t\tvhost-man\n\t\t\t\tTigase XMPP Server\n\t\t\t\t7.1.0-SNAPSHOT-b4226/5e7210f6 (2016-06-01/23:15:52)\n\t\t\t\ttigase.vhosts.VHostManager\n\t\t\t\n\n\t\t\t\n\t\t\t\tstats\n\t\t\t\tTigase XMPP Server\n\t\t\t\t7.1.0-SNAPSHOT-b4226/5e7210f6 (2016-06-01/23:15:52)\n\t\t\t\ttigase.stats.StatisticsCollector\n\t\t\t\n\n\t\t\t\n\t\t\t\tcluster-contr\n\t\t\t\tTigase XMPP Server\n\t\t\t\t7.1.0-SNAPSHOT-b4226/5e7210f6 (2016-06-01/23:15:52)\n\t\t\t\ttigase.cluster.ClusterController\n\t\t\t\n\t\t\n\n\t\t\n\t\t\t\n\t\t\n\t\n\n-----\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_101_-_Using_Tigase_-_P_-_Advanced_Options.asciidoc",
"content": "[[tigaseAdvancedOptions]]\n= Tigase Advanced Options\n:author: Daniel Wisnewski\n:date: 2016-03-28 14:55\n:version: v1.0 March 2016\n\n:toc:\n:numbered:\n:website: http://www.tigase.net\n\nThis section is designed to include a number of advanced configuration options available within Tigase, but may not have a relevant section yet to house them.\n\n== Enabling Support for storing offline messages without body content\n\nTigase now supports the full implementation or XEP-0334, See link:http://xmpp.org/extensions/xep-0334.html[XEP-0334] for protocol details.\n\nThis can be customized by setting a list of paths and xmlns to trigger and place storage of offline messages using the following settings in init.properties:\n-----\nsess-man/plugins-conf/amp/msg-store-offline-paths[s]=/message/received[urn:xmpp:receipts],/message/store-offline\n-----\n\nThis will require the enabling of AMP plugin, so be sure +--sm-plugins=+amp+ is enabled.\n\n[[emptyNicks]]\n== Enabling Empty Nicknames\n\nTigase can now support users with empty nicknames. This can be enabled by adding the following code is in init.properties.\n------\nsess-man/plugins-conf/jabber\\:iq\\:roster/empty_name_enabled=true\n------\n\n[[accountRegLimit]]\n== Account Registration Limits\n\nIn order to protect Tigase servers from DOS attacks, a limit on number of account registrations per second has been implemented. This may be configured by adding the following line in the init.properties file:\n-----\nsess-man/plugins-conf/jabber\\:iq\\:register/registrations-per-second=10\n-----\nThis setting allows for 10 registrations from a single IP per second. If the limit is exceeded, a +NOT_ALLOWED+ error will be returned.\n\n[[silentIgnore]]\n== Enable Silent Ignore on Packets Delivered to Unavailable Resources\n\nYou can now have Tigase ignore packets delivered to unavailable resources to avoid having a packet bounce around and create unnecessary traffic. You may set this globally, within standard message handling only, or within the AMP component using the following settings:\n\nGlobally:\n[source]\n-----\nsess-man/plugins-conf/silently-ignore-message=true\n-----\nMessage Processing Only:\n[source]\n-----\nsess-man/plugins-conf/message/silently-ignore-message=true\n-----\nAMP Component:\n[source]\n-----\nsess-man/plugins-conf/amp/silently-ignore-message=true\n-----\n\n[[errorCounting]]\n== Mechanism to count errors within Tigase\n\nA new processor within statistics has been added to count the number of errors that Tigase returns. This processor, named +error-counter+, will count all errors returned by Tigase, however by default the number is always zero if it is not enabled. It can be found as an MBean object in JMX under +ErrorStatistics+ and contains values for packets with +ERROR+ and grouped by type.\nTo enable counting of these errors, you must ensure the processor is included in your --sm-plugins:\n[source,properties]\n-----\n--sm-plugins=error-counter\n-----\n\n=== Including stream errors\n\nStream +ERROR+ packets are not included in the above counter by default as they are processed separately.\nTo enable this to be added to the counter, the following line must be in your init.properties file.\n[source,properties]\n-----\nc2s/processors[s]=stream-error-counter\n-----\n\n[[streamResumptiontimeout]]\n=== Stream resumption default & max-timeout\n\n+SteamManagementIOProcessor+ now has a setting that can be used to change the maximum timeout time it will wait for reconnection if a client does not send a time to wait. Two settings are now available:\n\n[source,properties]\n-----\nc2s/processors/urn\\:xmpp\\:sm\\:3/resumption-timeout[I]=90\n-----\nThe above setting in init.properties file will change the default timeout period to 90 seconds.\n\n[source,properties]\n-----\nc2s/processors/urn\\:xmpp\\:sm\\:3/max-resumption-timeout[I]=900\n-----\nThis setting will set the maximum time allowed for stream resumption to 900 seconds. This can be handy if you expect a number of mobile phones to connect to your server and want to avoid duplicate messages being sent back and forth.\n\n[[autoSub]]\nYou may setup a server to automatically approve presence subscriptions or roster authorizations for all users. Say you were hosting bots and wanted to automate the process. This can be done with the following settings:\n[source,properties]\n-----\nsess-man/plugins-conf/jabber\\:iq\\:roster/auto-authorize=true\nsess-man/plugins-conf/presence/auto-authorize=true\n-----\nBoth of these settings are false by default, and you may use them together or separately.\nThe following behavior is followed when they are both activated:\n\n- Upon sending a subscription request - Both contacts will each others' subscription and be added to each others' roster. Presence information will immediately be exchanged between both parties.\n- Upon sending presence with type either unsubscribe or unsubscribed follows the rules defined in RFC regarding processing of these stanzas (i.e. adjusting subscription type of user/contact), but without forwarding those stanzas to the receiving entity to avoid any notifications to the client. However, a roster push is generated to reflect changes to presence in user roster in a seamless manner.\n- Simply adding an item to the roster (i.e. with stanza with correct semantics) will also cause an automatic subscription between the user and the contact in a matter explained above.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_102_-_Statistics_Descriptions.asciidoc",
"content": "[[statsticsDescription]]\n= Statistics description\n:author: Daniel Wisnewski (daniel@tigase.org)\n:date: 2016-04-22 10:40\n:version: v1.0 April 2016\n\n\n:toc:\n:numbered:\n:website: http://www.tigase.org\n\nStatistics are divided between components and processors. You may see the same statistics collected for multiple components which are defined in common components section.\nNote that statistics are defined by {$component}/statistic so if you wanted Max queue size on pubsub, you would look for +pubsub/Max queue size+.\nStatistics will not be provided by components that are not enabled.\n\n== *Statistics common to components*\n\nThese statistics may be found in multiple components and may be seen multiple times.\nFor example both s2s and c2s will have Bytes sent statistic, so each can be found the following way:\n[source,properties]\n-----\ns2s/Bytes received\nc2s/Bytes received\n-----\n\n=== add-script last {interval}\n\nThe number of times that +add-script+ adhoc command has been run within the last interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+add-script/Average processing time+: The average time in ms, returned as an integer, it takes for +add-script+ to execute.\n\n*Available from the following components*:\n[source,list]\n-----\namp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, proxy, pubsub, rest, s2s, sess-man, ws2s\n-----\n\n*List of possible statistics*:\n[source,list]\n-----\n{compname}/adhoc-command/add-script last hour\n{compname}/adhoc-command/add-script last minute\n{compname}/adhoc-command/add-script last second\n{compname}/adhoc-command/add-script/Average processing time\n-----\n\n=== Average processing time on last 100 runs [ms]\n\nThe average processing time in milliseconds for all commands and scripts for this component over the last 100 times component is called. This number will populate with less than 100 runs, and will continue averaging until 100 runs happens, at that point, it's the most recent 100 instances.\nThis statistic will reset every time the server shuts down or restarts.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Available from the following components*:\n[source,list]\n-----\namp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, proxy, pubsub, rest, s2s, sess-man, ws2s\n-----\n\n*List of possible statistics*:\n[source,list]\n-----\n{compname}/Average processing time on last 100 runs [ms]\n-----\n\n=== Bytes received\n\nThe total number of bytes that the component has received during the current server instance. This statistic resets at server shutdown or restart.\n\n*Statistics Level*: FINE|FINEST\n\nc2s is FINE, all others are FINEST\n\n*Result Format*: Integer\n\n*Available from the following components*:\n[source,list]\n-----\nbosh, c2s, cl-comp, proxy, s2s, ws2s\n-----\n\n*List of possible statistics*:\n[source,list]\n-----\n{compname}/Bytes received\n-----\n\n=== Bytes sent\n\nThe total number of bytes that the component has sent during the current server instance. This statistic resets at server shutdown or restart.\n\n*Statistics Level*: FINE|FINEST\n\nc2s is FINE, all others are FINEST\n\n*Result Format*: Integer\n\n*Available from the following components*:\n[source,list]\n-----\nbosh, c2s, cl-comp, proxy, s2s, ws2s\n-----\n\n*List of possible statistics*:\n[source,list]\n-----\n{compname}/Bytes sent\n-----\n\n=== del-script last {interval}\n\nThe number of times that +del-script+ adhoc command has been run within the last interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+del-script/Average processing time+: The average time in ms, returned as an integer, it takes for +del-script+ to execute.\n\n*Available from the following components*:\n[source,list]\n-----\namp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, proxy, pubsub, rest, s2s, sess-man, ws2s\n-----\n\n*List of possible statistics*:\n[source,list]\n-----\n{compname}/adhoc-command/del-script last hour\n{compname}/adhoc-command/del-script last minute\n{compname}/adhoc-command/del-script last second\n{compname}/adhoc-command/del-script/Average processing time\n-----\n\n=== Last {interval} packets\n\nThe number of packets that have been handled by this component in the last interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Available from the following components*:\n[source,list]\n-----\namp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, proxy, pubsub, rest, s2s, sess-man, ws2s\n-----\n\n*List of possible statistics*:\n[source,list]\n-----\n{compname}/last hour packets\n{compname}/last minute packets\n{compname}/last second packets\n-----\n\n=== list-commands last {interval}\n\nThe number of +list-commands+ requests sent to the component in the last interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+list-commands/Average processing time+: The average time in ms, returned as an integer, it takes for +list-commands+ to execute.\n\n*Available from the following components*:\n[source,list]\n-----\namp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, proxy, pubsub, rest, s2s, sess-man, ws2s\n-----\n\n*List of possible statistics*:\n[source,list]\n-----\n{compname}/list-commands last hour\n{compname}/list-commands last minute\n{compname}/list-commands last second\n{compname}/list-commands/Average processing time\n-----\n\n=== {IN|OUT|Total} queue overflow\n\nThe number of times the in or out queue has overflown for this component. That is there are more packets queues than the max queue size.\nA total statistic is also available that combines both results.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Available from the following components*:\n[source,list]\n-----\namp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, proxy, pubsub, rest, s2s, sess-man, ws2s\n-----\n\n*List of possible statistics*:\n[source,list]\n-----\n{compname}/IN queue overflow\n{compname}/OUT queue overflow\n{compname}/Total queue overflow\n-----\n\n=== {in|out} queue wait: {priority}\n\nThe number of packets with {priority} priority currently in the incoming or outgoing queue.\n\n*Available {priority}*: SYSTEM|CLUSTER|HIGH|NORMAL|LOW|PRESENCE|LOWEST\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Available from the following components*:\n[source,list]\n-----\namp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, proxy, pubsub, rest, s2s, sess-man, ws2s\n-----\n\n*List of possible statistics*:\n[source,list]\n-----\n{compname}/In queue wait: SYSTEM\n{compname}/In queue wait: CLUSTER\n{compname}/In queue wait: HIGH\n{compname}/In queue wait: NORMAL\n{compname}/In queue wait: LOW\n{compname}/In queue wait: PRESENCE\n{compname}/In queue wait: LOWEST\n{compname}/Out queue wait: SYSTEM\n{compname}/Out queue wait: CLUSTER\n{compname}/Out queue wait: HIGH\n{compname}/Out queue wait: NORMAL\n{compname}/Out queue wait: LOW\n{compname}/Out queue wait: PRESENCE\n{compname}/Out queue wait: LOWEST\n-----\n\n=== {IN|OUT}_QUEUE processed {type}\n\nThe number of stanzas of different types that have been processed VIA the In or Out Queue of this component. This number will reset at the end of the server instance.\nEach component will have a list of the different types of stanzas it can process.\n\n*Available {type}*:\n[source,list]\n-----\nmessages\npresences\ncluster\nother\nIQ no XMLNS\nIQ http://jabber.org/protocol/disco#items\nIQ bind\nIQ jabber:iq:roster\nIQ session\nIQ vCard\nIQ command\nIQ jabber:iq:private\nIQ http://jabber.org/protocol/disco#info\ntotal IQ\n-----\n\nNOTE: Several statistics are only available from statistics component, shutdown thread will ONLY print the following: messages, presences, cluster, other, IQ no XLMNS, total IQ.\n\n*Statistics Level*: FINER\n\n*Result Format*: Integer\n\n*Available from the following components*:\n[source,list]\n-----\namp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, proxy, pubsub, rest, s2s, sess-man, ws2s\n-----\n\n*List of possible statistics*:\n[source,list]\n-----\n{compname}/IN_QUEUE processed messages\n{compname}/IN_QUEUE processed presences\n{compname}/IN_QUEUE processed cluster\n{compname}/IN_QUEUE processed other\n{compname}/IN_QUEUE processed IQ no XMLNS\n{compname}/IN_QUEUE processed IQ http://jabber.org/protocol/disco#items\n{compname}/IN_QUEUE processed IQ http://jabber.org/protocol/disco#info\n{compname}/IN_QUEUE processed IQ bind\n{compname}/IN_QUEUE processed IQ jabber:iq:roster\n{compname}/IN_QUEUE processed IQ jabber:iq:private\n{compname}/IN_QUEUE processed IQ session\n{compname}/IN_QUEUE processed IQ vCard\n{compname}/IN_QUEUE processed IQ command\n{compname}/IN_QUEUE processed total IQ\n{compname}/OUT_QUEUE processed messages\n{compname}/OUT_QUEUE processed presences\n{compname}/OUT_QUEUE processed cluster\n{compname}/OUT_QUEUE processed other\n{compname}/OUT_QUEUE processed IQ no XMLNS\n{compname}/OUT_QUEUE processed IQ http://jabber.org/protocol/disco#items\n{compname}/OUT_QUEUE processed IQ http://jabber.org/protocol/disco#info\n{compname}/OUT_QUEUE processed IQ bind\n{compname}/OUT_QUEUE processed IQ jabber:iq:roster\n{compname}/OUT_QUEUE processed IQ jabber:iq:private\n{compname}/OUT_QUEUE processed IQ session\n{compname}/OUT_QUEUE processed IQ vCard\n{compname}/OUT_QUEUE processed IQ command\n{compname}/OUT_QUEUE processed total IQ\n-----\n\n=== max queue size\n\nThe maximum number of items allowed in the packet queue for this component.\n\n*Statistics Level*:\n\n*Result Format*: Integer\n\n*Available from the following components*:\n[source,list]\n-----\namp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, muc, monitor, proxy, pubsub, rest, s2s, sess-man, ws2s\n-----\n\n*List of possible statistics*:\n[source,list]\n-----\n{compname}/max queue size\n-----\n\n=== Open Connections\n\nThe number of open connections to the component.\n\n*Statistics Level*: INFO|FINEST\n\nc2s is INFO, all other components are FINEST\n\n*Result Format*: Integer\n\n*Available from the following components*:\n[source,list]\n-----\nbosh, c2s, cl-comp, proxy, s2s, ws2s\n-----\n\n*List of possible statistics*:\n[source,list]\n-----\n{compname}/Open connections\n-----\n\n=== Packets received\n\nThe total number of packets received by the component from external sources in the current instance. This number resets at server shutdown or restart.\n\n*Statistics Level*: FINE\n\n*Result Format*: Integer\n\n*Available from the following components*:\n[source,list]\n-----\namp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, proxy, pubsub, rest, s2s, sess-man, ws2s\n-----\n\n*List of possible statistics*:\n[source,list]\n-----\n{compname}/Packets received\n-----\n\n=== Packets sent\n\nThe total number of packets sent by the component in the current instance. This number resets at server shutdown or restart.\n\n*Statistics Level*: FINE\n\n*Result Format*: Integer\n\n*Available from the following components*:\n[source,list]\n-----\namp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, proxy, pubsub, rest, s2s, sess-man, ws2s\n-----\n\n*List of possible statistics*:\n[source,list]\n-----\n{compname}/Packets sent\n-----\n\n=== Processed packets thread: {in|out}_{#}\n\nHow many packets have been processed in and out by each processing thread. Statistics will provide a list with each processing thread, and each thread having an in and an out counter.\nLet's say that we have 4 threads set for ws2s, a list will be seen like this:\n[source,list]\n-----\nws2s/Processed packets thread: in_0-ws2s\nws2s/Processed packets thread: in_2-ws2s\nws2s/Processed packets thread: in_3-ws2s\nws2s/Processed packets thread: in_4-ws2s\nws2s/Processed packets thread: out_0-ws2s\nws2s/Processed packets thread: out_1-ws2s\nws2s/Processed packets thread: out_2-ws2s\nws2s/Processed packets thread: out_3-ws2s\n-----\nNote that the processor counter starts with 0 and will count for as many threads as the component has as defined in xref:processingthreadsstat[{compname}/Processing threads].\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Available from the following components*:\n[source,list]\n-----\namp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, pubsub, proxy, rest, s2s, sess-man, ws2s\n-----\n\n*List of possible statistics*:\n[source,list]\n-----\n{compname}/Processed packets thread: in_0-{compname}\n{compname}/Processed packets thread: out_0-{compname}\n{compname}/Processed packets thread: in_1-{compname}\n{compname}/Processed packets thread: out_1-{compname}\n{compname}/Processed packets thread: in_2-{compname}\n{compname}/Processed packets thread: out_2-{compname}\n{compname}/Processed packets thread: in_3-{compname}\n{compname}/Processed packets thread: out_3-{compname}\n{compname}/Processed packets thread: in_4-{compname}\n{compname}/Processed packets thread: out_4-{compname}\n{compname}/Processed packets thread: in_5-{compname}\n{compname}/Processed packets thread: out_5-{compname}\n...\n-----\n\n[[processingthreadsstat]]\n=== processing threads\n\nThe number of threads provided for the particular component.\n\n*Statistics Level*: FINER\n\n*Result Format*: Integer\n\n*Available from the following components*:\n[source,list]\n-----\namp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, proxy, pubsub, rest, s2s, sess-man, ws2s\n-----\n\n*List of possible statistics*:\n[source,list]\n-----\n{compname}/processing threads\n-----\n\n=== Socket overflow\n\nThe number of times that this component has experienced socket overflow and had to drop packets. This does not include the number of dropped packets.\n\n*Statistics Level*: FINEST\n\n\n*Result Format*: Integer\n\n*Available from the following components*:\n[source,list]\n-----\nbosh, c2s, cl-comp, proxy, s2s, ws2s\n-----\n\n*List of possible statistics*:\n[source,list]\n-----\n{compname}/Socket overflow\n-----\n\n=== Total {in|out} queues wait\n\nThe number of packets in the inbound or outbound queue that are currently waiting to be sent. This includes packets of all types. This is an instant statistics, in that the number in queue is only as many in the queue the moment statistics are gathered.\n\n*Related Statistics*:\n+{compname}/Total queue wait+: A combined total of +Total in queue wait+ and +Total out queue wait+ statistics for this component.\n+Total queues wait+: A combined total of all component queue wait statistics.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Available from the following components*:\n[source,list]\n-----\namp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, muc, monitor, proxy, pubsub, rest, s2s, sess-man, ws2s\n-----\n\n*List of possible statistics*:\n[source,list]\n-----\n{compname}/Total in queues wait\n{compname}/Total out queues wait\n{compname}/Total queues wait\nTotal queues wait\n-----\n\n=== Total queues overflow\n\nThe number of times the component packet wait queue has overflown and had to drop packets. This statistic does not keep track of the number of dropped packets.\n\n*Related Statistics*:\n+total/Total queues overflow+: The combined total of all queue overflow statistics for all components.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Available from the following components*:\n[source,list]\n-----\namp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, proxy, pubsub, rest, s2s, sess-man, ws2s\n-----\n\n*List of possible statistics*:\n[source,list]\n-----\n{compname}/Total queues overflow\ntotal/Total queues overflow\n-----\n\n=== Waiting to send\n\nThe number of packets in the component's queue that are waiting to be sent. This number will usually be 0 however it will grow if a large number of packets are jamming up your system, or your queue sizes are set too low.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Available from the following components*:\n[source,list]\n-----\nbosh, c2s, cl-comp, proxy, s2s, ws2s\n-----\n\n*List of possible statistics*:\n[source,list]\n-----\n{compname}/Waiting to send\n-----\n\n=== Watchdog runs\n\nThe number of times watchdog has been run on this component to check for stale connections.\n\n*Statistics Level*: FINER\n\n*Result Format*: Integer\n\n*Available from the following components*:\n[source,list]\n-----\nbosh, c2s, cl-comp, s2s, ws2s\n-----\n\n*List of possible statistics*:\n[source,list]\n-----\n{compname}/Watchdog runs\n-----\n\n=== Watchdog stopped\n\nThe number of times watchdog identified and closed a connection it has found to be stale according to the settings in init.properties or by the defaults defined xref:watchdog[in this section].\n\n*Statistics Level*: FINER\n\n*Result Format*: Integer\n\n*Available from the following components*:\n[source,list]\n-----\nbosh, cl-comp, c2s, s2s, ws2s\n-----\n\n*List of possible statistics*:\n[source,list]\n-----\n{compname}/Watchdog stopped\n-----\n\n=== Watchdog tests\n\nThe number of times watchdog has found a potential stale connection and has conducted a test to determine whether or not to close the connection. This is per component in the current server instance.\n\n*Statistics Level*: FINER\n\n*Result Format*: Integer\n\n*Available from the following components*:\n[source,list]\n-----\nbosh, cl-comp, c2s, s2s, ws2s\n-----\n\n*List of possible statistics*:\n[source,list]\n-----\n{compname}/Watchdog tests\n-----\n\n== *AMP*\n\nNo exclusive amp specific statistics\n\n== *bosh*\n\n=== Bosh sessions\n\nThe number of currently open and running BOSH sessions to the server.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\nbosh/Bosh sessions\n-----\n\n=== pre-bind-session last {interval}\n\nThe number of times the pre-bind-session command has been executed within the last specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+bosh/pre-bind-session/Average processing time+: The average time in ms, returned as an integer, it takes for +pre-bind-session+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nbosh/adhoc-command/pre-bind-session last hour\nbosh/adhoc-command/pre-bind-session last minute\nbosh/adhoc-command/pre-bind-session last second\nbosh/adhoc-command/pre-bind-session/Average processing time\n-----\n\n== *c2s*\n\nNo exclusive c2s specific statistics\n\n== *cl-comp*\n\n=== adhoc-command/cluster-nodes-list last {interval}\n\nThe number of times per interval that the cluster-nodes-list command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+cl-comp/Adhoc-command/cluster-nodes-list/Average processing time+: The average time in ms, returned as an integer, it takes for +cluster-nodes-list+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\ncl-comp/adhoc-command/cluster-nodes-list last hour\ncl-comp/adhoc-command/cluster-nodes-list last minute\ncl-comp/adhoc-command/cluster-nodes-list last second\ncl-comp/adhoc-command/cluster-nodes-list/Average processing time\n-----\n\n=== adhoc-command/force-stop-service last {interval}\n\nThe number of times per interval that the force-stop-service command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+cl-comp/Adhoc-command/force-stop-service/Average processing time+: The average time in ms, returned as an integer, it takes for +force-stop-service+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\ncl-comp/adhoc-command/force-stop-service last hour\ncl-comp/adhoc-command/force-stop-service last minute\ncl-comp/adhoc-command/force-stop-service last second\ncl-comp/adhoc-command/force-stop-service/Average processing time\n-----\n\n=== adhoc-command/service-keys last {interval}\n\nThe number of times per interval that the service-keys command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+cl-comp/Adhoc-command/service-keys/Average processing time+: The average time in ms, returned as an integer, it takes for +service-keys+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\ncl-comp/adhoc-command/service-keys last hour\ncl-comp/adhoc-command/service-keys last minute\ncl-comp/adhoc-command/service-keys last second\ncl-comp/adhoc-command/service-keys/Average processing time\n-----\n\n=== adhoc-command/sim-serv-stopped {interval}\n\nThe number of times per interval that the sim-serv-stopped command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+cl-comp/Adhoc-command/sim-serv-stopped/Average processing time+: The average time in ms, returned as an integer, it takes for +sim-serv-stopped+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\ncl-comp/adhoc-command/sim-serv-stopped last hour\ncl-comp/adhoc-command/sim-serv-stopped last minute\ncl-comp/adhoc-command/sim-serv-stopped last second\ncl-comp/adhoc-command/sim-serv-stopped/Average processing time\n-----\n\n=== Average compression ratio\n\nThe average compression ratio of data sent to other clusters during the session.\n\n*Statistics Level*: FINE\n\n*Result Format*: Float\n\n*List of possible statistics*:\n[source,list]\n-----\ncl-comp/Average compression ratio\n-----\n\n=== Average decompression ratio\n\nThe average compression ratio of data received from other clusters during the session.\n\n*Statistics Level*: FINE\n\n*Result Format*: Float\n\n*List of possible statistics*:\n[source,list]\n-----\ncl-comp/Average decompression ratio\n-----\n\n=== Known cluster nodes\n\nThe number of cluster nodes currently connected to the server.\n\n*Statistics Level*: INFO\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\ncl-comp/Known cluster nodes\n-----\n\n=== Last {interval} disconnects\n\nThe number of cluster disconnections within the specified interval.\n\n*Available {interval}*: day|hour\n\n*Statistics Level*: FINE\n\n*Result Format*: Comma separated Array. For day, each array is the number of disconnections each hour, most recent first. For hour each array is the number of disconnections each minute, most recent first.\n\n*List of possible statistics*:\n[source,list]\n-----\ncl-comp/Last day disconnects\ncl-comp/Last hour disconnects\n-----\n\n=== Service connected time-outs\n\nThe number of time-outs during connection initialization of cluster nodes.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\ncl-comp/Service connected time-outs\n-----\n\n=== Total disconnects\n\nThe number of clusters that have disconnected during the current session.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\ncl-comp/Total disconnects\n-----\n\n== *eventbus*\n\nNo exclusive eventbus specific statistics\n\n== *message-archive*\n\n=== Removal time of expired messages (avg)\n\nThe average amount of time in milliseconds it takes to remove expired messages from the repository. This includes manual and automatic removal of messages.\n\n*Statistics Level*: FINE\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\nmessage-archive/Removal time of expired messages (avg)\n-----\n\n== *message-router*\n\n=== CPUs no\n\nThe number of CPUs available on the host machine.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\nmessage-router/CPUs no\n-----\n\n=== CPU usage\n\n% of available CPU power used by Tigase Server at the moment statistics are taken.\nTwo formats are available for CPU usage: A float integer which expresses a long decimal available from +CPU Usage [%]+, and a string which provides a rounded number with a % sign from +CPU usage+.\n\n*Statistics Level*: FINE\n\n*Result Format*: Float|String\n\n*List of possible statistics*:\n[source,list]\n-----\nmessage-router/CPU usage [%]\nmessage-router/CPU usage\n-----\n\n=== Free Heap\n\nThe amount of heap memory that is available for use, expressed in KB\n\n*Statistics Level*: FINE\n\n*Result Format* String\n\n*List of possible statistics*:\n[source,list]\n-----\nmessage-router/Free Heap\n-----\n\n=== Free NonHeap\n\nThe amount of non-heap memory that is available for use, expressed in KB\n\n*Statistics Level*: FINE\n\n*Result Format* String\n\n*List of possible statistics*:\n[source,list]\n-----\nmessage-router/Free NonHeap\n-----\n\n=== HEAP usage [%]\n\nTotal percent of HEAP memory in use by Tigase.\n\n*Statistics Level*: FINE\n\n*Result Format*: Float\n\n*List of possible statistics*:\n[source,list]\n-----\nmessage-router/HEAP usage [%]\n-----\n\n=== Local hostname\n\nThe local hostname of the physical server.\n\n*Statistics Level*: INFO\n\n*Result Format*: String\n\n*List of possible statistics*:\n[source,list]\n-----\nmessage-router/Local hostname\n-----\n\n=== Load average\n\nThe average system load for the previous minute. The way in which the load average is calculated is operating system specific but is typically a damped time-dependent average.\n\n*Statistics Level*: FINE\n\n*Result Format*: Float\n\n*List of possible statistics*:\n[source,list]\n-----\nmessage-router/Load average\n-----\n\n=== Max Heap mem\n\nMaximum amount of heap memory available as defined by JAVA_OPTIONS in tigase.conf, in Kb.\n\n*Statistics Level*: INFO\n\n*Result Format*: String\n\n*List of possible statistics*:\n[source,list]\n-----\nmessage-router/Max Heap mem\n-----\n\n=== Max NonHeap mem\n\nMaximum amount of non-heap memory available as defined by JAVA_OPTIONS in tigase.conf, in Kb.\n\n*Statistics Level*: FINE\n\n*Result Format*: String\n\n*List of possible statistics*:\n[source,list]\n-----\nmessage-router/Max NonHeap mem\n-----\n\n=== NONHEAP usage [%]\n\nTotal amount of NONHEAP memory in use expressed as a percentage.\n\n*Statistics Level*: FINE\n\n*Result Format*: Float\n\n*List of possible statistics*:\n[source,list]\n-----\nmessage-archive/NONHEAP usage [%]\n-----\n\n=== Threads count\n\nThe total number of processing threads available across all components.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\nmessage-router/Threads count\n-----\n\n=== Uptime\n\nThe total amount of time the server has been online for this session.\n\n*Statistics Level*: INFO\n\n*Result Format*: String\n\n*List of possible statistics*:\n[source,list]\n-----\nmessage-router/Uptime\n-----\n\n=== Used Heap\n\nThe amount of heap memory in use in KB.\n\n*Statistics Level*: INFO\n\n*Result Format*: String\n\n*List of possible statistics*:\n[source,list]\n-----\nmessage-router/Used Heap\n-----\n\n=== Used NonHeap\n\nThe amount of non-heap memory in use shown in KB.\n\n*Statistics Level*: FINE\n\n*Result Format*: String\n\n*List of possible statistics*:\n[source,list]\n-----\nmessage-router/Used NonHeap\n-----\n\n== *monitor*\n\n=== adhoc-command/load-errors last {interval}\n\nThe number of times per interval that the load-errors command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+monitor/Adhoc-command/load-errors/Average processing time+: The average time in ms, returned as an integer, it takes for +load-errors+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nmonitor/adhoc-command/load-errors last hour\nmonitor/adhoc-command/load-errors last minute\nmonitor/adhoc-command/load-errors last second\nmonitor/adhoc-command/load-errors/Average processing time\n-----\n\n== *muc*\n\n=== adhoc-command/remove-room last {interval}\n\nThe number of times per interval that the remove-room command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+muc/Adhoc-command/remove-room/Average processing time+: The average time in ms, returned as an integer, it takes for +remove-room+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nmonitor/adhoc-command/remove-room last hour\nmonitor/adhoc-command/remove-room last minute\nmonitor/adhoc-command/remove-room last second\nmonitor/adhoc-command/remove-room/Average processing time\n-----\n\n=== adhoc-command/default-room-config last {interval}\n\nThe number of times per interval that the default-room-command command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+muc/Adhoc-command/default-room-config/Average processing time+: The average time in ms, returned as an integer, it takes for +default-room-config+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nmuc/adhoc-command/default-room-config last hour\nmuc/adhoc-command/default-room-config last minute\nmuc/adhoc-command/default-room-config last second\nmuc/adhoc-command/default-room-config/Average processing time\n-----\n\n== *proxy*\n\n=== Average transfer size in KB\n\nAverage size of packets sent through the proxy component during the current session.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\nproxy/Average transfer size in KB\n-----\n\n=== KBytes transferred\n\nTotal number of Kb transferred through the proxy component.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\nproxy/KBytes transferred\n-----\n\n=== Open streams\n\nNumber of currently open proxy streams.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\nproxy/Open streams\n-----\n\n=== Transfers completed\n\nNumber of specific transfers completed through proxy component.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\nproxy/Transfers completed\n-----\n\n== *pubsub*\n\n=== Added new nodes\n\nThe total number of new nodes that has been added in the current server instance. This statistic is reset when the server resets.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/Added new nodes\n-----\n\n=== adhoc-command/delete-item last {interval}\n\nThe number of times per interval that the delete-item command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/adhoc-command/delete-item/Average processing time+: The average time in ms, returned as an integer, it takes for +delete-item+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/adhoc-command/delete-item last hour\npubsub/adhoc-command/delete-item last minute\npubsub/adhoc-command/delete-item last second\npubsub/adhoc-command/delete-item/Average processing time\n-----\n\n=== adhoc-command/delete-node last {interval}\n\nThe number of times per interval that the delete-node command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/adhoc-command/delete-node/Average processing time+: The average time in ms, returned as an integer, it takes for +delete-item+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/adhoc-command/delete-node last hour\npubsub/adhoc-command/delete-node last minute\npubsub/adhoc-command/delete-node last second\npubsub/adhoc-command/delete-node/Average processing time\n-----\n\n=== adhoc-command/list-items last {interval}\n\nThe number of times per interval that the list-items command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/adhoc-command/list-items/Average processing time+: The average time in ms, returned as an integer, it takes for +list-items+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/adhoc-command/list-items last hour\npubsub/adhoc-command/list-items last minute\npubsub/adhoc-command/list-items last second\npubsub/adhoc-command/list-items/Average processing time\n-----\n\n=== adhoc-command/list-nodes last {interval}\n\nThe number of times per interval that the list-nodes command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/adhoc-command/list-nodes/Average processing time+: The average time in ms, returned as an integer, it takes for +list-nodes+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/adhoc-command/list-nodes last hour\npubsub/adhoc-command/list-nodes last minute\npubsub/adhoc-command/list-nodes last second\npubsub/adhoc-command/list-nodes/Average processing time\n-----\n\n=== adhoc-command/publish-item last {interval}\n\nThe number of times per interval that the publish-item command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/adhoc-command/publish-item/Average processing time+: The average time in ms, returned as an integer, it takes for +publish-item+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/adhoc-command/publish-item last hour\npubsub/adhoc-command/publish-item last minute\npubsub/adhoc-command/publish-item last second\npubsub/adhoc-command/publish-item/Average processing time\n-----\n\n=== adhoc-command/retrieve-item last {interval}\n\nThe number of times per interval that the retrieve-item command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/adhoc-command/retrieve-item/Average processing time+: The average time in ms, returned as an integer, it takes for +retrieve-item+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/adhoc-command/retrieve-item last hour\npubsub/adhoc-command/retrieve-item last minute\npubsub/adhoc-command/retrieve-item last second\npubsub/adhoc-command/retrieve-item/Average processing time\n-----\n\n=== AdHocConfigCommandModule last {interval}\n\nThe number of times per interval that the AdHocConfigCommandModule command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/AdHocConfigCommandModule/Average processing time+: The average time in ms, returned as an integer, it takes for +AdHocConfigCommandModule+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/AdHocConfigCommandModule last hour\npubsub/AdHocConfigCommandModule last minute\npubsub/AdHocConfigCommandModule last second\npubsub/AdHocConfigCommandModule/Average processing time\n-----\n\n=== Affiliations count (in cache)\n\nThe total number of pubsub affiliations that are resident in cache memory. Affiliations include JIDs that are one of the following; Owner, Publisher, Publish-Only, Member, None, Outcast. This may not reflect total pubsub affiliations in repository.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/Affiliations count (in cache)\n-----\n\n\n=== Average DB write time [ms]\n\nThe average time of all DB writes from PubSub component. Average is calculated using two other statistics: (Total writing time / Database writes)\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/Average DB write time [ms]\n-----\n\n=== cache/hits last {interval}\n\nThe number of times the cache has achieved a hit within the last interval. A hit is when a request for information is matched to data that is inside the cache memory.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/cache/hits last hour\npubsub/cache/hits last minute\npubsub/cache/hits last second\n-----\n\n=== cache/hit-miss ratio per {interval}\n\nThe ratio of cache hits to cache misses over the specified period. A cache hit is when a request for information from the cache is matched with information in the cache. A miss is when that information request cannot find a match in cache. A miss only indicates that that information was not found in the cache, not that it is not in the repository.\n\n*Available {interval}*: hour|minute\n\n*Statistics Level*: FINE\n\n*Result Format*: Float\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/cache/hit-miss ratio per hour\npubsub/cache/hit-miss ratio per minute\n-----\n\n=== cache/requests last {interval}\n\nThe number of memory cache requests made within the last interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/cache/Requests last hour\npubsub/cache/Requests last minute\npubsub/cache/Requests last second\n-----\n\n=== Cached nodes\n\nThe number of nodes that is currently in memory cache.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/Cached nodes\n-----\n\n=== CapsModule\n\nThe number of times per interval that the CapsModule command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/CapsModule/Average processing time+: The average time in ms, returned as an integer, it takes for +CapsModule+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/CapsModule last hour\npubsub/CapsModule last minute\npubsub/CapsModule last second\npubsub/CapsModule/Average processing time\n-----\n\n=== db/GetNodeItems requests last {interval}\n\nThe number of times +GetNodeItems+ command has been run within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/db/GetNodeItems/Average processing time+: The average time in ms, returned as an integer, it takes for +GetNodeItems+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/db/GetNodeItems last hour\npubsub/db/GetNodeItems last minute\npubsub/db/GetNodeItems last second\npubsub/db/GetNodeItems/Average processing time\n-----\n\n=== DefaultConfigModule last {interval}\n\nThe number of times per interval that the DefaultConfigModule command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/DefaultConfigModule/Average processing time+: The average time in ms, returned as an integer, it takes for +DefaultConfigModule+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/DefaultConfigModule last hour\npubsub/DefaultConfigModule last minute\npubsub/DefaultConfigModule last second\npubsub/DefaultConfigModule/Average processing time\n-----\n\n=== DiscoverInfoModule last {interval}\n\nThe number of times per interval that the DiscoverInfoModule command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/DiscoverInfoModule/Average processing time+: The average time in ms, returned as an integer, it takes for +DiscoverInfoModule+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/DiscoverInfoModule last hour\npubsub/DiscoverInfoModule last minute\npubsub/DiscoverInfoModule last second\npubsub/DiscoverInfoModule/Average processing time\n-----\n\n=== DiscoverItemsModule last {interval}\n\nThe number of times per interval that the DiscoverItemsModule command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/DiscoverItemsModule/Average processing time+: The average time in ms, returned as an integer, it takes for +DiscoverItemsModule+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/DiscoverItemsModule last hour\npubsub/DiscoverItemsModule last minute\npubsub/DiscoverItemsModule last second\npubsub/DiscoverItemsModule/Average processing time\n-----\n\n=== JabberVersionModule last {interval}\n\nThe number of times per interval that the JabberVersionModule command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/JabberVersionModule/Average processing time+: The average time in ms, returned as an integer, it takes for +JabberVersionModule+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/JabberVersionModule last hour\npubsub/JabberVersionModule last minute\npubsub/JabberVersionModule last second\npubsub/JabberVersionModule/Average processing time\n-----\n\n=== ManageAffiiationsModule last {interval}\n\nThe number of times per interval that the ManageAffiliationsModule command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/ManageAffiliationsModule/Average processing time+: The average time in ms, returned as an integer, it takes for +ManageAffiliationsModule+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/ManageAffiliationsModule last hour\npubsub/ManageAffiliationsModule last minute\npubsub/ManageAffiliationsModule last second\npubsub/ManageAffiliationsModule/Average processing time\n-----\n\n=== ManageSubscriptionModule last {interval}\n\nThe number of times per interval that the ManageSubscriptionModule command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/ManageSubscriptionModule/Average processing time+: The average time in ms, returned as an integer, it takes for +ManageSubscriptionModule+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/ManageSubscriptionModule last hour\npubsub/ManageSubscriptionModule last minute\npubsub/ManageSubscriptionModule last second\npubsub/ManageSubscriptionModule/Average processing time\n-----\n\n=== NodeConfigModule last {interval}\n\nThe number of times per interval that the NodeConfigModule command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/NodeConfigModule/Average processing time+: The average time in ms, returned as an integer, it takes for +NodeConfigModule+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/NodeConfigModule last hour\npubsub/NodeConfigModule last minute\npubsub/NodeConfigModule last second\npubsub/NodeConfigModule/Average processing time\n-----\n\n=== NodeCreateModule last {interval}\n\nThe number of times per interval that the NodeCreateModule command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/NodeCreateModule/Average processing time+: The average time in ms, returned as an integer, it takes for +NodeCreateModule+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/NodeCreateModule last hour\npubsub/NodeCreateModule last minute\npubsub/NodeCreateModule last second\npubsub/NodeCreateModule/Average processing time\n-----\n\n=== NodeDeleteModule last {interval}\n\nThe number of times per interval that the NodeDeleteModule command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/NodeDeleteModule/Average processing time+: The average time in ms, returned as an integer, it takes for +NodeDeleteModule+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/NodeDeleteModule last hour\npubsub/NodeDeleteModule last minute\npubsub/NodeDeleteModule last second\npubsub/NodeDeleteModule/Average processing time\n-----\n\n=== PresenceCollectorModule last {interval}\n\nThe number of times per interval that the PresenceCollectorModule command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/PresenceCollectorModule/Average processing time+: The average time in ms, returned as an integer, it takes for +PresenceCollectorModule+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/PresenceCollectorModule last hour\npubsub/PresenceCollectorModule last minute\npubsub/PresenceCollectorModule last second\npubsub/PresenceCollectorModule/Average processing time\n-----\n\n=== PendingSubscriptionModule last {interval}\n\nThe number of times per interval that the PendingSubscriptionModule command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/PendingSubscriptionModule/Average processing time+: The average time in ms, returned as an integer, it takes for +PendingSubscriptionModule+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/PendingSubscriptionModule last hour\npubsub/PendingSubscriptionModule last minute\npubsub/PendingSubscriptionModule last second\npubsub/PendingSubscriptionModule/Average processing time\n-----\n\n=== PresenceNotifierModule last {interval}\n\nThe number of times per interval that the PresenceNotifierModule command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/PresenceNotifierModule/Average processing time+: The average time in ms, returned as an integer, it takes for +PresenceNotifierModule+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/PresenceNotifierModule last hour\npubsub/PresenceNotifierModule last minute\npubsub/PresenceNotifierModule last second\npubsub/PresenceNotifierModule/Average processing time\n-----\n\n=== PublishItemModule last {interval}\n\nThe number of times per interval that the PublishItemModule command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/PublishItemModule/Average processing time+: The average time in ms, returned as an integer, it takes for +PublishItemModule+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/PublishItemModule last hour\npubsub/PublishItemModule last minute\npubsub/PublishItemModule last second\npubsub/PublishItemModule/Average processing time\n-----\n\n=== PurgeItemsModule last {interval}\n\nThe number of times per interval that the PurgeItemsModule command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/PurgeItemsModule/Average processing time+: The average time in ms, returned as an integer, it takes for +PurgeItemsModule+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/PurgeItemsModule last hour\npubsub/PurgeItemsModule last minute\npubsub/PurgeItemsModule last second\npubsub/PurgeItemsModule/Average processing time\n-----\n\n=== Repository writes\n\nNumber of individual writes to Repository from the pubsub component since startup.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n[source,list]\n-----\npubsub/Repository writes\n-----\n\n=== RetractItemModule last {interval}\n\nThe number of times per interval that the RetractItemModule command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/RetractItemModule/Average processing time+: The average time in ms, returned as an integer, it takes for +RetractItemModule+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/RetractItemModule last hour\npubsub/RetractItemModule last minute\npubsub/RetractItemModule last second\npubsub/RetractItemModule/Average processing time\n-----\n\n=== RetrieveAffiliationsModule last {interval}\n\nThe number of times per interval that the RetrieveAffiliationsModule command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/RetrieveAffiliationsModule/Average processing time+: The average time in ms, returned as an integer, it takes for +RetrieveAffiliationsModule+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/RetrieveAffiliationsModule last hour\npubsub/RetrieveAffiliationsModule last minute\npubsub/RetrieveAffiliationsModule last second\npubsub/RetrieveAffiliationsModule/Average processing time\n-----\n\n=== RetrieveItemsModule last {interval}\n\nThe number of times per interval that the RetrieveItemsModule command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/RetrieveItemsModule/Average processing time+: The average time in ms, returned as an integer, it takes for +RetrieveItemsModule+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/RetrieveItemsModule last hour\npubsub/RetrieveItemsModule last minute\npubsub/RetrieveItemsModule last second\npubsub/RetrieveItemsModule/Average processing time\n-----\n\n=== RetrieveSubscriptionsModule last {interval}\n\nThe number of times per interval that the RetrieveSubscriptionsModule command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/RetrieveSubscriptionsModule/Average processing time+: The average time in ms, returned as an integer, it takes for +RetrieveSubscriptionsModule+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/RetrieveSubscriptionsModule last hour\npubsub/RetrieveSubscriptionsModule last minute\npubsub/RetrieveSubscriptionsModule last second\npubsub/RetrieveSubscriptionsModule/Average processing time\n-----\n\n=== SubscribeNodeModule last {interval}\n\nThe number of times per interval that the SubscribeNodeModule command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/SubscribeNodeModule/Average processing time+: The average time in ms, returned as an integer, it takes for +SubscribeNodeModule+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/SubscribeNodeModule last hour\npubsub/SubscribeNodeModule last minute\npubsub/SubscribeNodeModule last second\npubsub/SubscribeNodeModule/Average processing time\n-----\n\n=== Subscription count (in cache)\n\nThe total number of pubsub subscriptions that are resident in cache memory. This may not reflect total pubsub subscriptions in repository.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/Subscription count (in cache)\n-----\n\n=== Total writing time\n\nThe cumulative total of time pubsub component has written to the database expressed in milliseconds.\n\n*Statistics Level*: FINEST\n\n*Result Format*: String (###ms)\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/Total writing time\n-----\n\n=== UnsubscribeNodeModule last {interval}\n\nThe number of times per interval that the UnsubscribeNodeModule command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/UnsubscribeNodeModule/Average processing time+: The average time in ms, returned as an integer, it takes for +UnsubscribeNodeModule+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/UnsubscribeNodeModule last hour\npubsub/UnsubscribeNodeModule last minute\npubsub/UnsubscribeNodeModule last second\npubsub/UnsubscribeNodeModule/Average processing time\n-----\n\n=== Update subscription calls\n\nNumber of times Subscriptions have been updated (this includes new, deleted, and edited).\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/Update subscriptions calls\n-----\n\n=== XmppPingModule last {interval}\n\nThe number of times per interval that the XmppPingModule command has been executed.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+pubsub/XmppPingModule/Average processing time+: The average time in ms, returned as an integer, it takes for +XmppPingModule+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\npubsub/XmppPingModule last hour\npubsub/XmppPingModule last minute\npubsub/XmppPingModule last second\npubsub/XmppPingModule/Average processing time\n-----\n\n[[repo-factoryStatistics]]\n== *repo-factory*\n\n=== repo-factory/Number of data repositories\n\nThe number of data repositories setup for this XMPP server.\n\n*Statistics Level*: FINE\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\nrepo-factory/Number of data repositories\n-----\n\n=== repo-factory/repository {jdbclocation} connections count\n\nThe number of connections made to this database.\n\n*Statistics Level*: FINE\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\nrepo-factory/repository {jdbclocation} connections count\n-----\n\n=== repo-factory/repository {jdbclocation} reconnections\n\nThe number of reconnections made to this database.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\nrepo-factory/repository {jdbclocation} reconnections\n-----\n\n=== repo-factory/repository {jdbclocation} failed reconnections\n\nThe number of reconnections that have failed to connect to this database.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\nrepo-factory/repository {jdbclocation} failed reconnections\n-----\n\n== *rest*\n\nNo exclusive rest specific statistics\n\n== *s2s*\n\n=== adhoc-command/get-cid-connection last {interval}\n\nThe number of times get-cid-connection command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+s2s/adhoc-command/get-cid-connection/Average processing time+: The average time in ms, returned as an integer, it takes for +get-cid-connection+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\ns2s/adhoc-command/get-cid-connection last hour\ns2s/adhoc-command/get-cid-connection last minute\ns2s/adhoc-command/get-cid-connection last second\ns2s/adhoc-command/get-cid-connection/Average processing time\n-----\n\n=== adhoc-command/s2s-bad-state-conns last {interval}\n\nThe number of times s2s-bad-state-conns command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/s2s-bad-state-conns/Average processing time+: The average time in ms, returned as an integer, it takes for +s2s-bad-state-conns+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\ns2s/adhoc-command/s2s-bad-state-conns last hour\ns2s/adhoc-command/s2s-bad-state-conns last minute\ns2s/adhoc-command/s2s-bad-state-conns last second\ns2s/adhoc-command/s2s-bad-state-conns/Average processing time\n-----\n\n=== adhoc-command/reset-bad-state-conns last {interval}\n\nThe number of times reset-bad-state-conns command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/reset-bad-state-conns/Average processing time+: The average time in ms, returned as an integer, it takes for +reset-bad-state-conns+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\ns2s/adhoc-command/reset-bad-state-conns last hour\ns2s/adhoc-command/reset-bad-state-conns last minute\ns2s/adhoc-command/reset-bad-state-conns last second\ns2s/adhoc-command/reset-bad-state-conns/Average processing time\n-----\n\n=== CIDs number\n\nConnectionID for the server. This may include multiple CIDs if server is running multiple vhosts.\n\n*Statistics Level*: FINEST\n\n*Result Format*: String\n\n*List of possible statistics*:\n[source,list]\n-----\ns2s/CIDs number\n-----\n\n=== Total DB keys\n\nTotal number of database keys.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\ns2s/Total DB keys\n-----\n\n=== Total {incoming|outgoing}\n\nThe total number of server-to-server connections, outgoing is local server connecting to other servers, and incoming is connections from other servers. The results may or may not be the same.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\ns2s/Total incoming\ns2s/Total outgoing\n-----\n\n=== Total {incoming|outgoing} TLS\n\nThe total number of server-to-server connections using TLS, outgoing is local server connecting to other servers, and incoming is connections from other servers. The results may or may not be the same.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\ns2s/Total incoming TLS\ns2s/Total outgoing TLS\n-----\n\n=== Total outgoing handshaking\n\nTotal number of outgoing connections that are currently handshaking to other servers.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\ns2s/Total outgoing handshaking\n-----\n\n=== Total control waiting\n\nTotal number of connections that were manually told to wait.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\ns2s/Total control waiting\n-----\n\n=== Total waiting\n\nTotal number of connections that are currently waiting for response from other server.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\ns2s/Total waiting\n-----\n\n== *sess-man*\n\n=== Active user connections\n\nNumber of user connections that are considered active. An active user is a user that has sent stanzas to the server or through the server within the last 5 minutes.\n\n*Statistics Level*: FINER\n\n*Result Format*: Integer\n\n*list of possible statistics*:\n[source,list]\n-----\nsess-man/Active user connections\n-----\n\n=== adhoc-command/connection-time last {interval}\n\nThe number of times connection-time command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/connection-time/Average processing time+: The average time in ms, returned as an integer, it takes for +connection-time+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/adhoc-command/connection-time last hour\nsess-man/adhoc-command/connection-time last minute\nsess-man/adhoc-command/connection-time last second\nsess-man/adhoc-command/connection-time/Average processing time\n-----\n\n=== adhoc-command/http://jabber.org/protocol/admin#add-user last {interval}\n\nThe number of times admin#add-user command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/http://jabber.org/protocol/admin#add-user/Average processing time+: The average time in ms, returned as an integer, it takes for +admin#add-user+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/adhoc-command/http://jabber.org/protocol/admin#add-user last hour\nsess-man/adhoc-command/http://jabber.org/protocol/admin#add-user last minute\nsess-man/adhoc-command/http://jabber.org/protocol/admin#add-user last second\nsess-man/adhoc-command/http://jabber.org/protocol/admin#add-user/Average processing time\n-----\n\n=== adhoc-command/http://jabber.org/protocol/admin#add-user-tracker last {interval}\n\nThe number of times admin#add-user-tracker command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/http://jabber.org/protocol/admin#add-user-tracker/Average processing time+: The average time in ms, returned as an integer, it takes for +admin#add-user-tracker+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/adhoc-command/http://jabber.org/protocol/admin#add-user-tracker last hour\nsess-man/adhoc-command/http://jabber.org/protocol/admin#add-user-tracker last minute\nsess-man/adhoc-command/http://jabber.org/protocol/admin#add-user-tracker last second\nsess-man/adhoc-command/http://jabber.org/protocol/admin#add-user-tracker/Average processing time\n-----\n\n=== adhoc-command/http://jabber.org/protocol/admin#announce last {interval}\n\nThe number of times admin#announce command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/http://jabber.org/protocol/admin#announce/Average processing time+: The average time in ms, returned as an integer, it takes for +admin#announce+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/adhoc-command/http://jabber.org/protocol/admin#announce last hour\nsess-man/adhoc-command/http://jabber.org/protocol/admin#announce last minute\nsess-man/adhoc-command/http://jabber.org/protocol/admin#announce last second\nsess-man/adhoc-command/http://jabber.org/protocol/admin#announce/Average processing time\n-----\n\n=== adhoc-command/http://jabber.org/protocol/admin#change-user-password last {interval}\n\nThe number of times admin#change-user-password command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/http://jabber.org/protocol/admin#change-user-password/Average processing time+: The average time in ms, returned as an integer, it takes for +admin#change-user-password+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/adhoc-command/http://jabber.org/protocol/admin#change-user-password last hour\nsess-man/adhoc-command/http://jabber.org/protocol/admin#change-user-password last minute\nsess-man/adhoc-command/http://jabber.org/protocol/admin#change-user-password last second\nsess-man/adhoc-command/http://jabber.org/protocol/admin#change-user-password/Average processing time\n-----\n\n=== adhoc-command/http://jabber.org/protocol/admin#delete-user last {interval}\n\nThe number of times admin#delete-user command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/http://jabber.org/protocol/admin#delete-user/Average processing time+: The average time in ms, returned as an integer, it takes for +admin#delete-user+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/adhoc-command/http://jabber.org/protocol/admin#delete-user last hour\nsess-man/adhoc-command/http://jabber.org/protocol/admin#delete-user last minute\nsess-man/adhoc-command/http://jabber.org/protocol/admin#delete-user last second\nsess-man/adhoc-command/http://jabber.org/protocol/admin#delete-user/Average processing time\n-----\n\n=== adhoc-command/http://jabber.org/protocol/admin#end-user-session last {interval}\n\nThe number of times admin#end-user-session command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/http://jabber.org/protocol/admin#end-user-session/Average processing time+: The average time in ms, returned as an integer, it takes for +admin#end-user-session+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/adhoc-command/http://jabber.org/protocol/admin#end-user-session last hour\nsess-man/adhoc-command/http://jabber.org/protocol/admin#end-user-session last minute\nsess-man/adhoc-command/http://jabber.org/protocol/admin#end-user-session last second\nsess-man/adhoc-command/http://jabber.org/protocol/admin#end-user-session/Average processing time\n-----\n\n=== adhoc-command/http://jabber.org/protocol/admin#get-active-users last {interval}\n\nThe number of times admin#get-active-users command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/http://jabber.org/protocol/admin#get-active-users/Average processing time+: The average time in ms, returned as an integer, it takes for +admin#get-active-users+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-active-users last hour\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-active-users last minute\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-active-users last second\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-active-users/Average processing time\n-----\n\n=== adhoc-command/http://jabber.org/protocol/admin#get-active-user-num last {interval}\n\nThe number of times admin#get-active-user-num command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/http://jabber.org/protocol/admin#get-active-user-num/Average processing time+: The average time in ms, returned as an integer, it takes for +admin#get-active-user-num+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-active-user-num last hour\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-active-user-num last minute\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-active-user-num last second\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-active-user-num/Average processing time\n-----\n\n=== adhoc-command/http://jabber.org/protocol/admin#get-idle-users last {interval}\n\nThe number of times admin#get-idle-users command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/http://jabber.org/protocol/admin#get-idle-users/Average processing time+: The average time in ms, returned as an integer, it takes for +admin#get-idle-users+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-idle-users last hour\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-idle-users last minute\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-idle-users last second\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-idle-users/Average processing time\n-----\n\n=== adhoc-command/http://jabber.org/protocol/admin#get-idle-users-num last {interval}\n\nThe number of times admin#get-idle-users-num command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/http://jabber.org/protocol/admin#get-idle-users-num/Average processing time+: The average time in ms, returned as an integer, it takes for +admin#get-idle-users-num+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-idle-users-num last hour\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-idle-users-num last minute\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-idle-users-num last second\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-idle-users-num/Average processing time\n-----\n\n=== adhoc-command/http://jabber.org/protocol/admin#get-online-users-list last {interval}\n\nThe number of times admin#get-online-users-list command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/http://jabber.org/protocol/admin#get-online-users-list/Average processing time+: The average time in ms, returned as an integer, it takes for +admin#get-online-users-list+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-online-users-list last hour\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-online-users-list last minute\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-online-users-list last second\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-online-users-list/Average processing time\n-----\n\n=== adhoc-command/http://jabber.org/protocol/admin#get-top-active-users last {interval}\n\nThe number of times admin#get-top-active-users command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/http://jabber.org/protocol/admin#get-top-active-users/Average processing time+: The average time in ms, returned as an integer, it takes for +admin#get-top-active-users+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-top-active-users last hour\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-top-active-users last minute\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-top-active-users last second\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-top-active-users/Average processing time\n-----\n\n=== adhoc-command/http://jabber.org/protocol/admin#get-registered-users-list last {interval}\n\nThe number of times admin#get-registered-users-list command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/http://jabber.org/protocol/admin#get-registered-users-list/Average processing time+: The average time in ms, returned as an integer, it takes for +admin#get-registered-users-list+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-registered-users-list last hour\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-registered-users-list last minute\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-registered-users-list last second\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-registered-users-list/Average processing time\n-----\n\n=== adhoc-command/http://jabber.org/protocol/admin#get-user-roster last {interval}\n\nThe number of times admin#get-user-roster command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/http://jabber.org/protocol/admin#get-user-roster/Average processing time+: The average time in ms, returned as an integer, it takes for +admin#get-user-roster+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-user-roster last hour\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-user-roster last minute\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-user-roster last second\nsess-man/adhoc-command/http://jabber.org/protocol/admin#get-user-roster/Average processing time\n-----\n\n=== adhoc-command/http://jabber.org/protocol/admin#remove-user last {interval}\n\nThe number of times admin#remove-user command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/http://jabber.org/protocol/admin#remove-user/Average processing time+: The average time in ms, returned as an integer, it takes for +admin#remove-user+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/adhoc-command/http://jabber.org/protocol/admin#remove-user last hour\nsess-man/adhoc-command/http://jabber.org/protocol/admin#remove-user last minute\nsess-man/adhoc-command/http://jabber.org/protocol/admin#remove-user last second\nsess-man/adhoc-command/http://jabber.org/protocol/admin#remove-user/Average processing time\n-----\n\n=== adhoc-command/http://jabber.org/protocol/admin#user-stats last {interval}\n\nThe number of times admin#user-stats command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/http://jabber.org/protocol/admin#user-stats/Average processing time+: The average time in ms, returned as an integer, it takes for +admin#user-stats+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/adhoc-command/http://jabber.org/protocol/admin#user-stats last hour\nsess-man/adhoc-command/http://jabber.org/protocol/admin#user-stats last minute\nsess-man/adhoc-command/http://jabber.org/protocol/admin#user-stats last second\nsess-man/adhoc-command/http://jabber.org/protocol/admin#user-stats/Average processing time\n-----\n\n=== adhoc-command/get-user-info last {interval}\n\nThe number of times get-user-info command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/get-user-info/Average processing time+: The average time in ms, returned as an integer, it takes for +get-user-info+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/adhoc-command/get-user-info last hour\nsess-man/adhoc-command/get-user-info last minute\nsess-man/adhoc-command/get-user-info last second\nsess-man/adhoc-command/get-user-info/Average processing time\n-----\n\n=== adhoc-command/modify-user last {interval}\n\nThe number of times modify-user command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/modify-user/Average processing time+: The average time in ms, returned as an integer, it takes for +modify-user+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/adhoc-command/modify-user last hour\nsess-man/adhoc-command/modify-user last minute\nsess-man/adhoc-command/modify-user last second\nsess-man/adhoc-command/modify-user/Average processing time\n-----\n\n=== adhoc-command/oauth-credentials last {interval}\n\nThe number of times oauth-credentials command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/oauth-credentials/Average processing time+: The average time in ms, returned as an integer, it takes for +oauth-credentials+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/adhoc-command/oauth-credentials last hour\nsess-man/adhoc-command/oauth-credentials last minute\nsess-man/adhoc-command/oauth-credentials last second\nsess-man/adhoc-command/oauth-credentials/Average processing time\n-----\n\n=== adhoc-command/roster-fixer last {interval}\n\nThe number of times roster-fixer command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/roster-fixer/Average processing time+: The average time in ms, returned as an integer, it takes for +roster-fixer+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/adhoc-command/roster-fixer last hour\nsess-man/adhoc-command/roster-fixer last minute\nsess-man/adhoc-command/roster-fixer last second\nsess-man/adhoc-command/roster-fixer/Average processing time\n-----\n\n=== adhoc-command/roster-fixer-cluster last {interval}\n\nThe number of times roster-fixer-cluster command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/roster-fixer-cluster/Average processing time+: The average time in ms, returned as an integer, it takes for +roster-fixer-cluster+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/adhoc-command/roster-fixer-cluster last hour\nsess-man/adhoc-command/roster-fixer-cluster last minute\nsess-man/adhoc-command/roster-fixer-cluster last second\nsess-man/adhoc-command/roster-fixer-cluster/Average processing time\n-----\n\n=== adhoc-command/user-domain-perm last {interval}\n\nThe number of times user-domain-perm command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/user-domain-perm/Average processing time+: The average time in ms, returned as an integer, it takes for +user-domain-perm+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/adhoc-command/user-domain-perm last hour\nsess-man/adhoc-command/user-domain-perm last minute\nsess-man/adhoc-command/user-domain-perm last second\nsess-man/adhoc-command/user-domain-perm/Average processing time\n-----\n\n=== adhoc-command/user-roster-management last {interval}\n\nThe number of times user-roster-management command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/user-roster-management/Average processing time+: The average time in ms, returned as an integer, it takes for +user-roster-management+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/adhoc-command/user-roster-management last hour\nsess-man/adhoc-command/user-roster-management last minute\nsess-man/adhoc-command/user-roster-management last second\nsess-man/adhoc-command/user-roster-management/Average processing time\n-----\n\n=== adhoc-command/user-roster-management-ext last {interval}\n\nThe number of times user-roster-management-ext command has been executed within the specified interval.\n\n*Available {interval}*: hour|minute|second\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*Sub-level Statistics Available*:\n\n+adhoc-command/user-roster-management-ext/Average processing time+: The average time in ms, returned as an integer, it takes for +user-roster-management-ext+ to execute.\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/adhoc-command/user-roster-management-ext last hour\nsess-man/adhoc-command/user-roster-management-ext last minute\nsess-man/adhoc-command/user-roster-management-ext last second\nsess-man/adhoc-command/user-roster-management-ext/Average processing time\n-----\n\n=== Authentication timeouts\n\nThe number of connections that have timed out during the authentication process. Default timeout is 2 minutes.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of available statistics*:\n[source,list]\n-----\nsess-man/Authentication timeouts\n-----\n\n=== Closed user connections\n\nUser connections that have been terminated by the user (as opposed to the server).\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of available statistics*:\n[source,list]\n-----\nsess-man/Closed user connections\n-----\n\n=== default-handler/Invalid registrations\n\nNumber of invalid registrations attempted with the server\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of available statistics*:\n[source,list]\n-----\nsess-man/default-handler/Invalid registrations\n-----\n\n=== default-handler/Registered users\n\nNumber of registered users for this server.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of available statistics*:\n[source,list]\n-----\nsess-man/default-handler/Registered users\n-----\n\n=== Maximum user connections\n\nMaximum number of connections that have been made during server instance, this number includes users connecting multiple times.\n\n*Statistics Level*: INFO\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/Maximum user connections\n-----\n\n=== Maximum user sessions {today|yesterday}\n\nThe number of most simultaneous sessions within the specified interval. Today = previous 24 hours, Yesterday = 24 hours after previous 24 hours (does not go by calendar date).\n\n*Statistics Level*: INFO|FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/Maximum user sessions today\nsess-man/Maximum user sessions yesterday\n-----\n\n=== Registered accounts\n\nSum total of registered accounts for the server.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/Registered accounts\n-----\n\n=== Open user connections\n\nThe current number of open user connections. This may be interpreted as number of connections from users, however a user can have more than one connection (connection from mobile and PC for example).\n\n*Statistics Level*: INFO\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/Open user connections\n-----\n\n=== Open user sessions\n\nThe current number of open user sessions.\n\n*Statistics Level*: INFO\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/Open user sessions\n-----\n\n=== Total user connections\n\nThe cumulative number of connections that have been made to the server during the current instance.\n\n*Statistics Level*: FINER\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/Total user connections\n-----\n\n=== Total user sessions\n\nThe cumulative number of sessions that this server has negotiated during the current instance.\n\n*Statistics Level*: FINER\n\n*result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/Total user sessions\n-----\n\n=== presence/Users status changes\n\nThe number of presence changes for all users that have been conducted during the server instance.\n\n*Stastics Level*: INFO\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/presence/Users status changes\nsess-man/presence-state/Users status changes\n-----\n\n=== sess-man/Processor\n\nProcessor statistics will result in a field of labels and values exclusive to that processor.\nThe field shows as follows:\n[source,properties]\n-----\n, Queue: 0, AvTime: 0, Runs: 0, Lost: 0\n-----\nWhere:\nQueue: Number of packets in process queue\nAvTime: Average time in ms processor takes to conduct it's operation.\nRuns: Number of times Processor has been run.\nLost: Number of packets lost during processing.\n\n*Statistics Level*: FINEST\n\n*List of possible statistics*:\n[source,list]\n-----\nsess-man/Processor: message carbons\n\nsess-man/Processor: http://jabber.org/protocol/stats\n\nsess-man/Processor: jabber:iq:auth\n\nsess-man/Processor: vcard-temp\n\nsess-man/Processor: amp\n\nsess-man/Processor: presence-subscription\n\nsess-man/Processor: disco\n\nsess-man/Processor: msgoffline\n\nsess-man/Processor: urn:xmpp:blocking\n\nsess-man/Processor: urn:xmpp:ping\n\nsess-man/Processor: jabber:iq:register\n\nsess-man/Processor: urn:ietf:params:xml:ns:xmpp-sasl\n\nsess-man/Processor: prp\n\nsess-man/Processor: presence\n\nsess-man/Processor: message-archive-xep-0136\n\nsess-man/Processor: default-handler\n\nsess-man/Processor: jabber:iq:roster\n\nsess-man/Processor: starttls\n\nsess-man/Processor: presence-state\n\nsess-man/Processor: jabber:iq:version\n\nsess-man/Processor: urn:xmpp:time\n\nsess-man/Processor: session-open\n\nsess-man/Processor: jabber:iq:privacy\n\nsess-man/Processor: urn:ietf:params:xml:ns:xmpp-bind\n\nsess-man/Processor: http://jabber.org/protocol/commands\n\nsess-man/Processor: vcard-xep0292\n\nsess-man/Processor: session-close\n\nsess-man/Processor: urn:ietf:params:xml:ns:xmpp-session\n\nsess-man/Processor: jabber:iq:private\n\nsess-man/Processor: Average amp on last 100 runs [ms]\n\nsess-man/Processor: Average msgoffline on last 100 runs[ms]\n\nThese are example scripts included with Tigase for demonstration purposes, it is likely you will not encounter or need them.\n\nsess-man/groovy-example last hour\n\nsess-man/groovy-example last minute\n\nsess-man/groovy-example last second\n\nsess-man/groovy-example/Average processing time\n\nsess-man/hello last hour\n\nsess-man/hello last minute\n\nsess-man/hello last second\n\nsess-man/hello/Average processing time\n-----\n\n== *vhost-man*\n\n=== Checks is anonymous domain\n\nNumber of anonymous domain checks that have been run within vhost-man.\n\n*Statistics Level*: FINEST\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\nvhost-man/Checks is anonymous domain\n-----\n\n=== Checks: is local domain\n\nNumber of local domain checks that have been run within vhost-man.\n\n*Statistics Level*: FINER\n\n*Result Format*: Integer\n\n*List of possible statistics*:\n[source,list]\n-----\nvhost-man/Checks: is local domain\n-----\n\n=== Get components for local domain\n\nNumber of components loaded within local domain.\n\n*Statistics Level*: FINER\n\n*Result Format* Integer\n\n*List of possible statistics*:\n[source,list]\n-----\nvhost-man/Get components for local domain\n-----\n\n=== Get components for non-local domain\n\nNumber of components loaded outside local domain.\n\n*Statistics Level*: FINEST\n\n*Result Format* Integer\n\n*List of possible statistics*:\n[source,list]\n-----\nvhost-man/Get components for non-local domain\n-----\n\n=== Number of Vhosts\n\nNumber of configured and running Virtual Hosts.\n\n*Statistics Level*: FINE\n\n*Result Format* Integer\n\n*List of possible statistics*:\n[source,list]\n-----\nvhost-man/Number of VHosts\n-----\n\n== *ws2s*\n\nNo exclusive ws2s specific statistics\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_103_-_Components_-_K_-_C2S.asciidoc",
"content": "[[c2scomponent]]\n= Client to Server Communication\n:author: Daniel Wisnewski (daniel@tigase.org)\n:date: 2016-06-23 08:20\n:version: v1.0 June 2016\n\nClient to server communication is an integral part of XMPP communication. C2S handles all client communication to the server, and is responsible for filtering and handling remote communications.\nC2S CAN be disabled, however doing so will only allow communication of internal components, and S2S communications.\n\n= Configuration\n\n== Resumption timeout\nIt is now possible to set a default stream resumption timeout that the server uses. This allows control of how long a server will wait for a reconnection from a client. This can be particularly helpful to manage mobile clients connecting to your server as they may not have complete coverage, and you do not want to close the stream right away.\nBy default, Tigase sets this value to 60 seconds.\n\n[source,properties]\n-----\nc2s/processors/urn\\:xmpp\\:sm\\:3/resumption-timeout[I]=90\n-----\nThis sets the default timeout to 90 seconds. You may, if you choose, specify a maximum timout time, which will allow the server to wait between the default and maximum before a connection is closed.\n[source,properties]\n-----\nc2s/processors/urn\\:xmpp\\:sm\\:3/max-resumption-timeout[I]=900\n-----\n\nNOTE: If the max-resumption-timeout is not set, it will always equal the resumption-timeout number, or default is none is set.\n\nAvailable since v7.1.0\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_104_-_Using_Tigase_-_Q_-_Clustering.asciidoc",
"content": "[[tigaseClustering]]\n= Tigase Clustering\n:author: Daniel Wisnewski\n:version: v1.0 June 2016\n:date: 24-06-2016 11:00\n\nTigase Clustering allows the use of a number of servers to be unified in delivering, from what a client or user sees, a single unified platform.\nThere are two typical reasons why clustering should be employed:\n\n- High Availability\n\n By using clustering, services can be provided with a high reliability and redundancy. By using a network of multiple servers, content or services can be served on any of the clustered servers maintaining a consistent uptime without relying on one machine.\n\n- Load Balancing\n\n This type of cluster helps to distribute a workload over a number of servers to reduce bottlenecking from heavy resource loads on a particular server.\n\nWith Tigase, you don't have to choose between either/or!\n\n*Tigase Clustering* offers *Full Redundancy* and *Automatic Load Balancing* allowing addition of new nodes at runtime with a simple configuration. All without a severe tax on resource consumption.\n\nAll basic components support clustering configuration, and some may be turned on or off.\n\n== Configuration\nTo enable Clustering on Tigase servers, use the following line in your init.properties file:\n[source,properties]\n-----\n--cluster-mode=true\n-----\n\nThat's it!\n\n=== Custom Ports\nYou can customize ports for the cluster component, just be sure that each clustered server also has the same settings so they can communicate.\n[source,properties]\n-----\n--cl-comp-ports=4250,3540\n-----\nYou can fine tune each port configuration, however this is not typically needed.\n\n==== Custom Port Configuration\nEach port has it's own details that can be manipulated VIA the following ports. Again *THIS IS OPTIONAL*\n[source,properties]\n-----\ncl-comp/connections/4250/type[S]=accept\ncl-comp/connections/4250/socket[S]=plain\ncl-comp/connections/4250/ifc[s]=*\ncl-comp/connections/4250/remote-host[S]=localhost\ncl-comp/connections/4250/connections/tls/required[B]=false\n-----\n\n=== Multi-node configuration\nEach node should have +--cluster-mode=true+ enabled that you wish to connect to the cluster. They will automatically discover other nodes to connect to VIA Server to Server traffic.\nNodes that are added or removed will be periodically updated.\n\n=== Traffic Control\nYou can customize the traffic going between clustered servers with a few options.\n\n==== cm-ht-traffic-throttling\nThis setting will control the number of bytes sent over non-user connections. Namely, Server to Server or S2S connections.\n[source,properties]\n-----\n--cm-ht-traffic-throttling=xmpp:25k:0:disc,bin:200m:0:disc\n-----\nThe format is as follows: {traffic-type}:{maximum-traffic}:{max-lifespan-traffic}:{action}\n- *traffic-type* Specifies the type of traffic controlled. This can either be *XMPP* or *bin*. XMPP limits the number of packets transferred, whereas bin limits the number of bytes transferred.\n- *maximum-traffic* Specifies how many bytes or packets may be sent within one minute.\n- *max-lifespan-traffic* Specifies how many bytes or packets may be sent within the lifetime of the connection. 0 means unlimited.\n- *action* Specifies the action to be taken which can be *disc* which disconnects the connection, or *drop* which will drop any data exceeding the thresholds.\n\n==== cm-see-other-host\nThis allows the specific use of a load balancing mechanism by selecting +SeeOtherHostIfc+ implementation.\nFor more details, see xref:loadBalanding[Tigase Load Balancing] documentation.\n\n== Old configuration method\n\nWhile these options are still available these settings CAN be less reliable. *Use ONLY if you need specific setups that cannot be accommodated by the automatic cluster mode*.\n\n=== Specifying Specific nodes\nYou can still use the old method of specifying every node on each server.\nServer 3 needs the following set\n[source,properties]\n-----\n--cluster-nodes=serv1.xmpp-test.org,serv2.xmpp-test.org\n-----\nServer 2 needs\n[source,properties]\n-----\n--cluster-nodes=serv1.xmpp-test.org,serv3.xmpp-test.org\n-----\nand so on...\n\n==== Password and Port configuration\nYou may specify a password and port to specific cluster servers if that is required. To do so, you will need to add {password}:{port} to the domain, like this example:\n[source,properties]\n-----\n--cluster-nodes=serv1.xmpp-test.org:domainpass:5600\n-----\n\n== Checking Cluster Connections\n\nAfter setting up clustering you may want to verify that the clusters are operational. Right now it can be done in two manners - first by checking that there are actual network connections established between cluster nodes. The other is to check internal status of the server.\n\n=== Established connections\nThere are number of ways to check for opened connections, simplest one use command line. (Tigase uses port _5277_ for cluster connections)\n\n* Linux\n[source,sh]\n-----\n$ lsof -iTCP:5277 -sTCP:ESTABLISHED -P -n\n-----\n\n* Windows\n[source,sh]\n-----\nC:\\WINNT>netstat -anp tcp | find \":5277 \"\n-----\n\n=== Cluster nodes connected (using XMPP)\nVerifying clustering connectivity over XMPP protocol requires any XMPP client capable of http://xmpp.org/extensions/xep-0030.html[XEP-0030: Service Discovery]. It's essential to remember that only an administrator (a user whose JID is configured as administrative) has access.\n\n==== Psi XMPP Client\nFor the purpose of this guide a http://psi-im.org/[Psi] client will be used. After successfully configuring and connecting to account with administrative privileges we need to access _Service Discovery_, either from application menu or from context menu of the particular account account:\n\nimage:images/monitoring_xmpp_1.png[caption=\"Figure 1: \", title=\"Access service discovery\", alt=\"roster-discovery\", width=\"233\"]\n\nIn the _Service Discovery_ window we need to find _Cluster Connection Manager_ component. After expanding the tree node for the component a list of all cluster nodes will be presented with the current status (either _connected_ or _disconnected_). Node column will contain actual hostname of the cluster node:\n\nimage:images/monitoring_clustering.png[caption=\"Figure 2: \", title=\"List of cluster nodes\", alt=\"discovery-nodes\", width=\"558\"]\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_105_-_Configuration_-_F_-_Sess-man.asciidoc",
"content": "[[sessMan]]\n= Session Manager\n:author: Daniel Wisnewski\n:version: v1.0 June 2016\n:date: 24-06-2016 11:00\n\nTigase Session Manager is where most of Tigase basic options can be configured, and where many operations are controlled from.\nChanges to session manager can effect operations throughout an entire XMPP installation, so care must be made when changing settings here.\n\n[[sessManMobileOpts]]\n== Mobile Optimizations\nBy default, Tigase employs XEP-0352 Client State Indication which allows for a more streamlined mobile experiencing by allowing the XMPP server to suppress or reduce the number of updates sent to a client thereby reducing the number of stanzas sent to a mobile client that is inactive.\nThis employment is contained within the processor +ClientStateIndication+ and is independent from the MobileV1, MobileV2, MobileV3 settings.\n\nHowever, this can be fine tuned by using mobile plugins from Tigase which can be used at the same time by adding the following line to the init.properties file:\n[source,properties]\n-----\nsess-man/plugins-conf/urn\\:xmpp\\:csi\\:0/logic=tigase.xmpp.impl.MobileV1\n-----\nOptions are:\n\n=== MobileV1\nKeeps all presence stanzas in queue until client is active.\n\n=== MobileV2\nThis setting delays delivery of presences while client is in inactive state, but only keeps the last presence for each full jid.\n*This is the default setting for CSI logic*.\n\n=== MobileV3\nKeeps the same presence logic as MobileV2, but also queues Message Carbons.\n*Currently not supported by CSI processor, will cause issues*.\n\n=== Disabling CSI\nIf you wish to not use the +ClientStateIndication+ processor, set the following in your init.properties file:\n[source,properties]\n-----\n--sm-plugins=-urn:xmpp:csi:0\n-----\n\n=== A note about Mobile Plugins\nPreviously, you could enable Mobile optimization logic using +--sm-plugins=+Mobile_V1+.\n\nIf you have used these in the past, it is recommended you change your system to use the CSI processor with the appropriate mobile processing logic.\n\nIf you require v3 logic, or do not wish to use CSI, be sure to disable it using the above option.\n\n== Thread Pool Counts\nSession manager can control the number of available thread pools for each processor. By adding the following line to the init.properties file, the global thread pool can be increased by a specified factor:\n[source,properties]\n-----\nsess-man/sm-threads-factor[I]=3\n-----\nIn this case, the global thread pools is increased by a factor or 3.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_106_-_Components_-_L_-_Socks5.asciidoc",
"content": "[[socks5]]\n= Socks 5 Component\n:author: Daniel Wisnewski\n:date: 2016-07-26 10:35\n:version: v1.0 July 2016\n\n\nTigase SOCKS5 component allows for file transfers to be made over a SOCKS5 proxy in accordance with link:http://xmpp.org/extensions/xep-0065.html[XEP-0065 SOCKS5 Bytestreams]. This allows for some useful features such as:\n- transfer limits per user, domain, or global\n- recording transfers between users\n- quotas and credits system implementation\n\n== Installation\nTigase SOCKS5 component comes built into the dist-max archives for Tigase XMPP server, and requires the component to be listed in init.properties file:\n[source,properties]\n-----\n--comp-name-3=proxy\n--comp-class-3=tigase.socks5.Socks5ProxyComponent\n-----\n\nYou will also need to decide if you wish to use database-based features or not. If you wish to simply run the socks5 proxy without features such as quotas, limits add the following line:\n[source,properties]\n-----\nproxy/verifier-class=tigase.socks5.verifiers.DummyVerifier\n-----\n\nThis will enable the SOCKS5 Proxy without any advanced features. If you wish to use those features, see the configuration section below.\n\n== Database Preparation\nIn order to use the more advanced features of the SOCKS5 Proxy Component, your database needs to be prepared with the proper schema prior to running the server.\n\nYou may either edit an existing database, or create a new database for specific use with the Proxy.\n\n=== Edit Existing Database\nYou can add the proper schema to your existing database using the DBSchemaLoader utility included with Tigase. The database folder contains the schema file for your type of database.\n\nFirst, backup your database before performing any actions and shut down Tigase XMPP Server.\n\nThen from the Tigase installation directory run the following command:\n[source,bash]\n-----\njava -cp \"jars/*\" tigase.util.DBSchemaLoader -dbType {derby,mysql,postgresql,sqlserver} - dbHostname {db address} -dbName {dbname} -rootUser root -rootPass root -file database/{dbtype}-socks5-schema.sql\n-----\nYou should see the following dialogue\n-----\nLogLevel: CONFIG\ntigase.util.DBSchemaLoader \t \t CONFIG Properties: [{dbHostname=localhost, logLevel=CONFIG, dbType=derby, file=database/derby-socks5-schema.sql, rootUser=root, dbPass=tigase_pass, dbName=tigasedb, schemaVersion=7-1, rootPass=root, dbUser=tigase_user}]\ntigase.util.DBSchemaLoader \t validateDBConnection \t INFO Validating DBConnection, URI: jdbc:derby:tigasedb;create=true\ntigase.util.DBSchemaLoader \t validateDBConnection \t CONFIG DriverManager (available drivers): [[jTDS 1.3.1, org.apache.derby.jdbc.AutoloadedDriver@34a245ab, com.mysql.jdbc.Driver@3941a79c, org.postgresql.Driver@6e2c634b]]\ntigase.util.DBSchemaLoader \t validateDBConnection \t INFO Connection OK\ntigase.util.DBSchemaLoader \t validateDBExists \t INFO Validating whether DB Exists, URI: jdbc:derby:tigasedb;create=true\ntigase.util.DBSchemaLoader \t validateDBExists \t INFO Exists OK\ntigase.util.DBSchemaLoader \t loadSchemaFile \t INFO Loading schema from file: database/derby-socks5-schema.sql, URI: jdbc:derby:tigasedb;create=true\ntigase.util.DBSchemaLoader \t loadSchemaFile \t INFO completed OK\ntigase.util.DBSchemaLoader \t shutdownDerby \t INFO Validating DBConnection, URI: jdbc:derby:tigasedb;create=true\ntigase.util.DBSchemaLoader \t shutdownDerby \t WARNING Database 'tigasedb' shutdown.\ntigase.util.DBSchemaLoader \t printInfo \t INFO\n\nDatabase init.properties configuration:\n\n--user-db=derby\n--user-db-uri=jdbc:derby:tigasedb;create=true\n-----\n\nOne this process is complete, you may begin using SOCKS5 proxy component.\n\n=== Create New Database\n\nIf you want to create a new database for the proxy component and use it as a separate socks5 database, create the database using the appropriate schema file in the database folder.\nOnce this is created, add the following line to your init.properties folder.\n[source,properties]\n-----\nproxy/repo-url=driver:address\n-----\n\nFor example, a mysql database will have this type of URL: jdbc:mysql://localhost/SOCKS?user=root&password=root to replace {database URL}. For more options, check the database section of xref:databasePreperation[this documentation].\n\n== Configuration\n\n=== *+verifier-class+*\n[source,properties]\n-----\nproxy/verifier-class=\n-----\nSpecifies the class used to verify transfer limits. The following options are available:\n\n==== +LimitsVerifier+\n- Class Name: +tigase.socks5.verifiers.LimitsVerifier+\n\nUses the database to store limits and record the amount of data transferred VIA the proxy. It accepts one parameter, +transfer-update-quantization+ which is used to create a value to check if the value of transferred bytes should be updated in the database or not. By default, this value is 1MB.\n\nNOTE: Low values can slow down file transfers, while high values can allow for users to exceed quotas.\n\n==== +DummyVerifier+\n- Class Name: tigase.socks5.verifiers.DummyVerifier\n\nThis accepts file transfers VIA SOCKS5 proxy from any user and does not check limitations against the database.\n\n=== *+socks5-repo-cls+*\n[source,properties]\n-----\nproxy/socks5-repo-cls=\n-----\n\nSpecifies implementation of repository used to store usage statistics. Two options are available for this setting:\n- tigase.socks5.verirepository.JDBCSocks5Repository - Uses the database implementation.\n- tigase.socks5.repository.DummySocks5Repository - ignores data storage, and is the default implementation.\n\n\n=== *+repo-url+*\n[source,properties]\n-----\nproxy/repo-url=\n-----\nThe database connection URL for the socks5 repository.\n\n=== *+verifier-params+*\n[source,properties]\n-----\nproxy/repo-params=\n-----\n\nComma separated parameters for +LimitsVerifier+ which will override the defaults. All of these limits are on a per calendar month basis.\nFor example, a user is limited to 10MB for all transfers. If he transfers 8MB between the 1st and the 22nd, he only has 2MB left in his limit. On the 1st of the following month, his limit is reset to 10MB.\n\nAvailable parameters:\n\n- +global-limit+ - Transfer limit for all domains in MB per month.\n- +instance-limit+ - Transfer limit for server instance in MB per month.\n- +default-domain-limit+ - The Default transfer limit per domain in MB per month.\n- +default-user-limit+ - The default transfer limit per user in MB per month.\n- +default-file-limit+ - The default transfer limit per file in MB per month.\n\n=== *+remote-addresses+*\n[source,properties]\n-----\nproxy/remote-addresses=\n-----\n\nA comma separated list of IP addresses that will be accessible VIA the Socks5 Proxy. This can be useful if you want to specify a specific router address to allow external traffic to transfer files using the proxy to users on an internal network.\n\n== Database usage for specific settings\nThe above configuration allows for global settings, however you may also define specifics for users and the scopes of those limitations by editing the database information directly.\n\nThe +user_id+ field denotes the scope of the limitation.\n\n. Using a +domain_name+ defines limits for all users whose JIDs are within that domain.\n. Using a +JID+ of a user defines limit for this exact user.\n\nIf the value set is larger than 0, that is the specific limit.\nIf value is equal to 0 the limit is not overridden and the global limit is used.\nIf value equals -1 proxy will forbid any transfer for this user.\nIt there is no value for user in this table, a new row will be created during first transfer and limits for domain or global limits will be used.\n\nSocks5 database is setup in this manner:\n\n[width=\"100%\",frame=\"topbot\",options=\"header\"]\n|=================================\n|uid |user_id |sha1_user_id |domain |sha1_domain |filesize_limit |transfer_limit_per_user |transfer_limit_per_domain\n|1 |user@domain.com |c35f2956d804e01ef2dec392ef3adae36289123f |domain.com |e1000db219f3268b0f02735342fe8005fd5a257a |0 |3000 |0\n|2 |domain.com |e1000db219f3268b0f02735342fe8005fd5a257a |domain.com |e1000db219f3268b0f02735342fe8005fd5a257a |500 |0 |0\n|=================================\n\nThis example table shows that user@domain.com is limited to 3000MB per transfer whereas all users of domain.com are limited to a max file size of 500MB.\nThis table will populate as users transfer files using the SOCKS5 proxy, once it begins population, you may edit it as necessary.\nA second database is setup tig_socks5_connections that records the connections and transmissions being made, however it does not need to be edited.\n\n\n\n== Example init.properties block\nCombined, your init.properties should look like the below excerpt to run socks5 transfers using a separate database.\n\n[source,properties]\n-----\nproxy/repo-url=jdbc:mysql://localhost/SOCKS?user=root&password=root\nproxy/verifier-class=tigase.socks5.verifiers.LimitsVerifier\nproxy/socks5-repo-cls=tigase.socks5.verirepository.JDBCSocks5Repository\n-----\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_10_-_Configuration_-_A_-_Tigase_XMPP_Server_init.properties_Configuration.asciidoc",
"content": "[[initPropertiesGuide]]\n= Tigase XMPP Server init.properties Configuration\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2013-02-09 03:54\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\ninit.properties is a slightly extended version of the Java properties file with (key, value) pairs.\n\nComment lines will have as it's first non-white space ASCII character either '#' or '!'.\n\nThe key starts with first non-white space ASCII character and ends on either first white space ASCII character or either of '=' or ':'. Therefore if your key contains any of '=', ':' or white space characters you have to escape them with backslash \\'\\': \\: or \\=.\n\nAll examples below specify 'vhosts' as a key and 'test-a, test-b, test-c' as a value:\n\n[source,bash]\n-----\nvhosts=test-a, test-b, test-c\nvhosts : test-a, test-b, test-c\n vhosts = test-a, test-b, test-c\n-----\n\nPossible types are:\n\n- *[S]* (or nothing) - Characters string: 'abcdef'\n- *[s]* - String array: 'abcdef, ghaijk, lmnopq'\n- *[B]* - Boolean: 'true' or 'false'\n- *[b]* - Boolean array: 'true, true, false'\n- *[L]* - Long number: 1234567890\n- *[l]* - Long array: '12334, 45435, 45645'\n- *[I]* - Integer number: 123456\n- *[i]* - Integer array: '123, 456, 678'\n\nThere are lots of parameters which have broader meaning than just one property. Some of them affect many configuration settings or can generate whole sections in the XML file. Most of them starts with \\'--' double hyphen. Please note, each property put in the init.properties file starting with \\'--' becomes a JVM system property (without \\'--' at the beginning).\n\n//example init.properties goes here\n\nReference the property guide for a description of properties.\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#admins[--admins]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#authDb[--auth-db]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#authDbUri[--auth-db-uri]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#authDomainRepoPool[--auth-domain-repo-pool]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#authRepoPool[--auth-repo-pool]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#authRepoPoolSize[--auth-repo-pool-size]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#bindExtHostnames[--bind-ext-hostnames]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#boshCloseConnection[--bosh-close-connection]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#boshExtraHeadersFile[--bosh-extra-headers-file]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#clConnRepoClass[--cl-conn-repo-class]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#clientAccessPolicyFile[--client-access-policy-file]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#clusterConnectAll[--cluster-connect-all]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#clusterMode[--cluster-mode]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#clusterNodes[--cluster-nodes]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#cmHtTrafficThrottling[--cm-ht-traffic-throttling]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#cmSeeOtherHost[--cm-see-other-host]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#cmTrafficThrottling[--cm-traffic-throttling]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#cmpnamePorts[--cmpname-ports]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#compClass[--comp-class]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#compName[--comp-name]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#crossDomainPolicyFile[--cross-domain-policy-file]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#dataRepoPoolSize[--data-repo-pool-size]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#debug[--debug]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#debugPackages[--debug-packages]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#domainFilterPolicy[--domain-filter-policy]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#elementsNumberLimit[--elements-number-limit]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#extComp[--ext-comp]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#extcompRepoClass[--extcomp-repo-class]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#external[--external]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#hardenedMode[--hardened-mode]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#maxQueueSize[--max-queue-size]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#monitoring[--monitoring]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#netBuffHighThroughput[--net-buff-high-throughput]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#netBuffStandard[--net-buff-standard]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#newConnectionsThrottling[--new-connections-throttling]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#nonpriorityQueue[--nonpriority-queue]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#queueImplementation[--queue-implementation]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#rosterImplementation[--roster-implementation]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#s2sEjabberdBugWorkaroundActive[--s2s-ejabberd-bug-workaround-active]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#s2sSecret[--s2s-secret]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#s2sSkipTlsHostnames[--s2s-skip-tls-hostnames]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#scriptDir[--script-dir]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#smClusterStrategyClass[--sm-cluster-strategy-class]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#smPlugins[--sm-plugins]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#smThreadsPool[--sm-threads-pool]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#sslCertsLocation[--ssl-certs-location]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#sslContainerClass[--ssl-container-class]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#sslDefCertDomain[--ssl-def-cert-domain]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#statsHistory[--stats-history]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#stringprepProcessor[--stringprep-processor]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#test[--test]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#tigaseConfigRepoClass[--tigase-config-repo-class]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#tigaseConfigRepoUri[--tigase-config-repo-uri]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#tlsJdkNssBugWorkaroundActive[--tls-jdk-nss-bug-workaround-active]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#trusted[--trusted]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#userDb[--user-db]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#userDbUri[--user-db-uri]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#userDomainRepoPool[--user-domain-repo-pool]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#userRepoPool[--user-repo-pool]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#userRepoPoolSize[--user-repo-pool-size]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#vhostAnonymousEnabled[--vhost-anonymous-enabled]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#vhostMaxUsers[--vhost-max-users]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#vhostMessageForwardJid[--vhost-message-forward-jid]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#vhostPresenceForwardJid[--vhost-presence-forward-jid]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#vhostRegisterEnabled[--vhost-register-enabled]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#vhostTlsRequired[--vhost-tls-required]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#virtHosts[--virt-hosts]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#watchdogDelay[--watchdog_delay]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#watchdogPingType[--watchdog_ping_type]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#watchdogTimeout[--watchdog_timeout]\n\n*Property name:* link:http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#configType[config-type]\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_11_-_Configuration_-_B_-_Startup_Files_tigase.sh_and_tigase.asciidoc",
"content": "[[manualconfig]]\n= Startup File for tigase.sh - tigase.conf\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 21:18\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nProperty file names for +tigase.sh+ startup script is a second parameter for the startup script. It can be skipped if environmental variables are set in different location or in different way.\n\nConfig file for startup script simply sets number of environment variables with the location of required components. Possible variables to set in this file are:\n\n- *JAVA_HOME* - location of Java installation home directory. *Must be set*.\n- *TIGASE_HOME* - location of Tigase installation home directory. _By default script try to find this location by searching directories from the location where the script has been run._\n- *TIGASE_CONSOLE_LOG* - file to which all console messages will be redirected if server is run in background. By default it will be: _TIGASE_HOME/logs/tigase-console.log_. *_If this file/directory is not writable by Tigase process all console messages will be redirected to /dev/null_*\n- *TIGASE_PID* location of the file with server PID number. By default it will be _TIGASE_HOME/logs/tigase.pid_.\n- *JAVA_OPTIONS* - options for JVM like size of RAM allocated for the JVM, properties and so on.\n- *TIGASE_OPTIONS* - additional options for Tigase server program. You can tweak initial parameters for your environment here.\n\nSample file to run *Tigase* with *PostgreSQL* database may look like:\n\n[source,bash]\n-----\nENC=\"-Dfile.encoding=UTF-8 -Dsun.jnu.encoding=UTF-8\"\nDRV=\"-Djdbc.drivers=org.postgresql.Driver\"\nJAVA_OPTIONS=\"${ENC} ${DRV} -server -Xms100M -Xmx100M \"\nCLASSPATH=\"\"\nTIGASE_CONFIG=\"tigase-pgsql.xml\"\nTIGASE_OPTIONS=\" --property-file etc/init.properties \"\n-----\n\nPlease note encoding settings. JVM by default uses encoding set in operating system environment. XMPP protocol, however uses +UTF-8+ for all data processing. So the ENC settings enforces +UTF-8+ encoding for all operations.\n\nAnother significant setting is \\'*CLASSPATH*'. It is intentionally set to an empty string. The *tigase.sh* startup script builds the *CLASSPATH* on it's own from files found in *jars/* and *libs/* directories. It is advised to set the *CLASSPATH* to the empty string because the Tigase server scans all available classes to find all components and plugins implementation. If the *CLASSPATH* contains lots of libraries which are not used anyway it can cause a long startup time and high system loads.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_12_-_Configuration_-_C_-_Linux_Settings_for_High_Load_Systems.asciidoc",
"content": "[[linuxhighload]]\n= Linux Settings for High Load Systems\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 21:18\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nThere are a few basic settings you have to adjust for high load systems to make sure the server has enough resources to handle a big number of network connections.\n\nThe main parameter is a maximum number of opened files allowed for the process to keep at the same time. Each network connection uses a file handler, therefore if the limit is too low you can quickly run out of handlers and the server can not accept any more connections.\n\nThis limit is set on 2 levels - on the kernel level (*fs.file-max*) and on the system level (*nofile*).\n\nAnother kernel property which can be important in certain configurations (like transports installations or when you use proxy for Bosh connections) is: *net.ipv4.ip_local_port_range*. This parameter can be set the same way as the +fs.file-max+ property.\n\n== fs.file-max\n\nThe *fs.file-max* kernel property is set via sysctl command. You can see current settings by executing the command:\n\n[source,sh]\n-----\n# sysctl fs.file-max\nfs.file-max = 358920\n-----\n\nIf you plan to run high load service with large number of server connections, then this parameter should be at least as twice big as the number of network connections you expect to support. You can change this setting by executing the command:\n\n[source,java]\n-----\n# sysctl -w fs.file-max=360000\nfs.file-max = 360000\n-----\n\n== net.ipv4.ip_local_port_range\n\nYou can see current settings by executing the command:\n\n[source,sh]\n-----\n# sysctl net.ipv4.ip_local_port_range\nnet.ipv4.ip_local_port_range = 32768\t61000\n-----\n\nYou can change this setting by executing the command:\n\n[source,sh]\n-----\n# sysctl -w net.ipv4.ip_local_port_range=\"1024 65000\"\nnet.ipv4.ip_local_port_range = 1024 65000\n-----\n\n== TCP_keepalive\n\nAccording to link:http://blog.kolargol.eu/2006/06/tcpkeepalive.html[blog.kolargol.eu] or link:http://www.gnugk.org/keepalive.html[www.gnugk.org/] some keepalive settings should be changed to improve reliability.\n\n[source,sh]\n-----\n# sysctl -w net.ipv4.tcp_keepalive_time=\"60\"\nnet.ipv4.tcp_keepalive_time = 60\n# sysctl -w net.ipv4.tcp_keepalive_probes=\"3\"\nnet.ipv4.tcp_keepalive_probes = 3\n# sysctl -w net.ipv4.tcp_keepalive_intvl=\"90\"\nnet.ipv4.tcp_keepalive_intvl = 90\n-----\n\n== /etc/sysctl.conf\n\nThe above commands let the system remember new settings until the next system restart. If you want to make the change permanent you have to edit the file: */etc/sysctl.conf* and add the property at the end of the file:\n\n[source,sh]\n-----\nfs.file-max=360000\nnet.ipv4.ip_local_port_range=1024 65000net.ipv4.tcp_keepalive_time=60\nnet.ipv4.tcp_keepalive_probes=3\nnet.ipv4.tcp_keepalive_intvl=90\n-----\n\nIt will be automatically loaded next time you start the server.\n\nCommand:\n\n[source,sh]\n-----\n# sysctl -p\n-----\n\nCauses the +/etc/systcl.conf+ to be reloaded which is useful when you have added more parameters to the file and don't want to restart the server.\n\n== nofile\n\nThis is the property used by the system limits. For example running the command +ulimit -a+ shows you all limits set for the current user:\n\n[source,sh]\n-----\n# ulimit -a\ncore file size (blocks, -c) 0\ndata seg size (kbytes, -d) unlimited\nfile size (blocks, -f) unlimited\npending signals (-i) 38912\nmax locked memory (kbytes, -l) 32\nmax memory size (kbytes, -m) unlimited\nopen files (-n) 40960\npipe size (512 bytes, -p) 8\nPOSIX message queues (bytes, -q) 819200\nstack size (kbytes, -s) 8192\ncpu time (seconds, -t) unlimited\nmax user processes (-u) 38912\nvirtual memory (kbytes, -v) unlimited\nfile locks (-x) unlimited\n-----\n\nTo make it even more interesting and more complex, there are 2 types of system limits:\n*soft limit* which can be temporarily exceeded by the user and\n*hard limit* which can not be exceeded.\nTo see your *hard limit* execute command:\n\n[source,sh]\n-----\n# ulimit -a -H\ncore file size (blocks, -c) unlimited\ndata seg size (kbytes, -d) unlimited\nfile size (blocks, -f) unlimited\npending signals (-i) 38912\nmax locked memory (kbytes, -l) 32\nmax memory size (kbytes, -m) unlimited\nopen files (-n) 40960\npipe size (512 bytes, -p) 8\nPOSIX message queues (bytes, -q) 819200\nstack size (kbytes, -s) unlimited\ncpu time (seconds, -t) unlimited\nmax user processes (-u) 38912\nvirtual memory (kbytes, -v) unlimited\nfile locks (-x) unlimited\n-----\n\nThe hard limits are usually bigger then the soft limits or sometimes the same.\n\nFor us the most important parameter is: *open files*. You can change the property in file: +/etc/security/limits.conf+. You have to append 2 following lines to the end of the file:\n\n[source,sh]\n-----\njabber soft nofile 350000\njabber hard nofile 350000\n-----\n\nWhere the *jabber* is the user name of the account running you IM service. You can also set the limits for all users on the machine in a following way:\n\n[source,sh]\n-----\n* soft nofile 350000\n* hard nofile 350000\n-----\n\nFor those changes to make an effect you have to logout from the modified account and login again. New limits should be applied.\n\n== su and init script\n\nIf one intends to use init scripts for startup purposes (or simply wants to be able to start the server utilizing su command) it's necessary to adjust PAM configuration by modifying /etc/pam.d/su file and uncomment following line:\n\n[source,sh]\n-----\nsession required pam_limits.so\n-----\n\nAfterwards the init scripts will respect configured limits.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_13_-_Configuration_-_D_-_Configuration_Storage_Options.asciidoc",
"content": "[[confChanges5x]]\n= Configuration Storage Options in Tigase\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-01-06 20:22\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nThe whole configuration framework for the Tigase server has been redesigned and rewritten for v5.1. This was done to cleanup all the configuration code and logic as well as extend the current functionality to allow for configuration storage in different kinds of repositories - memory, file, database, ...\n\nAlthough this article is titled configuration changes, version 5.x still follows our policy about backward compatibility. So the changes could be considered extensions rather than complete overhauls.\n\nThere is however one change which can affect a few users. Those who use the server and worked with it's configuration remember the mess and confusion related to duality in the server configuration - the +init.properties+ file and +tigase.xml+ file. This is now over.\n\n== Default Behavior\n\nBy default Tigase server loads tigase.conf.ConfigurationCache class which stores the whole configuration in memory. Please note that the +init.properties+ file with initial settings is always loaded if it is available at the given location and all settings in this file work exactly as before. For more details, please refer to the online documentation.\n\nA couple of times 'initial configuration' and 'whole configuration' were mentioned. What is this about, what is the difference?\n\nThe 'initial configuration' are startup settings provided by the user in the +init.properties+ file. Most of the server elements use far more configuration parameters which are set to sensible default values if they are not provided by the user. The configuration framework in Tigase server always keeps the complete configuration of all active elements. This is implemented in such a way to make it possible to present currently used settings to the end-users or administrators and allow them to change the server parameters during runtime.\n\n== Storing Configuration in SQL Database\n\nThere is one more configuration storage implemented right now. It allows you to store the server settings in the SQL database. In most cases this is not quite useful, just opposite, very inconvenient.\nHowever. there is at least one case where you really want to keep the server configuration in the SQL database. This is in the cluster mode. If you have a Tigase cluster system of 10 or more nodes it is much easier to keep the configuration in a single central location and manage it from there, rather then go to every single machine every time you want to change some settings.\nYou can even change any settings for all cluster nodes with a single database query.\n\nYou set the SQL storage the same way as you set it for XML file. However, there is one more parameter as you have to provide also database connection string for the server so it knows where to connect to for the settings:\n\n. Parameters in init.properties file:\n+\n[source,bash]\n-----\n--tigase-config-repo-class=tigase.conf.ConfigSQLRepository\n--tigase-config-repo-uri=connection-uri\n-----\n. Alternatively you can provide system properties to the JVM:\n+\n[source,bash]\n-----\n-Dtigase-config-repo-class=tigase.conf.ConfigSQLRepository\n-Dtigase-config-repo-uri=connection-uri\n-----\n\nPlease note, the current implementation for the SQL storage automatically creates the tables necessary to operate if it does not exist. So you don't have to worry about the schema, but you should make sure that the database user used by the Tigase has permissions to create a table.\n\nConfiguration is stored in table with following schema:\n\n[source,sql]\n-----\ncreate table tigase_configuration (\n-- The component name by which the configuration parameter\n-- is used.\n component_name varchar(127) NOT NULL,\n\n-- The configuration property key name or identifier.\n key_name varchar(127) NOT NULL,\n\n-- The configuration property value\n value varchar(8191) NOT NULL,\n\n-- The cluster node by which the configuration property is read,\n-- if empty it will be read by all cluster nodes.\n cluster_node varchar(255) NOT NULL DEFAULT '',\n\n-- Additional, secondary identifier for the configuration property.\n-- The configuration can be organized in a hierarchical way to allow\n-- multiple occurrences of the same property name for a single\n-- component, for example you can have the same property for\n-- different tcp/ip ports set to a different value:\n-- c2s/5222/port_type=plain\n-- c2s/5223/port_type=ssl\n-- the port number is a secondary identifier.\n key_node varchar(127) NOT NULL DEFAULT '',\n\n-- Not currently used. In future it will be used to distinguish between\n-- different kind of properties (initial settings, defaults, updated by\n-- user, etc...)\n flag varchar(32) NOT NULL DEFAULT 'DEFAULT',\n\n-- The system detects basic Java types and stores information about\n-- the property type, when the property is read the original property\n-- type is restored and provided to the component without need for\n-- a parsing or conversion.\n value_type varchar(8) NOT NULL DEFAULT 'S',\n\n-- It is not currently used. In the future it will be used to reload\n-- settings changed in last, defined period of time. Basically, the\n-- system can automatically check the configuration database to\n-- see whether some properties have been updated, then reload\n-- them and apply automatically.\n last_update timestamp,\n\nprimary key(cluster_node, component_name, key_node,\n key_node, flag));\n-----\n\n== Reverting To the Old Behavior\n\nWhile using the +tigase.xml+ file is still possible and the old behavior can be preserved, it is now disabled by default. By default the Tigase server reads only +init.properties+ file with initial settings and stores all the complete configuration in memory only.\n\nThe +init.properties+ works exactly as before and all old parameters are still working exactly as before. The only difference is the lack of the tigase.xml which is not created or read by default if it is present. The main advantage is that you don't have to remove it each time you change something in the +init.properties+ to pick up new settings.\n\nFirstly we will go into how to re-enable the server to check and use the +tigase.xml+ file to retain functionality with older settings. This is actually very simple to accomplish. The Tigase server now, offers pluggable repository support. This means that you can easily extend current functionality with a different configuration storage by writing own class which reads and writes configuration parameters.\n\nBy default class +tigase.conf.ConfigurationCache+ is loaded which stores configuration in memory only.\n\nPlease note, the +init.properties+ file is always read if it exists at a given location.\n\nTo revert to the old behavior you just need to pass a parameter to Tigase server with a class name which is responsible for keeping server parameters in the old XML file. You can do it in two ways:\n\n. Add a parameter to init.properties file:\n+\n[source,bash]\n-----\n--tigase-config-repo-class=tigase.conf.ConfigXMLRepository\n-----\n. Or you can pass a system property to the JVM at the startup time:\n+\n[source,bash]\n-----\n-Dtigase-config-repo-class=tigase.conf.ConfigXMLRepository\n-----\n\n== Going Further\n\nAs the configuration mechanism in the Tigase server offers pluggable storage engines, you can easily write your own engine by implementing the interface: +tigase.conf.ConfigRepositoryIfc+ or by extending one of current implementations.\n\nThe whole configuration framework is pluggable and you can replace it completely if it does not suit you well enough. Your implementation has to extend +tigase.conf.ConfiguratorAbstract+ class and can be set using JVM system property (as this is configuration framework you can't do this via any configuration system):\n\n[source,sh]\n-----\n-Dtigase-configurator=tigase.conf.Configurator\n-----\n\nThe example above shows the parameter set to the default configuration framework.\n\n== Message Router Implementation is Configurable Too\n\nThe Message router component was the only component which was fixed to the Tigase instance. In theory it could always have been replaced but in practice there was no way of doing it as that was the first element loaded at startup.\n\nNow Tigase message router implementation can be easily replaced to and it can be made a configurable option if needed.\n\nAt the server startup time the code creates configurator and calls method: +getMessageRouterClassName()+ which by default returns class: +tigase.server.MessageRouter+. You can extend the configurator and provide any different class name instead which implements required interfaces. You can even make it configureable as it is no longer tied to the server instance.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_13_-_Configuration_-_E_-_JVM_settings.asciidoc",
"content": "[[jvm_settings]]\n= JVM settings and recommendations\n:author: Daniel Wisnewski \n:version: v1.0, June 2016.\n:date: 2016-06-02\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nTigase configuration file `tigase.conf` (described in more detail in <>) mentioned a couple of environmental variables which are related to the operation of the JVM. In this guide we would like to expound on those configuration options and provide hints for the optimal settings.\n\nSettings included in the `etc/tigase.conf` are as follows:\n\n[source, bash]\n----\n#GC=\"-XX:+UseBiasedLocking -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:NewRatio=2 -XX:+CMSIncrementalMode -XX:-ReduceInitialCardMarks -XX:CMSInitiatingOccupancyFraction=70 -XX:+UseCMSInitiatingOccupancyOnly\"\n#EX=\"-XX:+OptimizeStringConcat -XX:+DoEscapeAnalysis -XX:+UseNUMA\"\n\n#GC_DEBUG=\" -XX:+PrintTenuringDistribution -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -Xloggc:logs/jvm.log -verbose:gc \"\n\n#PRODUCTION_HEAP_SETTINGS=\" -Xms5G -Xmx5G \" # heap memory settings must be adjusted on per deployment-base!\nJAVA_OPTIONS=\"${GC} ${GC_DEBUG} ${EX} ${ENC} ${DRV} ${JMX_REMOTE_IP} -server ${PRODUCTION_HEAP_SETTINGS} ${DNS_RESOLVER} ${INTERNAL_IP} ${EXTERNAL_IP} -XX:MaxDirectMemorySize=128m \"\n----\n\nAnd while this file utilizes bash variables, JVM configuration options can be used in the same manner on all operating systems.\n\nThe guide will consists of two main parts - memory settings and Garbage Collector tweaks descriptions and hints.\n\nWe recommend using `-server` JVM parameter in all cases.\n\n== Heap Sizing\n\nFor the non-production deployments (development or stating environments) we recommend using default memory settings of the JVM (which depends on the underlaying operating system), which result i automatic memory allocation and, by the rule of thumb - are the safest in such environments.\n\nFor the production environments we recommend a fixed size HEAP - both initial and maximum size, which can be set with (respectively)`-Xms` and `-Xmx` JVM flags - ideally to the same value (which should be roughtly 95% of the available memory, if Tigase will be the only service on the machine) to avoid allocation and deallocation.\n\nFor convenience it's possible to uncomment line with `PRODUCTION_HEAP_SETTINGS` and adjust parameters accordingly.\n\n== GC settings\n\nLet's start with stating that there is no \"one to rule them all\" - each deployment and use-case is different, however we will try to give a couple of pointers and recommendations proceed with short introduction to GC itself.\n\nXMPP is quite specific in terms of memory allocation - short-lived objects (various types of stanzas) usually exceed number of long-lived objects (user connections and related data). This is important bit of information in the context of how usually JVM HEAP is organised and how Garbage Collector works. On the most basic level Heap is separated into couple of regions:\n\n=== Generations\n\n* *Young Generation*, which is further divided in to:\n** *Eden* - the region when the objects are usually allocated when they are created;\n** *Survivor Spaces* - (_to_ and _from_ - one of which is always empty) - responsible for storing all live object remaining after collecting *Young Generation* (process is repeated several times until objects are finally considered _old enough_);\n* *Old Generation* - (_Tenured Space_) - responsible for live objects remaining after running GC on *Survivor Spaces* - those would be _long-lived_ objects (usually user connections and associated data);\n\n=== Minor, Major and Full GC - optimizing\n\nGeneral thinking suggests that:\n* *Minor GC* cleans Young generation;\n* *Major GC* cleans Tenured space;\n* *Full GC* cleans all heap.\n\nHowever, while we can certainly state that Minor GC cleans Young generation it's a bit more difficult to differentiate Major and Full GC, especially considering that Major GC can be quite often triggered by Minor GC and some garbage collectors can perform cleaning concurrently. Instead of focusing of distinguishing phases one should pay closer attention to actual operations of Garbage Collector itself - uncommenting the line `GC_DEBUG=\" -XX:+PrintTenuringDistribution -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -Xloggc:logs/jvm.log -verbose:gc \"` in `etc/tigase.conf` (or adding same properties to the java commandline) and subsequently analyzing the results should prove more helpful. In addition monitoring GC operation using for example VisualVM (with VisualGC plugin) will also be helpful.\n\n=== Settings for XMPP\n\nIdeally we should limit both number of GC pauses as well as their duration. After running rather tests following conclusions were made:\n\n* Garbage Collection is the faster the more dead objects occupies given space, therefore on high-traffic installation it’s better to have rather large YoungGen resulting in lower promotion of the objects to the OldGen;\n* with JVM8 default sizing of Young / Old generation changed, even tho NewRatio is still defaulting to “2” - setting it explicitly to \"2\" brought back previous sizing;\n* Concurrent Mark and Sweep (CMS) enabled (applies to Tenured space only) with explicit configuration of NewRatio set to default value of 2 (i.e. `-XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:NewRatio=2`) in general behaves best;\n* For small installations (few core CPU, less memory) with low traffic default Parallel collector may be a better solution;\n* Using Heap size adjusted to the actual usage is better as the larger the heap the larger are spaces over which collection needs to be performed thus resulting in longer pauses; in case of huge heaps G1 collector may be better solution to avoid longer pauses;\n\nConsidering all of the above using following options should be a good starting point toward further optimizing of Garbage Collection:\n\n`GC=\"-XX:+UseBiasedLocking -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+CMSIncrementalMode -XX:-ReduceInitialCardMarks -XX:CMSInitiatingOccupancyFraction=70 -XX:+UseCMSInitiatingOccupancyOnly\"`\n\n=== GC settings worth considering\n\nIn addition to the general recommendation to use CMS collector, following options (or changes to the options) may be worth considering:\n\n* `-XX:NewRatio=2` - defines the ratio between the young and tenured generation is 1:2. In other words, the combined size of the eden and survivor spaces will be one-third of the total heap size. The parameters NewSize and MaxNewSize bound the young generation size from below and above. Setting these to the same value fixes the young generation, just as setting -Xms and -Xmx to the same value fixes the total heap size.\n* `-XX:CMSInitiatingOccupancyFraction=percent` - sets the percentage of the old generation occupancy (0 to 100) at which to start a CMS collection cycle.\n* `-XX:+UseCMSInitiatingOccupancyOnly` - instructs the JVM not to base its decision when to start a CMS cycle on run time statistics but instead it uses the value of CMSInitiatingOccupancyFraction for every CMS cycle.\n* `-XX:ParallelGCThreads=x` - sets the number of threads used for parallel garbage collection in the young and old generations. The default value depends on the number of CPUs available to the JVM. If the Tigase JMV is the only one running on the installation default value is recommended.\n* `-XX:ConcGCThreads=x` - sets the number of threads used for concurrent GC. The default value depends on the number of CPUs available to the JVM. If the Tigase JMV is the only one running on the installation default value is recommended.\n* `-XX:+UseBiasedLocking` and `-XX:+DoEscapeAnalysis` - designed to eliminate locking overhead, however their effect on performance is unpredictable therefore testing is required; reduced locking should improve concurrency and, on current multi-core hardware, improve throughput.\n* `-XX:+OptimizeStringConcat` - enables the optimization of String concatenation operations. This option is enabled by default.\n* `-XX:+UseNUMA` - enables performance optimization of an application on a machine with nonuniform memory architecture (NUMA - most modern computers are based on NUMA architecture) by increasing the application's use of lower latency memory. By default, this option is disabled and no optimization for NUMA is made. The option is only available when the parallel garbage collector is used (-XX:+UseParallelGC).\n* `-XX:-UseCompressedOops` -- disables the use of compressed pointers. By default, this option is enabled, and compressed pointers are used when Java heap sizes are less than 32 GB. When this option is enabled, object references are represented as 32-bit offsets instead of 64-bit pointers, which typically increases performance when running the application with Java heap sizes less than 32 GB. This option works only for 64-bit JVMs.\n\n== What to use with Machine x, y, z?\n\n=== Server class machine (non-VM), > 16GB, >= 8 core CPU\n\nFor such setup enabling CMS garbage collector is recommended. Depending on the traffic usage and particular use-case adjusting NewRatio may be needed. Adjusting Xms and Xms sizes for actual available memory is needed (or better yet, for the actual traffic!). Following should be used:\n[source, bash]\n----\nGC=\"-XX:+UseBiasedLocking -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:NewRatio=2 -XX:+CMSIncrementalMode -XX:-ReduceInitialCardMarks -XX:CMSInitiatingOccupancyFraction=70 -XX:+UseCMSInitiatingOccupancyOnly\"\nEX=\"-XX:+OptimizeStringConcat -XX:+DoEscapeAnalysis -XX:+UseNUMA\"\n\n#GC_DEBUG=\" -XX:+PrintTenuringDistribution -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -Xloggc:logs/jvm.log -verbose:gc \"\n\nPRODUCTION_HEAP_SETTINGS=\" -Xms15G -Xmx15G \" # heap memory settings must be adjusted on per deployment-base!\nJAVA_OPTIONS=\"${GC} ${GC_DEBUG} ${EX} ${ENC} ${DRV} ${JMX_REMOTE_IP} -server ${PRODUCTION_HEAP_SETTINGS} ${DNS_RESOLVER} ${INTERNAL_IP} ${EXTERNAL_IP} -XX:MaxDirectMemorySize=128m \"\n----\n\nFor installation with lot of available memory and intention to utilize it all, using G1GC collector may be a better idea :\n[source, bash]\n----\nGC=\"-XX:+UseG1GC -XX:ConcGCThreads=4 -XX:G1HeapRegionSize=2 -XX:InitiatingHeapOccupancyPercent=35 -XX:MaxGCPauseMillis=100\"\nEX=\"-XX:+OptimizeStringConcat -XX:+DoEscapeAnalysis -XX:+UseNUMA\"\n\n#GC_DEBUG=\" -XX:+PrintTenuringDistribution -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -Xloggc:logs/jvm.log -verbose:gc \"\n\nPRODUCTION_HEAP_SETTINGS=\" -Xms60G -Xmx60G \" # heap memory settings must be adjusted on per deployment-base!\nJAVA_OPTIONS=\"${GC} ${GC_DEBUG} ${EX} ${ENC} ${DRV} ${JMX_REMOTE_IP} -server ${PRODUCTION_HEAP_SETTINGS} ${DNS_RESOLVER} ${INTERNAL_IP} ${EXTERNAL_IP} -XX:MaxDirectMemorySize=128m \"\n----\n\n=== VM machine, 8GB of RAM, 4 core CPU equivalent\n\nFor such setup enabling CMS garbage collector is also recommended. Depending on the traffic usage and particular use-case adjusting NewRatio may be needed (and configuring NewRatio is a must!). Adjusting Xms and Xms sizes for actual available memory is needed (or better yet, for the actual traffic!). Following should be used:\n[source, bash]\n----\nGC=\"-XX:+UseBiasedLocking -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:NewRatio=2 -XX:+CMSIncrementalMode -XX:-ReduceInitialCardMarks -XX:CMSInitiatingOccupancyFraction=70 -XX:+UseCMSInitiatingOccupancyOnly\"\nEX=\"-XX:+OptimizeStringConcat -XX:+DoEscapeAnalysis -XX:+UseNUMA\"\n\n#GC_DEBUG=\" -XX:+PrintTenuringDistribution -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -Xloggc:logs/jvm.log -verbose:gc \"\n\nPRODUCTION_HEAP_SETTINGS=\" -Xms7G -Xmx7G \" # heap memory settings must be adjusted on per deployment-base!\nJAVA_OPTIONS=\"${GC} ${GC_DEBUG} ${EX} ${ENC} ${DRV} ${JMX_REMOTE_IP} -server ${PRODUCTION_HEAP_SETTINGS} ${DNS_RESOLVER} ${INTERNAL_IP} ${EXTERNAL_IP} -XX:MaxDirectMemorySize=128m \"\n----\n\n=== VM machine with 4GB or less of RAM, and less than 4 core CPU equivalent\n\nSmall installations with limited resources could operate better with default (for JVM versions up to 8, which is the most current at the moment of the writing). Again - depending on the traffic usage and particular use-case adjusting NewRatio may be needed. Adjusting Xms and Xms sizes for actual available memory is recommended (or better yet, for the actual traffic!). Following should be used (i.e. `GC` line should be commented so the defaults will be used):\n[source, bash]\n----\n#GC=\"-XX:+UseBiasedLocking -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:NewRatio=2 -XX:+CMSIncrementalMode -XX:-ReduceInitialCardMarks -XX:CMSInitiatingOccupancyFraction=70 -XX:+UseCMSInitiatingOccupancyOnly\"\nEX=\"-XX:+OptimizeStringConcat -XX:+DoEscapeAnalysis -XX:+UseNUMA\"\n\n#GC_DEBUG=\" -XX:+PrintTenuringDistribution -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -Xloggc:logs/jvm.log -verbose:gc \"\n\nPRODUCTION_HEAP_SETTINGS=\" -Xms3G -Xmx3G \" # heap memory settings must be adjusted on per deployment-base!\nJAVA_OPTIONS=\"${GC} ${GC_DEBUG} ${EX} ${ENC} ${DRV} ${JMX_REMOTE_IP} -server ${PRODUCTION_HEAP_SETTINGS} ${DNS_RESOLVER} ${INTERNAL_IP} ${EXTERNAL_IP} -XX:MaxDirectMemorySize=128m \"\n----\n\n== Additional resources\n\n* https://docs.oracle.com/javase/8/docs/technotes/guides/vm/gctuning/sizing.html[Sizing the Generations]\n* http://www.c0t0d0s0.org/archives/6617-About-Java,-parallel-garbage-collection-and-processor-sets.html[About Java, parallel garbage collection and processor sets]\n* http://hiroshiyamauchi.blogspot.cl/2009/12/gc-threads.html[GC Threads]\n* https://github.com/chewiebug/GCViewer#readme[GCViewer readme]\n* http://docs.oracle.com/javase/7/docs/technotes/guides/vm/performance-enhancements-7.html[Java HotSpot™ Virtual Machine Performance Enhancements]\n* https://plumbr.eu/java-garbage-collection-handbook[Java Garbage Collection handbook]\n* Useful JVM Flags\n** https://blog.codecentric.de/en/2012/07/useful-jvm-flags-part-1-jvm-types-and-compiler-modes/[Part 1 - JVM Types and Compiler Modes]\n** https://blog.codecentric.de/en/2012/07/useful-jvm-flags-part-2-flag-categories-and-jit-compiler-diagnostics/[Part 2 - Flag Categories and JIT Compiler Diagnostics)]\n** https://blog.codecentric.de/en/2012/07/useful-jvm-flags-part-3-printing-all-xx-flags-and-their-values/[Part 3 - Printing all XX Flags and their Values]\n** https://blog.codecentric.de/en/2012/07/useful-jvm-flags-part-4-heap-tuning/[Part 4 - Heap Tuning]\n** https://blog.codecentric.de/en/2012/08/useful-jvm-flags-part-5-young-generation-garbage-collection/[Part 5 - Young Generation Garbage Collection]\n** https://blog.codecentric.de/en/2013/01/useful-jvm-flags-part-6-throughput-collector/[Part 6 - Throughput Collector]\n** https://blog.codecentric.de/en/2013/10/useful-jvm-flags-part-7-cms-collector/[Part 7 - CMS Collector]\n** https://blog.codecentric.de/en/2014/01/useful-jvm-flags-part-8-gc-logging/[Part 8 - GC Logging]\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_14_-_Security.asciidoc",
"content": "= Security\n:author: Daniel Wisnewski\n:version: v1.0 October, 2015\n:date: 2015-05-10 13:31\n\nThe articles here cover advanced security features built into to Tigase Server, and some options for adding your own levels of security.\n\n[[blockingCommand]]\n== XEP-0191 Support\n\nThe simplest security feature, however, inside an XMPP server is the ability to block users and JIDS. link:http://xmpp.org/extensions/xep-0191[XEP-0191] specifies the parameters of simple blocking without using privacy lists. Below is a breakdown and some sample commands you may find helpful.\nTo enable this feature, be sure the following is in your init.properties file:\n----\n--sm-plugins +urn:xmpp:blocking\n----\nIf you have other plugins running, then just add ++urn:blocking+ to the list to activate this feature.\n\n\nTo confirm if your installation of Tigase supports this feature, a quick disco#info of your server should reveal the following feature:\n-----\n\n-----\n\nBlocked users are stored on the server on a per-JID basis, so one user may only see his or her blocked JIDs. Lists of blocked JIDs will return as an IQ stanza with a list of fields. To retrieve the blocklist, the following command is issued:\n[source,xml]\n-----\n\n \n\n-----\nThe server responds:\n[source,xml]\n-----\n\n \n \n \n \n\n-----\n\nTo block a JID, a similar stanza to the one above is sent to the server with the items of the blocked JIDs you wish to add:\n[source,xml]\n-----\n\n \n \n \n\n-----\nThe server will then push an unavailable presence to blocked contacts. Communication between a contact that is blocked, and an entity that blocked it will result in a error:\n[source,xml]\n-----\n\n Hello, are you online?\n \n \n \n \n\n-----\n\nUnblocking a contact is just as easy as blocking, send an unblock stanza to the server:\n[source,xml]\n-----\n\n \n \n \n\n-----\nThe server will begin pushing presence information to unblocked contacts and resources so long as permissions have not changed between.\n\nYou may also opt to unblock all contacts and essentially clear out your blocked list using the following command:\n[source,xml]\n-----\n\n \n\n-----\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_15_-_Security_-_A_-_Server_Certificates.asciidoc",
"content": "[[ServerCertificates]]\n= Server Certificates\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 21:18\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\n\n- xref:certspem[Creating and Loading the Server Certificate in pem Files]\n- xref:startcomCertificate[Installing StartCom Certificate in Your Linux System]\n//- xref:keytoolKeystore[Server Certificate Using Keytool and Keystore]\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_16_-_Security_-_A_-_Server_Certificates_-_1_-_Creating_and_Loading_the_Server_Certificate_in_PEM_Files.asciidoc",
"content": "[[certspem]]\n= Creating and Loading the Server Certificate in pem Files\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 21:18\n:Revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\n== Server Certificates\n\nServer certificates are needed when you use secure socket connections - SSL/TLS.\n\nFor secure socket connection a proper certificate is needed. You can either generate your own self-signed certificate or obtain certificate from trusted third party organization.\n\nHere are steps how to obtain certificate from a trusted organization.\n\n=== Generating your Own Certificates\n\nSelf-signed certificates can be generated easily on a Linux system. Although it may not be considered a 'trusted' certificate authority, it can be useful to test server installations. *We do not recommend regular use of self-signed certificates*.\n\nNote that Tigase v5.0 and later can automatically create self signed PEM files if needed. However we will cover doing this process by hand.\n\nThis tutorial assumes you are running a Linux-based operating system with access to command shell, and the 'Openssl' package is installed on the system.\n\nThe process takes the following steps: +\n1. Create a local private key. This file ends with .key extension. It is recommended to create a new private key for the process. +\n2. Generate a certificate request. This file ends with the .csr extension and is the file sent to the Certificate Authority to be signed. +\n3. CA signs private key. This can be done by your own computer, but can also be done by private CAs for a fee. +\n4. Results are obtained from the CA. This is a .crt file which contains a separate public certificate. +\n5. Combine the .csr and .crt file into a unified .pem file. Tigase requires keys to be non-password protected PEM files. +\n\n.Generate local private key\n[source,sh]\n-----\nopenssl genrsa -out[domain.com.key] 1024\n-----\nThis command generates a private key using a 1024 bit RSA algorithm. -out designates the name of the file, in this case it will be *domain.com.key*. The exact name is not important, and the file will be created in whatever directory you are currently in.\n\n.Generate a certificate request:\n[source,sh]\n-----\nopenssl req -nodes -key domain.com.key -out domain.com.csr\n-----\nThis command generates a certificate request using the file specified after -key, and the result file will be domain.com.csr. You will be asked a series of questions to generate the request.\n\n[source,sh]\n-----\nCountry Name (2 letter code) [AU]:AU\nState or Province Name (full name) [Some-State]:Somestate\nLocality Name (eg, city) []:Your city name\nOrganization Name (eg, company) [Internet Widgits Pty Ltd]:Company name\nOrganizational Unit Name (eg, section) []:Department or any unit\nCommon Name (eg, YOUR name) []:*.yourdomain.com\nEmail Address []:your_email_address@somedomain.com\n\nPlease enter the following 'extra' attributes\nto be sent with your certificate request\nA challenge password []:\nAn optional company name []:\n-----\n\n.Sign the Certificate Request:\nNow the .csr file will be signed by a Certificate Authority. In this tutorial, we will be self-signging our certificate. This practice however is generally not recommended, and you will receive notifications that your certificate is not trusted. There are commercial offers from companies to sign your certificate from trusted sources. Please see the xref:OtherSources[Certificate From Other Providers] section for more information.\n[source,bash]\n-----\nopenssl x509 -req -days 365 -in domain.com.csr -signkey domain.com.key -out domain.com.crt\n-----\nThis command signs the certificate for 365 days and generates the domain.com.crt file. You can, of course use any number of days you like.\n\n.Generate PEM file\nYou should now have the following files in the working directory:\n..\\\ndomain.com.key\ndomain.com.csr\ndomain.com.crt\n\n[source,sh]\n-----\ncat yourdomain.com.crt yourdomain.com.key > yourdomain.com.pem\n-----\n\nIf the certificate is issued by third-party authority you will have to attach the certificate chain, that being certificate of the authority who has generated your certificate. You normally need to obtain certificates for your chain from the authority who has generated your certificate. For example, if you have a certificate from XMPP federation you need to download link:http://www.startssl.com/certs/ca.pem[StartCom root certificate] *and* link:http://www.startssl.com/certs/sub.class1.server.ca.pem[intermediate ICA certificate]. In such cases the pem file is created using following command:\n\n[source,sh]\n-----\ncat yourdomain.com.crt yourdomain.com.key sub.class1.xmpp.ca.crt ca.crt > yourdomain.com.pem\n-----\n\nThe result file should looks similar to:\n\n[source,sh]\n------\n-----BEGIN CERTIFICATE-----\nMIIG/TCCBeWgAwIBAgIDAOwZMA0GCSqGSIb3DQEBBQUAMIGMMQswCQYDVQQGEwJJ\n.\n.\n.\npSLqw/PmSLSmUNIr8yQnhy4=\n-----END CERTIFICATE-----\n-----BEGIN RSA PRIVATE KEY-----\nWW91J3JlIGtpZGRpbmchISEKSSBkb24ndCBzaG93IHlvdSBvdXIgcHJpdmF0ZSBr\n.\n.\n.\nZXkhISEhCkNyZWF0ZSB5b3VyIG93biA7KSA7KSA7KQo=\n-----END RSA PRIVATE KEY-----\n-----BEGIN CERTIFICATE-----\nMIIHyTCCBbGgAwIBAgIBATANBgkqhkiG9w0BAQUFADB9MQswCQYDVQQGEwJJTDEW\n.\n.\n.\nxV/stleh\n-----END CERTIFICATE-----\n------\n\nFor Tigase server as well as many other servers (Apache 2.x), the order is following; your domain certificate, your private key, authority issuing your certificate, root certificate.\n\n*Note! Tigase requires full certificate chain in PEM file (described above)! Different applications may require pem file with certificates and private key in different order. So the same file may not be necessarily used by other services like Web server or e-mail server. Currently, Tigase can automatically sort certificates in PEM file while loading it.*\n\n== Installing/Loading Certificate To the Tigase Server\n\nFrom version *3.1.0-b802* of Tigase server, installing and loading certificates is very easy. The server can load all certificates directly from *pem* files. You just need to create a separate pem file for each of your virtual domains and put the file in a directory accessible by the server. Tigase server can automatically load all *pem* files found in given directory. By default, and to make things easy, we recommend the +Tigase/certs+ directory.\n\n[[OtherSources]]\n== Certificate From Other Providers\n\nThere is number of certificate providers offering certificates either for free or for money. You can use any of them, however you have to be aware that sometimes certificates might not be recognized by all XMPP servers, especially if it's one from a new provider. Here is an example list of providers:\n\n- link:https://www.cacert.org/[CAcert] - free certificates with an excellent Web GUI for managing generated certificates and identities.\n- link:https://www.startssl.com/[StartCom] - both free and paid certificates, class 1, 2 and 3. Very good GUI for managing certificates and identities.\n- link:https://www.verisign.com/[Verisign] - very expensive certificates comparing to above provides but the provider is recognized by everybody. If you have a certificate from Verisign you can be sure it is identified as a valid certificate.\n- link:http://www.comodo.com/business-security/digital-certificates/ssl-certificates.php[Comodo Certificate Authority] offers different kind of commercial certificates\n\nTo obtain certificate from a third party authority you have to go to its website and request the certificate using certificate request generated above. I cannot provide any instructions for this as each of the providers listed have different requirements and interfaces.\n\n[[onecertmultipledomain]]\n== Using one certificate for multiple domains\nBy default, each virtual hosts will require it's own certificate. However, if you choose to use one certificate for all virtual hosts, Tigase supports that option.\nFor example, if you have host1.example.net, host2.example.net, and host3.example.net each vhost will need some configuration:\n[source,properties]\n-----\nbasic-conf/virtual-hosts-cert-host1.example.net=/home/tigase/certs/host1.pem\nbasic-conf/virtual-hosts-cert-host2.example.net=/home/tigase/certs/host2.pem\nbasic-conf/virtual-hosts-cert-host3.example.net=/home/tigase/certs/host3.pem\n-----\nThis may be time consuming if you have many Vhosts, or expect to generate many more. The good news is, now one certificate can be used for ALL Vhosts using the following configuration line:\n[source,properties]\n-----\nbasic-conf/virt-hosts-cert-*.example.net=/home/tigase/certs/certificate.pem\n-----\n\nNow any Vhosts created will use the same certificate located at /home/tigase/certs/certificate.pem. *NOTE:* This is an all or nothing option, if you wish to customize each Vhost, you will need to do so individually.\n\n\n== Tigase Server Configuration for 5.1.0 and older\n\nStarting from version 5.1.0 and newer it's not needed to use external libraries nor extra configuration in the init.properties file. With this version Tigase uses, loaded by default thus no need to configure it, following class:\n\n[source,bash]\n-----\n--ssl-container-class=tigase.io.SSLContextContainer\n-----\n\nOlder versions require different configurations. In order to be able to load server certificates directly from *pem* files you need to have *tigase-extras* package installed in your server *libs/* directory in version at least *0.1.0*. If you use a Tigase server binary package other than *mini*, this library is included by default. If you haven't changed anything in your XML configuration file, put following line in your +initial.properties+ file:\n\n[source,bash]\n-----\n--ssl-container-class=tigase.extras.io.PEMSSLContextContainer\n-----\n\nCopy all your *pem* files with certificates into certs/ subdirectory in Tigase server installation, stop the server, remove XML configuration file and start the server. XML configuration will be automatically regenerated with the new SSLContainer used by all components and all certificates will be automatically loaded.\n\nIf you have changed your XML configuration file, and do not want to lose those changes, you will now have to manually change the existing SSLContainer class with the new one. Just replace all occurrences of the default SSLContainer - tigase.io.SSLContextContainer with the new - tigase.extras.io.PEMSSLContextContainer, copy all your *pem* files with certificates into certs/ subdirectory in Tigase server installation and restart the server.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_17_-_Security_-_A_-_Server_Certificates_-_2_-_Installing_StartCom_Certificate_in_your_Linux_System.asciidoc",
"content": "[[startcomCertificate]]\n= Installing StartCom Certificate in Your Linux System\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 21:18\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nThe third party authority for free XMPP server certificates is link:http://cert.startcom.org/[Startcom]. Startcom root certificates are not normally known to your system as a valid a certificate and appear as a self-signed certificate.\n\nTo make it known to your system as valid you will have to install it in your system.\n\nIn any case on any operating system, you have to download the certificate from the issuer link:http://cert.startcom.org/?lang=en&app=110[web site].\n\n== Gentoo Linux\n\n. Copy downloaded ca.crt file to /etc/ssl/certs/starcom_ca.crt file.\n. Run command:\n+\n[source,sh]\n-----\nupdate-ca-certificates\n-----\n\nAll done. To test it, run following command:\n\n[source,sh]\n-----\nopenssl s_client -connect tigase.org:5223 -CApath /etc/ssl/certs\n-----\n\nScroll the output up and look for something like:\n\n[source,bash]\n-----\nverify return:1\n-----\n\nWhich means certificate verification was successful. If you find however:\n\n[source,bash]\n-----\nverify return:0\n-----\n\nLook one line up for an error message which may look like this:\n\n[source,bash]\n-----\nverify error:num=19:self signed certificate in certificate chain\n-----\n\nWhich means the root certificate is still not recognized in your system.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_18_-_Security_-_A_-_Server_Certificates_-_3_-_Server_Certificate_Using_Keytool_and_Keystore.asciidoc",
"content": "[[keytoolKeystore]]\n= Server Certificate Using Keytool and Keystore\n:author: Bartosz Malkowski \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 21:18\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nTo allow secure connections through SSL or TLS channel you need a SSL certificate.\n\nThe main purpose of SSL certificate is to provide connecting entity with proof of identity of your server. A Significant role in proving the identity of your server is played by a trusted third party - usually the issuer of the certificate.\n\nCertificate issued by trusted third parties usually come with a cost. However, you can also use self signed certificate which works just as well. The downside is it gives an authentication warning on client software upon connection.\n\nTigase server binary package and source repositories contain so-called \"dummy\" certificates which do not refer to any real site name. This certificate is temporary and should be used only for initial testing of your server. It should be replaced with either a self signed certificate or one issued by trusted third party organization as soon as possible.\n\nHere are instructions how to install certificates for Tigase server.\n\n_Please note! You must use the *keytool* program included in JDK-1.6 or later. The utility included in earlier versions can not import third party signed certificates correctly._\n\n== Self Signed Certificate\n\nIf you don't have a third party signed certificate, you should generate a self-signed certificate.\n\nSome XMPP clients don't work correctly with DSA keys, so we need to use RSA algorithm for generation. To generate private and public keypair, you should use keytool with the following commands:\n\n[source,sh]\n-----\nkeytool -genkey -alias yourdomain -keystore rsa-keystore \\\n -keyalg RSA -sigalg MD5withRSA\n-----\n\nWhere +yourdomain+ is a domain part of _JIDs_ on your _XMPP_ server. If you want to have TLS support for virtual domains, you have to create certificate for each virtual domain. If you have just one domain, or for some reason you have to use one certificate for all domains, use +default+ as an alias.\n\nNow, enter the password to protect the keystore:\n\n[source,sh]\n-----\nEnter keystore password: 123456\n-----\n\nThe keytool will ask several questions about the certificate data. First question is very important! You must enter the hostname of your XMPP server!!\n\n[source,sh]\n-----\nWhat is your first and last name?\n [Unknown]: jabber.myserver.org\nWhat is the name of your organizational unit?\n [Unknown]:\nWhat is the name of your organization?\n [Unknown]:\nWhat is the name of your City or Locality?\n [Unknown]:\nWhat is the name of your State or Province?\n [Unknown]:\nWhat is the two-letter country code for this unit?\n [Unknown]:\nIs CN=jabber.myserver.org, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown correct?\n [no]: yes\n-----\n\nIn last step you can enter a new password for the certificate key. At the moment different passwords for both keystore and keys are not supported so you must have the same passwords for each.\n\n[source,sh]\n-----\nEnter key password for \n (RETURN if same as keystore password):\n-----\n\nNow you have to copy the rsa-keystore file to directory certs/ in your tigase server installation directory. The file may be installed in different location, but then corrections to config file are required. Refer to xref:manualconfig[manual configuration] for details.\n\n== Certificate from Certificate Authority\n\nIf you don't have third-party signed certificate yet but you want to have one, you could obtain it from link:http://www.cacert.org/[cacert.org] for free.\n\nFirst, you have to generate a Certificate Request using keytool:\n\n[source,sh]\n-----\nkeytool -certreq -alias yourdomain -keystore rsa-keystore\n-----\n\nWhere +yourdomain+ is a domain name for which this certificate is generated. If you need support for multiple virtual domains, you need to have certificate for each domain separately and assign proper alias to the certificates. If you have just one domain or for some reason you want to use one certificate use +default+ as an alias for all domains.\n\nKeytool generates the request:\n\n[source,bash]\n------\n-----BEGIN NEW CERTIFICATE REQUEST-----\nMIIBrzCCARgCAQAwbzEQMA4GA1UEBhMHVW5rbm93bjEQMA4GA1UECBMHVW5rbm93bjEQMA4GA1UE\nBxMHVW5rbm93bjEQMA4GA1UEChMHVW5rbm93bjEQMA4GA1UECxMHVW5rbm93bjETMBEGA1UEAxMK\nc2VydmVyLm9yZzCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAs73Y70725OcG0j4kpCfDX59e\nqhz2gdGOO0LyMO7rm4m+ZCenq8E88M0RJ8/LV/7q0mtOAzbI8dtXZnmJ74xihCH8ZTFpVDMyFWgk\nWCj2kz+IUD9vWt6i1UepSkr1a/jYmVMN3RSaoS+j+QLBsJ4rWeOHgIdbiF5tnMhoZMXU//0CAwEA\nAaAAMA0GCSqGSIb3DQEBBAUAA4GBAHY5r9rftqiKESbbkCcfVhvnUqN4aMTC8/zXWwzBX8guC0kd\nH46+p6eizwJg6p+h6rqShG2OqXCPrJzO3buHr1jEWRTlB8l5CM53L/xq61nYuaSf5R7Vv/RX2+aD\nJyoBqYIoSUED0+Sjhej0SUPTOdpA/bfnqdfdtckday4vsLPC\n-----END NEW CERTIFICATE REQUEST-----\n------\n\nNow send the request to your Certificate Authority. The CA issues a signed certificate and sends it to you. It may may look like:\n\n[source,bash]\n------\n-----BEGIN CERTIFICATE-----\nMIICUDCCAbkCBEUqAK0wDQYJKoZIhvcNAQEEBQAwbzEQMA4GA1UEBhMHVW5rbm93bjEQMA4GA1UE\nCBMHVW5rbm93bjEQMA4GA1UEBxMHVW5rbm93bjEQMA4GA1UEChMHVW5rbm93bjEQMA4GA1UECxMH\nVW5rbm93bjETMBEGA1UEAxMKc2VydmVyLm9yZzAeFw0wNjEwMDkwNzU2MjlaFw0wNzAxMDcwNzU2\nMjlaMG8xEDAOBgNVBAYTB1Vua25vd24xEDAOBgNVBAgTB1Vua25vd24xEDAOBgNVBAcTB1Vua25v\nd24xEDAOBgNVBAoTB1Vua25vd24xEDAOBgNVBAsTB1Vua25vd24xEzARBgNVBAMTCnNlcnZlci5v\ncmcwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALO92O9O9uTnBtI+JKQnw1+fXqoc9oHRjjtC\n8jDu65uJvmQnp6vBPPDNESfPy1f+6tJrTgM2yPHbV2Z5ie+MYoQh/GUxaVQzMhVoJFgo9pM/iFA/\nb1reotVHqUpK9Wv42JlTDd0UmqEvo/kCwbCeK1njh4CHW4hebZzIaGTF1P/9AgMBAAEwDQYJKoZI\nhvcNAQEEBQADgYEAQqRPdkbc/pdDcPIWOThn2XPp0gitPkXq89ZM1mb0Pib1OISj9ekjqhEZz0UA\ncI6g1XttpY6hKi6Gg+mRbwiHNVebkDLamE2UIcVJ1wBtowYeOcV1CcLnlj91ScMKNhfD5ebQL+be\ntWWrJX3ep+80kF/NdVkc7htGOhLebopp8SQ=\n-----END CERTIFICATE-----\n------\n\nSave the Certificate to a disk file.\n\nNow that you have third-party signed certificate, you have to import it with *keytool* program to server certificate storage.\n\n_Note! You must have a root CA certificate!!! You can download the cert from CA (ie.: root.crt) and import:_\n\n[source,sh]\n-----\nkeytool -import -keystore rsa-keystore -file root.crt \\\n -alias root\n-----\n\nLast step is import the Certificate to your keystore:\n\n[source,sh]\n-----\nkeytool -import -alias yourdomain -keystore rsa-keystore \\\n -file your-certificate.cer\n-----\n\nWhere +yourdomain+ is a domain name for which this certificate has been generated. If you need support for multiple virtual domains you have to import certificate for each domain separately and assign proper alias to each certificate. If you have just one domain or for some reason you want to use one certificate use +default+ as an alias for all domains.\n\nIt's also good to import root CA certificate to this keystore. //You must find it on CA website.\n\n[source,sh]\n-----\nkeytool -import -keystore rsa-keystore -file rootCA.cer\n-----\n\nIt may also generate certreq using +openssl+ for use in other services like WWW. In such a case you may have your private key and certificate in separate files. Let's say private key is in ssl.key file and certificate is in +ssl.crt+ file. To merge them into a single file together use following command:\n\n[source,sh]\n-----\nopenssl pkcs12 -export -inkey ssl.key -in ssl.crt \\\n -out mycert.pfx -name \"default\"\n-----\n\nNow you can load certificate with a private key to your keystore:\n\n[source,sh]\n-----\nkeytool -importkeystore -srckeystore mycert.pfx \\\n -srcstoretype pkcs12 -destkeystore rsa-keystore \\\n -srcalias default -destalias yourdomain \\\n -destkeypass your_keystore_pass\n-----\n\n*Note!* _Please note -destkeypass parametr. Your keys password must be the same as keystore password. Otherwise it won't work._\n\nNow you have to copy file +rsa-keystore+ to directory +certs/+ in your tigase server installation. The file could also be installed in different location but then corrections to the config file are required. Refer to configuration documentation for details.\n\nFinally, don't forget to modify tigase server configuration file and set proper password for your keystore.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_19_-_Security_-_B_-_Authentication_Connectors.asciidoc",
"content": "[[customAuthentication]]\n= Custom Authentication Connectors\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 21:18\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nThis article presents configuration options available to the administrator and describe how to set Tigase server up to use user accounts data from a different database.\n\nThe first thing to know is that Tigase server always opens 2 separate connections to the database. One connection is used for user login data and the other is for all other user data like the user roster, vCard, private data storage, privacy lists and so on...\n\nIn this article we still assume that Tigase server keeps user data in it's own database and only login data is retrieved from the external database.\n\nAt the moment Tigase offers following authentication connectors:\n\n- 'mysql', 'pgsql', 'derby' - standard authentication connector used to load user login data from the main user database used by the Tigase server. In fact the same physical implementation is used for all JDBC databases.\n- 'drupal' - is the authentication connector used to integrate the Tigase server with link:http://drupal.org/[Drupal CMS].\n- 'libresource' - is the authentication connector used to integrate the Tigase server with link:http://dev.libresource.org/[Libresource Collaboration platform].\n- 'tigase-auth' - is the authentication connector which can be used with any database. It executes stored procedures to perform all actions. Therefore it is a very convenient way to integrate the server with an external database if you don't want to expose the database structure. You just have to provide a set of stored procedures in the database. While implementing all stored procedures expected by the server might be a bit of work it allows you to hide the database structure and change the SP implementation at any time. You can add more actions on user login/logout without restarting or touching the server. And the configuration on the server side is very simple. For detailed description of this implementation please refer to xref:tigaseAuthConnector[Tigase Auth documentation].\n- 'tigase-custom' - is the authentication connector which can be used with any database. Unlike the 'tigase-auth' connector it allows you to define SQL queries in the configuration file. The advantage of this implementation is that you don't have to touch your database. You can use either simple plain SQL queries or stored procedures. The configuration is more difficult as you have to enter carefully all SQL queries in the config file and changing the query usually involves restarting the server. For more details about this implementation and all configuration parameters please refer to xref:custonAuthConnector[Tigase Custom Auth documentation].\n\nAs always the simplest way to configure the server is through the +init.properties file+. In the article describing this file you can find long list with all available options and all details how to handle it. For the authentication connector setup however we only need 2 options:\n\n- '--auth-db = connector'\n- '--auth-db-uri = database connection url'\n\nIf you happen to keep the user data in the same database as user authentication data you can even skip the second parameter as Tigase automatically assumes settings from the '--user-db-uri' it '--auth-db-uri' is missing.\n\n'--auth-db-uri' stored a standard JDBC connection URL and is exactly the same as for all other settings. For example if you store authentication data in a 'drupal' database on 'localhost' the URL might look like:\n\n[source,bash]\n-----\n--auth-db-uri = jdbc:mysql://localhost/drupal?user=user&password=passwd\n-----\n\n'--auth-db' stored just a connector name or connector implementation class. For convenience Tigase has predefined short names for the most common connectors but you can always use the class name if you know it. You have to use a class name if you want to attach your own authentication connector. The following 2 settings are equal:\n\n[source,bash]\n-----\n--auth-db = tigase-auth\n-----\n\n[source,bash]\n-----\n--auth-db = tigase.db.jdbc.TigaseAuth\n-----\n\nIn the same exact way you can setup connector for any different database type:\n\n[source,bash]\n-----\n--auth-db = drupal\n-----\n\n[source,bash]\n-----\n--auth-db = tigase-custom\n-----\n\nYou can normally skip configuring connectors for the default Tigase database format: 'mysql', 'pgsql' and 'derby' as they are applied automatically if the parameter is missing.\n\nOne more important thing to know is that you will have to modify '--user-db-uri' if you use a custom authentication connector. This is because if you retrieve user login data from the external database this external database is usually managed by an external system. User accounts are added without notifying Tigase server. Then, when the user logs in and tries to retrieve the user roster, the server can not find such a user in the roster database.\n\nTo keep user accounts in sync between the authentication database and the main user database you have to add following option to the end of the database connection URL: 'autoCreateUser=true'.\n\nFor example:\n\n[source,bash]\n-----\n--user-db-uri=jdbc:mysql://localhost/tigasedb?user=nobody&password=pass&autoCreateUser=true\n-----\n\nIf you are interested in even further customizing your authentication connector by writing your own queries or stored procedures, please have a look at 2 following guides:\n\n- xref:tigaseAuthConnector[Tigase Auth guide]\n- xref:custonAuthConnector[Tigase Custom Auth guide]\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_20_-_Security_-_B_-_Authentication_Connectors_-_1_-_Tigase_Auth_Connector.asciidoc",
"content": "[[tigaseAuthConnector]]\n= Tigase Auth Connector\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 21:18\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nThe Tigase Auth connector with shortcut name: *tigase-auth* is implemented in the class: link:https://projects.tigase.org/projects/tigase-server/repository/changes/src/main/java/tigase/db/jdbc/TigaseAuth.java[tigase.db.jdbc.TigaseAuth]. It allows you to connect to any external database to perform user authentication.\nYou can find more details how to setup a custom connector in the xref:customAuthConnector[Custom Authentication Connectors] guide.\n\nTo make this connector working you have to prepare your database to offer set of stored procedures for Tigase server to perform all the authentication actions. The best description is the example schema with all the stored procedures defined. Please refer to the Tigase link:https://projects.tigase.org/projects/tigase-server/repository/revisions/master/show/database[SVN repository] for the schema definition files.\n\nFiles with the stored procedures implementations are located in link:https://projects.tigase.org/projects/tigase-server/repository/revisions/master/show/database[postgresql-schema-4.sql] file for PostgreSQL database.\n\nThe absolute minimum of stored procedures you have to implement is:\n\n- *TigUserLoginPlainPw* - to perform user authentication. The procedure is always called when the user tries to login to the XMPP server. This is the only procedure which must be implemented and actually must work.\n- *TigUserLogout* - to perform user logout. The procedure is always called when the user logouts or disconnects from the server. This procedure must be implemented but it can be empty and can do nothing. It just needs to exist because Tigase expect it to exist and attempts to call it.\n\nWith these 2 above stored procedures you can only perform user login/logouts on the external database. You can't register a user account, change user password or remove the user. In many cases this is fine as all the user management is handled by the external system.\n\nIf you however want to allow for account management via XMPP you have to implement also following procedures:\n\n- *TigAddUserPlainPw* - to add a new user account\n- *TigRemoveUser* - to remove existing user account\n- *TigUpdatePasswordPlainPw* - to change a user password for existing account\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_21_-_Security_-_B_-_Authentication_Connectors_-_2_-_Tigase_Custom_Auth_Connector.asciidoc",
"content": "[[custonAuthConnector]]\n= Tigase Custom Auth Connector\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 21:18\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nThe Tigase Custom Auth connector with shortcut name: *tigase-custom* is implemented in the class: link:https://projects.tigase.org/projects/tigase-server/repository/changes/src/main/java/tigase/db/jdbc/TigaseCustomAuth.java[tigase.db.jdbc.TigaseCustomAuth]. It allows you to connect to any external database to perform user authentication and use a custom queries for all actions.\n\nYou can find more details how to setup a custom connector in the Custom Authentication Connectors guide.\n\nThe basic configuration is very simple:\n\n[source,bash]\n-----\n--auth-db = tigase-custom\n--auth-db-uri = jdbc:mysql://localhost/drupal?user=user&password=passwd\n-----\n\nThat's it.\n\nThe connector loads correctly and starts working using predefined, default list of queries. In most cases you also might want to define your own queries in the configuration file. The shortest possible description is the following example of the content from the +init.properties+ file:\n\n[source,bash]\n-----\n# This query is used to check connection to the database, whether it is still alive or not\nbasic-conf/auth-repo-params/conn-valid-query=select 1\n\n# This is database initialization query, normally we do not use it, especially in\n# clustered environment\nbasic-conf/auth-repo-params/init-db-query=update tig_users set online_status = 0\n\n# Below query performs user authentication on the database level.\n# The Tigase server does not need to know authentication algorithm or password\n# encoding type, it simply passes user id (BareJID) and password in form\n# which was received from the client, to the stored procedure. If the\n# authentication was successful the procedure returns user bare JID or null otherwise.\n# The Tigase checks whether the JID returned from the query matches\n# JID passed as a parameter. If they match, the authentication is successful.\nbasic-conf/auth-repo-params/user-login-query={ call TigUserLoginPlainPw(?, ?) }\n\n# Below query returns number of user accounts in the database, this is mainly used\n# for the server metrics and monitoring components.\nbasic-conf/auth-repo-params/users-count-query={ call TigAllUsersCount() }\n\n# Below query is used to add a new user account to the database\nbasic-conf/auth-repo-params/add-user-query={ call TigAddUserPlainPw(?, ?) }\n\n# Below query is used to remove existing account with all user's data from the database\nbasic-conf/auth-repo-params/del-user-query={ call TigRemoveUser(?) }\n\n# This query is used for the user authentication if \"user-login-query\" is not defined,\n# that is if there is no database level user authentication algorithm available. In such\n# a case the Tigase server loads user's password from the database and compares it\n# with data received from the client.\nbasic-conf/auth-repo-params/get-password-query=select user_pw from tig_users where user_id = ?\n\n# Below query is used for user password update in case user decides to change his password\nbasic-conf/auth-repo-params/update-password-query=update tig_users set user_pw = ? where user_id = ?\n\n# Below query is called on user logout event. Usually we use a stored procedure which\n# records user logout time and marks user as offline in the database\nbasic-conf/auth-repo-params/user-logout-query=update tig_users, set online_status = online_status - 1 where user_id = ?\n\n# This is configuration setting to specify what non-sasl authentication mechanisms\n# expose to the client\nbasic-conf/auth-repo-params/non-sasl-mechs=password,digest\n\n# This is configuration setting to specify what sasl authentication mechanisms expose to the client\nbasic-conf/auth-repo-params/sasl-mechs=PLAIN,DIGEST-MD5\n-----\n\nQueries are defined in the configuration file and they can be either plain SQL queries or stored procedures. If the query starts with characters: '\\{ call' then the server assumes this is a stored procedure call, otherwise it is executed as a plain SQL query. Each configuration value is stripped from white characters on both ends before processing.\n\nPlease don't use semicolon ';' at the end of the query as many JDBC drivers get confused and the query may not work.\n\nSome queries can take arguments. Arguments are marked by question marks '?' in the query. Refer to the configuration parameters description for more details about what parameters are expected in each query.\n\nThe first example shows how to put a stored procedure as a query with 2 required parameters.\n\n[source,java]\n-----\nadd-user-query={ call TigAddUserPlainPw(?, ?) }\n-----\n\nThe same query with plain SQL parameters instead:\n\n[source,java]\n-----\nadd-user-query=insert into users (user_id, password) values (?, ?)\n-----\n\nThe order of the query arguments is important and must be exactly as described in specification for each parameter.\n\n- 'conn-valid-query' - Query executing periodically to ensure active connection with the database.\n+\nTakes no arguments.\n+\nExample query: 'select 1'\n\n- 'init-db-query' - Database initialization query which is run after the server is started.\n+\nTakes no arguments.\n+\nExample query: 'update tig_users set online_status = 0'\n\n- 'add-user-query' - Query adding a new user to the database.\n+\nTakes 2 arguments: +(user_id (JID), password)+\n+\nExample query: 'insert into tig_users (user_id, user_pw) values (?, ?)'\n\n- 'del-user-query' - Removes a user from the database.\n+\nTakes 1 argument: +(user_id (JID))+\n+\nExample query: 'delete from tig_users where user_id = ?'\n\n- 'get-password-query' - Retrieves user password from the database for given user_id (JID).\n+\nTakes 1 argument: +(user_id (JID))+\n+\nExample query: 'select user_pw from tig_users where user_id = ?'\n\n- 'update-password-query' - Updates (changes) password for a given user_id (JID).\n+\nTakes 2 arguments: +(password, user_id (JID))+\n+\nExample query: 'update tig_users set user_pw = ? where user_id = ?'\n\n- 'user-login-query' - Performs user login. Normally used when there is a special SP used for this purpose. This is an alternative way to a method requiring retrieving user password. Therefore at least one of those queries must be defined: +user-login-query+ or +get-password-query.+\n+\nIf both queries are defined then user-login-query is used. Normally this method should be only used with plain text password authentication or sasl-plain.\n+\nTigase expects a result set with user_id to be returned from the query if login is successful and empty results set if the login is unsuccessful.\n+\nTakes 2 arguments: +(user_id (JID), password)+\n+\nExample query: 'select user_id from tig_users where (user_id = ?) AND (user_pw = ?)'\n\n- 'user-logout-query' - This query is called when user logs out or disconnects. It can record that event in the database.\n+\nTakes 1 argument: +(user_id (JID))+\n+\nExample query: 'update tig_users, set online_status = online_status - 1 where user_id = ?'\n\n- 'non-sasl-mechs' - Comma separated list of NON-SASL authentication mechanisms. Possible mechanisms are: +password+ and +digest+. The digest mechanism can work only with +get-password-query+ active and only when password are stored in plain text format in the database.\n\n- 'sasl-mechs' - Comma separated list of SASL authentication mechanisms. Possible mechanisms are all mechanisms supported by Java implementation. The most common are: +PLAIN, DIGEST-MD5, CRAM-MD5+.\n+\n\"Non-PLAIN\" mechanisms will work only with the +get-password-query+ active and only when passwords are stored in plain text format in the database. Application: Tigase Server\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_22_-_Security_-_B_-_Authentication_Connectors_-_3_-_Drupal_Authentication_Added.asciidoc",
"content": "[[drupalAuthentication]]\n= Drupal Authentication\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 21:18\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nCurrently, we can only check authentication against a *Drupal* database at the moment. Full *Drupal* authentication is not implemented as of yet.\n\nAs *Drupal* keeps encrypted passwords in database the only possible authorization protocols are those based on PLAIN passwords.\n\nTo protect your passwords *Tigase* server must be used with SSL or TLS encryption.\n\nImplementation of a *Drupal* database based authorization is located in +tigase.db.jdbc.DrupalAuth+ class. Although this class is capable of adding new users to the repository I recommend to switch in-band registration off due to the caching problems in *Drupal.* Changes in database are not synchronized with *Drupal* yet. Functionality for adding new users is implemented only to ease user accounts migration from different repository types from earlier *Tigase* server installations.\n\nThe purpose of that implementation was to allow all accounts administration tasks from *Drupal* like: account creation, all accounts settings, like e-mail, full name, password changes and so on.\n\n*Tigase* server uses following fields from *Drupal* database: name (user account name), pass (user account password), status (status of the account). Server picks up all changes instantly. If user status is not 1 then server won't allow user to login trough XMPP even if user provides valid password.\n\nThere is no _Roster_ management in *Drupal* yet. So Roster management have to be done from the XMPP client.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_23_-_Security_-_B_-_Authentication_Connectors_-_4_-_LDAP_Authentication_Connector.asciidoc",
"content": "[[LDAPauth]]\n= LDAP Authentication Connector\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2012-03-30 21:56\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nFrom version 5.1.0, rev. (build) 2881 Tigase XMPP Server offers support for authenticating users against an LDAP server in *Bind* *Authentication* mode.\n\nConfiguration for the LDAP support is really simple you just have to add a few lines to your +init.properties+ file.\n\n[source,bash]\n-----\n# LDAP Authentication connector\n--auth-db = tigase.db.ldap.LdapAuthProvider\n# LDAP connection URI\n--auth-db-uri=ldap://ldap.tigase.com:389\n# LDAP access parameters\nbasic-conf/auth-repo-params/user-dn-pattern=cn=USER_ID,ou=people,dc=tigase,dc=org\n-----\n\nPlease note the *USER_ID* element, this is a special element of the configuration which is used to authenticate particular user. Tigase LDAP connector replaces it with appropriate data during authentication. You can control what Tigase should put into this part. In your configuration you must replace this string with one of the following:\n\n. *%1$s* - use user name only for authentication (JabberID's localpart)\n. *%2$s* - use domain name only for authentication (JabberID's domain part)\n. *%3$s* - use the whole Jabber ID (JID) for authentication\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_24_-_Security_-_B_-_Authentication_Connectors_-_5_-_Configuration_of_SASL_EXTERNAL.asciidoc",
"content": "[[saslExternal]]\n= Configuration of SASL EXTERNAL\n:author: Bartosz Malkowski \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2013-11-27 13:34\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nIn order to enable SASL External add following line to the +init.properties+ file\n\n[source,bash]\n-----\nc2s/clientCertCA=/path/to/cacert.pem\n-----\n\nFile +cacert.pem+ contains Certificate Authority certificate which is used to sign clients certificate.\n\nClient certificate must include user's Jabber ID as +XmppAddr+ in +subjectAltName+:\n__________________________\nAs specified in RFC 3920 and updated in RFC 6120, during the stream negotiation process an XMPP client can present a certificate (a “client certificate”). If a JabberID is included in a client certificate, it is encapsulated as an id-on-xmppAddr Object Identifier (“xmppAddr”), i.e., a subjectAltName entry of type otherName with an ASN.1 Object Identifier of “id-on-xmppAddr” as specified in Section 13.7.1.4 of RFC 6120.footnote:[http://xmpp.org/extensions/xep-0178.html#c2s[XEP-0178]]\n__________________________\n\nIt is possible to make client certificate required:\n\n[source,bash]\n-----\nc2s/clientCertRequired[B]=true\n-----\n\nIf this option will be enabled, then client must provide certificate. This certificate will be verified against +c2s/clientCertCA+. If client does not provide certificate or certificate will be invalid, TLS handshake will be interrupted and client will be disconnected.\n\nUsing this options does not force client to use SASL EXTERNAL. Client still may authenticate with other SASL mechanisms.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_25_-_Security_-_C_-_Packet_Filtering.asciidoc",
"content": "[[tigase41packetFiltering]]\n= Packet Filtering\n:author: not known\n:version: v1.0 initial release\n:date: 2015-07-13 16:39\n\n:toc:\n\nTigase offers different ways to filter XMPP packets flying through the server. The most common use for packet filtering is to restrict users from sending or receiving packets based on the sender or received address.\n\nThere are also different possible scenarios: time based filtering, content filtering, volume filtering and so on.\n\nAll pages in this section describe different filtering strategies.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_26_-_Security_-_C_-_Packet_Filtering_-_1_-_Domain_Based_Packet_Filtering.asciidoc",
"content": "[[domainBasedPacketFiltering]]\n= Domain Based Packet Filtering\n:author: not known\n:version: v1.0 initial release\n:date: 2015-07-13 16:43\n\nDomain based packet filtering is a simple filter allowing to restrict user communication based on the source/destination domain name. This is especially useful if we want to limit user communication within a single - own domain only or a list of domains.\n\nA company might not wish to allow employers to chat during work hours with anybody in the world. A company may also have a few different domains used by different branches or departments. An administrator may restrict communication to a list of domains.\n\n== Introduction\n\nThe restriction is on a per-user basis. So the administrator can set a different filtering rules for each user. There is also a per-domain configuration and global-installation setting (applied from most general to most specific, i.e. from installation to user).\n\nRegular users can not change the settings. So this is not like a privacy list where the user control the filter. Domain filter can not be changed or controlled by the user. The system administrator can change the settings based on the company policy.\n\nThere are predefined rules for packet filtering:\n\n. `ALL` - user can send and receive packets from anybody.\n. `LOCAL` - user can send and receive packets within the server installation only and all it's virtual domains.\n. `OWN` - user can send and receive packets within his own domains only\n. `BLOCK` - user can't communicate with anyone. This could be used as a means to temporarily disable account or domain.\n. `LIST` - user can send and receive packets within listed domains only (i.e. _whitelist_).\n. `BLACKLIST` - user can communicate with everybody (like `ALL`), except contacts on listed domains.\n. `CUSTOM` - user can communicate only within custom created rules set.\n\nWhitelist (`LIST`) and blacklist (`BLACKLIST`) settings are mutually exclusive, i.e. at any given point of time only one of them can be used.\n\nThose rules applicable to particular users are stored in the user repository and are loaded for each user session. If there are no rules stored for a particular user server tries to apply rules for a VHost of particular user, and if there is no VHost filtering policy server uses global server configuration. If there is no filtering policy altogether server applies defaults based on following criteria:\n\n. If this is *Anonymous* user then *LOCAL* rule is applied\n. For all *other* users *ALL* rule is applied.\n\n== Configuration\n\nFiltering is performed by the domain filter plugin which must be loaded at startup time. It is loaded by default if the plugins list is not set in the configuration file. However if you have a list of loaded plugins in the configuration file make sure *domain-filter* is on the list.\n\nThere is no other configuration required for the plugin to work.\n\n== Administration, Rules Management\n\nAlthough controlling domain filtering rules is possible for each user separately, it is not practical for large installations. In most cases users are stored in the database and a third-party system keeps all the user information.\n\nTo change the rule for a single user you can use loadable administration scripts feature and load link:https://projects.tigase.org/projects/tigase-server/repository/revisions/master/entry/src/main/groovy/tigase/admin/UserDomainFilter.groovy[UserDomainFilter.groovy] script. It enables modifying rules for a given user JID.\n\n== Implementation\n\nIf you have a third party system which keeps and manages all user information than you probably have your own UserRepository implementation which allows the Tigase server to access user data. Filtering rules are loaded from user repository using following command:\n\n[source,java]\n-----\nrepo.getData(user_id, null, DomainFilter.ALLOWED_DOMAINS_KEY, null)\nrepo.getData(user_id, null, DomainFilter.ALLOWED_DOMAINS_LIST_KEY, null)\n-----\n\nWhere *user_id* is user Jabber ID without resource part, *DomainFilter.ALLOWED_DOMAINS_KEY* is a property key: \"allowed-domains\". The user repository MUST return one of following only:\n\n. `ALL` - if the user is allowed to communicate with anybody\n. `LOCAL` - if the user is allowed to communicate with users on the same server installation.\n. `OWN` - if the user is allowed to communicate with users within his own domain only.\n. `LIST` - list of domains within which the user is allowed to communicate with other users. No wild-cards are supported. User's own domain should be included too.\n. `BLACKLIST` - list of domains within which the user is NOT allowed to communicate with other users. No wild-cards are supported. User's own domain should NOT be included.\n. `CUSTOM` - list of rules defining custom communication permissions (server processes stanza according to first matched rule, similar to XEP-0016) in the following format:\n\n[source]\n-----\nruleSet = rule1;rule2;ruleX;\n\nrule = order_number|policy|UID_type[|UID]\n\norder_number = any integer;\npolicy = (allow|deny);\nUID_type = [jid|domain|all];\nUID = user JID or domain, for example pubsub@test.com; if UID_type is ALL then this is ignored.\n-----\n\nFor example:\n\n[source]\n-----\n1|allow|self;\n2|allow|jid|admin@test2.com;\n3|allow|jid|pubsub@test.com;\n4|deny|all;\n-----\n. `null` - a java null if there are no settings for the user.\n\nIn case of `LIST` and `BLACKLIST` filtering options, it's essential to provide list of domains for the whitelisting/blacklisting. *DomainFilter.ALLOWED_DOMAINS_LIST_KEY* is a property key: \"allowed-domains-list\". The user repository MUST return semicolon separated list of domains: `domain1.com;domain2.com,domain3.org`\n\nThe filtering is performed by the link:https://projects.tigase.org/projects/tigase-server/repository/revisions/master/entry/src/main/java/tigase/xmpp/impl/DomainFilter.java[`tigase.xmpp.impl.DomainFilter`] plugin. Please refer to source code for more implementation details.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_27_-_Security_-_D_-_Access_Control_List.asciidoc",
"content": "[[accessControlList]]\n= Access Control Lists in Tigase\n:author: Artur Hefczyc\n:version: v1.0 October 2015\n:date: 2015-10-26 08:51\n\n:toc:\n:numbered:\n:website: http://www.tigase.net\n\nTigase offers support for *Access Control List (ACL)* to allow for fine grained access to administration commands on the server.\n\nBy default, all administration commands are only accessible (visible through service discovery and can be executed) by the service administrators. Service administrators are existing accounts with JIDs (*BareJIDs*) listed in the +init.properties+ file under --admins.\n\nAdditionally, other XMPP users and entities can be assigned permissions to execute a command or commands using Tigase's ACL capabilities.\n\nThe following is a list of possible ACL modifiers for administrator command accessibility:\n\n- *ALL* - Everybody can execute the command, even users from different federated servers.\n- *ADMIN* - Local server administrators can execute the command, this is a default setting if no ACL is set for a command.\n- *LOCAL* - All users with accounts on the local server can execute the command. Users from other, federated servers will not be able to execute the command.\n- *DOMAIN* - Only users with accounts on the selected domain will be able to execute the command. It may be useful to setup a domain specifically for admin accounts, and automatically all users within that domain would be able to run the command.\n- *JID* - Comma separated list of JIDs of users who can execute the command.\n\nIn any case, regardless of ACL settings, any command can be executed and accessed by the designated service wide administrators, that is accounts listed as admins in the init.properties file.\n\nMultiple ACL modifiers can be combined and applied for any command. This may not always makes sense. For example ALL supersedes all other settings, so it does not make sense to combine it with any other modifier. However, most others can be combined with JID to broaden access to specific accounts.\n\nOn Tigase server the Access Control List is checked for the first matching modifier. Therefore if you combine ALL with any other modifier, anybody from a local or remote service will always be able to execute the command, no matter what other modifiers are added.\n\nPlease note, the ACL lists work on the command framework level. Access is verified before the command is actually executed. There might be additional access restrictions within a command itself. In many cases, even if all local users are permitted to execute a command (LOCAL modifier), some commands allow only to be executed by a domain owner or a domain administrator (and of course by the service-wide administrators as well). All the commands related to a user management such as adding a new user, removing a user, password changes, etc… belong to this category.\nWhen conducting domain (vhost) management, creation/registration of a new domain can be done by any local user (if LOCAL ACL modifier is set) but then all subsequent domain management tasks such as removing the vhost, updating its configuration, setting SSL certificate can be done by the domain owner or administrator only.\n\nThe ACL list is set for a specific Tigase component and a specific command. Therefore the configuration property must specify all the details. So the general format for configuring ACL for a command is this:\n\n+comp-id/command/command-id=ACL_modifier,ACL_modifier,ACL_modifier+\n\nThe breakdown is as such:\n\n- *comp-id* is the Tigase server component ID such as: +sess-man+, +vhost-man+, +c2s+, etc..\n- *command* is a static text which indicates that the property is for component's command settings.\n- *command-id* is a command ID for which we set the ACL such as +query-dns+, +http://jabber.org/protocol/admin#add-user+, +user-roster-management+, etc…\n\nHere are a few examples:\n\n_Allowing local users to create and manage their own domains_\n[source,bash]\n-----\nvhost-man/command/comp-repo-item-add=LOCAL\nvhost-man/command/comp-repo-item-remove=LOCAL\nvhost-man/command/comp-repo-item-update=LOCAL\nvhost-man/command/ssl-certificate-add=LOCAL\n-----\n\nIn fact all the commands except +item-add+ can be executed by the domain owner or administrator.\n\n_Allowing local users to execute user management commands:_\n[source,bash]\n-----\nsess-man/command/http\\://jabber.org/protocol/admin#add-user=LOCAL\nsess-man/command/http\\://jabber.org/protocol/admin#change-user-password=LOCAL\nsess-man/command/http\\://jabber.org/protocol/admin#delete-user=LOCAL\nsess-man/command/http\\://jabber.org/protocol/admin#get-online-users-list=LOCAL\nsess-man/command/http\\://jabber.org/protocol/admin#get-registered-user-list=LOCAL\nsess-man/command/http\\://jabber.org/protocol/admin#user-stats=LOCAL\nsess-man/command/http\\://jabber.org/protocol/admin#get-online-users-list=LOCAL\n-----\n\nAs in the previous example, the commands will by executed only by local users who are the specific domain administrators.\n\n_Allowing users from a specific domain to execute +query-dns+ command and some other users for given JIDs from other domains:_\n-----\nvhost-man/command/query-dns=DOMAIN:tigase.com,admin@tigase.org,frank@example.com\n-----\n\nTo be able to set a correct ACL property you need to know component names and command IDs. Component IDs can be found in the service discovery information on running server or in the server logs during startup. A command ID can be found in the command script source code. Each script contains a list of metadata at the very beginning of it's code. One of them is +AS:CommandId+ which is what you have to use for the ACL setting.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_28_-_Database_Management.asciidoc",
"content": "[[databasemgnt]]\n= Database Management\n:author: daniel wisnewski\n:version: v1.0 July 2015\n:date: 2015-07-16 12:49\n\n:website: http://tigase.net\n\nTigase is coded to perform with multiple database types and numbers.\nOwing to it's versatile nature, there are some tools and procedures that may be of use to certain administrators.\n\n== Recommended database versions\nAs of v7.1.0 here are the minimum and recommended versions of databases for use with Tigase:\n\n\n[width=\"100%\",frame=\"topbot\",options=\"header\"]\n|=================================\n|Database |Recommended Version |Minimum Version |Additional Information\n|DerbyDB |10.12.1.1 |10.12.1.1 |Included with Tigase XMPP Server\n|MySQL |5.6 |5.5 |\n|SQLServer |2012 |2008 R2 |\n|MongoDB |2.6 |2.6 |Driver not working with mongoDB 3.0 or newer.\n|=================================\n\nAlthough Tigase may support other versions of databases, these are the ones we are most familiar with in offering support and advice. Use of databases outside these guidelines may result in unforeseen errors.\n\n== xref:databasePreperation[Database Preparation]\nPreparing new databases in case installer setup is not an option.\n\n== xref:hashedPasswords[Hashed Passwords in User Database]\nProviding more secure password storage.\n\n== xref:multidb[Multiple Databases in Tigase]\nOptions for using multiple databases for different purposes in Tigase.\n\n== xref:dbImportingData[Importing User Data]\nTips to move data repositories from one to another database.\n\n== xref:existingData[Import Existing Database]\nThis section has some depreciated information, however it may be handy to upgrade, or manually connect databases.\n\n== xref:oldVerSchemas[Old Version Schemas and Updates]\nContains our old Schema updates, if you have an old installation of Tigase and want to move to a more current version, see the guides revelant to you.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_29_-_Database_Management_-_A_-_Database_Preparation.asciidoc",
"content": "[[databasePreperation]]\n= Database Preparation\n:author: Artur Hefczyc \n:author: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2012-07-15 06:42\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nTigase uses generally the same database schema and the same set of stored procedures and functions on every database. However, the schema creation scripts and code for stored procedures is different for each database. Therefore the manual process to prepare database is different for each database system.\n\nOf course the simplest and easiest way to prepare database is to use Tigase installer or webinstaller which automates the whole process. Sometimes this is not possible. A second option is to use the +DBSchemaLoader+ utility in Tigase. If either of those won't work, or won't suit your needs, provided are set of guides describing initialization and preparation process for each supported database.\n\n-xref:dbSchemaLoader[The DBSchemaLoader Utility]\n- xref:prepareMysql[Prepare the MySQL Database for the Tigase Server]\n- xref:hashedPasswords[Hashed User Passwords in Database]\n- xref:prepareDerby[Prepare the Derby Database for the Tigase Server]\n- xref:prepareMssql[Prepare the MS SQL Server Database for the Tigase Server]\n- xref:preparePostgresql[Prepare the PostgreSQL Database for the Tigase Server]\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_29_-_Database_Management_-_A_-_Database_Preperation_-_1_-_DbSchemaLoader.asciidoc",
"content": "[[dbSchemaLoader]]\n= +dbSchemaLoader+ Utility\n:author: Daniel Wisnewski\n:author: v1.0, March 2016: Reformatted for AsciiDoc.\n:date: 2016-03-14 14:30\n\n:numbered:\n:toc:\n:website: http://www.tigase.net\n\nIncluded with Tigase is the +dbSchemaLoader+ Utility, which can be used to apply schema files to databases. It is able to operate with Derby, MySQL, SQLServer, and PostgreSQL databases.\nIn order to use this utility with any of the databases, you will need to first have the database environment up and running, and have established user credentials. You may use root or an account with administrator write privileges.\n\nIMPORTANT: All commands in this guide are required to be running from the Tigase installation directory.\n\n== Operation & Variables\n\nFirst, lets cover the DBSchemaLoader operation and variables:\n\n*Operation*\nThe utility is run using the java -cp command from the Tigase installation directory. Be sure that you have JDK v1.8 or later installed.\nLinux\n[source,command]\n-----\njava -cp \"jars/*\" tigase.util.DBSchemaLoader\n-----\nor from a Windows environment\n-----\njava -cp jars/* tigase.util.DBSchemaLoader\n-----\nThese commands will be followed by a combination of the following variables\n\n*Variables*\n\nUse the following options to customize. Options in bold are required, {potential options are in brackets}.::\n* *-dbType database_type {derby, mysql, postgresql, sqlserver}*\n* -schemaVersion schema version {4, 5, 5-1}\n* *-dbName database name*\n* -dbHostname database hostname (default is localhost)\n* -dbUser tigase username\n* -dbPass tigase user password\n* -rootUser database root username\n* -rootPass database root password\n* *-file path to sql schema file* {database/derby-schema-7-1.sql}\n* -query sql query to execute\n* -logLevel java logger Level\n* -adminJID comma separated list of admin JIDs\n* -adminJIDpass password (one for all entered JIDs)\n\nWith that out of the way, lets look at some examples.\nLets say you have a new mysql database server with root user root and password rood (to keep things simple, we do not recommend this). The MySQL database is hosted locally, your command would be as follows:\n[source,cmd]\n-----\njava -cp \"jars/*\" tigase.util.DBSchemaLoader -dbType mysql -dbName tigasedb -rootUser root -rootPass root -schemaVersion -adminJID admin@example.com -adminJIDpass password 7.1 -file database/mysql-schema-7-1.sql\n-----\nThis will create the tigasedb database, add an Admin user as admin@example.com with password 'password', and apply the v7.1 schema files. Output will look like this:\n[source,cmd]\n-----\nLogLevel: CONFIG\n\ntigase.util.DBSchemaLoader \t \t CONFIG Properties: [{dbHostname=localhost, logLevel=CONFIG, adminJID=admin@example.com, dbType=mysql, file=database/mysql-schema-7-1.sql, rootUser=root, adminJIDpass=password, dbPass=tigase_pass, dbName=tigasedb, schemaVersion=7.1, rootPass=root, dbUser=tigase_user}]\n\ntigase.util.DBSchemaLoader \t validateDBConnection \t INFO Validating DBConnection, URI: jdbc:mysql://localhost/?user=root&password=root\n\ntigase.util.DBSchemaLoader \t validateDBConnection \t CONFIG DriverManager (available drivers): [[org.apache.derby.jdbc.AutoloadedDriver@10f87f48, org.postgresql.Driver@1b2c6ec2, com.mysql.jdbc.Driver@50040f0c, jTDS 1.3.1]]\n\ntigase.util.DBSchemaLoader \t validateDBConnection \t INFO Connection OK\ntigase.util.DBSchemaLoader \t validateDBExists \t INFO Validating whether DB Exists, URI: jdbc:mysql://localhost/tigasedb?user=tigase_user&password=tigase_pass\n\ntigase.util.DBSchemaLoader \t validateDBExists \t INFO Doesn't exist, creating...\n\ntigase.util.DBSchemaLoader \t validateDBExists \t INFO OK\n\ntigase.util.DBSchemaLoader \t loadSchemaFile \t INFO Loading schema from file: database/mysql-schema-7-1.sql, URI: jdbc:mysql://localhost/tigasedb?user=root&password=root\ntigase.util.DBSchemaLoader \t loadSchemaFile \t INFO completed OK\n\ntigase.util.DBSchemaLoader \t printInfo \t INFO\n\nDatabase init.properties configuration:\n\n--user-db=mysql\n--user-db-uri=jdbc:mysql://localhost/tigasedb user=tigase_user&password=tigase_pass&useUnicode=true&characterEncoding=UTF-8\n-----\n\nTIP: The utility will automatically generate the lines you need to add to your init.properties file to use this database!\n\nAt this time, it is suggested to load the PubSub schema since you will have to change very little of the command:\n\n[source,cmd]\n-----\njava -cp \"jars/*\" tigase.util.DBSchemaLoader -dbType mysql -dbName tigasedb -rootUser root -rootPass root -file database/mysql-pubsub-schema-3.2.0.sql\n-----\n\nShould you wish to use the Socks5 Proxy component, you will need to load that schema as well\n[source,cmd]\n-----\njava -cp \"jars/*\" tigase.util.DBSchemaLoader -dbType mysql -dbName tigasedb -rootUser root -rootPass root -file database/mysql-socks5-schema.sql\n-----\n\nAt this time you're finished setting up a database for use with Tigase!\nFor other databases that are supported, the operations will be very similar with only the -dbType and perhaps the -dbHostname being different.\n\n== -Query function\n\nShould you decide to customize your own functions, or have specific information you want to put into the database, you can use the -query function to perform a single query step.\n[source,cmd]\n-----\njava -cp \"jars/*\" tigase.util.DBSchemaLoader -dpType mysql -dbName tigasedb -rootUser root -rootPass root -query \"CREATE TABLE tigasedb.EXTRA_TABLE (id INT(6) UNSIGNED AUTO_INCREMENT PRIMARY KEY, name VARCHAR(10) NOT NULL)\"\n-----\nOf course this would break the schema for tigasedb by adding an unexpected table, you will receive the following message:\n-----\ntigase.util.DBSchemaLoader printInfo WARNING Database schema is invalid\n-----\n\nBut this is a demonstration how you may run a query through the database without the need to use another tool. Note that you will need to select the specific database for each query.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_30_-_Database_Management_-_A_-_Database_Preparation_-_1_-_Prepare_the_MySQL_Database_for_Tigase_Server.asciidoc",
"content": "[[prepareMysql]]\n= Prepare the MySQL Database for the Tigase Server\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 21:18\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nThis guide describes how to prepare MySQL database for connecting Tigase server.\n\n== Basic Setup\n\nThe MySQL database can be prepared in many ways. Most Linux distributions contain tools which allow you to go through all steps from the shell command line. To make sure it works on all platforms in the same way, we will first show how to do it under MySQL command line client.\n\n=== Configuring from MySQL command line tool\n\nRun the MySQL command line client in either Linux or MS Windows environment and enter following instructions:\n\n. Create the database for the Tigase server:\n+\n[source,sql]\n-----\nmysql> create database tigasedb;\n-----\n. Add the +tigase_user+ user and grant him access to the +tigasedb+ database. Depending on how you plan to connect to the database (locally or over the network) use one of following commands or all if you are not sure:\n+\n*Grant access to tigase_user connecting from any network address.*\n+\n[source,sql]\n-----\nmysql> GRANT ALL ON tigasedb.* TO tigase_user@'%'\n IDENTIFIED BY 'tigase_passwd';\n-----\n+\n*Grant access to tigase_user connecting from localhost.*\n+\n[source,sql]\n-----\nmysql> GRANT ALL ON tigasedb.* TO tigase_user@'localhost'\n IDENTIFIED BY 'tigase_passwd';\n-----\n+\n*Grant access to tigase_user connecting from local machine only.*\n+\n[source,sql]\n-----\nmysql> GRANT ALL ON tigasedb.* TO tigase_user\n IDENTIFIED BY 'tigase_passwd';\n-----\n+\nFor the Tigase server version 4.x additional permissions must be granted for the database user:\n+\n[source,sql]\n-----\nmysql> GRANT SELECT, INSERT, UPDATE ON mysql.proc TO 'tigase_user'@'localhost';\nmysql> GRANT SELECT, INSERT, UPDATE ON mysql.proc TO 'tigase_user'@'%';\nmysql> GRANT SELECT, INSERT, UPDATE ON mysql.proc TO 'tigase_user';\n-----\n+\nAnd now you can update user permission changes in the database:\n+\n[source,sql]\n-----\nmysql> FLUSH PRIVILEGES;\n-----\n. Load the proper mysql schema into the database. Full installations of Tigase will have all the SQL file you need to create and update the database. First, switch to the database you have just created:\n+\n[source,sql]\n-----\nmysql> use tigasedb;\n-----\n+\nWe are assuming you run the mysql client in Linux from the Tigase installation directory.\n+\n[source,sql]\n-----\nmysql> source database/mysql-7-1-schema.sql;\n-----\n+\nFor the Tigase server version v7.1.0 you have to use proper schema version which is 5.1. You will also need to manually load the PubSub schema as well, current version is v3.2.0. All modern versions will load previous schemas first so no need to do a manual upgrade.\n+\n[source,sql]\n-----\nmysql> source database/mysql-pubsub-schema-3.2.0.sql;\n-----\n+\nIf you plan to use the Socks5 component, you will also need to add that schema as well.\n+\n[source,sql]\n-----\nmysql> source database/mysql-socks5-schema.sql;\n-----\n+\nOn Windows you have probably to enter the full path, assuming Tigase is installed in C:\\Program Files\\Tigase:\n+\n[source,sql]\n-----\nmysql> source c:/Program Files/Tigase/database/mysql-7-1-schema.sql;\nmysql> source c:/Program Files/Tigase/database/mysql-pubsub-schema-3.2.0.sql;\nmysql> source c:/Program Files/Tigase/database/mysql-socks5-schema.sql;\n-----\n+\n\n\n== Configuring From the Linux Shell Command Line\n\nFollow steps below to prepare the MySQL database:\n\n. Create the database space for the Tigase server:\n[source,sql]\n-----\nmysqladmin -p create tigasedb\n-----\n. Add the +tigase_user+ user and grant access to the tigasedb database. Depending on how you plan to connect to the database (locally or over the network) use one of following commands or all if you are not sure:\n*Grant access to tigase_user connecting from any network address.*\n[source,sql]\n-----\necho \"GRANT ALL ON tigasedb.* TO tigase_user@'%' \\\n IDENTIFIED BY 'tigase_passwd'; \\\n FLUSH PRIVILEGES;\" | mysql -u root -pdbpass mysql\n-----\n*Grant access to tigase_user connecting from localhost.*\n[source,sql]\n-----\necho \"GRANT ALL ON tigasedb.* TO tigase_user@'localhost' \\\n IDENTIFIED BY 'tigase_passwd'; \\\n FLUSH PRIVILEGES;\" | mysql -u root -pdbpass mysql\n-----\n*Grant access to tigase_user connecting from local machine only.*\n[source,sql]\n-----\necho \"GRANT ALL ON tigasedb.* TO tigase_user \\\n IDENTIFIED BY 'tigase_passwd'; \\\n FLUSH PRIVILEGES;\" | mysql -u root -pdbpass mysql\n-----\n. Load the proper mysql schema into the database. Full installations of Tigase will have all the SQL file you need to create and update the database.\n[source,sql]\n-----\nmysql -u dbuser -p tigasedb < mysql-schema-7-1.sql\nmysql -u dbuser -p tigasedb < mysql-pubsub-schema-3.2.0.sql\n-----\n\nIf you want to use the socks5 component, then oyu will need to include the following line as well:\n[source,sql]\n-----\nmysql -u dbuser -p tigasedb < mysql-socks5-schema.sql\n-----\n\n== Configuring MySQL for UTF-8 Support\n\nIn my.conf put following lines:\n\n[source,bash]\n-----\n[mysql]\ndefault-character-SET=utf8\n\n[client]\ndefault-character-SET=utf8\n\n[mysqld]\ninit_connect='SET collation_connection = utf8_general_ci; SET NAMES utf8;'\ncharacter-set-server=utf8\ndefault-character-SET=utf8\ncollation-server=utf8_general_ci\nskip-character-set-client-handshake\n-----\n\nThen connect to the database from the command line shell check settings:\n\n[source,sql]\n-----\nSHOW VARIABLES LIKE 'character_set_database';\nSHOW VARIABLES LIKE 'character_set_client';\n-----\n\nIf any of these shows something else then 'utf8' then you need to fix it using the command:\n\n[source,sql]\n-----\nALTER DATABASE tigasedb DEFAULT CHARACTER SET utf8;\n-----\n\nYou can now also test your database installation if it accepts UTF-8 data. The easiest way to ensure this is to just to create an account with UTF-8 characters:\n\n[source,sql]\n-----\ncall TigAddUserPlainPw('żółw@some.domain.com', 'żółw');\n-----\n\nAnd then check that the account has been created:\n\n[source,sql]\n-----\nSELECT * FROM tig_users WHERE user_id = 'żółw@some.domain.com';\n-----\n\nIf the last command gives you no results it means there is still something wrong with your settings. You might also want to check your shell settings to make sure your command line shell supports UTF-8 characters and passes them correctly to MySQL:\n\n[source,sh]\n-----\nexport LANG=en_US.UTF-8\nexport LOCALE=UTF-8\nexport LESSCHARSET='utf-8'\n-----\n\nIt seems that MySQL 5.0.x also needs extra parameters in the connection string: '&useUnicode=true&characterEncoding=UTF-8' while MySQL 5.1.x seems to not need it but it doesn't hurt to have it for both versions. You have to edit 'etc/init.properties' file and append this to the database connection string.\n\nFor MySQL 5.1.x, however, you need to also update code for all database stored procedures and functions used by the Tigase. They are updated for Tigase version 4.4.x and up, however if you use an older version of the Tigase server, you can reload stored procedures using the file from SVN.\n\n== Other MySQL Settings Worth Considering\n\nThere are a number of other useful options, especially for performance improvements. Please note, you will have to review them as some of them may impact data reliability and are useful for performance or load tests installations only.\n\n[source,bash]\n-----\n# InnoDB seems to be a better choice\n# so lets make it a default DB engine\ndefault-storage-engine = innodb\n-----\n\nSome the general MySQL settings which mainly affect performance:\n\n[source,bash]\n-----\nkey_buffer = 64M\nmax_allowed_packet = 32M\nsort_buffer_size = 64M\nnet_buffer_length = 64K\nread_buffer_size = 16M\nread_rnd_buffer_size = 16M\nthread_stack = 192K\nthread_cache_size = 8\nquery_cache_limit = 10M\nquery_cache_size = 64M\n-----\n\nInnoDB specific settings:\n\n[source,bash]\n-----\n# Keep data in a separate file for each table\ninnodb_file_per_table = 1\n# Allocate memory for data buffers\ninnodb_buffer_pool_size = 1000M\ninnodb_additional_mem_pool_size = 100M\n# A location of the MySQL database\ninnodb_data_home_dir = /home/databases/mysql/\ninnodb_log_group_home_dir = /home/databases/mysql/\n# The main thing here is the 'autoextend' property\n# without it your data file may reach maximum size and\n# no more records can be added to the table.\ninnodb_data_file_path = ibdata1:10M:autoextend\ninnodb_log_file_size = 10M\ninnodb_log_buffer_size = 32M\n# Some other performance affecting settings\ninnodb_flush_log_at_trx_commit = 2\ninnodb_lock_wait_timeout = 50\ninnodb_thread_concurrency = 16\n-----\n\nThese settings may not be fully optimized for your system, and have been only tested on our systems. If you have found better settings for your systems, feel free to link:http://tigase.net/contact[let us know].\n//I am certainly not a database expert nor MySQL expert and I do not pretend to be one. So any comments or suggestions you may have are very welcome and appreciated.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_31_-_Database_Management_-_A_-_Database_Preparation_-_2_-_Prepare_the_Derby_Database_for_Tigase_Server.asciidoc",
"content": "[[prepareDerby]]\n= Prepare the Derby Database for the Tigase Server\n:author: Wojciech Kapcia \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2012-06-21 13:28\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nThis guide describes how to prepare Derby database for connecting the Tigase server.\n\n== Basic Setup\n\nPreparation of Derby database is quite simple, but the following assumptions are made\n\n- +DerbyDB+ - Derby database name\n- +database/+ directory contains all necessary schema files\n- +jars/+ and +libs/+ directories contains Tigase and Derby binaries\n\n=== General Approach\n\nFrom the main Tigase directory execute following commands (Linux and Windows accordingly)\n\n*Linux*\n[source,sh]\n-----\njava -Dij.protocol=jdbc:derby: -Dij.database=\"DerbyDB;create=true\" -cp libs/derby.jar:libs/derbytools.jar:jars/tigase-server.jar org.apache.derby.tools.ij database/derby-schema-7.1.sql\n-----\n\n*Windows*\n[source,sh]\n-----\njava -Dij.protocol=jdbc:derby: -Dij.database=\"DerbyDB;create=true\" -cp libs\\derby.jar;libs\\derbytools.jar;jars\\tigase-server.jar org.apache.derby.tools.ij \"database\\derby-schema-7-1.sql\"\n-----\n\nThis will create Derby database named DerbyDB in the main Tigase directory and load Tigase schema for version 7.1.\n\nYou will need to repeat this process again to add the PubSub schema into the database.\n\n*Linux*\n[source,sh]\n-----\njava -Dij.protocol=jdbc:derby: -Dij.database=\"DerbyDB;create=true\" -cp libs/derby.jar:libs/derbytools.jar:jars/tigase-server.jar org.apache.derby.tools.ij database/derby-pubsub-schema-3.2.0.sql\n-----\n\n*Windows*\n[source,sh]\n-----\njava -Dij.protocol=jdbc:derby: -Dij.database=\"DerbyDB;create=true\" -cp libs\\derby.jar;libs\\derbytools.jar;jars\\tigase-server.jar org.apache.derby.tools.ij \"database\\derby-pubsub-schema-3.2.0.sql\"\n-----\n\nIf you wish to use the Sock5 Proxy Component, you will need to add that schema as well:\n\n*Linux*\n[source,sh]\n-----\njava -Dij.protocol=jdbc:derby: -Dij.database=\"DerbyDB;create=true\" -cp libs/derby.jar:libs/derbytools.jar:jars/tigase-server.jar org.apache.derby.tools.ij database/derby-socks5-schema.sql\n-----\n\n*Windows*\n[source,sh]\n-----\njava -Dij.protocol=jdbc:derby: -Dij.database=\"DerbyDB;create=true\" -cp libs\\derby.jar;libs\\derbytools.jar;jars\\tigase-server.jar org.apache.derby.tools.ij \"database\\derby-socks5-schema.sql\"\n-----\n\n== Connecting Tigase to database\n\nOnce the database is setup, configure the init.properties file in Tigase and add the following configuration:\n[source,properties]\n-----\njdbc:derby:{location of derby database};\n-----\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_32_-_Database_Management_-_A_-_Database_Preparation_-_3_-_Prepare_the_MS_SQL_Server_Database_for_Tigase_Server.asciidoc",
"content": "[[prepareMssql]]\n= Prepare the MS SQL Server Database for the Tigase Server\n:author: Wojciech Kapcia \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2013-09-04 14:57\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nThis guide describes how to prepare the MS SQL Server database for connecting the Tigase server to it.\n\n== Basic Setup\n\nIt's expected that a working installation of Microsoft SQL Server is present. The following guide will describe the necessary configurations required for using MS SQL Server with Tigase XMPP Server.\n\n== Preparing MS SQL Server Instance\n\nAfter installation of MS SQL Server an instance needs to be configure to handle incoming JDBC connections. For that purpose it's required to open _SQL Server Configuration Manager_. In the left-hand side panel navigate to _SQL Server Configuration Manager_, then _SQL Server Network Configuration -> Protocols for $\\{INSTANCE_NAME}_. After selecting instance in the right-hand side panel select TCP/IP and open _Properties_, in the Protocol tab in General section select Yes for Enabled property. In the IP Addresses tab select Yes for Active and Enabled properties of all IP Addresses that you want MS SQL Server to handle. Subsequently set the TCP Port property (if missing) to the default value - 1433. A restart of the instance may be required afterwards.\n\n== Configuration using MS SQL Server Management Studio\n\nIn order to prepare the database you can use either a wizard or execute queries directly in the Query Editor. Firstly you need to establish a connection to the MS SQL Server instance. From Object Explorer select Connect and in the Connect to Server dialog enter administrator credentials.\n\n=== Using Wizards\n\n- Create Login\n+\nIn the left-hand side panel select Security -> Logins and from context menu choose New Login, in the Wizard window enter desired Login name, select SQL Server authentication and enter desired password subsequently confirming action with OK\n\n- Create Database\n+\nFrom the Object Explorer select Databases node and from context menu select New Database; in the Wizard window enter desired Database name and enter previously created Login name into Owner field; subsequently confirming action with OK.\n\n=== Using Queries\n\nFrom the Object Explorer root node's context menu select New Query. In the Query windows execute following statements adjusting details to your liking:\n\n\n[source,sql]\n-----\nUSE [master]\nGO\n\nCREATE DATABASE [tigasedb];\nGO\n\nCREATE LOGIN [tigase] WITH PASSWORD=N'tigase12', DEFAULT_DATABASE=[tigasedb]\nGO\n\nALTER AUTHORIZATION ON DATABASE::tigasedb TO tigase;\nGO\n-----\n\n== Import Schema\n\nFrom the File menu Select Open -> File (or use Ctrl+O) and then open following files:\n\n- sqlserver-schema-7-1-schema.sql\n- sqlserver-schema-7-1-sp.sql\n- sqlserver-schema-7-1-props.sql\n- sqlserver-pubsub-schema-3.2.0.sql\n\nSubsequently select created database from the list of Available Databases (Ctrl+U) available on the toolbar and execute each of the opened files in the order listed above.\n\n== Configuring from command line tool\n\nCreation of the database and import of schema can be done from command line as well. In order to do that, execute following commands from the directory where Tigase XMPP Server is installed otherwise paths to the schema need to be adjusted accordingly:\n\n[source,bash]\n-----\nsqlcmd -S %servername% -U %root_user% -P %root_pass% -Q \"CREATE DATABASE [%database%]\"\nsqlcmd -S %servername% -U %root_user% -P %root_pass% -Q \"CREATE LOGIN [%user%] WITH PASSWORD=N'%password%', DEFAULT_DATABASE=[%database%]\"\nsqlcmd -S %servername% -U %root_user% -P %root_pass% -d %database% -Q \"ALTER AUTHORIZATION ON DATABASE::%database% TO %user%;\"\nsqlcmd -S %servername% -U %root_user% -P %root_pass% -d %database% -i database\\sqlserver-schema-7-1-schema.sql\nsqlcmd -S %servername% -U %root_user% -P %root_pass% -d %database% -i database\\sqlserver-schema-7-1-sp.sql\nsqlcmd -S %servername% -U %root_user% -P %root_pass% -d %database% -i database\\sqlserver-schema-7-1-props.sql\nsqlcmd -S %servername% -U %root_user% -P %root_pass% -d %database% -i database\\sqlserver-pubsub-schema-3.2.0.sql\n-----\n\nAbove can be automatized with provided script %tigase-server%\\scripts\\db-create-sqlserver.cmd (note: it needs to be executed from main Tigase XMPP Server directory due to maintain correct paths):\n\n[source,sh]\n-----\n$ scripts\\db-create-sqlserver.cmd %database_servername% %database_name% %tigase_username% %tigase_password% %root_username% %root_password%\n-----\n\nIf no parameters are provided then the following defaults are used:\n\n[source,bash]\n-----\n%database_servername%=localhost\n%database_name%=tigasedb\n%tigase_username%=tigase\n%tigase_password%=tigase12\n%root_username%=root\n%root_password%=root\n-----\n\n== Tigase configuration - init.properties\n\nConfiguration of the MS SQL Server follows general database convention. For MS SQL Support --user-db needs to be set to sqlserver:\n\n[source,bash]\n-----\n--user-db=sqlserver\n-----\n\nand the --user-db-uri needs to point to the configured database:\n\n[source,bash]\n-----\n--user-db-uri=jdbc:[jtds:]sqlserver://db_hostname:port[;property=val]\n-----\n\nwhere any number of additional parameters can (and should) consist of:\n\n- databaseName - name of the database\n- user - username configured to access database\n- password - password for the above username\n- schema - name of the database schema\n- lastUpdateCount - 'false' value causes all update counts to be returned, including those returned by server triggers\n\nExample:\n\n[source,sh]\n-----\n--user-db-uri=jdbc:sqlserver://hostname:1433;databaseName=tigasedb;user=tigase;password=tigase12;schema=dbo;lastUpdateCount=false\n-----\n\n== JDBC: jTDS vs MS JDBC driver\n\nTigase XMPP Server supports two JDBC drivers intended to be used with Microsoft SQL Server - one created and provided by Microsoft itself and the alternative implementation - jTDS. Tigase is shipped with the latter in the distribution packages. Starting with the version 7.1.0 we recommend using jDTS driver that is shipped with Tigase as JDBC driver created by Microsoft can cause problems with some components in cluster installations. MS driver can be downloaded form the website: link:http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=11774[JDBC Drivers 4.0, 4.1 for SQL Server] then unpack the archive. Copy sqljdbc_4.0/enu/sqljdbc4.jar file to $\\{tigase-server}/jars directory.\n\nDepending on the driver used --user-db-uri needs to be configured accordingly.\n\n- Microsoft driver:\n+\n[source,bash]\n-----\n--user-db-uri=jdbc:sqlserver://...\n-----\n- jDTS driver\n+\n[source,bash]\n-----\n--user-db-uri=jdbc:jdts:sqlserver://...\n-----\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_33_-_Database_Management_-_A_-_Database_Preparation_-_4_-_Prepare_the_PostgreSQL_Database_for_Tigase_Server.asciidoc",
"content": "[[preparePostgresql]]\n= Prepare the PostgreSQL Database for the Tigase Server\n:author: Andrzej Wojcik \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2012-06-16 09:38\n:Revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nThis guide describes how to prepare PostgreSQL database for connecting to Tigase server.\n\n== Basic Setup\n\nThe PostgreSQL database can be prepared in many ways. Below are presented two possible ways. The following assumptions apply to both methods:\n\n- +admin_db_user+ - database user with admin rights\n- +tigase_user+ - database user for Tigase\n- +tigasedb+ - database for Tigase\n\n=== Configuring from PostgreSQL Command Line Tool\n\nRun the PostgreSQL command line client and enter following instructions:\n\n. Add the +tigase_user+:\n+\n[source,sql]\n-----\npsql=# create role tigase_user with login password 'tigase123';\n-----\n. Create the database for the Tigase server with +tigase_user+ as owner of database:\n+\n[source,sql]\n-----\npsql=# create database tigasedb owner tigase_user;\n-----\n. Load database schema to initialize the Tigase server from the file that corresponds to the version of Tigase you want to use. First you need to switch to +tigasedb+.\n+\n[source,sql]\n-----\npsql=# \\connect tigasedb\n-----\n+\nBegin by applying the basic Schema\n+\n[source,sql]\n-----\npsql=# \\i database/postgresql-schema-7-1.sql\n-----\n+\nContinue by adding the PubSub Schema\n+\n[source,sql]\n-----\npsql=# \\i database/postgresql-pubsub-schema-3.2.0.sql\n-----\n+\nAnd finally if you wish to use Socks5 Proxy component, add that schema:\n[source,sql]\n-----\npsql=# \\i database/postgresql-socks5-schema.sql\n-----\n\n=== Configuring From the Linux Shell Command Line\n\nFollow steps below to prepare the PostgreSQL database:\n\n. Add the +tigase_user+:\n+\n[source,sql]\n-----\ncreateuser -U admin_db_user -W -D -R -S -P tigase_user\n-----\n+\nYou will be asked for credentials for admin_db_user and password for new database user.\n. Create the database for the Tigase server with tigase_user as owner of database:\n+\n[source,sql]\n-----\ncreatedb -U admin_db_user -W -O tigase_user tigasedb\n-----\n. Load database schema to initialize the Tigase server from the file that corresponds to the Tigase version you want to use.\n+\n[source,sql]\n-----\npsql -q -U tigase_user -W tigasedb -f database/postgresql-schema-7-1.sql\npsql -q -U tigase_user -W tigasedb -f database/postgresql-pubsub-schema-3.2.0.sql\n-----\n+\nIf you want to use the socks5 proxy component, then add the following line:\n+\n[source,sql]\n-----\npsql -q -U tigase_user -W tigasedb -f database/postgresql-socks5-schema.sql\n-----\nThe above commands should be executed from the main Tigase directory. The initialization schema file should be also available locally in database/ directory of your Tigase installation.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_34_-_Database_Management_-_A_-_Database_Preperation_-_5_-_Prepare_Tigase_for_MongoDB.asciidoc",
"content": "[[mongoDBSupport]]\n= Preparing Tigase for MongoDB\n:author: not known\n:version: v1.0 October, 2015\n:date: 2015-01-10 12:22\n\n:toc:\n:numbered:\n:website: http://www.tiagse.org\n\nTigase now supports MongoDB for auth, settings, and storage repositories. If you wish to use MongoDB for Tigase, please use this guide to help you.\n\n== Dependencies\n\nTo run Tigase MongoDB support library requires drivers for MongoDB for Java which can be downloaded from link:https://github.com/mongodb/mongo-java-driver/releases[here]. This driver needs to be placed in +/jars+ directory located in Tigase XMPP Server installation directory.\n\n== Configuration\n\n=== Configuration of user repository for Tigase XMPP Server\n\nTo configure Tigase XMPP Server to use MongoDB you need to set +--user-db-uri=+ in etc/init.properties file to proper MongoDB URI pointing to which MongoDB database should be used (it will be created by MongoDB if it does not exist).\n+--user-db+ property should not be set to let Tigase XMPP Server autodetect proper implementation of +UserRepository+. Tigase XMPP Server will create proper collections in MongoDB if they do not exist so no schema files are necessary.\n\nExample configuration of XMPP Server pointing to MongoDB database +tigase_test+ in a local instance:\n[source,bash]\n-----\n--user-db-uri=mongodb://localhost/tigase_test\n-----\nIf Tigase Server is not able to detect a proper storage layer implementation, it can be forced to use one provided by Tigase using the following lines in +etc/init.properties+ file:\n-----\n--user-db=tigase.mongodb.MongoRepository\n--auth-db=tigase.mongodb.MongoRepository\n-----\nEvery component should be able to use proper implementation to support MongoDB using this URI. Also MongoDB URI can be passed as any URI in configuration of any component.\n\n=== Configuration for MUC\nBy default, MUC component will use MongoDB to store data if Tigase is configured to use it as a default store. However, if you would like to use a different MongoDB database to store MUC message archive, you can do this by adding the following line to +etc/init.properties+ file:\n[source]\n-----\nmuc/history-db-uri=mongodb://localhost/tigase_test\n-----\nIf MUC components fails to detect and use a proper storage layer for MongoDB, you can force it to use one provided by Tigase by using the following line in the +init.properties+ file:\n-----\nmuc/history-db=tigase.mongodb.muc.MongoHistoryProvider\n-----\n\n=== Configuration for PubSub\nBy default, PubSub component will use MongoDB to store data if Tigase is configured to use it as a default store. However, if you would like to use a different MongoDB database to store PubSub component data, you can do this by adding the following line to +etc/init.properties+ file:\n[source]\n-----\npubsub/pubsub-repo-url=mongodb://localhost/tigase_test\n-----\nIf the PubSub components fails to detect and use a proper storage layer for MongoDB, you can force it to use one provided by Tigase by using the following line in the +init.properties+ file:\n-----\npubsub/pubsub-repo-class=tigase.mongodb.pubsub.PubSubDAOMongo\n-----\n\n=== Configuration for Message Archiving\nBy default, the Message Archiving component will use MongoDB to store data if Tigase is configured to use it as a default store. However, if you would like to use a different MongoDB database to store message archives, you can do this by adding the following line to +etc/init.properties+ file:\n[source]\n-----\nmessage-archive/archive-repo-uri=mongodb://localhost/tigase_test\n-----\nIf Message Archiving component fails to detect and use a proper storage layer for MongoDB, you can force it to use one provided by Tigase by using the following line in the +init.properties+ file:\n-----\nmessage-archive/archive-repo-class=tigase.mongodb.archive.MongoMessageArchiveRepository\n-----\n\n== Schema Description\nThis description contains only basic description of schema and only basic part of it. More collections may be created if additional components of Tigase XMPP Server are loaded and configured to use MongoDB.\n\n=== Tigase XMPP Server Schema\nBasic schema for UserRespository and AuthRepository consists of two collections:\n. tig_users - contains list of users\n. tig_nodes - contains data related to users in tree-like way\n\n+tig_users+ collection contains the following fields:\n\n.tig_users\n[width=\"50%\",options=\"header\"]\n|=====================================================================\n|Name\t |Description\n|_id\t |id of user which is SHA256 hash of users jid (raw byte array)\n|user_id\t |contains full user jid\n|domain\t |domain to which user belongs for easier lookup of users by domain\n|password\t |password of user (or hash of password)\n|=====================================================================\n\n+tig_nodes+ collection contains the following fields\n\n.tig_nodes\n[width=\"50%\",options=\"header\"]\n|=====================================================================\n|Name\t |Description\n|_id\t |id of row autogenerated by MongoDB\n|uid\t |id of user which is SHA256 hash of users jid (raw byte array)\n|node\t |full path of node in tree-like structure separated by / (may not exist)\n|key\t |key for which value for node is set\n|value\t |value which is set for node key\n|=====================================================================\n\nTigase XMPP Server also uses additional collections for storage of Offline Messages\n\n.msg_history collection\n[width=\"50%\",options=\"header\"]\n|=====================================================================\n|Name\t |Description\n|from\t |full user jid of message sender\n|from_hash\t|SHA256 hash of message sender jid as raw byte array\n|to\t |full users jid of message recipient\n|to_hash\t|SHA256 hash of message recipient full jid as raw byte array\n|ts\t |timestamp of message as date\n|message\t|serialized XML stanza containing message\n|expire-at\t|timestamp of expiration of message (if message contains AMP expire-at set)\n|=====================================================================\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_35_-_Database_Management_-_B_-_Hashed_User_Passwords_in_Database.asciidoc",
"content": "[[hashedPasswords]]\n= Hashed User Passwords in Database\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2012-10-09 03:13\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nBy default, user passwords are stored in plain-text in the Tigase's database. However, there is an easy way to have them encoded in either one of already supported ways or to even add a new encoding algorithm on your own.\n\nStoring passwords in hashed format in the database makes it possible to avoid using a plain-text password authentication mechanism. You cannot have hashed passwords in the database and non-plain-text password authentication. On the other hand, the connection between the server and the client is almost always secured by SSL/TLS so the plain-text password authentication method is perhaps less of a problem than storing plain-text passwords in the database.\n\nNevertheless, it is simple enough to adjust this in Tigase's database and we will add an option in the Tigase installer to allow you to make the decision on install.\n\n== Shortcut\nConnect to your database from a command line and execute following statement for MySQL database:\n\n[source,sql]\n-----\ncall TigPutDBProperty('password-encoding', 'encoding-mode');\n-----\n\nWhere encoding mode is one of the following:\n\n- *MD5-PASSWORD* the database stores MD5 hash code from the user's password.\n- *MD5-USERID-PASSWORD* the database stores MD5 hash code from concatenated user's bare JID and password.\n- *MD5-USERNAME-PASSWORD* the database stores MD5 hash code from concatenated user's name (localpart) and password.\n\nFor example:\n\n[source,sql]\n-----\ncall TigPutDBProperty('password-encoding', 'MD5-PASSWORD');\n-----\n\n== Full Route\nThe way passwords are stored in the DB is controlled by Tigase database schema property. Properties in the database schema can be set by a stored procedure called: +TigPutDBProperty(key, value)+. Properties from the DB schema can be retrieved using another stored function called: +TigGetDBProperty(key)+.\n\nThe simplest way to call them is via command-line interface to the database.\n\nFor the purpose of this guide let's say we have a MySQL database and a test account: *test@example.com* with password *test77*.\n\nBy default, most of DB actions for Tigase, are performed using stored procedures including user authentication. So, the first thing to do is to make sure the stored procedures are working correctly.\n\n=== Create a Test User Account\nTo add a new user account we use a stored procedure: +TigAddUserPlainPw(bareJid, password)+. As you can see there is this strange appendix to the procedure name: *PlainPw*. This procedure accepts plain passwords regardless how it is stored in the database. So it is safe and easy to use either for plain-text passwords or hashed in the DB. There are also versions of procedures without this appendix but they are sensitive on the data format and always have to pass password in the exact format it is stored in the database.\n\nSo, let's add a new user account:\n\n[source,sql]\n-----\ncall TigAddUserPlainPw('test@example.com', 'test77');\n-----\n\nIf the result was 'Query OK', then it means the user account has been successfully created.\n\n=== Test User Authentication\nWe can now test user authentication:\n\n[source,sql]\n-----\ncall TigUserLoginPlainPw('test@example.com', 'test77');\n-----\n\nIf authentication was successful the result looks like this:\n\n[source,sql]\n---------------------\n+--------------------+\n| user_id |\n+--------------------+\n| 'test@example.com' |\n+--------------------+\n1 row in set (0.01 sec)\n\nQuery OK, 0 rows affected (0.01 sec)\n---------------------\n\nIf authentication was unsuccessful, the result looks like this:\n\n[source,sql]\n----------\n+---------+\n| user_id |\n+---------+\n| NULL |\n+---------+\n1 row in set (0.01 sec)\n\nQuery OK, 0 rows affected (0.01 sec)\n----------\n\n=== Password Encoding Check\n+TigGetDBProperty+ is a function, not a procedure in MySQL database so we have to use select to call it:\n\n[source,sql]\n-----\nselect TigGetDBProperty('password-encoding');\n-----\n\nMost likely output is this:\n\n[source,sql]\n----------------------------------------\n+---------------------------------------+\n| TigGetDBProperty('password-encoding') |\n+---------------------------------------+\n| NULL |\n+---------------------------------------+\n1 row in set, 1 warning (0.00 sec)\n----------------------------------------\n\nWhich means a default password encoding is used, in plain-text and thus no encoding. And we can actually check this in the database directly:\n\n[source,sql]\n-----\nselect uid, user_id, user_pw from tig_users where user_id = 'test@example.com';\n-----\n\nAnd expected result with plain-text password format would be:\n\n[source,sql]\n-------------------------------------\n+-----+--------------------+---------+\n| uid | user_id | user_pw |\n+-----+--------------------+---------+\n| 41 | 'test@example.com' | test77 |\n+-----+--------------------+---------+\n1 row in set (0.00 sec)\n-------------------------------------\n\n=== Password Encoding Change\nNow let's set password encoding to MD5 hash:\n\n[source,sql]\n-----\ncall TigPutDBProperty('password-encoding', 'MD5-PASSWORD');\n-----\n\n'Query OK', means the password encoding has been successfully changed. Of course we changed the property only. All the existing passwords in the database are still in plain-text format. Therefore we expect that attempt to authenticate the user would fail:\n\n[source,sql]\n----------\ncall TigUserLoginPlainPw('test@example.com', 'test777');\n+---------+\n| user_id |\n+---------+\n| NULL |\n+---------+\n1 row in set (0.00 sec)\n\nQuery OK, 0 rows affected (0.00 sec)\n----------\n\nWe can fix this by updating the user's password in the database:\n\n[source,sql]\n---------------------\n\ncall TigUpdatePasswordPlainPw('test@example.com', 'test777');\nQuery OK, 1 row affected (0.01 sec)\n\nmysql> call TigUserLoginPlainPw('test@example.com', 'test777');\n+--------------------+\n| user_id |\n+--------------------+\n| 'test@example.com' |\n+--------------------+\n1 row in set (0.00 sec)\n\nQuery OK, 0 rows affected (0.00 sec)\n---------------------\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_36_-_Database_Management_-_C_-_Tigase_Server_and_Multiple_Databases.asciidoc",
"content": "[[multidb]]\n= Tigase Server and Multiple Databases\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2012-10-02 04:23\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nSplitting user authentication data from all other XMPP information such as roster, vcards, etc... was almost always possible in Tigase XMPP Server. Possible and quite simple thing to configure. Also it has been always possible and easy to assign a different database for each Tigase component (MUC, PubSub, AMP), for recording the server statistics. Almost every data type or component can store information in a different location, simple and easy to setup through the configuration file.\n\nHowever it is much less known that it is also possible to have a different database for each virtual domain. This applies to both the user repository and authentication repository. This allows for very interesting configuration such as user database sharding where each shard keeps users for a specific domain, or physically split data based on virtual domain if each domain refers to a different customer or group of people.\n\nHow can we do that then?\n\nThis is very easy to do through the Tigase's configuration file.\n\nTypically the well known lines:\n\n[source,sh]\n-----\n--auth-db=tigase-custom\n--auth-db-uri=jdbc:mysql://db1.tigase/dbname?user&password\n--user-db=mysql\n--user-db-uri=jdbc:mysql://db2.tigase/dbname?user&password\n-----\n\nDefine just a default databases for both user repository and authentication repository. Default means it is used when there is no repository specified for a particular virtual domain. However, you can have a separate, both user and authentication repository for each virtual domain.\n\nHere is, how it works:\n\n[source,sh]\n-----\n# First, let's define our default database for all VHosts\n--auth-db=tigase-custom\n--auth-db-uri=jdbc:mysql://db1.tigase/dbname?user&password\n--user-db=mysql\n--user-db-uri=jdbc:mysql://db2.tigase/dbname?user&password\n\n# Now, we have VHost: domain1.com\n# User authentication data for this VHost is stored in Drupal database\n--auth-db[domain1.com]=drupal\n--auth-db-uri[domain1.com]=jdbc:mysql://db7.tigase/dbname?user&password\n# All other user data is stored in Tigase's standard database in MySQL\n--user-db[domain1.com]=mysql\n--user-db-uri[domain1.com]=jdbc:mysql://db4.tigase/dbname?user&password\n\n# Next VHost: domain2.com\n# User authentication is in LDAP server\n--auth-db[domain2.com]=tigase.db.ldap.LdapAuthProvider\n# Pretty standard Tigase's definition for the database (repository)\n# connection string\n--auth-db-uri[domain2.com]=ldap://ldap.domain2.com:389\n# Now is something new, we have a custom authentication repository\n# settings for a single domain.\n# Please note how we define the VHost for which we set custom parameters\nbasic-conf/auth-repo-params/domain2.com/user-dn-pattern=cn=,ou=,dc=,dc=\n# All other user data is stored in the same as default repository\n--user-db[domain2.com]=mysql\n--user-db-uri[domain2.com]=jdbc:mysql://db2.tigase/dbname?user&password\n\n# Next VHost: domain3.com\n# Again user authentication is in LDAP server but pointing to\n# a different LDAP server with different access credentials\n--auth-db[domain3.com]=tigase.db.ldap.LdapAuthProvider\n# Pretty standard Tigase's definition for the database\n# (repository) connection string\n--auth-db-uri[domain3.com]=ldap://ldap.domain3.com:389\n# Now is something new, we have a custom authentication\n# repository settings for a single domain\n# Please note how we define the VHost for which we set custom parameters\nbasic-conf/auth-repo-params/domain3.com/user-dn-pattern=cn=,ou=,dc=,dc=\n# All other user data is stored on the domain3 server in PostgreSQL database\n--user-db[domain3.com]=pgsql\n--user-db-uri[domain3.com]=jdbc:pgsql://db.domain3.com/dbname?user&password\n\n# For VHost: domain4.com all the data, both authentication and\n# user XMPP data are stored on a separate\n# MySQL server with custom stored procedures for both user\n# login and user logout processing.\n--auth-db[domain4.com]=tigase-custom\n--auth-db-uri[domain4.com]=jdbc:mysql://db14.domain4.com/dbname?user&password\nbasic-conf/auth-repo-params/domain4.com/user-login-query={ call UserLogin(?, ?) }\nbasic-conf/auth-repo-params/domain4.com/user-logout-query={ call UserLogout(?) }\nbasic-conf/auth-repo-params/domain4.com/sasl-mechs=PLAIN,DIGEST-MD5\n--user-db[domain4.com]=mysql\n--user-db-uri[domain4.com]=jdbc:mysql://db14.domain4.com/dbname?user&password\n-----\n\nAs you can see, it requires some writing but flexibility is very extensive and you can setup as many separate databases as you need or want. If one database (recognized by the database connection string) is shared among different VHosts, Tigase still uses a single connection pool, so it won't create an excessive number of connections to the database.\n\nI hope this helps with more complex setups and configuration cases.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_37_-_Database_Management_-_D_-_Importing_User_Data.asciidoc",
"content": "[[dbImportingData]]\n= Importing User Data\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 21:18\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nYou can easily copy data between Tigase compatible repositories that is repositories for which there is a database connector. However, it is not that easy to import data from an external source. Therefore a simple data import functionality has been added to repository utilities package.\n\nYou can access repository utilities through command +./bin/repo.sh+ or +./scripts/repo.sh+ depending on whether you use a binary package or source distribution.\n\n+-h+ parameter gives you a list of all possible parameters:\n\n[source,sh]\n-------------\n./scripts/repo.sh -h\n\nParameters:\n -h this help message\n -sc class source repository class name\n -su uri source repository init string\n -dc class destination repository class name\n -du uri destination repository init string\n -dt string data content to set/remove in repository\n -u user user ID, if given all operations are only for that ID\n if you want to add user to AuthRepository parameter must\n in form: \"user:password\"\n -st perform simple test on repository\n -at simple test for adding and removing user\n -cp copy content from source to destination repository\n -pr print content of the repository\n -n data content string is a node string\n -kv data content string is node/key=value string\n -add add data content to repository\n -del delete data content from repository\n ------------\n -roster check the user roster\n -aeg [true|false] Allow empty group list for the contact\n -import file import user data from the file of following format:\n user_jid, password, roser_jid, roster_nick, subscription, group\n\n\n\nNote! If you put UserAuthRepository implementation as a class name\n some operation are not allowed and will be silently skipped.\n Have a look at UserAuthRepository to see what operations are\n possible or what operation does make sense.\n Alternatively look for admin tools guide on web site.\n-------------\n\nThe most critical parameters are the source repository class name and the initialization string. Therefore there are a few example preset parameters which you can use and adjust for your system. If you look inside the +repo.sh+ script you can find at the end of the script following lines:\n\n[source,sh]\n-----\nXML_REP=\"-sc tigase.db.xml.XMLRepository -su ../testsuite/user-repository.xml_200k_backup\"\nMYSQL_REP=\"-sc tigase.db.jdbc.JDBCRepository -su jdbc:mysql://localhost/tigase?user=root&password=mypass\"\nPGSQL_REP=\"-sc tigase.db.jdbc.JDBCRepository -su jdbc:postgresql://localhost/tigase?user=tigase\"\n\njava $D -cp $CP tigase.util.RepositoryUtils $MYSQL_REP $*\n-----\n\nYou can see that the source repository has been set to MySQL database with +tigase+ as the database name, +root+ the database user and +mypass+ the user password.\n\nYou can adjust these settings for your system.\n\nNow to import data to your repository simply execute the command:\n\n[source,sh]\n-----\n./bin/repo.sh -import import-file.txt\n-----\n\n_Note, the import function is available from_ *b895*\n\nThe format of the import file is very simple. This is a flat file with comma separated values:\n\n[source,bash]\n-----\njid,password,roster_jid,roster_nick,subscriptio,group\n-----\n\nTo create such a file from MySQL database you will have to execute a command like this one:\n\n[source,sql]\n-----\nSELECT a, b, c, d INTO OUTFILE 'import-file.txt'\nFIELDS TERMINATED BY ','\nLINES TERMINATED BY '\\n'\nFROM test_table;\n-----\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_38_-_Database_Management_-_E_-_Integrating_Existing_Databases.asciidoc",
"content": "[[existingData]]\n= Importing Existing Data\n:author: Daniel Wisnewski\n:version: v1.0 October, 2015\n:date: 2015-05-10 13:35\n\nInformation about importing user data from other databases.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_39_-_Database_Management_-_E_-_Integrating_Existing_Databases_-_1_-_Connecting_Tigase_Server_to_MySQL_Database.asciidoc",
"content": "[[connectingTigaseToMysql]]\n= Connecting the Tigase Server to MySQL Database\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 21:16\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nPlease before continuing reading of this manual have a look at the xref:prepareMysql[initial MySQL database setup]. It will help you with database preparation for connecting with Tigase server.\n\nThe easiest way to setup Tigase server for connecting with MySQL database is to use the xref:tigase3xconfiguration[configuration wizards] (configuration generators) which release you from manually editing the XML configuration file and allow you quickly regenerate the XML configuration file in case of problems.\n\nThe article describes an older way for using configuration generators which is a bit more difficult and doesn't work on Windows systems. The guide below describes a new way to use them which is simpler and can be applied to Windows systems as well. It is using the +init.properties+ file where you can put all your initial configuration parameters.\n\nThis guide describes MySQL database connection parameters.\n\nThis guide is actually very short as there are example configuration files which can be used and customized for your environment.\n\nUnfortunately these files are not included yet in the server version 3.x binary release and you have to download them from the SVN repository using following links:\n\n. link:https://projects.tigase.org/projects/tigase-server/repository/changes/etc/tigase-mysql.conf[tigase-mysql.conf] - the Tigase server startup file. The only difference from the default one is that it points to the file described below to load initial parameters.\n. link:https://projects.tigase.org/projects/tigase-server/repository/changes/etc/init-mysql.properties[init-mysql.properties] - the file contains a few initial parameters which can/should be adjusted to your environment. Here is a content of the file with each line described:\n+\n[source,bash]\n-----\n# Load standard set of the server components.\n# Look at the http://www.tigase.org/configuration-wizards\n# document for other possible values. Normally you don't\n# need to change this line.\nconfig-type=--gen-config-def\n# List of administrator accounts, please replace them with\n# administrator accounts in your installation\n--admins=admin@tigase.org,admin@test-d\n# The line says that the database used by the Tigase server is 'mysql'\n# Look at the configuration wizards article for different options\n# You can also put here a Java class name if you have a custom\n# implementation for a database connector.\n--user-db=mysql\n# The line contains the database connection string. This is database\n# specific string and for each kind of database it may look differently.\n# Below string is for MySQL database. Please modify it for your system.\n# MySQL connector requires connection string in the following format:\n# jdbc:mysql://[hostname]/[database name]?user=[user name]&password=[user password]\n--user-db-uri=jdbc:mysql://localhost/tigasedb?user=tigase_user&password=mypass\n# Virtual domains for your server installation, comma separated list of vhosts\n--virt-hosts=tigase.org,test-d,localhost\n# Select what packages you want to have logging switched for\n# The below setting is recommended for the initail setup and it is required\n# when asking for help with setting the server up\n--debug=server\n-----\n\nDownload both files and put them to your +etc/+ directory.\n\nEdit the +init-mysql.properties+ for your environment.\n\nRemove the XML configuration file.\n\nStart the server using following command:\n\n[source,sh]\n-----\n./bin/tigase.sh start etc/tigase-mysql.conf\n-----\n\n_Ask more questions if you got stuck or need any help with this._\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_40_-_Database_Management_-_E_-_Integrating_Existing_Databases_-_2_-_Integrating_Tigase_Server_with_Drupal.asciidoc",
"content": "[[integrateWithDrupal]]\n= Integrating Tigase Server with Drupal\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 21:16\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nTigase supports integration with Drupal on many levels. At the moment this guide can work with Drupal version 4.x and 5.x. They may also work with Drupal 6.x but this version hasn't been tested.\n\nFirst of all, Tigase can authenticate users against a Drupal database which means you have the same user account for both Drupal website and the XMPP server. Moreover in such a configuration all account management is done via Drupal web interface like account creation, password change update user details and so on. Administrator can temporarily disable user account and this is followed by Tigase server too.\n\n== Connecting to Drupal Database\nThe best way to setup Tigase with Drupal database is via configuration wizards that is +init.properties+ file where you can put initial setting for Tigase configuration.\n\nIf you look in +etc/+ directory of your Tigase installation you should find a few files there. The one we want to base our configuration on is: +init-mysql.properties+. In some older packages the file might be missing, then you can download it from the link:https://projects.tigase.org/projects/tigase-server/repository/changes/etc/init-mysql.properties[SVN repository].\n\nIf you look inside the file and strip all the comments you would see following lines:\n\n[source,bash]\n-----\nconfig-type=--gen-config-def\n--admins=admin@tigase.org,admin@tigase.net\n--user-db=mysql\n--user-db-uri=jdbc:mysql://localhost/tigasedb?user=tigase_user&password=mypass\n--virt-hosts=tigase.org,tigase.net\n--debug=server\n-----\n\nAll you need to connect to Drupal database are 2 following lines:\n\n[source,bash]\n-----\n--auth-db=drupal\n--auth-db-uri=jdbc:mysql://localhost/drupal?user=drupalusr&password=drupalpass\n-----\n\nLet's combine it in a single file called +etc/init-drupal.properties+:\n\n[source,bash]\n-----\nconfig-type=--gen-config-def\n--admins=admin@tigase.org,admin@tigase.net\n--auth-db=drupal\n--auth-db-uri=jdbc:mysql://localhost/drupal?user=drupalusr&password=drupalpass\n--user-db=mysql\n--user-db-uri=jdbc:mysql://localhost/tigasedb?user=tigase_user&password=mypass\n--virt-hosts=tigase.org,tigase.net\n--debug=server\n-----\n\nIn theory you can load Tigase database schema to Drupal database and then both +db-uris+ would have the same database connection string. More details about setting up and connecting to MySQL database can be found in the xref:prepareMysql[MySQL guide].\n\nYou need also to edit +etc/tigase.conf+ file to point to your newly created properties file. The last line which looks like this:\n\n[source,bash]\n-----\nTIGASE_OPTIONS=\" --property-file etc/init.properties \"\n-----\n\nshould be changed to following:\n\n[source,bash]\n-----\nTIGASE_OPTIONS=\" --property-file etc/init-drupal.properties \"\n-----\n\nMake sure you have Java-6 installed and +JAVA_HOME+ is set to the correct location. If +JAVA_HOME+ is not set you can add following line to +etc/tigase.conf+ file:\n\n[source,bash]\n-----\nJAVA_HOME=\"/your/java-6-location\"\n-----\n\nThe best way to check whether the variable is set correctly is with command:\n\n[source,sh]\n-----\n$ ls -l $JAVA_HOME/bin/java\n-----\n\nshould list you the file without error.\n\nCheck also if the +logs/+ directory is created in your Tigase server location as sometimes unpacking application doesn't create empty directories.\n\nNow when you have the configuration file and databases ready to use you can start the Tigase server with the following command:\n\n[source,sh]\n-----\n./bin/tigase.sh start etc/tigase.conf\n-----\n\nIf you run the Tigase server installed from sources the command would be:\n\n[source,sh]\n-----\n./scripts/tigase.sh start etc/tigase.conf\n-----\n\nThere are system startup scripts for Gentoo and Mandriva Linux on +bin/+ or +scripts/+ directory which can be used to automatically start the server when system starts.\n\nNow you can register an account on your Drupal website and connect with an XMPP client using the account details.\n\n*Note!* _You have to enable plain password authentication in your XMPP client to connect to Tigase server with Drupal database_\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_41_-_Database_Management_-_E_-_Integrating_Existing_Databases_-_3_-_Integrating_Tigase_Server_with_LibreSource.asciidoc",
"content": "[[integrateWithLibreSource]]\n= Integrating Tigase Server With LibreSource\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 21:16\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\n*This document is still not finished.*\n\nTaken directly from link:http://dev.libresource.org/[LibreSource] page:\n\n_LibreSource is a collaborative platform dedicated to both software development and community building. Based on Java/J2EE technology, LibreSource is a modular web server that users can customize online by combining resources and rights: wiki pages, forum, trackers, files, download areas, etc. All the tools are included and integrated._\n\n== Short Introduction\nIntegration between *Tigase* server and *LibreSource* is on a database level. It is implemented in the same way as integration with *Drupal* but with slightly more functions available.\n\nBasically LibreSource system maintains own database with all it's data and Tigase connects to LibreSource database to authenticate users. All user data specific to XMPP service are kept in separate tables which can be located in the same database as LibreSource data or in different database.\n\nCurrent list of features included in the integration:\n\n- XMPP users authentication against user data stored in LibreSource database.\n- Recording XMPP user on-line status in LibreSource database. This can be displayed on the Web page as additional user info.\n- Recording user last login time and this information can also be available on Web page.\n- Checking user account status. So if the user account is disabled in LibreSource system then this user will not be able to login to XMPP service too.\n- User account creation. This feature might be useful during testing time or user data transition from an old Tigase installation to LibreSource system. _Please note! This feature should be normally disabled on live system. All user account management should be done from LibreSource system because of data caching._\n- User account deletion. _Please note! This feature should be normally disabled on live system. All user account management should be done from LibreSource system because of data caching._\n\nA few assumptions:\n\n. LibreSource data are kept in PostgreSQL database - +libresource+ and database user is demo.\n. For use in cases where Tigase data are stored in MySQL database name is tigase, database user is dbuser and database user password is +dbpass+\n\n== How to set Tigase up\nNow we will focus on setting things up to have both services up and running together. Below is example of the most complex environment to run where LibreSource is using PostgreSQL database and Tigase is using a MySQL database. All basic user data needed for authentication is kept by LibreSource, so Tigase has to connect to PostgreSQL database also in order to authenticate users.\n\n. First you need LibreSource system up and running. Please refer to LS documentation for details.\n. Install Tigase server in the normal way including loading Tigase database schema. Database tables used by Tigase server use different naming convention so you can simply load Tigase DB schema to the same database as LibreSource data. It is also possible and recommended to keep Tigase data in separate database.\n. Using configuration wizards generate configuration for Tigase server to connect to LibreSource database. Here is the sample file with parameters for configuration wizard assuming following setup:\n - LibreSource data are kept in PostgreSQL database: +libresource,+ user: +demo+\n - Tigase data are kept in MySQL database: +tigase+, user: +dbuser+, password: +dbpass+\n - No external components are connected to Tigase server\n - Tigase works for domain: +domain.net+\n+\n[source,bash]\n-----\nENC=\"-Dfile.encoding=UTF-8 -Dsun.jnu.encoding=UTF-8\"\nDRV=\"-Djdbc.drivers=com.mysql.jdbc.Driver:org.postgresql.Driver\"\n\nJAVA_OPTIONS=\"${ENC} ${DRV} -server -Xms100M -Xmx100M \"\nTIGASE_CONFIG=\"etc/tigase-mysql-libresource.xml\"\nTIGASE_OPTIONS=\"--gen-config-def \\\n --user-db mysql \\\n --user-db-uri jdbc:mysql://localhost/tigase?user=dbuser&password=dbpass&autoCreateUser=true \\\n --auth-db libresource \\\n --auth-db-uri jdbc:postgresql://localhost/libresource?user=demo \\\n --virt-hosts domain.net,localhost \"\n-----\n. A simpler example where all data (LibreSource and Tigase) are stored in the same database:\n - LibreSource data are kept in PostgreSQL database: +libresource+, user: +demo+\n - Tigase data are kept also in PostgreSQL database: +libresource+, user: +demo+\n - No external components are connected to Tigase server\n - Tigase works for domain: +domain.net+\n+\n[source,bash]\n-----\nENC=\"-Dfile.encoding=UTF-8 -Dsun.jnu.encoding=UTF-8\"\nDRV=\"-Djdbc.drivers=com.mysql.jdbc.Driver:org.postgresql.Driver\"\n\nJAVA_OPTIONS=\"${ENC} ${DRV} -server -Xms100M -Xmx100M \"\nTIGASE_CONFIG=\"etc/tigase-mysql-libresource.xml\"\nTIGASE_OPTIONS=\"--gen-config-def \\\n --user-db pgsql \\\n --user-db-uri jdbc:postgresql://localhost/libresource?user=demo&autoCreateUser=true \\\n --auth-db libresource \\\n --auth-db-uri jdbc:postgresql://localhost/libresource?user=demo \\\n --virt-hosts domain.net,localhost \"\n-----\n\nNow, you can run Tigase as normal and it all works.\n\n*Note!* _You have to load Tigase database schema for user data. Please refer to guide for specific database: xref:mysql2database[MySQL] or xref:postgresDB2[PostgreSQL]._\n\n== Migration From an old Tigase Installation to LibreSource\nTigase package includes additional tools to make it easier to manage and control you installation. One is used to change configuration settings - +config.sh+ and another is used to manipulate user data in repository - +repo.sh+.\n\nDepending on whether you use Tigase version built from sources or binary version these scripts might be available in either +scripts/+ or +bin/+ subdirectories. To make things simpler let's assume they are stored in +scripts/+ directory.\n\nAssuming you have an old Tigase server installation with number of users in MySQL database and you want to migrate all of them to LibreSource there are 2 steps involved:\n\n. User data migration\n. Changing your existing configuration\n\n=== Data Migration\nFirst we need to migrate user data used for authentication. That data will be used by both services: _LibreSource_ and _Tigase_ and they normally stored in _LibreSource_ database. Therefore we have to use _LibreSource_ database connector to handle the data (write or read). _Tigase_ server will be using _LibreSource_ database for reading only but during migration time we need to write user accounts to LS database. Sample command to migrate user accounts looks like this:\n\n[source,sh]\n-----\n./scripts/repo.sh -sc tigase.db.jdbc.JDBCRepository \\\n -su \"jdbc:mysql://localhost/tigase?user=dbuser&password=dbpass\" \\\n -dc tigase.db.jdbc.LibreSourceAuth \\\n -du \"jdbc:postgresql://localhost/libresource?user=demo\" \\\n -cp\n-----\n\nThe above command will copy all user accounts from MySQL tigase database to +libresource+ database. Please refer to repository management tool documentation for information how to migrate single or selected user accounts.\n\nIf you want to keep all Tigase server data in the same database you have to copy also all other user data like rosters, vCards and so on.\n\nFirst thing we have to do is load the database schema for Tigase data. Because Tigase tables have distinct names from LibreSource, there is no danger for any conflict. As in the above example let's assume LibreSource's data is stored in libresource database and database user name is +demo+:\n\n[source,sh]\n-----\npsql -q -U demo -d libresource -f database/postgresql-schema.sql\n-----\n\nNow we can load and transfer all user data from MySQL database to LibreSource:\n\n[source,sh]\n-----\n./scripts/repo.sh -sc tigase.db.jdbc.JDBCRepository \\\n -su \"jdbc:mysql://localhost/tigase?user=dbuser&password=dbpass\" \\\n -dc tigase.db.jdbc.JDBCRepository \\\n -du \"jdbc:postgresql://localhost/libresource?user=demo\" \\\n -cp\n-----\n\nThis command looks siumilar to the previous one. Just a Java class used for handling destination database is different.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_42_-_Database_Management_-_E_-_Integrating_Existing_Databases_-_4_-_MySQL_Database_Use.asciidoc",
"content": "[[mysql2database]]\n= MySQL Database Use\n:author: Artur Hefczyc \n:date: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 21:16\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nThis guide describes how to configure Tigase server to use link:http://www.mysql.com/[MySQL] database as a user repository.\n\nIf you used an XML based user repository before you can copy all user data to MySQL database using repository management tool. All steps are described below.\n\n== MySQL Database Preparation\nTo load db schema to your MySQL instance first create database:\n\n[source,sh]\n-----\nmysqladmin -p create tigase\n-----\n\nAnd then you can load database schema:\n\n[source,sh]\n-----\nmysql -u dbuser -p tigase < mysql-schema.sql\n-----\n\n== Server Configuration\nNow you have to change configuration to load a jdbc module instead of XML based repository. Using configuration management script, first change class name handling repository.\n\nTo see current settings run command:\n\n[source,sh]\n-----\n$ ./scripts/config.sh -c tigase-config.xml -print -key session_1/user-repo-class\n-----\n\nAs a result you should see something like:\n\n[source,sh]\n-----\nsession_1/user-repo-class = tigase.db.xml.XMLRepository\n-----\n\nYou can see that current setting points to the XML repository implementation. To use jdbc module for connecting to MySQL database you have to set tigase.db.jdbc.JDBCRepository class (enter text below in one line):\n\n[source,sh]\n-----\n$ ./scripts/config.sh -c tigase-config.xml -print -key session_1/user-repo-class -value tigase.db.jdbc.JDBCRepository -set\n-----\n\nAs a result you will see new value set for the parameter:\n\n[source,bash]\n-----\nsession_1/user-repo-class = tigase.db.jdbc.JDBCRepository\n-----\n\nYou have also to set the same value as authorization repository unless you want to use different authorization data source:\n\n[source,sh]\n-----\n $ ./scripts/config.sh -c tigase-config.xml -print -key session_1/auth-repo-class -value tigase.db.jdbc.JDBCRepository -set\n-----\n\nAnd again as a result we can see:\n\n[source,bash]\n-----\nsession_1/auth-repo-class = tigase.db.jdbc.JDBCRepository\n-----\n\nNext step is to set the database connection string. Assuming you have database: *tigase* on *localhost* with database user: *dbuser* and password *dbpass* your connection string will look like this:\n\n[source,bash]\n-----\njdbc:mysql://localhost/tigase?user=dbuser&password=dbpass\n-----\n\nTo set this in your configuration file, you have to the configuration management script 2 times. First for user data repository and second for authorization data repository:\n[source,sh]\n-----\n$ ./scripts/config.sh -c tigase-config.xml -print -key session_1/user-repo-url -value \"jdbc:mysql://localhost/tigase?user=dbuser&password=dbpass\" -set\n$ ./scripts/config.sh -c tigase-config.xml -print -key session_1/auth-repo-url -value \"jdbc:mysql://localhost/tigase?user=dbuser&password=dbpass\" -set\n-----\n\n*Note quotes around connection string.* They are needed to make sure the shell won't interpret special characters.\n\nNow the configuration is ready to load the jdbc module and connect to your database.\n\nOne more thing you need to do is to tell JVM which jdbc driver to use to connect to database. Depending on your MySQL and jdbc installation it might be: +com.mysql.jdbc.Driver.+ To set is as database driver you have to set is a jdbc.drivers property value. Usually you do this by adding -D parameter to Java call:\n\n[source,sh]\n-----\n $ java -Djdbc.drivers=com.mysql.jdbc.Driver tigase.server.XMPPServer\n-----\n\nIf you use tigase.sh script to run server you will have to add +-Djdbc.drivers=com.mysql.jdbc.Driver+ to the startup script +init.Properties+ property file to +JAVA_OPTIONS+ values.\n\n== User Data Import\nIf you previously used an XML based user repository, you can import all data into a MySQL database using repository management tool. This is quite long command so let me list all required parameters first with brief explanation:\n\n. *-cp* copy content of the source repository to destination repository.\n. *-sc* *tigase.db.xml.XMLRepository* source repository class.\n. *-su* *user-repository.xml* source repository connection string - assuming your user repository is in +user-repository.xml+ file.\n. *-dc* *tigase.db.jdbc.JDBCRepository* destination repository class.\n. *-du* *\"jdbc:mysql://localhost/tigase?user=dbuser&password=dbpass\"* destination repository connection string.\n\nAnd now whole command. Enter all in one line:\n\n[source,sh]\n-----\n$ ./scripts/repo.sh -cp -sc tigase.db.xml.XMLRepository -su user-repository.xml -dc tigase.db.jdbc.JDBCRepository -du \"jdbc:mysql://localhost/tigase?user=dbuser&password=dbpass\"\n-----\n\nFor more information how to use command line administration tools refer to xref:commandLineTools2[command line tools guide.]\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_43_-_Database_Management_-_E_-_Integrating_Existing_Databases_-_5_-_PostgreSQL_Database.asciidoc",
"content": "[[postgresDB2]]\n= PostgreSQL Database Use\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 21:16\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nThis guide describes how to configure Tigase server to use link:http://www.postgresql.org/[PostgreSQL] database as a user repository.\n\nIf you used an XML based user repository before you can copy all user data to PostgreSQL database using repository management tool. All steps are described below.\n\n== PostgreSQL Database Preparation\nCreate new database user account which will be used to connect to your database:\n\n[source,sh]\n-----\n# createuser\nEnter name of user to add: tigase\nShall the new user be allowed to create databases? (y/n) y\nShall the new user be allowed to create more new users? (y/n) y\n-----\n\nNow using new database user account create database for your service:\n\n[source,sh]\n-----\n# createdb -U tigase tigasedb\nCREATE DATABASE\n-----\n\nNow you can load the database schema:\n\n[source,sh]\n-----\n# psql -U tigase -d tigasedb -f postgresql-schema.sql\n-----\n\nNow the database is ready for Tigase server to use.\n\n== Server Configuration\nServer configuration is identical as MySQL database setup. The same jdbc module is used to connect to PostgreSQL database as for MySQL. The only difference is the connection string which usually looks like:\n\n[source,bash]\n-----\njdbc:postgresql://localhost/tigasdb?user=tigase\n-----\n\nSo for more detailed guide how to change configuration refer to xref:mysql2database[MySQL database use guide] or if you look for a more automatic configuration file generation refer to xref:3xconfiguration[configuration wizards] page.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_44_-_Database_Management_-_F_-_Schema_Updates.asciidoc",
"content": "[[oldVerSchemas]]\n= Schema Updates\n:author: Daniel wisnewski\n:version: v1.0, October 2015\n:date: 2015-10-05 13:41\n\nThis is a repository for Schema updates in case you have to upgrade from older installations.\n\n\n- xref:tigaseServer71[Tigase Server Schema v7.1 Updates] Applies to v7.1.0 and v7.2.0\n- xref:tigase51schemaupgrade[Upgrades to v5.1 of Tigase]\n. xref:derby51upgrade[Derby Database Schema Upgrade for Tigase 5.1]\n. xref:mysql51upgrade[MySQL Database Schema Upgrade for Tigase 5.1]\n. xref:postgresql51upgrade[PostgreSQL Database Schema Upgrade for Tigase 5.1]\n- xref:tigase40schemaUpgrade[MySQL Database Schema Upgrade for Tigase 4.0]\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_45_-_Database_Managament_-_F_-_Schema_Updates_-_A_-_Tigase_Server_7.1.asciidoc",
"content": "[[tigaseServer71]]\n= Tigase Server Schema v7.1 Updates\n:author: Daniel Wisnewski\n:version: v1.0 October 2015\n:Date: 2015-10-12 15:36\n\n:numbered:\n:website: http://www.tigase.org\n\n[[v710notice]]\n== *FOR ALL USERS UPGRADING TO v7.1.0 FROM A v7.0.2 INSTALLATION*\nThe schema has changed for the main database, and the pubsub repository. In order to upgrade to the new schemas, you will need to do the following: +\n\n1. Upgrade the Main database schema to v7.1 using the database/${DB_TYPE}-schema-upgrade-to-7-1.sql file\n\n2. Upgrade the Pubsub Schema to v3.1.0 using the database/${DB_TYPE}-pubsub-schema-3.1.0.sql file\n\n3. Upgrade the Pubsub Schema to v3.2.0 using the database/${DB_TYPE}-pubsub-schema-3.2.0.sql file\n\nAll three commands may be done at the same time in that order, it is suggested you make a backup of your current database to prevent data loss.\n\n\n== Tigase Schema Change for v7.1\nTigase has made changes to its database to include primary keys in the tig_pairs table to improve performance of the Tigase server. This is an auto-incremented column for Primary Key items appended to the previous schema.\n\n*You MUST update your database to be compliant with the new v7.1 schema. If you do not, Tigase will not function properly.*\n\n_This change will affect all users of Tigase using v7.1.0 and newer._\n\nIf you are installing a new version of v7.1.0 on a new database, the schema should automatically be installed.\n\nFirst, shut down any running instances of Tigase to prevent conflicts with database editing. Then from command line use the DBSchemaLoader class to run the -schema-upgrade-to-7.1.sql file to the database. The command is as follows:\n\nIn a linux environment\n[source,bash]\n-----\njava -cp \"jars/*\" tigase.util.DBSchemaLoader -dbHostname ${HOSTNAME} -dbType ${DB_TYPE} -rootUser ${ROOT_USER} -dbPass ${DB_USER_PASS} -dbName ${DB_NAME} -schemaVersion ${DB_VERSION} -rootPass ${ROOT_USER_PASS} -dbUser ${DB_USER} -adminJID \"${ADMIN_JID}\" -adminJIDpass ${ADMIN_JID_PASS} -logLevel ALL -file database/${DB_TYPE}-schema-upgrade-to-7-1.sql\n-----\n\nIn a windows environment\n[source,bash]\n-----\njava -cp jars/* tigase.util.DBSchemaLoader -dbHostname ${HOSTNAME} -dbType ${DB_TYPE} -rootUser ${ROOT_USER} -dbPass ${DB_USER_PASS} -dbName ${DB_NAME} -schemaVersion ${DB_VERSION} -rootPass ${ROOT_USER_PASS} -dbUser ${DB_USER} -adminJID \"${ADMIN_JID}\" -adminJIDpass ${ADMIN_JID_PASS} -logLevel ALL -file database/${DB_TYPE}-schema-upgrade-to-7-1.sql\n-----\n\nAll variables will be required, they are as follows: +\n\n* ${HOSTNAME} - Hostname of the database you wish to upgrade. +\n* ${DB_TYPE} - Type of database [derby, mysql, postgresql, sqlserver]. +\n* ${ROOT_USER} - Username of root user. +\n* ${ROOT_USER_PASS} - Password of specified root user. +\n* ${DB_USER} - Login of user that can edit database. +\n* ${DB_USER_PASS} - Password of the specified user. +\n* ${DB_NAME} - Name of the database to be edited. +\n* ${DB_VERSION} - In this case, we want this to be 7.1. +\n* ${ADMIN_JID} - Bare JID of a database user with admin privileges. Must be contained within quotation marks. +\n* ${ADMIN_JID_PASS} - Password of associated admin JID. +\n\nPlease note that the SQL file for the update will have an associated database with the filename. i.e. postgresql-update-to-7.1.sql for postgresql database.\n\nA finalized command will look something like this:\n[source,bash]\n-----\njava -cp \"jars/*\" tigase.util.DBSchemaLoader -dbHostname localhost -dbType mysql -rootUser root -rootPass root -dbUser admin -dbPass admin -schemaVersion 7.1 -dbName Tigasedb -adminJID \"admin@local.com\" -adminJIDPass adminpass -logLevel ALL -file database/mysql-schema-upgrade-to-7.1.sql\n-----\n\nOnce this has successfully executed, you may restart you server. Watch logs for any db errors that may indicate an incomplete schema upgrade.\n\n\n[[pubSub71]]\n== Changes to Pubsub Schema\nTigase has had a change to the PubSub Schema, to upgrade to PubSub Schema v7.1 without having to reform your databases, use this guide to update your databases to be compatible with the new version of Tigase.\n\n*NOTE* Current PubSub Schema is v3.2.0, you will need to repeat these instructions for v3.1.0 and then v3.2.0 before you run Tigase V7.1.0.\n\nThe PubSub Schema has been streamlined for better resource use, this change affects all users of Tigase.\nTo prepare your database for the new schema, first be sure to create a backup! Then apply the appropriate PubSub schema to your MySQL and it will add the new storage procedure.\n\nAll these files should be in your /database folder within Tigase, however if you are missing the appropriate files, use the links below and place them into that folder.\n\nThe MySQL schema can be found link:https://projects.tigase.org/projects/tigase-pubsub/repository/revisions/master/entry/database/mysql-pubsub-schema-3.1.0.sql[Here].\n\nThe Derby schema can be found link:https://projects.tigase.org/projects/tigase-pubsub/repository/changes/database/derby-pubsub-schema-3.1.0.sql[Here].\n\nThe PostGRESQL schema can be found link:https://projects.tigase.org/projects/tigase-pubsub/repository/changes/database/postgresql-pubsub-schema-3.1.0.sql[Here].\n\nThe MS SQL schema can be found link:https://projects.tigase.org/projects/tigase-pubsub/repository/changes/database/sqlserver-pubsub-schema-3.1.0.sql[Here].\n\nThe same files are also included in all distributions of v7.1.0 in +[tigaseroot]/database/+ . All changes to database schema are meant to be backward compatible.\n\n\nYou can use a utility in Tigase to update the schema using the following command from the Tigase root:\nLinux\n-----\njava -cp \"jars/*\" tigase.util.DBSchemaLoader\n-----\nor from a Windows environment\n-----\njava -cp jars/* tigase.util.DBSchemaLoader\n-----\n*NOTE: Some variation may be necessary depending on how your java build uses -cp option*\n\nUse the following options to customize. Options in bold are required.::\n* *[-dbType database_type {derby, mysql, postgresql, sqlserver}]*\n* [-schemaVersion schema version {4, 5, 5-1} ]\n* *[-dbName database name]*\n* [-dbHostname database hostname] (default is localhost)\n* [-dbUser tigase username]\n* [-dbPass tigase user password]\n* *[-rootUser database root username]*\n* *[-rootPass database root password]*\n* *[-file path to sql schema file]*\n* [-query sql query to execute]\n* [-logLevel java logger Level]\n* [-adminJID comma separated list of admin JIDs]\n* [-adminJIDpass password (one for all entered JIDs]\n\n*Arguments take following precedent: query, file, whole schema*\n\nAs a result your final command should look something like this:\n-----\njava -cp \"jars/*\" tigase.util.DBSchemaLoader -dbType mysql -dbName tigasedb -dbUser root -dbPass password -file database/mysql-pubsub-schema-3.1.0.sql\n-----\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_46_-_Database_Management_-_F_-_Schema_Updates_-_B_-_Tigase_Server_Version_5.x.asciidoc",
"content": "[[tigase51schemaupgrade]]\n= Tigase 5.1 Database Schema Upgrade\n:author: Wojciech Kapcia \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2012-07-16 11:10\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nWe had to make a small change to the database schema for Tigase version 5.1.0.\n\nIt does not affect data or data structure, only the way in which some data is accessed in database. We added one more stored procedure which has to be installed in database if you upgrade your installation from a previous Tigase version\n\nThe schema upgrade is very simple and safe but make sure the current database schema is in version 4.0.\nIf you happen to use ancient version of Tigase earlier than 4.0 and you want to upgrade to 5.1, you have to run xref:tigase40schemaupgrade[4.0 upgrade script] first.\n\nPlease follow detailed guide for the database applicable to your installation: xref:derby51upgrade[Derby], xref:mysql51upgrade[MySQL], xref:postgresql51upgrade[PostgreSQL].\n\n- xref:derby51upgrade[Derby Database Schema Upgrade for Tigase 5.1]\n- xref:mysql51upgrade[MySQL Database Schema Upgrade for Tigase 5.1]\n- xref:postgresql51upgrade[PostgreSQL Database Schema Upgrade for Tigase 5.1]\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_47_-_Database_Management_-_F_-_Schema_Updates_-_B_-_Tigase_Server_Version_5.x_-_1_-_Derby.asciidoc",
"content": "[[derby51upgrade]]\n= Derby Database Schema Upgrade for Tigase 5.1\n:author: Wojciech Kapcia \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2012-06-20 19:12\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nThe schema upgrade is very simple and safe but make sure the current database schema is in version 4.0.\n\nFirst things first - make a database backup:\n\n[source,sh]\n-----\ntar -czf derbyDB.tar.gz /path/to/derbyDB\n-----\n\nIf you need to restore database for any reason simply extract files from the backup archive:\n\n[source,sh]\n-----\nrm -rf /path/to/derbyDB\ntar -xf derbyDB.tar.gz\n-----\n\nNow we can run schema upgrade script\n\n[source,sh]\n-----\njava -Dij.protocol=jdbc:derby: -Dij.database=\"/path/to/derbyDB\" \\\n\t\t-Dderby.system.home=`pwd` \\\n\t\t-cp libs/derby.jar:libs/derbytools.jar:jars/tigase-server.jar \\\n\t\torg.apache.derby.tools.ij database/postgresql-schema-upgrade-to-5-1.sql\n-----\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_48_-_Database_Management_-_F_-_Schema_Updates_-_B_-_Tigase_Server_Version_5.x_-_2_-_MySQL_Database_Schema_Upgrade_for_Tigase_5.1.asciidoc",
"content": "[[mysql51upgrade]]\n= MySQL Database Schema Upgrade for Tigase 5.1\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2012-04-21 03:58\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nThe schema upgrade is very simple and safe but make sure the current database schema is in version 4.0.\n\nAssumptions:\n\n. *tigasedb* is a database name\n. *tigase_user* is a database user name\n. *mypass* is database user password\n\nFirst things first - make a database backup:\n\n[source,sh]\n-----\nmysqldump -u tigase_user -pmypass tigasedb > tigasedb_dump.sql\n-----\n\nIf you need to restore database for any reason execute following commands:\n\n[source,sh]\n-----\nmsyqladmin -u tigase_user -pmypass drop tigasedb\nmysqladmin -u tigase_user -pmypass create tigasedb\nmysql -u tigase_user -pmypass tigasedb < tigasedb_dump.sql\n-----\n\n_Note! You may be required to use root user and his password to execute mysqladmin commands._\n\nNow we can run schema upgrade script\n\n[source,sh]\n-----\nmysql -u tigase_user -pmypass tigasedb < database/mysql-schema-upgrade-to-5-1.sql\n-----\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_49_-_Database_Management_-_F_-_Schema_Updates_-_B_-_Tigase_Server_Version_5.x_-_3_-_PostgreSQL_Database_Schema_Upgrade_for_Tigase_5.1.asciidoc",
"content": "[[postgresql51upgrade]]\n= PostgreSQL Database Schema Upgrade for Tigase 5.1\n:author: Andrzej Wojcik \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2012-06-16 11:03\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nThe schema upgrade is very simple and safe but make sure the current database schema is in version 4.0.\n\nAssumptions:\n\n- *tigasedb* is a database name\n- *tigase_user* is a database user name\n- *admin_db_user* is database admin user name\n\nFirst things first - make a database backup:\n\n[source,sql]\n-----\npg_dump -U tigase_user -W tigasedb > tigasedb_dump.sql\n-----\n\nIf you need to restore database for any reason execute following commands:\n\n[source,sql]\n-----\ndropdb -U admin_db_user -W tigasedb\ncreatedb -U admin_db_user -W -O tigase_user tigasedb\npsql -U tigase_user -W tigasedb < tigasedb_dump.sql\n-----\n\nNow we can run schema upgrade script\n\n[source,sql]\n-----\npsql -q -U tigase_user -W tigasedb -f database/postgresql-schema-upgrade-to-5-1.sql\n-----\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_51_-_Database_Management_-_F_-_Schema_Updates_-_C_-_Tigase_Server_Version_4.x.asciidoc",
"content": "[[tigasev4x]]\n= Tigase Server Version 4.x\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-01-06 20:22\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nSchema Upgrades for Tigase server version 4.x.\n\n- xref:tigase40schemaUpgrade[MySQL Database Schema Upgrade for Tigase 4.0]\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_52_-_Database_Management_-_F_-_Schema_Updates_-_C_-_Tigase_Server_Version_4.x_-_1_-_MySQL_Database_Schema_Upgrade_for_Tigase_4.0.asciidoc",
"content": "[[tigase40schemaupgrade]]\n= MySQL Database Schema Upgrade for Tigase 4.0\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-01-06 20:18\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nFor number of reasons the database schema had to be changed for Tigase server version 4.0. The most important are:\n\n- Compliance with the XMPP RFC which says that each part of JID may have up to 1023 characters. We store in the database user JIDs without resource names thus the maximum possible size of the user id is 2047. There aren't really JIDs that long yet, but we experienced quite long JIDs in a few installations already. So it was decided to prepare Tigase to accept any JID allowed by RFC.\n\n- Performance and flexibility - the Tigase server now accesses database using stored procedures. This allows for any database storage format and it doesn't really matter for Tigase server what is the database schema how data is organized inside. What it needs is just bunch of stored procedures to access the data. This allows for much more flexibility in storing user data as well as much easier integration with third-party systems as well as organize data in more efficient way.\n\nTherefore when you run the Tigase server now it may (depending on what exact SVN revision you use) refuse to start if it detects that the database schema is not updated. If it happens just follow steps below to update the database schema and start the server again. Updating of the database schema is very easy and almost fully automated process. Just follow the steps below and you should be able to run the new version of Tigase server in a few minutes or even seconds depending on your database size. It took around 7 minutes to update our database with 200k user accounts on an average machine.\n\n*Note. Do not update the database schema before Tigase server tells you to do so. Be sure to do a database backup before starting the schema update.*\n\n_Please note. I have done a few schema upgrades already in a few different configurations and here are a few tips which might be useful if something goes wrong:_\n\n. *You really, REALLY have to do the DB backup (database dump) before upgrading.* _If you don't you might not be able to revert database on your own._\n. _In case of error:_ *ERROR 1419 (HY000) at line 31 in file: 'database/mysql-schema-4-sp.schema': You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)* _Restore the database following description found below and run the update again as MySQL super user._\n. _The following error may manifest itself in many ways from the NullPointerException in Tigase server log file to message like this:_ *User does not have access to metadata required to determine stored procedure parameter types. If rights can not be granted, configure connection with \"noAccessToProcedureBodies=true\" to have driver generate parameters that represent INOUT strings irregardless of actual parameter types.* _The best solution to this is to grant proper permissions to this user. Enter the MySQL command line mode as MySQL super user:_\n+\n[source,sql]\n-----\n$ mysql -u root -proot_passwd mysql\nmysql> GRANT SELECT, INSERT, UPDATE ON \\`mysql\\`.\\`proc\\` TO 'tigase_user'@'localhost';\nmysql> GRANT SELECT, INSERT, UPDATE ON \\`mysql\\`.\\`proc\\` TO 'tigase_user'@'%';\nmysql> GRANT SELECT, INSERT, UPDATE ON \\`mysql\\`.\\`proc\\` TO 'tigase_user';\nmysql> FLUSH PRIVILEGES;\n$\n-----\n\nAssumptions:\n\n. *tigasedb* is a database name\n. *tigase_user* is a database user name\n. *mypass* is database user password\n\nFirst things first - make a database backup:\n\n[source,sh]\n-----\nmysqldump -u tigase_user -pmypass tigasedb > tigasedb_dump.sql\n-----\n\nIf you need to restore database for any reason execute following commands:\n\n[source,sh]\n-----\nmsyqladmin -u tigase_user -pmypass drop tigasedb\nmysqladmin -u tigase_user -pmypass create tigasedb\nmysql -u tigase_user -pmypass tigasedb < tigasedb_dump.sql\n-----\n\n_Note! You may be required to use_ *root* _user and password to execute mysqladmin commands. Ok we have the database backup and we know how to restore it. Now we can run schema upgrade script:_\n\n[source,sh]\n-----\nmysql -u tigase_user -pmypass tigasedb < database/mysql-schema-upgrade-to-4.sql\n-----\n\n_The script should generate output like this:_\n\n[source,sh]\n-----\nDroping index for user_id column\nResizing user_id column to 2049 characters to comply with RFC\nCreating a new index for user_id column for first 765 bytes of the field\nAdding sha1_user_id column\nAdding user_pw column\nAdding last_login column\nAdding last_logout column\nAdding online_status column\nAdding failed_logins column\nAdding account_status column\nCreating a new index for user_pw column\nCreating a new index for last_login column\nCreating a new index for last_logout column\nCreating a new index for account_status column\nCreating a new index for online_status column\nResizing node column to 255 characters\nChanging pval column type to mediumtext\nLoading stored procedures definitions\nSetting passwords encoding in the database\nConverting database to a new format\nCreating a new index for sha1_user_id column\nSetting schema version to 4.0\nAll done, database ready to use!\n-----\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_53_-_Components.asciidoc",
"content": "[[loadComponent]]\n= Configuring the Tigase Server to Load a Component\n\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 21:18\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nA detailed description of all the configuration options is in the +init.properties+ guide where you can also find information described below and much more. The purpose of this document is to give you a brief introduction on how to load a component into Tigase server without the need to dig through all the details.\n\nI will show how to load 2 components into Tigase server using a configuration in the init.properties file: link:https://projects.tigase.org/projects/tigase-muc[MUC] and link:https://projects.tigase.org/projects/tigase-pubsub[PubSub].\n\nThe only step is to tell the server what components to load, how to name them and optionally give some extra parameters. To do so open the +init.properties+ file you use in your installation.\n\nLet's say you want to just add PubSub for now. All you need to do is add 2 lines to the properties file:\n\n[source,bash]\n-----\n--comp-name-1=pubsub\n--comp-class-1=tigase.pubsub.PubSubComponent\n-----\n\nThe first line contains the component name 'pubsub' and the main class for this component is: 'tigase.pubsub.PubSubClusterComponent'. It doesn't really matter what the component name is, the only requirement is that it must be unique among other components names. Because you can load many components, it helps to provide descriptive names thus 'pubsub' is a good name for a 'PubSub' component.\n\nYou can of course add more components, even PubSub components to the same server. Just remember that each of them would need to have a different name then. For example:\n\n[source,bash]\n-----\n--comp-name-2=pubsub-priv\n--comp-class-2=tigase.pubsub.PubSubComponent\n-----\n\nAlthough this may be rare, it allows for wide compatibility and platform stability.\n\nNormally, however we want to load few different components like PubSub, MUC, MSN Transport and so on.... Therefore instead of the above second PubSub we can load the MUC component:\n\n[source,bash]\n-----\n--comp-name-2=muc\n--comp-class-2=tigase.muc.MUCComponent\n-----\n\nChanges to the init.properties file will take effect upon server restart.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_54_-_Components_-_A_-_StanzaSender.asciidoc",
"content": "[[stanzaSender]]\n= StanzaSender\n\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-04-06 21:18\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nStanzaSender is a component which makes it easier to integrate XMPP server with other third-party tools.\n\nIt simply allows you to send stanzas from your application without implementing any XMPP specific code. The component regularly reads specified data source for XMPP packets to send. The data source can be a SQL database, directory on your filesystem, or anything you might want.\n\nIf you have a Web application for example for which you want to send notifications of an event to selected users you can install link:https://projects.tigase.org/projects/tigase-server/repository/revisions/master/show/src/main/java/tigase/server/ssender[StanzaSender] component on your Tigase server. It will help you to easily distribute your messages to end-users.\n\n== How it Works\n\nThe module itself doesn't do anything, it just schedules tasks and sends stanzas which come from anywhere. To do the actual work of retrieving stanzas from data source the component uses *tasks*.\n\nIn theory the task can retrieve XMPP packets for sending from any location or may just generate stanzas on its own.\n\nIn practice there are 2 *tasks* already implemented and ready to use. You can treat them as a sample code for implementation of your own tasks customised for your specific needs or you can just use these tasks as they are.\n\nThe tasks which are available are:\n\n- +FileTask+ retrieving stanzas from directory in file system.\n- +JDBCTask+ retrieving stanzas from SQL database.\n\n=== FileTask\n\n+FileTask+ implements tasks for cyclic retrieving stanzas from a directory and sending them to the StanzaHandler object.\n\nIt looks for any new stanza to send. Any single file can contain only a single stanza to send and any entry in database table can also contain only a single stanza to send. Files on hard disk and records in databases are deleted after it is read.\n\nAny file in a given directory is treated the same way - Tigase assumes it contains valid XML data with XMPP stanza to send. You can however set in configuration, using wildchars which files contain stanzas. All stanzas must contain complete data including correct \"_from_\" and \"_to_\" attributes.\n\nBy default it is looking for +*.stanza+ files in +/var/spool/jabber/+ folder but you can specify different directory names in the initialization string. Here is a sample initialization strings:\n\n- +/var/spool/jabber/*.stanza+\n- +/var/spool/jabber/*+\n\nThe last is equal to:\n\n- +/var/spool/jabber/+\n\nNote the last forward slash '/' is required in such case if the last element of the path is a directory.\n\n*Please note! Tigase must have writing permissions for this directory, otherwise it may not function properly.*\n\n=== JDBCTask\n\n+JDBCTask+ implements tasks for cyclic retrieving stanzas from database and sending them to the StanzaHandler object.\n\nDatabase table format:\n\n- *id* - numerical unique record identifier.\n- *stanza* - text field containing valid XML data with XMPP stanza to send.\n\nAny record in this table is treated the same way - Tigase assumes it contains valid XML data with XMPP stanza to send. No other data are allowed in this table. All stanzas must be complete including correct \"_from_\" and \"_to_\" attributes.\n\nBy default it is looking for stanzas in +xmpp_stanza+ table, but you can specify a different table name in the connection string. For example:\n\n+jdbc:mysql://localhost/tigasedb?user=tigase&password=pass&table=xmpp_stanza+\n\nPlease note the last parameter which is specific to +JDBCTask+. You can specify the table name which stores stanzas for sending, if omitted default value is: +xmpp_stanza+.\n\n== Configuration\n\nStanzaSender is a Tigase component so the configuration is similar to that of all other components. The simplest way to get the settings for *StanzaSender* is by generating a configuration with all possible components. To do this you have to run Tigase server with +--gen-config-all+ parameter set.\n\nBy default this component name is *ssend* and here is a content of the configuration file for *StanzaSender*:\n\nIt is one of +msg-receivers+:\n\n[source,bash]\n-----\n\n ...\n \n\n-----\n\nTo activate the component and a specify class name for it following entries has been added:\n\n[source,bash]\n-----\n\n\n-----\n\nAnd the main settings section for the component:\n\n[source,bash]\n-----\n\n \n \n \n \n \n \n \n \n-----\n\nMost parameters should be pretty clear but some may need a little explanation.\n\n=== General +StanzaSender+ parameters:\n\n- *default-interval* number which specifies in seconds how often should the task look in data source for new packets to send.\n- *max-queue-size* is a number which specifies internal packets queue size. This is used to prevent the component from consuming all the memory for data in case the component can not process them.\n- *stanza-listeners* is a list of task names to load. Each task can read XMPP packets to send from different data sources. You can load as many listeners (tasks) as you need. Each task must read stanzas from different data sources.\n\nFor each task from the +stanza-listeners+ list there is a separate section with parameters for each task:\n\n- *active* boolean switch allowing you to turn on/off the task without removing configuration completely.\n- *class-name* Java class name which implements the task. This class must extend +tigase.server.ssender.SenderTask+ and it is loaded at runtime.\n- *init-string* is kind of data source connection string. For database it is just database connection string, for file system this is just a directory name. It may be even different for different tasks. The 2 tasks already implemented have some specific features: +FileTask+ allows you to use wild-chars in directory/ file name specification and +JDBCTask+ allows you to specify additional parameter at the end of JDBC connection string - database table name. For specific examples look at above config sections.\n- *interval* is a number which allows you to specify different interval in seconds for checking data source for each task.\n\n*NOTE:* Each task has own separate parameters list.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_55_-_Components_-_B_-_Tigase_HTTP_API.asciidoc",
"content": "= Tigase HTTP API\n:author: Daniel Wisnewski & Andrzej Wójcik\n:version: v1.2 August 2015\n:date: 2015-23-08 10:13\n\n:toc:\n:numbered:\n:website: http://www.tigase.org\n\nWelcome to the Tigase HTTP API users guide. The HTTP API allows you to manage, configure, chat, and send commands to Tigase server using a simple, easy-to-use interface right from your browser!\nWe will guide you through setup, running, and going through some features of the HTTP API.\n\n== Requirements\nThe HTTP API Requires Tigase version v5.0.3 but we recommend using the latest version of Tigase which will give you the easiest setup and functionality.\nCurrent versions of Tigase include most of the required files needed to run the API, however you will need to add one more library: servlet-api-3.1.jar which is available link:https://projects.tigase.org/attachments/download/1504/servlet-api-3.1.jar[Here].\nPlace that file in your /jars directory and you're all setup and good to go.\n\n*Please note, earlier versions of Tigase installer may have not included another required file: javax.servlet-api.jar*\n\nThis file is included in the archive distributions, and may be extracted to the /jars directory from there.\n\nFor older versions of the API, please see link:https://projects.tigase.org/projects/tigase-http-api/wiki/Dependencies[the Tigase HTTP API Wiki].\n\n== Setup & Configuration\nOnce all the requirements in place, all you need to do is add the following lines to Tigase's init.properties file:\n[source,properties]\n----\n--comp-name-3=http\n--comp-class-3=tigase.http.HttpMessageReceiver\n----\nNote that the class and name number is not important, so long as you don't have anything else with the same number.\n\nWith this default configuration Tigase will attempt to start an http server at port 8080 and run the default modules such as RestModule which will add context for the REST API in /rest path.\nRestModule will also load all groovy scripts located in scripts/rest/xxx directories and it will bind it to proper action for the /rest/xxx/ paths. More than one directory can be used, think of xxx as a wildcard.\n\n=== Advanced Configuration\nThe HTTP component has a variety of configuration options, lets see them in detail here\n\n[[httpCompProp]]\n==== Component Properties\nPlease note, for settings mentioning {compname} replace them with the exact text found as --comp-name, which may be http, rest, or something you have set custom in init.properties.\n\n{compname}/http/ports[i]=8088,8096::\n Sets a comma separated list of ports on which the HTTP server listens for connections. 8080 is set by default.\n\n{compname}/2222/socket=ssl::\n Sets the port you wish the HTTP server to listen to for HTTPS connections to 2222\n\n{compname}/4096/domain=example.com::\n Sets 4096 as the port number you want to listen to HTTPS connections *AND* set the domain name of the SSL certificate from Tigase XMPP server certificate store to be used.\n\n{compname}/server-class=::\n Sets the name of the class used to manage the HTTP server. The following names may be used\n * *tigase.http.jetty.JettyStandaloneHttpServer* - starts standalone Jetty HTTP Server instance *(requires Tigase HTTP API - Jetty HTTP Server)*\n * *tigase.http.jetty.JettyOSGiHttpServer* - uses Jetty HTTP Server instance available as OSGi service (may be used only in OSGi envoirment) *(requires Tigase HTTP API - Jetty HTTP Server)*\n * *tigase.http.java.JavaStandaloneHttpServer* - uses HttpServer provided by Java JDK to start standalone HTTP server (may not work on JDK from every JDK provider)\n\n{compname}/http/port::\n An older version of the /ports[i] setting, it is still supported, but expect to be phased out.\n\n{compname}/setup/admin-credentials::\n Sets a user and password combination that can access the web installer setup pages. By default administrator JIDs listed in --admins property are granted access, however you may specifiy a specific user and password to give access in addition to those JIDs. +\n Format is [username:password] So for example, _http/setup/admin-credentials=admin:password_ +\n Note that this stores the information in *plaintext on init.properties file*, and *this is an optional setting*.\n\n==== Modules\nTigase HTTP API component provides functionalities as modules which may be enabled or disabled and configured separately.\nCommon settings for modules which can be passed in component properties in following format component_name/module_id/module_setting:\n\n- active[B]= Values true/false to enable or disable module\n- context-path= Path of HTTP context under which module should be available\n- vhosts[s]= Comma separated list of virtual hosts under which the module should be availble. If this setting is not set, the HTTP module will be available for all virtual hosts.\n\nWith those ideas in mind, lets look at the available modules for the HTTP API.\n\n===== Rest Module\nThis module provides support for the REST API. enable it by using this line in the init.properties file:\n----\nhttp/RestModule/active[B]=true\n----\nAssuming that comp-name for the class is +http+\n\nrest-scripts-dir=::\n Path to directory containing scripts processing REST requests. By default this directory is scripts/rest\napi-keys[s]=::\n Comma separated list of strings which would be possible to use as keys to pass api-key parameter to request an authorization to execute.\n If nothing is passed, then no request will be allowed. To allow any request, this property needs to be set to +open_access+.\n\n===== DNS Webservice Module\n\n+dns-webservice+ module provides support for resolution of DNS names using the HTTP protocol. This might be useful for web applications that need to resolve DNS address to a specific IP. For example, discover IP and port of WebSocket service to use to connect to XMPP server.\n\nTo activate this module, use the following line;\n[source,properties]\n----\nhttp/dns-webservice/active[B]=true\n----\nAssuming that comp-name for the class is +http+\n\n== Use of the HTTP API\nTo begin using the HTTP API, point a browser to the following url\nhttp://your.server.domain:8080/ui/ and you will be presented with the following image to login with.\n\nimage:images/http-login.jpg[]\n\nUse your admin-level XMPP id and it's password to login. Please use bare JID for logins.\n\n*NOTE: Normal users can login here as well to use chat and basic functions, but they will not have admin privileges as shown in this guide*\n\n== Browser interface walk-through\n\n=== Chat\n\nChat is the first window that you will see after logging in. It's quite bare here since there is no roster to speak of. If you had a roster, users would be shown.\nLets add a user. Click the user add icon, and then fill in the fields below.\n\nimage:images/http-add-new.jpg[]\n\nOnce both users have added and authorized each other's roster listing, the users and groups will be shown on the left, with the right side being used for chat functionality.\n\nimage:images/http-chat.jpg[]\n\n=== Discovery\nThe Discovery tab encapsulates the service discovery function of XMPP servers, and will provide a list of available services. Clicking on the service will give you options for executing commands, checking settings, MUC rooms and more.\n\n=== Management\nThe Management tab is your administration and settings tool for the XMPP server. Here you can change settings, add and remove users, send server-wide notifications, write and execute scripts, and even obtain server statistics at a glance.\n\n*NOTE: some changes to settings may be instant, and others require a server restart*\n\n=== Statistics\nThe statistics tab lists all running components in the server.\n\n== HTTP API Scripting\nScripts in the HTTP API component are used for processing all of requests.\n\nTo add a new action to HTTP API component you need to create a script in Groovy in which there is an implementation of class extending tigase.http.rest.Handler class. The URI of the script will be created from the location of script in scripts folder.\nFor example, if TestHandler script with regular a expression will be set to +/test+ and will be placed in +scripts/rest/tested+, the handler will be called for following URI +/rest/tested/test+.\n\n=== Properties\nIf you are extending classes, you will need to set the following properties:\n\nregex::\n regular expression which is used to match request URI and parse parameters embedded in URI, example below:\n\n /\\/([^@\\/]+)@([^@\\/]+)/\n\n\nrequiredRole::\n Role of the user required to be able to access this URI. Available values: null, \"user\", \"admin\". If requiredRole is not null, authentication will be required.\n\nisAsync::\n If set to true, it will be possible to wait for results, perhaps waiting for an IQ stanza to send results.\n\n=== Properties Containing Closures\nExtended class should also set closures for one or more of the following properties: +execGet+, +execPut+, +execPost+, and +execDelete+ depending on which HTTP action or actions you need to support for the following URI. Each closure *has dynamic arguments lists*.\nBelow is a list of arguments passed to closure which describes how and when the list of arguments change.\n\nI) *service*:\n Implementation of Service interface, used to access database or send/recieve XMPP stanzas.\n\nII) *callback*:\n Closure which needs to be called to return data. Accepts only one argument of type +String,byte[],Map+. If data is type of Map it will be encoded to JSON or XML depending on 'Content-Type' header.\n\nIII) *user*:\n Will be passed only if +requiredRole+ is not null. *In other cases this argument will not be in arguments list!*\n\nIV) *content*:\n Parsed content of the request. *Will not be in arguments list if Content-Length of request is empty*. If Content-Type is of XML or JSON type, type returned as Map. Otherwise it will be an instance of +HttpServletRequest+.\n\nV) *x*:\n Additional arguments passed to callback are groups from regular expression matching URI. *Groups are not passed as list, but are added to a list of arguments as next arguments*.\n\nIf the property for corresponding HTTP action is not set, the component will return a 404 HTTP error.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_56_-_Components_-_B_-_Tigase_HTTP_API_-_1_-_REST_API_Guide.asciidoc",
"content": "[[restAPI]]\n= REST API & HTTP Guide\n:author: many people\n:date: 2015-11-09 10:22\n:version: v1.0 September 2015\n\n:toc:\n:numbered:\n:website: http://www.tigase.org\n\nThis component covers both REST API as well as basic HTTP component configuration.\nREST stands for REpresentational State Transfer which is a stateless communication method that in our case passes commands using HTTP GET, PUT, POST, and DELETE commands to resources within the Tigase server.\nAlthough REST uses HTTP to receive commands, REST itself is not intended for use in a browser.\n\n== Setup & Configuration\nTigase's REST component requires the following in classpath\n\n- +servlet-api-3.1.jar+\n\nIf you have installed Tigase v7.1.0 or later, the jar is already installed. If you are using an older version of Tigase, you may download the file from link:https://projects.tigase.org/attachments/download/1504/servlet-api-3.1.jar[this link].\nOnce this is installed, you will also need to add the following lines in your init.properties file to enable the HTTP component.\n\n[source,bash]\n------\n--comp-name-4=http\n--comp-class-4=tigase.http.HttpMessageReceiver\n------\nIn this default configuration, Tigase will try to start a standalone Jetty HTTP server at port 8080 and start up the default modules, including +RestModule+ which will add context for REST API in the /rest path. +RestModule+ will also load all groovy scripts located in +scripts/rest/*+ directories and will bind them to proper actions for the +/rest/*+ paths.\n\n*NOTE:* Scripts that handle HTTP requests are available in the component repository in +src/scriopts/groovy/tigase/rest/+ directory.\n\n=== Component Properties\nHere are some additional properties for the +HttpMessageReceiver+ component that can be set in the init.properties file.\n\n- +{compname}/http/ports[i]=+ - Sets a comma separated list of ports on which the HTTP server will listen for connections. Default is 8080.\n- +{compname}/*********/socket=ssl+ - Sets the port for SSL connections, replace ### with the port number of your choice.\n- +{compname}/*********/domain=example.com+ - This sets the domain name of the SSL certificate from Tigase XMPP certificate store, also sets the port to ### to listen for HTTPS connections.\n- +{compname}/server-class=+ - Sets the name of the class used to manage the HTTP server. Currently there are the following options:\n. +tigase.http.JettyStandaloneHttpServer+ - Starts standalone Jetty HTTP Server instance *(requires Tigase HTTP API - Jetty HTTP Server)*\n. +tigase.http.jetty.JettyOSGIHttpServer+ - Uses Jetty HTTP Server instance available as OSGi service (may be used only in OSGi envoirment) *(require Tigase HTTP API - Jetty HTTP Server)*\n. +tigase.http.java.JavaStandaloneHttpServer+ - Uses +HttpServer+ provided by Java JDK to start standalone HTTP server (may not work on JDK from every JDK provider).\n. +{compname}/http/threads=+ - Sets the number of threads available for HTTP component. Default is 4.\n. +{compname}/http/request-timeout=+ - Sets the timeout time in ms for threads to close on inactive connections. Default is 60 seconds.\n\n=== Modules\nTigase's REST Component comes with two modules that can be enabled, disabled, and configured separately.\nCommon settings for modules for component properties are used in the following format: +component_name/module_id/module_setting/+\nthe following settings are available for both listed modules:\n\n- +active[B]+ - Boolean values true/false to enable or disable the module.\n- +context-path+ - Path of HTTP context under which the module should be available.\n- +vhosts[s]+ - Comma separated list of virtual hosts for which the module should be available. If not configured, the module will be available for all vhosts.\n\n==== Rest Module\nThis is the Module that provides support for the REST API.\nAvailable properties:\n\n- +rest-scripts-dir+ - Provides ability to specify path to scripts processing REST requests if you do not wish to use default (scripts/rest).\n- +api-keys[s]+ - Comma separated list of strings which would be possible to use as keys to pass +api-key+ parameter to request authorization for request execution. If nothing is passed, then no request will be allowed. To allow any request, this property needs to be set using the following:\n-----\nhttp/rest/api-keys[s]=open_access\n-----\nYou may set api-keys to any string you wish, however, when you make requests of the HTTP API service, the included API key must match *EXACTLY*. Keep the API key to ASCII characters to maintain compatibility. For example, if you were to set the following API key:\n-----\nhttp/rest/api-key[s]=a7D2dm3lps138w\n-----\nRequests made to the HTTP service must conclude with the same key: +http://localhost:8080/rest/adhoc/sess-man@domain.com?api-key=a7D2dm3lps138w+\n\n==== +dns-webservice+\nThis module provides resolution of DNS names using HTTP protocol. This particular module might be useful for web applications that need to resolve the DNS address to a particular IP. For example to help discover the IP and port of WebSocket services used to connect to the XMPP server.\n\n== Usage Examples\nHere are some examples using the HTTP API using available scripts.\n\n=== Retrieving list of available ad-hoc commands\nTo retrieve a list of available commands, REST needs to use the GET method from the following resource: +/rest/adhoc/sess-man@domain.com+. This provides a list of available adhoc commands from the sess-man@domain.com resource. This can be change to any bare JID that you wish to get commands from so it can be a MUC room, monitor component, or in this case, the Session manager.\nWith the server running, lets connect to the address +http://localhost:8080/rest/+ and the following resource +/adhoc/sess-man@domain.com+ which will retrieve a list of all ad-hoc commands available at sess-man@domain.com. This particular action is protected by authentication using HTTP basic authentication so valid credentials are necessary. User credentials are available in the Tigase's user database installation, so use the bare JID and password of an admin-authorized account to conduct this activity.\nThe result will be an XML format output of available commands, similar to an IQ stanza, below an example of that result.\n\n[source,xml]\n-----\n\n \n sess-man@domain.com\n http://jabber.org/protocol/admin#get-active-users\n Get list of active users\n \n \n sess-man@domain.com\n del-script\n Remove command script\n \n \n sess-man@domain.com\n add-script\n New command script\n \n\n-----\n\nThere is also the ability to return a JSON formatted result. To achieve this, you need to pass +Content-Type: application/json+ to the HTTP header of the request, or add the +type+ parameter and set it to +application/json+ setting. An example of a JSON result is below.\n[source,java]\n-----\n{\n \"items\": [\n {\n \"jid\": \"sess-man@domain.com\",\n \"node\": \"http://jabber.org/protocol/admin#get-active-users\",\n \"name\": \"Get list of active users\"\n },\n {\n \"jid\": \"sess-man@domain.com\",\n \"node\": \"del-script\",\n \"name\": \"Remove command script\"\n },\n {\n \"jid\": \"sess-man@domain.com\",\n \"node\": \"add-script\",\n \"name\": \"New command script\"\n }\n ]\n}\n-----\nAgain, either of these methods can be used on any component with available ad-hoc commands. Feel free to experiment and see what options are available for each component.\n\n=== Executing ad-hoc commands\nOnce you have found a command you wish to use, you can send that command using the HTTP POST method. In this example, lets request a list of active users as seen in the previous section. *NOTE:* like the previous example, these commands require basic HTTP authentication.\n\nThe following command is sent to +http://localhost:8080/rest/adhoc/sess-man@domain.com+\n[source,xml]\n-----\n\n http://jabber.org/protocol/admin#get-active-users\n \n \n domainjid\n domain.com\n \n \n max_items\n 25\n \n \n\n-----\nThis particular command reqiures the three fields ++, +domainjid+, and +max_items+. These three values are the node for the command, as returned in available commands, the domain results are to be returned from, and the maximum number of results. Keep in mind that +Content-type: text/xml+ must be passed to the HTTP header to get an XML result. Not doing so may yield errors or incomprehensible results.\nThe result for this command will look like this:\n\n[source,xml]\n-----\n\n sess-man@domain.com\n http://jabber.org/protocol/admin#get-active-users\n \n \n Users: 3\n \n admin@domain.com\n user1@domain.com\n morbo@domain.com\n \n \n\n-----\n\nSimilar results can be sent and received using JSON in a similar fashion. Again, be sure to set +ContentType: application/json+ in the header or default settings.\n\n[source,java]\n-----\n{\n \"command\" : {\n \"node\" : \"http://jabber.org/protocol/admin#get-active-users\",\n \"fields\" : [\n {\n \"var\" : \"domainjid\",\n \"value\" : \"subdomain.domain.com\"\n },\n {\n \"var\" : \"max_items\",\n \"value\" : \"25\"\n }\n ]\n }\n}\n-----\n\nThe results will look quite similar to the XML results:\n\n[source,java]\n-----\n{\n \"command\": {\n \"jid\": \"sess-man@domain.com\",\n \"node\": \"http://jabber.org/protocol/admin#get-active-users\",\n \"fields\": [\n {\n \"var\": \"Users: 2\",\n \"label\": \"text-multi\",\n \"value\": [\n \"minion1@subdomain.domain.com\",\n \"overadmin@subdomain.domain.com\"\n ]\n }\n ]\n }\n}\n-----\n\n[we should take another approach, and use something more permanent, like add or delete a user]\n\n=== Sending any XMPP Stanza\nXMPP messages or any other XMPP stanza can be sent using this API by sending HTTP POST request on http://localhost:8080/rest/stream/api-key=API_KEY with a serialized XMPP stanza as content, where API_KEY is the API key specified in the init.properties file.\nEach request needs to be authorized by sending a valid administrator JID and password as a user/password of BASIC HTTP authorization method. The content of the HTTP request should be encoded in UTF-8 and +Content-Type+ should be set to application/xml.\n\n==== Handling of request\nIf no +from+ attribute is set in the stanza, the HTTP API component will supplant it's JID instead, however if one is set it will be preserved. However, in iq stanzas, if no +from+ attribute is set the HTTP response content will be sent back as a response. Successful requests will return a HTTP response code of 200.\n\n*Examples:*\nAny of these examples must be sent as an HTTP POST request to /rest/stream/?api-key=API_KEY of the HTTP API component.\n\n===== Sending XMPP message with +from+ set to HTTP API component a full JID\n[source,xml]\n-----\n\n Example message 1\n\n-----\n\n===== Sending XMPP message with +from+ set to HTTP API component with a bare JID\n[source,xml]\n-----\n\n Example message 1\n\n-----\n\n===== Sending XMPP message with from set to a specified JID to a full JID\n[source,xml]\n-----\n\n Example message 1\n\n-----\n\n== Sending messages through REST\nYou can also send messages, or really any XMPP stanza to users and components through REST API. Sending XMPP messages or stanzas using HTTP is realized as a groovy script bundled in the installation package from v7.0.2. If you want to be sure your current install supports this feature, check for the presence of +Stream.groovy+ file in the +scripts/rest/stream/+ directory.\n\nAs in other examples, be sure that you have the following line in your init.properties:\n[source,bash]\n-----\nhttp/rest/api-keys[s]=test_key\n-----\nYou may also opt to have +open_access+ set to disable API key parameter.\n\n=== Usage\nUsing the HTTP POST method, XMPP stanzas can be sent using the built in HTTP API. In a local installation, the request can be sent to +http://localhost:8080/rest/stream/?api-key=API_KEY+ with a seralized XMPP stanza as content, where API_KEY is the API key for HTTP API which is set in +etc/init.properties+ as +rest/api-keys[s]+. In the case we laid out, it would be +test_key+. Because XMPP uses XML for formatting, all content in these requests *MUST* be encoded in UTF-8 and +Content-type+ must be set to +application/xml+.\nLets take a look at some examples.\n\n_In all examples the data is sent as an HTTP POST request to /rest/stream/?api-key=test-key._\n\n==== Send XMPP stanza with from set to HTTP API component to bare JID\n[source,xml]\n-----\n\n Example message 1\n\n-----\nOnce this message is sent, the Groovy script adds the remaining information automatically, and the following is what is receieved by test@example.com/resource-1.\n[source,xml]\n-----\n\n Example message 1\n\n-----\nAs you can see, the HTTP component is automatically populated as the sender.\n\n==== Send XMPP stanza with from set to HTTP API component to full JID\n[source,xml]\n-----\n\n Example message 1\n\n-----\nThe syntax and formatting is the same, with the recepiant messaging being exactly the same.\n[source,xml]\n-----\n\n Example message 1\n\n-----\n\n==== Send XMPP stanza with from set to specified JID\nYou may specify any JID that is registered in the server to send the stanza, ones that use a name that is not registered will return an error.\n[source,xml]\n-----\n\n Example message 1\n\n-----\nEnds with the result being somewhat customized.\n[source,xml]\n-----\n\n Example message 1\n\n-----\n\n[[avatarRetrievalRequests]]\n=== Avatar retrieval requests\nThere are different formats for avatar retrieval depending on how they are stored, see below for the resources for each type of avatar.\n\n- +/rest/avatar/user@domain+ - which returns first avatar found (PEP, VCard4 or VCardTemp in this order)\n- +/rest/avatar/user@domain/avatar+ - which returns PEP avatar\n- +/rest/avatar/user@domain/vcard4+ - which returns avatar from VCard4\n- +/rest/avatar/user@domain/vcard-temp+ - which returns avatar from VCardTemp\n\n== Setting HTTP API Privacy Rules\nThe HTTP API component has settings that allow you to specify who is allowed to use the HTTP API interface, keeping unauthorized users from accessing the feature. This feature is implemented using a Groovy admin ad-hoc stript for the Session Manager component. As a result of this method, it will be avaiulable to execution using the default GTTP API componene capability to execute the script. The actual work of filtering, however, will be conducted by the +DomainFilter+ plugin.\n\n[[getUserInfoREST]]\n== New Rest API added to obtain a JID login time\n+GetUserInfo+ command has been expanded to obtain user login and logout times in addition to standard information. To obtain the information, send a POST request to http://xmpp.domain.net:8080/rest/adhoc/sess-man@xmpp.domain.net?api-key=test-api-key with the following:\n[source,xml]\n-----\n\n get-user-info\n \n \n accountjid\n user@xmpp.domain.net\n \n \n Show connected resources in table\n true\n \n \n\n-----\n\n=== Configuration\nThe HTTP API privacy scipt is loaded automatically. +DomainFilter+ is a default plugin loaded by Tigase on startup. This means there is very little you need to do to have this running.\nAgain, you may define a custom API key to limit access using the following line in init.properties\n[source,properties]\n------\nhttp/rest/api-keys[s]=test_key\n------\n\n=== Usage\nSetting privacy rules can be done by sending a POST request to the session manager using this address: +http://localhost:8080/rest/sess-man@domain.com?api-key=test_key+\n[source,xml]\n-----\n\n user-domain-perm\n \n \n jid\n user@domain.com\n \n \n fiteringPolicy\n CUSTOM\n \n \n filteringList\n \n 1|allow|self;\n 2|allow|jid|admin@test2.com;\n 3|allow|jid|pubsub@test.com;\n 4|deny|all;\n \n \n \n\n-----\nHere all parameters are passed to be excuted by ad-hot command. Using the +user-domain-perm+ node we were able to add jids to a +CUSTOM+ filter. Here is a brief breakdown:\n\n- +jid+ denotes which JID the settings will be applied too.\n- +filteringPolicy+ - This uses a +CUSTOM+ type list that allows for multi-item list of custom processing rules.\n- +filteringLise - This is a multi-item list, semi-colon delimited, where each line denotes one item with a rule in this format: +order_number|policy|UID_type[|UID]:+\n - +order_number+ can be any integer, as long as no numbers repeat.\n - +policy+ can either +allow+ or +deny+.\n - +UID_type+ is the User ID Type, can be +jid+, +domain+, or +all+.\n - +UID+ is the user JID affected. If +UID_type+ is set to +all+ then this will be ignored.\n\nThese ad-hoc commands replicate settings found in xref:domainBasedPacketFiltering[Domain Based Packet Filtering] in the admin guide. They may also be influenced by the link:http://docs.tigase.org/tigase-server-Properties_Guide/html?#domainFilterPolicy[--domain-filter-policy] property of init.properties.\n\n\n== Scripting\nAs you can see from the above commands, Tigase uses pre-defined scripts for processing of all requests in HTTP API.\nAlthough the list may be small for now, this does mean with a little bit of Groovy scripting, you can create your own scripts to interpret REST commands and send them to the server!\n\nAll scripts for this purpose will be an implementation of class extending +tigase.http.rest.Handler+ class. The URI of the scripts will be inside the scripts folder. For example, if the script uses +TestHandler+ with a regular expression set to +/test+ and is placed inside the +scripts/rest/+ the handler will be called with this URI: +scripts/rest/test/+.\n\n=== Properties\nWhen extending classes, you will need to set the following listed properties.\nregex::\n Regular expression which is used to match request URI and parse parameters embedded in URI, for example:\n\n -----\n /\\/([^@\\/]+)@([^@\\/]+)/\n -----\n\nrequiredRole::\n Role of user required to be able to access this URI. Available values are +null+, +user+, and +admin+. Authentication for the script will be required if +requiredRole+ is not null.\n\nisAsync::\n If set to true, it will be possible to wait for results pending the arrival of IQ stanzas for instance.\n\n==== Properties containing closures\nExtended class should also set for closures for one or more of the following properties: +execGet+, +execPut+, +execPost+, +execDelete+, depending on which HTTP action is needed to support the following URI. Each closure has a *dynamic arguments list* generated at runtime. Below is a list of arguments passed to closure which describe how and when the list of arguments change.\n\nservice::\n Implementation of service interface which is used to access database or send/receove XMPP stanzas.\n\ncallback::\n Callback closures needs to be called to return data. However they only accept one argument of type +string,byte[],Map+. If data is Map tupe, it will be encoded to JSON or XML depending on Content-Type header.\n\nuser::\n Is passed only if requiredRole is not null. Otherwise this argument will not be in the argument list.\n\ncontent::\n Parsed content of the request. *This will not be in the list of arguments if Content-Lengeth of request is empty.* If Content-Type is set to XML or JSON the return result will be as Map, otherwise it will be an instance of +HttpServletRequest+.\n\nx::\n Additional arguments passed to callback are groups from regular expression matching the URI. Groups are not passed as a list, but are added to the list of arguments and next arguments.\n\nIf a property for corresponding HTTP action is not set, the component will return an HTTP 404 error.\n\n=== Example Script\n\nLets have a look at a script that is included with the install package to get a better idea of how these scripts work.\nThis script will GET a list of all registered account and output them according to an HTML file we will look at later.\n[source,java]\n-----\nimport tigase.http.rest.Service\nimport tigase.xmpp.BareJID\n\n/**\n * Class implements ability to retrieve by service administrator list of registered accounts\n * Handles requests for /rest/users/\n *\n * Example format of content of response:\n * user1@domainuser2@domain2\n */\nclass UsersHandler extends tigase.http.rest.Handler {\n\n public UsersHandler() {\n\t\tdescription = [\n\t\t\tregex : \"/\",\n\t\t\tGET : [ info:'Retrieve list of registered user jids',\n\t\t\t\tdescription: \"\"\"Request do not require any parameters and returns list of all registered user accounts on this server (for all vhosts).\n\nExample response will look like this:\n\\${util.formatData([users:[items:['user1@example.com','user2@example.com','user1@example2.com'],count:3]])}\n\"\"\"]\n\t\t];\n regex = /\\//\n requiredRole = \"admin\"\n isAsync = false\n execGet = { Service service, callback, jid ->\n def users = service.getUserRepository().getUsers()\n callback([users:[items:users, count:users.size()]]);\n }\n }\n\n}\n-----\nAs we can see, it's a fairly short code. First it calls the rest service (required for all of the REST activity), and the BareJID handler.\nNext we extend out custom class to extend +tigase.http.rest.Handler+. Our author has provided a helpful description of the code to better describe it's operation and expected result.\nThe last section is the actual code that defines what will match our query, in this case anything, a requirement that an admin make the command, that the connection will terminate with results, and what commands will be passed.\n\nThe matching HTML, which will shape the output of the code is included here.\n[source,html]\n-----\n${ util.include('header', [title:'All users']) }\n
\n${ util.include('footer') }\n-----\nThis file builds a table using the user fields from the GET request. *NOTE:* Not all scripts need a matching HTML file, basic requests may not need special handling.\n\n== REST API & PubSub\nAll PubSub Scripts are found within the +scripts/rest/pubsub+ directory of Tigase's installation directory. All examples in this section are prepared for a PubSub component available at pubsub@example.com. To use these examples for your installation, that JID needs to be replaced with with your pubsub JID.\n\nAll parameters passed in the content of HTTP request needs to be wrapped with ++ tag at the root of the XML document. Returned results will be wrapped within the ++ tag in the root of the XMl document.\n\n=== Create a Node\nHTTP URL: example.com/rest/pubsub/pubsub@example.com/create-node\n\nAvailable HTTP methods:\n\n*GET*\n\nMethod returns example content which contains all required and optional parameters that may be passed to the newly created node.\n\n*POST*\n\nCommand requires fields +node+ and +pubsub#node_type+ to be filled with proper values for execution.\n\n- +node+ Field contains id of node to create\n- +owner+ Field may contain JID or JIDS which will be considered owner of the node. If this field is empty, server will use JID of HTTP API Component (rest@example.com)\n- +pubsub#node_type+ Field should contain one of two types:\n * +leaf+ Node to items that will be published\n * +collection+ Node to nodes what will contain other nodes\n\nBelow is an example of creating a +leaf+ type node with the owner set to admin@example.com.\n[source,xml]\n-----\n\n example\n admin@example.com\n \n leaf\n \n\n-----\nServer response:\n[source,xml]\n-----\n\n \n Operation successful\n \n\n-----\n\n=== Delete a node\nHTTP URL: example.com/rest/pubsub/pubsub@example.com/delete-node\n\nAvailable HTTP methods:\n\n*GET*\n\nCommand returns example content which contains all required and operational parameters that may be passed.\n\n*POST*\n\nCommand requires field +node+ to be filled where +node+ is the id of the node to delete.\n\nBelow is an example of removing a node with an id of +example+\n[source,xml]\n-----\n\n example\n\n-----\nServer response\n[source,xml]\n-----\n\n \n Operation successful\n \n\n-----\n\n=== Subscribe to a node\nHTTP URI: example.com/rest/pubsub/pubsub@example.com/subscribe-node\n\nAvailable HTTP methods:\n\n*GET*\n\nMethod returns example content which contains all required and optional parameters that may be passed.\n\n*POST*\n\nCommand requires +node+ and +jid+ fields to be filled.\n\n- +node+ is the id of the node to subscribe too.\n- +jid+ is the JID or JIDS to be subscribed to the node.\n\nBelow is an example of the XML information passed between client and server with +test1@example.com+ and +test2@example.com+ subscribing to +example+ node.\n[source,xml]\n-----\n\n example\n \n test1@example.com\n test2@example.com\n \n\n-----\nServer response:\n[source,xml]\n-----\n\n \n Operation successful\n \n\n-----\n\n=== Unsubscribe from a node\nHTTP URI: example.com/rest/pubsub/pubsub@example.com/unsubscribe-node\n\nAvailable HTTP methods:\n\n*GET*\n\nMethod returns example content which contains all required and optional parameters that may be passed.\n\n*POST*\n\nLike the Subscribe to a node section, the command requires both the +node+ and +jid+ fields to be filled.\n\n- +node+ is the id of the node to unsubscribe from.\n- +jid+ is the JID or JIDS to be unsubscribed from the node.\n\nBelow is an example of the XML information passed between client and server with +test1@example.com+ and +test2@example.com+ unsubscribing to +example+ node.\n[source,xml]\n-----\n\n example\n \n test@example.com\n test2@example.com\n \n\n-----\nServer response:\n[source,xml]\n-----\n\n \n Operation successful\n \n\n-----\n\n=== Publish an item to a node\nHTTP URI: example.com/rest/pubsub/pubsub@example.com/publish-item\n\nAvailable HTTP methods:\n\n*GET*\n\nMethod returns example content which contains all required and optional parameters that may be passed.\n\n*POST*\n\nCommand requires the +node+ and +entry+ fields to be filled.\nAvailable fields:\n\n- +node+ Field contains the id of the node to be published to.\n- +item-id+ Field to contain the id of the entry to publish.\n- +expire-at+ Field may contain a timestamp after which item should not be delivered to subscribed users. Timestamp should follow this pattern: YYYY-MM-DDhh:mm:ss with a trailing Z to indicate UTC time in a 24h format.\n- +entry+ Field should contain multi-line entry content which should be valid XML value for an item.\n\nBelow is an example exchange between client and server for publishing an item with id +item-1+ to node +example+ .\n[source,xml]\n-----\n\n example\n item-1\n 2015-05-13T16:05:00+02:00\n \n \n Example 1\n Example content\n \n \n\n-----\nServer response:\n[source,xml]\n-----\n\n \n Operation successful\n \n\n-----\n\n=== List Available Nodes\nHTTP URI: example.com/rest/pubsub/pubsub.example.com/list-nodes\n\nAvailable HTTP methods\n\n*GET*\n\nThis method returns list of available PubSub nodes for the domain passed as part of the URI (+pubsub.example.com+).\n\nBelow is an example exchange between client and server for listing all nodes, the result having +test+, +node_54idf40037+ and +node_3ws5lz0037+\n[source,xml]\n-----\n\nList of available nodes\n\ntest\nnode_54idf40037\nnode_3ws5lz0037\n\n\n-----\n\n=== List Published Items on Node\nHTTP URI: example.com/rest/pubsub/pubsub.example.com/list-items\n\nAvailable HTTP methods\n\n*GET*\n\nMethod returns example content which contains all required and optional parameters that may be passed.\n\n*POST*\n\nThis command requires the +node+ field to be filled. The +node+ field contains the ID of the node from which we want the list of published items.\n\nBelow is an example exchange between client and server asking for all items published in the example node.\n[source,xml]\n-----\n\nexample\n\n-----\n\nServer Response\n[source,xml]\n-----\n\nList of PubSub node items\n\nexample\n\n\nitem-1\nitem-2\n\n\n-----\n\nItems item-1 and item-2 are the listed items.\n\n=== Retrieve Published Item on Node\nHTTP URI: example.com/rest/pubsub/pubsub.example.com/retrieve-item\n\nAvailable HTTP methods\n\n*GET*\n\nMethod returns example content which contains all required and optional parameters that may be passed.\n\n*POST*\n\nCommand requires that fields +node+ and +item-id+ are filled.\nAvailable Fields:\n- +node+ The node the item is published to.\n- +item-id+ The id of the item you wish to retrieve.\n\nExample communication between client and server:\n[source,xml]\n-----\n\nexample\nitem-1\n\n-----\n\nServer response:\n[source,xml]\n-----\n\nRetrive PubSub node item\n\nexample\n\n\nitem-1\n\n\n<item expire-at="2015-05-13T14:05:00Z" id="item-1"><item-entry>\n<title>Example 1</title>\n<content>Example content</content>\n</item-entry></item>\n\n\n\n-----\n\nNode that inside the item element, there is an XML encoded element, this will be retrieved without any decoding.\n\n== Other Example REST Commands and Documentation\nOther example REST commands, and accompanied documentation can be found at localhost:8080/rest/ on any server running Tigase and the HTTP component.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_57_-_Components_-_B_-_Tigase_HTTP_API_-_2_-_Admin_UI.asciidoc",
"content": "[[adminUI]]\n= Admin UI Guide\n:author: Daniel Wisnewski\n:version: v2.0 Sept 2015\n:date: 2015-02-09 10:28\n\n:toc:\n:numbered:\n:website: http://www.tigase.org\n\nThe Admin User Interface is an HTTP-based interface that sends REST commands to the server to update configurations, change settings, and retrieve statistics.\n\n== A Note about REST\nREST stands for REpresentational State Transfer which is a stateless communication method that in our case passes commands using HTTP GET, PUT, POST, and DELETE commands to resources within the Tigase server.\nAlthough REST uses HTTP to receive commands, REST itself is not intended for use in a browser. For more information, please see the REST API guide.\n\n\n== Configuration\nAllows you to list server components and their configurations, as well as manage server components and plugins.\n\nList server/component configuration section covers all the component options including the basic-conf and will allow you to change each setting by changing the values in the field and clicking submit. All settings are listed by the component name in the dropdown menu either as default, or as defined by --component-name property.\n\nimage:images/admin-componentconfig.jpg[]\n\nManage active server components allows you to do exactly that, but you can also add and disable components from this interface.\n\nimage:images/admin-managecomponent.jpg[]\n\nHere you can List, Add, Edit, and Remove components.\n- *List* provides a list of all running components, each with its name, info, and class.\n- *Add* provides an interface to add a class and a name for components. You will not be able to add invalid component names or classes.\n- *Edit* enables you to edit the specific properties of any running component. Even options for which there are no current values will be listed, you can consider this list a comprehensive list of settings and options for the current component.\n- *Remove* provides a way to remove running components.\n\nManaging server plugins allows you to turn on or off plugins from this window VIA check-boxes. Note that the changes are made in real-time.\n\nimage:images/admin-manageplugins.jpg[]\n\n== Example Scripts\nThis is a list of script examples that can be run and do menial functions for each component. They may not have particular value themselves, but are present to be used as reference when writing custom scripts.\nGet list of available commands is one script, that is present for every component that is active on the server, and as its title implies, will provide a list of all commands for that component. Lastly, the two scripts from the xref:scriptingSupport[Scripting section] of this guide. Generally, there is not much needed to see in this section.\n\n== Notifications\nThis section has one simple command: to be able to send a mass message to all logged in users.\nThere are three types of messages that can be sent from this section:\n- *normal* Messages will show as a pop-up in most clients.\n- *headline* Certain clients will take headline messages and insert them into MUC or chats between users, otherwise it will create a pop-up like normal messages.\n- *chat* Chat messages will open up a chat dialog with users.\n\n== Other\nThis section contains a considerable list of options and settings affecting server functions.\n\n=== Activate log tracker for a user\nThis allows you to set a log file to track a specific user. Set the bare or full JID of the user you want to log, and a name of the files you wish the log to be written to. The files will be written in the root Tigase directory unless you give a directory like logs/filename. The log files will be named with a .0 extension and will be named .1, .2, .3 and so on as each file reaches 10MB by default. filename.0 will always be the most recent.\nLogging will start once the command has been issued, and cease once the server restarts.\n\n=== Add SSL certificate\nHere you can add SSL certificates from PEM files to specific virtual hosts. Although Tigase can generate its own self-signed certificates, this will override any default certificates.\nThe certificates cannot contain a passphrase, or be encrypted. Be sure that the contents contain both the certificate and private key data.\nYou also have the option to save the certificate to disk, making the change permanent.\n\n=== Add listener script\nThis section allows you to create a custom function for the eventbus component. These scripts can have the server conduct certain operations if set criteria are met. You may write the script in either Groovy or EMCAscript. Please see the xref:eventbus[eventbus section] for more details.\n\n=== Add Monitor Task\nYou can write scripts for Groovy or ECMAScript to add to monitor tasks here. This only adds the script to available scripts however, you will need to run it from another prompt.\nNote that these scripts may only work with the monitor component.\n\n=== Add Monitor Timer Task\nThis section allows you to add monitor scripts in Groovy while using a delay setting which will delay the start of the script.\n\n=== Add New Item - ext\nDepending on whether you have any external components loaded or not, this may show. This allows you to add additional external components to the running instance of Tigase.\n\n=== Add New Item - Vhost\nThis allows you to add new virtual hosts to the XMPP server. A breakdown of the fields is as follows:\n\n- Domain name: the full domain name of the new vhost. Tigase will not add anything to this domain, so if it is ti be a subdomain of example.com, you will need to enter sub.domain.com.\n- Enabled: Whether the domain is turned on or off.\n- Anonymous enabled: Allow anonymous logins.\n- In-band registration: Whether or not to allow users to register accounts upon login.\n- TLS required: Require logins to the vhost to conduct a TLS handshake before opening streams.\n- S2S secret: a server-generated code to differentiate traffic between servers, typically there is no need to enter your own, but you may if you need to get into low level code.\n- Domain filter policy: Sets the filter policy for this domain, see xref:domainBasedPacketFiltering[This section] for a description of the rules.\n- Domain filter domains: a specific setting to restrict or control cross domain traffic.\n- Max users: maximum users allowed to be registered to the server.\n- Allowed C2S, BOSH, Websocket ports: Comma separated list of ports that this vhost will check for all of these services.\n- Presence forward address: specific address where presence information is forwarded too. This may be handy if you are looking to use a single domain for presence processing and handling.\n- Message forward address: Specific address where all messages will be sent too. This may be useful to you if you have a single server handling AMP or message storage and want to keep the load there.\n- Other Parameters: Other settings you may wish to pass to the server, consider this a section for options after a command.\n- Owner: The owner of the vhost who will also be considered an administrator.\n- Administrators: comma separated list of JIDs who will be considered admins for the vhost.\n- XEP-0136 Message Archiving Enabled: Whether to turn on or off this feature.\n- XEP-0136 Required store method: If XEP-0136 is turned on, you may restrict the portion of message that is saved. This is required for any archiving, if null, any portion of the message may be stored.\n- Client certificate required: Whether the client should submit a certificate to login.\n- Client certificate CA: The Certificate Authority of the client certificate.\n- XEP-0136 retention period: integer of number of days message archives will be set.\n- Trusted JIDs: Comma separated list of JIDs who will be added to the trusted list, these are JIDS that may conduct commands, edit settings, or other secure work without needed secure logins.\n- XEP-0136 retention type: Sets the type of data that retention period will use. May be User defined (custom number type), Unlimited, or Number of Days.\n- XEP-0136 - store MUC messages: Whether or not to store MUC messages for archiving. Default is user, which allows users to individually set this setting, otherwise tue/false will override.\n- see-other-host redirection enabled: in servers that have multiple clusters, this feature will help to automatically repopulate the cluster list if one goes down, however if this is unchecked, that list will not change and may attempt to send traffic to a down server.\n- XEP-0136 Default store method: The default section of messages that will be stored in the archive.\n\n=== Change user inter-domain communication permission\nHere you can restrict users to be able to communicate on specific domains, this works similar to the domain filtering policy using the same rule sets. For more details, see xref:domainBasedPacketFiltering[Domain Based Packet Filtering] section for rule details and specifics.\nNote that the changes may be made to mutiple JIDs at the same time.\n\n=== Connections Time\nLists the longest and average connection time from clients to servers.\n\n=== Create Node\nThis section allows you to create a new node for the pubsub component. Here is a breakdown of the fields:\n\n- The node to create: this is the name of the node that will be created.\n- Owner JID: user JID who will be considered the owner of the node.\n- pubsub#node type: sets the type of node the the new node will be. Options include:\n * *leaf* Node that can publish and be published too.\n * *collection* A collection of other nodes.\n- A friendly name for the node: Allows spaces and other characters to help differentiate it from other nodes.\n- Whether to deliver payloads with event notifications: as it says, to publish events or not.\n- Notify subscribers when the configuration changes: default is false\n- Persist items to storage: whether or not to physically store items in the node.\n- Max # of items to persist: Limit how many items are kept in the node archive.\n- The collection with which the node is affiliated: If the node is to be in a collection, place that node name here.\n- Specify the subscriber model: Choose what type of subscriber model will be used for this node. Options include:\n * *authorize* - Requires all subscriptions to be approved by the node owner before items will be published to the user. Also only subscribers may retrieve items.\n * *open* - All users may subscribe and retrieve items from the node.\n * *presence* - Typically used in an instant message environment. Provides a system under which users who are subscribed to the owner JID's presence with a from or both subscription may subscribe from and retrieve items from the node.\n * *roster* - This is also used in an instant message environments, Users who are both subscribed to the owners presence AND is placed in specific allowed groups by the roster are able to subscribe to the node and retrieve items from it.\n * *whitelist* - Only explicitly allowed JIDs are allowed to subscribe and retrieve items from the node, this list is set by the owner/administrator.\n- Specify the Publisher model: Choose what type of publisher model will be used for this node. Options include:\n * *open* - Any user may publish to this node.\n * *publishers* - Only users listed as publishers may be able to publish.\n * *subscribers* - Only subscribers may publish to this node.\n- When to send the last published item: This allows you to decide if and when the last published item to the node may be sent to newly subscribed users.\n * *never* - Do not send the last published item.\n * *on_sub* - Send the last published item when a user subscribes to the node.\n * *on_sub_and_presence* - Send the last published item to the user after a subscription is made, and the user is available.\n- The domains allowed to access this node: Comma separated list of domains for which users can access this node. By default is is blank, and there is no domain restriction.\n- Whether to deliver items to available users only: Items will only be published to users with available status if this is selected.\n- Whether to subscription expired when subscriber going offline: This will make all subscriptions to the node valid for a single session and will need to be re-subscribed upon reconnect.\n- The XSL transformation which can be applied to payloads in order to generate an appropriate message body element: Since you want a properly formatted element, you can add an XSL transformation here to address any payloads or extra elements to be properly formatted here.\n- The URL of the XSL transformation which can be applied to payloads in order to generate an appropriate message body element: This would be the URL of the XSL Transform, e.g. http://www.w3.org/1999/XSL/Transform.\n- Roster groups allowed to subscribe: a list of groups for whom users will be able to subscribe. If this is blank, no user restriction will be imposed.\n- Notify subscribers when owner changes their subscription or affiliation state: This will have the node send a message in the case of an owner changing affiliation or subscription state.\n- Allows get list of subscribers for each subscriber: Allows subscribers to produce a list of other subscribers to the node.\n- Whether to sort collection items by creation date or update time: options include\n * *byCreationDate* - Items will be sorted by the creation date, i.e. when the item was made.\n * *byUpdateTime* - Items will be sorted by the last update time, i.e. when the item was last edited/published/etc..\n\n=== DNS Query\nA basic DNS Query form.\n\n=== Default config - Pubsub\nHere you may set the default configuration for any new pubsub node. These changes will be made for all future nodes, but will not affect currently active nodes.\n\n=== Default room config\nThis page allows admins to set the default configuration for any new MUC rooms that may be made on the server.\n\n=== Delete Monitor Task\nThis removes a monitor task from the list of available monitor scripts. This action is not permanent as it will revert to inital settings on server restart.\n\n=== Delete Node\nProvides a space to remove a node from the server. It must be the full name of the node, and only one node can be removed at a time.\n\n=== Deleting ALL Nodes\nThis page allows the logged in admin to delete all nodes from the associated vhost. This change is irreversible, be sure to read and check the box before submitting the command.\n\n=== Fix User's Roster\nYou can fix a users roster from this prompt. Fill out the bare JID of the user and the names you wish to add or remove from the roster. This will NOT edit a user's roster, but rather compare client roster to database and fix any errors between them.\n\n=== Fix User's Roster on Tigase Cluster\nThis does the same as the Fix User's Roster, but can apply to users who may not be logged into the local vhost, but are logged into a clustered server.\n\n=== Get User Roster\nAs the title implies this gets a users' roster and displays it on screen. You can use a bare or full JID to get specific rosters.\n\n=== Get any file\nEnables you to see the contents of any file in the tigase directory. By default you are in the root directory, if you wish to go into directory use the following format:\nlogs/tigase.log.0\n\n=== Get Configuration File\nIf you don't want to type in the location of a configuration file, you can use this prompt to bring up the contents of either tigase.conf or init.properties.\n\n=== Get init.properties File\nWill output the current init.properties file, this includes any modifications made during the current server session.\n\n=== Get list available commands\nThis may be listed multiple times for different components, but this will do as the section suggest and list available commands for that particular component.\n\n=== Load test\nHere you can run a test with the pubsub component on any node to test functionality and proper settings for the node.\n\n=== Load Errors\nWill display any errors the server encounters in loading and running. Can be useful if you need to address any issues.\n\n=== New command script\nThis space allows you to create a new command script that will work within the associated component. Note that under the hyperlinked title, there is a listing of muc.server.org or pubsub.server.org, use these to determine where the new command will operate.\n\n=== OAuth Credentials\nThis allows the setting of new custom OAuth credentials for the server, and you can also require the use of OAuth tokens for users when they login. This is a setting for the specific host you are logged into. If you are logged into xmpp1.domain.com, it will not affect settings for xmpp2.domain.com.\n\n=== Pre-Bind BOSH user session\nThis allows a JID to be paired with a BOSH session before that user logs in, can reduce CPU use if you have a user that logs in via BOSH on a regular basis, or a web client that will regularly connect. You may also specify HOLD and WAIT integers to affect how BOSH operates with the associated JID.\n\n=== Publish item to node\nThis window allows you to not only test, but publish an item to the specified node. All fields must be filled in in order to avoid the server dropping an improperly formatted stanza.\n\n=== Read ALL nodes\nHere you can display all nodes and items from nodes that are currently in storage.\n\n=== Rebuild database\nThis will force Tigase to rebuild databases for the pubsub component, this may be useful for pubsub subscribers who continue to get pushed events after they unsubscribe.\n\n=== Reload component repository\nThis will reload any vhosts that the server is running. This may be useful if one is disconnected or broken during runtime.\n\n=== Remove an item\nThis will remove a running vhost from the server, you will be presented with a list to pick from.\n\n=== Remove command script\nLike new command script, take a look at the subheading to determine which component you want to remove the script from. Once there, select the command you wish to remove from the server. If remove from disk is selected, then the change will be permanent. Otherwise, the command will be removed until the next server restart.\n\n=== Remove listener script\nSelect from a list the listener script you wish to remove. This will only affect custom listener scripts added to the eventbus component.\n\n=== Remove room\nThis provides fields to remove a room from the MUC component. you may suggest an alternative room which will move occupants to the alternative room once the current one is removed.\n\n=== Retrieve items\nHere you can retrieve items from PubSub nodes, this simulates the get IQ stanza from the pubsub component.\n- Service name - The address of the pubsub component.\n- Node name - Item node to retrieve items from.\n- Item ID - The item ID of the item you wish to retrieve.\n- Items Since - UTC timestamp to start search from: YYYY-MM-DDTHH:MM:SSZ\n\n=== S2S Bad State Connections\nThis will list any connections to other servers that are considered bad or stale. This will populate very rarely as Tigase automatically adjusts around clustered servers that go down. In the event a connection stays bad, it is recommended to reset those connections in the next space.\n\n=== S2S Reset Bad State Connections\nThis will reset the connections with other servers that are considered bad and have shown up in the S2S Bad State Connections page.\n\n=== S2S Get CID Connection State\nFor internal developer use only.\n\n=== Subscribe to a node\nThis provides a space for an administrator to manually have a JID subscribe to a particular node.\n\n=== Unsubscribe from node\nHere you can unsubscribe users from a particular node. Users can be a comma separated list.\n\n=== Update item configuration\nTypically two entries will be seen for this entry, one for basic-conf and another for vhost-man. They each have their own sections, but provide for a plethora of server options. Changes to the server are done in realtime, and may not be permanent.\n\n==== basic-conf\nThis will prompt a list of nearly every component setting currently available in the Tigase installation. They are broken down as follows:\nComponent/catagory or setting/setting\nSo for example, if you wanted to change admins for the eventbus component, you will select 'eventbus/admins'.\nAnother example might be if you wanted to turn on or off a task in monitor component, lets say disk-checker-task, you would find 'monitor/disk-checker-task/enabled'.\nClicking Submit query will show current status and settings, and possible fields to change. Most changes done in this manner will be reset to default or as written in init.properties file on server restart.\n\n\n==== vhost-man\nYou will be presented with a list of domains that Tigase is currently hosting, you will be able to change settings for one domain at a time using this function. Once a domain is selected, you will be able to set or change the following settings:\n\n- Domain name: the full domain name of the new vhost. Tigase will not add anything to this domain, so if it is ti be a subdomain of example.com, you will need to enter sub.domain.com.\n- Enabled: Whether the domain is turned on or off.\n- Anonymous enabled: Allow anonymous logins.\n- In-band registration: Whether or not to allow users to register accounts upon login.\n- TLS required: Require logins to the vhost to conduct a TLS handshake before opening streams.\n- S2S secret: a server-generated code to differentiate traffic between servers, typically there is no need to enter your own, but you may if you need to get into low level code.\n- Domain filter policy: Sets the filter policy for this domain, see xref:domainBasedPacketFiltering[This section] for a description of the rules.\n- Domain filter domains: a specific setting to restrict or control cross domain traffic.\n- Max users: maximum users allowed to be registered to the server.\n- Allowed C2S, BOSH, Websocket ports: Comma separated list of ports that this vhost will check for all of these services.\n- Presence forward address: specific address where presence information is forwarded too. This may be handy if you are looking to use a single domain for presence processing and handling.\n- Message forward address: Specific address where all messages will be sent too. This may be useful to you if you have a single server handling AMP or message storage and want to keep the load there.\n- Other Parameters: Other settings you may wish to pass to the server, consider this a section for options after a command.\n- Owner: The owner of the vhost who will also be considered an administrator.\n- Administrators: comma separated list of JIDs who will be considered admins for the vhost.\n- XEP-0136 Message Archiving Enabled: Whether to turn on or off this feature.\n- XEP-0136 Required store method: If XEP-0136 is turned on, you may restrict the portion of message that is saved. This is required for any archiving, if null, any portion of the message may be stored.\n- Client certificate required: Whether the client should submit a certificate to login.\n- Client certificate CA: Client Certificate Authority.\n- XEP-0136 retention period: Integer of number of days message archives will be set.\n- Trusted JIDs: Comma separated list of JIDs who will be added to the trusted list, these are JIDS that may conduct commands, edit settings, or other secure work without needed secure logins.\n- XEP-0136 retention type: Sets the type of data that retention period will use. May be User defined (custom number type), Unlimited, or Number of Days.\n- XEP-0136 - store MUC messages: Whether or not to store MUC messages for archiving. Default is user, which allows users to individually set this setting, otherwise true/false will override.\n- see-other-host redirection enabled: in servers that have multiple clusters, this feature will help to automatically repopulate the cluster list if one goes down, however if this is unchecked, that list will not change and may attempt to send traffic to a down server.\n- XEP-0136 Default store method: The default section of messages that will be stored in the archive.\n\n\n=== Update user roster entry\nThis section allows admins to edit individual users rosters, although it provides similar functionality to fix users roster, this is designed for precision editing of a user roster.\n\n- Roster owner JID: The BareJID of the user roster you wish to edit.\n- JID to manipulate: The specific BareJID you want to add/remove/change.\n- Comma separated groups: Groups you wish to add the JID too.\n- Operation Type: What function will be performed?\n * *Add* - Add the JID to manipulate to the owner JID's roster and groups.\n * *Remove* - Remove the JID to manipulate from the owner JID's roster and groups.\n- Subscription type: The type of subscription stanza that will be sent to the server, and subsequently between the two users will be employed.\n * *None* - Select this if neither the owner or the user to be manipulated wishes to receive presence information.\n * *From* - The Roster Owner will not receive presence information from the JID to manipulate, but the opposite will be true.\n * *To* - The JID to manipulate will not receive presence information from the Roster Owner, but the opposite will be true.\n * *Both* - Both JIDs will receive presence information about each other.\n\n=== Update user roster entry extended version\nThis section is an expanded version of the previous one, all fields already specified are the same with these additions:\n\n- Roster owner name: A friendly name or nickname if you wish to change/create one. *not required*\n- Comma separated of owner groups: Groups that the user wants to join/leave. *not required*\n- Roster item JID: The specific JID that needs to be edited.\n- Roster item name: A friendly name or nickname that will be changed/created. *not required*\n- Comma separated list of item groups: A group or list of groups that the roster item JID will be added to/removed from.\n- Action:\n * *Add/update item* - Will add or update the item JID in the roster owner's roster.\n * *Remove item* - Will remove the item JID from the roster owner's roster.\n * *Add/update both rosters* - Will add or update the item in both roster owner and roster item's roster.\n * *Remove from both rosters* - Will remove the item from both roster owner and roster item's roster.\n\n== Scripts\nThis section will enable administrators to custom write or enter their own scripts for specific components. Each active component will have an entry for new and remove command scripts and scripts written there will be for that component.\n\n=== New Command Script\n- Description: A friendly name of the script, will be the title of the link in the menu on the left.\n- Command ID: Internal command that Tigase will use when referencing this script.\n- Group: The group for the script, which may be any of the headings on the left (Configuration, Example scripts, Notifications, Other etc..) or your own. If no group exists, a new one will be created.\n- Language: The language the script is written in. Currently Tigase supports Groovy and EMCAScript.\n- Script text: the fulltext of the script.\n- Save to disk: Scripts that are saved to disk will be permanently stored in the server's directory /scripts/admin/[Component]/commandID.js *NOTE* Scripts that are NOT saved to disk will not survive a server restart.\n\n=== Remove Command Script\nAs with New Command Script, there is an entry for each component. This page will provide a space to remove commands for the selected component.\nYou will be provided a list of scripts associated with that component. You also have the open to remove from disk, which will permanently delete the script from the hard drive the server is on. If this is unchecked, the script will be unavailable until the next restart.\n\n== Statistics\nThis section is more useful to test statistics scripts and components, as many of them produce very small amounts of information, however these may be collected by other components or scripts for a better information display.\n\n=== Get User Statistics\nProvides a script output of user statistics including how many active sessions are in use, number of packets used, specific connections and their packet usage and location. All resources will return individual stats along with IP addresses.\n\n=== Get Active User List\nProvides a list of active users under the selected domain within the server. An active user is considered a user currently logged into the XMPP server.\n\n=== Get list of idle users\nProvides a list of users who are idle on the server.\n\n=== Get list of online users\nProvides a list of users who are currently online.\n\n=== Get number of active users\nProvides a list of active users, users who are not idle or away.\n\n=== Get number of idle users\nProvides a number of idle users.\n\n=== Get top active users\nWill produce a list of user-limited users who are considered most active in packets sent.\n\n== Users\n=== Add User\nHere you can add new users to any domain handled by vHosts, users are added to database immediately and are able to login. *NOTE: You cannot bestow admin status to these users in this section.*\n\n=== Change User Password\nThis enables you to change the password of any user in the database. Although changes will take effect immediately, users currently logged in will not know the password has been changed until they try to log in again.\n\n=== Delete User\nThis removes the user or users (comma separated) from the database. The deleted users will be kicked from the server once submit is clicked.\n\n=== End user session\nDisconnects the current selected user by ending their session with the server.\n\n=== Get User Info\nThis section allows admins to get information about a specific user including current connections as well as offline and online messages awaiting delivery.\n\n=== Get registered user list\nThis will display all registered users for the selected domain up to the number specified.\n\n=== Modify User\nAllows you to modify some user details including E-mail and whether it is an active user.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_58_-_Components_-_B_-_Tigase_HTTP_API_-_3_-_Web_Client.asciidoc",
"content": "[[webClient]]\n= Tigase Web Client\n:author: Daniel Wisnewski\n:date: 2015-26-08 08:41\n:version: v1.0 August 2015\n\n:toc:\n:numbered:\n:website: http://www.tigase.org\n\nTigase now has a fully featured XMPP client built right into the HTTP interface. Everything you would expect from an XMPP client can now be done from the comfort of your browser window with no software install required!\n\nLets walk through setup.\n\nTigase web client requires the +Http.Message.Receiver+ plugin to be active. To enable this add the following lines to your init.properties file:\n\n------\n--comp-name-5:http\n--comp-class-5:tigase.HttpMessageReceiver\n------\n*NOTE: If you selected HTTP API to be enabled on setup, you already have everything you need.*\nThis sets up an HTTP server with the default port of 8080. See the HTTP API guide for component configuration.\n\nTo access the client, point a browser to the following address:\nxmpp.your-server.net:8080/ui/\n\nIt will ask you for a login, any bare JID of users registered with the server will work.\n*NOTE: Use your bare JID for login*\n\nOnce you have logged in successfully, you will be presented with the following screen.\n\nimage:images/WebUI-Home.jpg[]\n\nThe commands are broken into categories shown here. All changes made in these sections are instant and should be seen the same as if you were using an external XMPP client like Psi.\n\n*NOTE* The BOSH client will automatically translate all requests to the server name. In some rare cases this may not be resolvable by the browser and you will be unable to login. Should that happen, you may disable that feature using the following line in your init.properties:\n\nbosh/send-node-hostname[B]=false\n\nYou may have to specifically designate the bosh URL when using the advanced tag in the login screen.\n\n== Chat\nThis is the default window, and your main interface for chatting inside XMPP with this server. *NOTE: you can only communicate to users logged onto the current server, or connected clusters*\nUsers from your roster will be on the left panel, the right all active discussions and MUCs, as well as the currently selected chat will be available.\n\nimage:images/WebUI-Chat.jpg[]\n\nUsers that are logged in and on your roster will be displayed on the left side. Double-clicking will bring up a new chat window with the user. You can Right-click on them to bring up a sub menu with the following;\n\nimage:images/WebUI-Usersubmenu.jpg[]\n\n- *Chat* replicates a double-click and opens a new window for chat.\n- *Modify* brings up a dialogue that allows you to change the JID of the contact, a nickname, and group.\n- *Delete* removes the user from your roster. This will also remove subscription authorization for the selected user to receive presence information effectively removing you from their roster. *NOTE: this will not block user packets from your JID*\n- *Info* brings up the User Info (this is the disco#info command for the selected user)\n\nThe top right section has a few icons with specific functionality, they are;\n\nimage:images/WebUI-Chat-Add-New.jpg[] adds a new user to your roster.\n\nimage:images/WebUI-Chat-NewMUC.jpg[] creates a new Multi-user chatroom.\n\nimage:images/WebUI-Chat-Profile.jpg[] allows you to edit your user information such as picture and nickname.\n\nimage:images/WebUI-Chat-CloseWindow.jpg[] closes the active chat window.\n\nimage:images/WebUI-Chat-settings.jpg[] provides a place to change your password or publish changes to your user info. *NOTE: you are limited to changing the General fields*\n\n== Discovery\nThis is your service discovery panel, which breaks down by component in the sidebar. Each component name and its associated JID is listed to help you find what you need. Most components give you an option to Execute commands with a few exceptions allowing browsing and the ability to join a MUC.\n\n*Browse* allows you to dig deeper into certain components; for example list the chatrooms available in the MUC component. At the top of the page the specific JID of the component are you in will be displayed. This is a text field, and can be edited to reflect the JID of the component (or just the server name) to navigate.\n\nimage:images/WebUI-Browse-Comp.jpg[]\n\n*Join to Room* will join you to a MUC room that is selected. Alternatively, selecting Join to Room while MUC component is selected, you can join and start a new MUC room.\n\n*Execute Command* Provides a hierarchy of commands and options to view and edit settings, run commands and scripts, view contents of files, and see statistics. Since each Component can have a unique structure it is best to explore each to see what options are available.\n\n== Management\nThis is an advanced window for settings and management for the XMPP server.\n\n=== Configuration\n==== List server/component configuration\nFrom a drop-down menu you can view all the active components, or the server configuration (basic-conf). This is a read-only list of the current settings.\n\n==== Manage active server components\nThis section gives you a drop-down menu for components\n- *List* will provide a list of active running components with the following format\n component name :: componentInfo{Title=Server, Server version/revision (submission date), Class=component class} For example:\n amp :: componentInfo{Title=Tigase XMPP Server, Version=7.1.0-SNAPSHOT-b3990/574c329f (2015-08-28/10:32:06), Class=tigase.server.amp.AmpComponent}\n\n- *Add* Allows you to activate a component in a similar way you would in the init.properties files. define a name for the component, and the class for the component. Once you click Confirm that component will be active and running.\n\n- *Edit* will allow you to edit details of the selected component. All possible values for the component will be listed, even ones that do not have specific settings. Changes will be immediate, although changes will revert to ones specified in init.properties upon restart.\n\n- *Remove* allows you to remove components from a dropdown list. Components will be removed upon confirmation, however settings will be reverted on server restart.\n\n==== Manage active server plugins\nHere is a list of all available plugins, and you can activate or deactivate them by checking or un-checking each one and clicking confirm. All changes are made in realtime, however changes will be reverted on server restart.\n\n=== Notifications\nThis section has one simple command: to be able to send a mass message to all logged in users. You may choose to change the type of message to headline or Normal which will show as a pop-up in most XMPP clients. Chat messages will open up a chat dialog with users.\n\n=== Other\nThis section contains a considerable list of options and settings affecting server functions.\n\n=== Activate log tracker for a user\nThis allows you to set a log file to track a specific user. Set the bare or full JID of the user you want to log, and a name of the files you wish the log to be written to. The files will be written in the root Tigase directory unless you give a directory like logs/filename. The log files will be named with a .0 extension and will be named .1, .2, .3 and so on as each file reaches 10MB by default. filename.0 will always be the most recent.\nLogging will cease once the server restarts.\n\n=== Add SSL certificate\nHere you can add SSL certificates from PEM files to specific virtual hosts. Although Tigase can generate its own self-signed certificates, this will override those default certificates.\n\n=== Add Monitor Task\nYou can write scripts for Groovy or ECMAScript to add to monitor tasks here. This only adds the script to available scripts however, you will need to run it from another prompt.\n\n=== Add Monitor Timer Task\nThis section allows you to add monitor scripts in Groovy while using a delay setting which will delay the start of the script.\n\n=== Add New Item - ext\nProvides a method to add external components to the server. By default you are considered the owner, and the Tigase load balancer is automatically filled in.\n\n=== Add New Item - Vhost\nThis allows you to add new virtual hosts to the XMPP server\n\n=== Change user inter-domain communication permission\nYou can restrict users to only be able to send and receive packets to and from certain virtual hosts. This may be helpful if you want to lock users to a specific domain, or prevent them from getting information from a statistics component.\n\n=== Connections Time\nLists the longest and average connection time from clients to servers.\n\n=== DNS Query\nA basic DNS Query form.\n\n=== Default room config\nAllows you to set the default configuration for new MUC rooms. This will not be able to modify current in use and persistent rooms.\n\n=== Delete Monitor Task\nThis removes a monitor task from the list of available monitor scripts. This action is not permanent as it will revert to initial settings on server restart.\n\n=== Fix User's Roster\nYou can fix a users roster from this prompt. Fill out the bare JID of the user and the names you wish to add or remove from the roster. You can edit a users roster using this tool, and changes are permanent.\n\n=== Fix User's Roster on Tigase Cluster\nThis does the same as the Fix User's Roster, but can apply to users in clustered servers.\n\n=== Get User Roster\nAs the title implies this gets a users' roster and displays it on screen. You can use a bare or full JID to get specific rosters.\n\n=== Get any file\nEnables you to see the contents of any file in the tigase directory. By default you are in the root directory, if you wish to go into directory use the following format:\nlogs/tigase.log.0\n\n=== Get Configuration File\nIf you don't want to type in the location of a configuration file, you can use this prompt to bring up the contents of either tigase.conf or init.properties.\n\n=== Get init.properties File\nWill output the current init.properties file, this includes any modifications made during the current server session.\n\n=== Load Errors\nWill display any errors the server encounters in loading and running. Can be useful if you need to address any issues.\n\n=== New command script - Monitor\nAllows you to write command scripts in Groovy and store them physically so they can be saved past server restart and run at any time. Scripts written here will only be able to work on the Monitor component.\n\n=== New command script - MUC\nAllows you to write command scripts in Groovy and store them physically so they can be saved past server restart and run at any time. Scripts written here will only be able to work on the MUC component.\n\n=== OAUth credentials\nUses OAuth to set new credentials and enable or disable a registration requirement with a signed form.\n\n=== Pre-Bind BOSH user session\nAllows admins to pre-bind a BOSH session with a full or bare JID (with the resource automatically populated on connection). You may also specify HOLD or WAIT parameters.\n\n=== Reload component repository\nThis will show if you have any external components and will reload them in case of any stuck threads.\n\n=== Scripts\nThis section provides a list of command scripts for all active components. Each component has the following options\n- *Get list available commands* will list script commands for the component divided by either Scripts or Groups.\n- *New command script* provides a method to author new command scripts for specific components written in EMCAScript or Groovy. You do have an option to save the script to disk which will make the script permanent within the server.\n- *Remove command script* allows you to remove the selected script from the repository. If Remove from disk is not checked, the script will be unavailable until server restart. If it is, it will be permanently removed from the server.\n\nYou will be unable to edit or run commands from this section.\n\n=== Statistics\nThese statistics might be more useful as script results yield small bits of data, but you may find them useful when looking for server loads or finding user issues.\n\n==== Get User Statistics\nProvides a script output of user statistics including how many active sessions are in use, number of packets used, specific connections and their packet usage and location. All resources will return individual stats along with IP addresses.\n\n==== Get Active User List\nProvides a list of active users under the selected domain within the server. An active user is considered a user currently logged into the XMPP server.\n\n==== Get list of idle users\nThis will list all idle users separated by vhost.\n\n==== Get list of online users\nThis will list users separated by the vhost they are connected to. The list will include the bare JID as well as any resources for that JID.\n\n==== Get number of active users\nThis displays the number of current active users.\n\n==== Get number of idle users\nThis section returns the number of active users per specific vhost.\n\n===== Get top active users\nThis will list the top number of active users by packets sent and online time. This list will only be built with users currently online and from all vhosts.\n\n=== Users\n\n==== Add New User\nHere you can add new users to any domain handled by vHosts, users are added to database immediately and are able to login. *NOTE: You cannot bestow admin status to these users in this section.*\n\n==== Change user password\nAllows for admins to change the password of a specific user without needing to know the original password for the selected bare JID. Users currently logged in will not know password has been changed until they attempt to re-login.\n\n==== Delete user\nProvides a text window for admins to input the bare JID of the user they wish to remove from the server.\n\n==== Get User Info\nThis section allows admins to get information about a specific user including current connections as well as offline and online messages awaiting delivery.\n\n==== Get registered user list\nProvides a list of vhosts to search and a maximum number of users to list. Once run, the script will display a list of registered bare JIDs of users from the selected vhost.\n\n==== Modify User\nAllows you to modify some user details including E-mail and whether it is an active user.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_59_-_Components_-_C_-_Message_Archiving.asciidoc",
"content": "[[messageArchiving]]\n= Message Archiving Component\n\n:author: Daniel Wisnewski\n:version: v1.0 Sept 2015\n:date: 2015-17-09 13:29\n\n:source: https://projects.tigase.org/projects/message-archiving/wiki/Wiki\n\n:toc:\n:numbered:\n:website: http://www.tigase.org\n\n*NOTE: This component is incomplete and does not support all methods specified in XEP-0136*\nTigase server supports many of the features in XEP-0136, however it is not yet in full compliance with the XEP. The reason for this is that it uses the archived message date as the thread id of message due to the face that some clients sens messages with no thread id (e.g. Psi, Psi+). Due to this fact it is also possible to query the component about messages without specifying thread ids. For now the component also stores bare JIDs of recipients.\n\n\n== Installation\n\nThe message archiving component is not included with the standard build of Tigase, and thus will need to be compiled or downloaded. Here are the two methods:\n\n=== Download\n\nThe easiest way is to download the link:https://projects.tigase.org/attachments/download/3435/tigase-message-archiving-1.2.0-SNAPSHOT.jar[tigase-message-archiving-1.2.0-SNAPSHOT.jar] file into your /jars directory.\n\n=== Compile\n\nThe Tigase Message Archive component is kept in a separate repository from Tigase-server. It will compile in a similar manner though. Be sure you have Maven 3.0 or later installed. (to check use +mvn version+)\nFirst, obtain a clone of the repository using the following command:\n[source,bash]\n-----\n$ git clone https://repository.tigase.org/git/message-archiving.git\n-----\nThe repository will be downloaded to the /message-archiving/ directory.\n-----\n$cd message-archiving\n/message-archiving$ mvn clean package\n-----\nOnce Maven has finished compiling, go into the /target directory and you will find the required jar there. Move that to Tigase's /jars folder and your component is ready to run.\n\n== Configuration\n\nTo activate message archiving, place the following lines in the init.properties file:\n[source,bash]\n-----\n--comp-name-3=message-archive\n--comp-class-3=tigase.archive.MessageArchiveComponent\n-----\nThese two lines are the component required to be active. As with activating any component, be sure the component name and class match, and that the number is not used by another component.\n-----\nmessage-archive/archive-repo-uri=jdbc:mysql://localhost/messagearchivedb?user=test&password=test\n-----\nThis next line defines that message archives will be stored in a specific database, in this case +messagearchivedb+ hosted on localhost. If this is blank, the archive will be stored in the default user repository.\n-----\n--sm-plugins=message-archive-xep-0136\nsess-man/plugins-conf/message-archive-xep-0136/component-jid=archive@host.com\n-----\nThe next line turns on the message archive plugin, while this is not always necessary, in order to configure extra options, this line is needed.\nFinally, this line specifies the name for the component, if left blank the component's JID will be message-archive@local-machine-name.\n\n*NOTE: Message tagging can take up considerable resources!*\nThere are a high number of prepared statements which are used to process and archive messages as they go through the server, and you may experience an increase in resource use with the archive turned on. It is recommended to drecrease the repository connection pool to help balance server load from this component using the following line in init.properties:\n[source,bash]\n-----\n--data-repo-pool-size=5\n-----\n\n[[nonBodyStore]]\n=== Saving Options\n\nBy default, Tigase Message Archive will only store the message body with some metadata, this can exclude messages that are lacking a body. If you decide you wish to save non-body elements within Message Archive, you can now can now configure this using the following line from init.properties:\n-----\nsess-man/plugins-conf/unified-archive/msg-archive-paths[s]=/message/body,/message/subject\n-----\nWhere above will set the archive to store messages with or elements.\n\nTIP: Enabling this for elements such as iq, or presence will quickly load the archive. Configure this setting carefully!\n\n== Usage\n\nNow that we have the archive component running, how do we use it? Currently, the only way to activate and modify the component is through XMPP stanzas. Lets first begin by getting our default settings from the component:\n[source,xml]\n----\n\n \n\n----\nIt's a short stanza, but it will tell us what we need to know, Note that you do not need a from or a to for this stanza. The result is as follows:\n[source,xml]\n----\n\n\n\n\n\n\n\n\n\n----\nSee below for what these settings mean.\n\n=== XEP-0136 Field Values\n\n::\n - *Required Attributes*\n * +save=+ Boolean turning archiving on or off\n - *Optional Settings*\n * +scope=+ Determines scope of archiving, default is +\\'stream'+ which turns off after stream end, or may be +\\'global'+ which keeps auto save permanent,\n\n::\n Default element sets default settings for OTR and save modes, includes an option for archive expiration.\n - *Required Attribures*\n * +otr=+ Specifies setting for Off The Record mode. Available settings are:\n ** +approve+ The user MUST explicitly approve OTR communication.\n ** +concede+ Communications MAY be OTR if requested by another user.\n ** +forbid+ Communications MUST NOT be OTR.\n ** +oppose+ Communications SHOULD NOT be OTR.\n ** +prefer+ Communications SHOULD be OTR.\n ** +require+ Communications MUST be OTR.\n * +save=+ Specifies the portion of messages to archive, by default it is set to +body+.\n ** +body+ Archives only the items within the elements.\n ** +message+ Archive the entire XML content of each message.\n ** +stream+ Archive saves every byte of communication between server and client. (Not recommended, high resource use)\n - *Optional Settings*\n * +expire=+ Specifies after how many seconds should the server delete saved messages.\n\n::\n The Item element specifies settings for a particular entity. These settings will override default settings for the specified JIDS.\n - *Required Attributes*\n * +JID=+ The Jabber ID of the entity that you wish to put these settings on, it may be a full JID, bare JID, or just a domain.\n * +otr=+ Specifies setting for Off The Record mode. Available settings are:\n ** +approve+ The user MUST explicitly approve OTR communication.\n ** +concede+ Communications MAY be OTR if requested by another user.\n ** +forbid+ Communications MUST NOT be OTR.\n ** +oppose+ Communications SHOULD NOT be OTR.\n ** +prefer+ Communications SHOULD be OTR.\n ** +require+ Communications MUST be OTR.\n * +save=+ Specifies the portion of messages to archive, by default it is set to +body+.\n ** +body+ Archives only the items within the elements.\n ** +message+ Archive the entire XML content of each message.\n ** +stream+ Archive saves every byte of communication between server and client. (Not recommended, high resource use)\n - *Optional Settings*\n * +expire=+ Specifies after how many seconds should the server delete saved messages.\n\n::\n This element specifies the user preference for available archiving methods.\n - *Required Attributes*\n * +type=+ The type of archiving to set\n ** +auto+ Preferences for use of automatic archiving on the user's server.\n ** +local+ Set to use local archiving on user's machine or device.\n ** +manual+ Preferences for use of manual archiving to the server.\n * +use=+ Sets level of use for the type\n ** +prefer+ The selected method should be used if it is available.\n ** +concede+ This will be used if no other methods are available.\n ** +forbid+ The associated method MUST not be used.\n\nNow that we have established settings, lets send a stanza changing a few of them:\n[source,xml]\n-----\n\n \n \n \n \n \n \n \n\n-----\nThis now sets archiving by default for all users on the domain.com server, forbids OTR, and prefers auto save method for archiving.\n\n== Manual Activation\n\nTurning on archiving requires a simple stanza which will turn on archiving for the use sending the stanza and using default settings.\n[source,xml]\n----\n\n \n \n \n\n----\nA sucessful result will yield this response from the server:\n[source,xml]\n----\n\n----\nOnce this is turned on, incoming and outgoing messages from the user will be stored in +tig_ma_msgs+ table in the database.\n\n== Automatic Activation of MUC messages\n\nEnabling this feature allows MUC messages to be stored in the Message Archive repository and are added in the same way as for any other message. For this setting consider the MUC room JID, this will be the \"user\" that the messages will be archived with. This is the same JID used for retrevial as well as sending to storage. Archived MUC messages will be in the same format as normal archival messages with one exception, each message will have a ++ attribute attached which will be the room nick for the user that sent the message.\nThis feature is disabled by default.\n\n*NOTE:* It is worth to mention that even if more than on user resources joins the same room and each resource will receive the same messages, then only a single message will be stored in Message Archiving repository.\nIt is also important to note that MUC messages are archived to user messages archive only when user is joined to MUC room. For example, if message was sent to room but it was not sent to particular user, it will not be archived.\n\n=== Configuration\n\nEnabling archiving of MUC messages is done by adding one more line to your init.properties file. Along with defining +comp-name+ and +comp-class+ add this line:\n[source,bash]\n-----\nsess-man/plugins-conf/message-archive-xep-0136/store-muc-messages=value\n-----\n+value+ may be one of the following values:\n- +user+ Allows value to be set on domain level by user if the domain level setting allows that. [what?]\n- +true+ Enables the feature for all users in every hosted domain. This cannot be overridden by settings for individual domains or users.\n- +false+ Disables the feature for all users in every hosted domain. This cannot be overridden by settings for individual domains or users.\n\nTo configure this setting for individual vhosts, you will need to execute a configuration command using one of the following settings:\n- +user+ Allows user to start this feature\n- +true+ Enables feature for users of the configured domain. Users will be unable to disable this feature.\n- +false+ Disables feature for users of the configured domain. Users will be unable to disable this feature.\n\n== Searching for Messages\n\nTigase Message Archiving Component allows users to query for messages or collections that contain a string. A simple stanza sent to the message archive component will begin a search. For example, the following stanza requests a search for messages with \"test failed\" in the element. *NOTE:* Searches can *ONLY* be conducted within elements.\n[source,xml]\n-----\n\n test failed\n\n-----\n\n*This query element must be the child of a +list+ or +retrieve+ element.*\n\nSearch options include:\n\n- +with=+ Specify JID of user sending message\n- +from=+ Search from this time and date, Format: YYYY-MM-DDTHH:MM:SSZ Time is in 24h set to GMT\n- +end=+ Search until this time and date, Format: YYYY-MM-DDTHH:MM:SSZ Time is in 24h set to GMT\n\n\n=== Example queries\n\nRetrieving messages with \"test failed\" string with user juliet@capulet.com between 2014-01-01 00:00:00 and 2014-05-01 00:00:00\n[source,xml]\n-----\n\n \n \n test failed\n \n \n\n-----\n\nRetrieving collections containing messages with \"test failed\" string with user juliet@capulet.com between 2014-01-01 00:00:00 and 2014-05-01 00:00:00\n[source,xml]\n-----\n\n \n \n test failed\n \n \n\n-----\n\n== Message Tagging Support\n\nTigase now is able to support querying message archives based on tags created for the query. Currently, Tigase can support the following tags to help seach through message archives:\n- +hashtag+ Words prefixed by a hash (#) are stored with a prefix and used as a tag, for example #Tigase\n- +mention+ Words prefixed by an at (@) are stored with a prefix and used as a tag, for example @Tigase\n\n*NOTE:* Tags must be written in messages from users, they do not act as wildcards. To search for #Tigase, a message must have #Tigase in the element.\n\nThis feature allows users to query and retrieve messages or collections from the archive that only contain one or more tags.\n\n=== Activating Tagging\n\nTo enable this feature, the following line must be in the init.properties file (or may be added with Admin or Web UI)\n[source,bash]\n-----\nmessage-archiving/tags-support[B]=true\n-----\nWhere +message-archiving+ is the class name of the component.\n\nUsage\n~~~~~\nTo execute a request, the tags must be individual children elements of the +retrieve+ or +list+ element like the following request:\n[source,xml]\n-----\n\n #People\n @User1\n\n-----\n\nYou may also specify specific senders, and limit the time and date that you wish to search through to keep the resulting list smaller. That can be accomplished by adding more fields to the retrieve element such as +'with'+, +'from+', and +'end'+ . Take a look at the below example:\n[source,xml]\n-----\n\n \n \n #People\n @User1\n \n \n\n-----\nThis stanza is requesting to retrieve messages tagged with @User1 and #people from chats with the user juliet@capulet.com between January 1st, 2014 at 00:00 to May 1st, 2014 at 00:00.\n\n*NOTE:* All times are in Zulu or GMT on a 24h clock.\n\nYou can add as many tags as you wish, but each one is an *AND* statement; so the more tags you include, the smaller the results.\n\n=== Tag Searching\n\nYou can also retrieve a list of Tags that have already been used and are stored in the message archive. You can search for exact or a partial of the tag or mention. The following request is searching for tags that are 'like' #test, in this case any tags with #test present will show in a list.\n[source,xml]\n----\n\n \n\n----\n\nThe result will return tags with #test in them:\n[source,xml]\n----\n\n \n #test1\n #test123\n #testwin\n \n 0\n 2\n 3\n \n \n\n----\n\nYou may retrieve a list of tags or mentions by using just the # or @ symbols in the +like=+ field.\n\n[[maPurging]]\n== Purging Information from Message Archive\n\nThis feature allows for automatic removal of entries older than a configured number of days from the Message Archive. It is designed to clean up database and keep its size within reasonable boundaries.\n\nThere are 4 settings available for this feature:\nTo enable the feature:\n+message-archive/remove-expired-messages[B]=true+\n\nThis setting changes the initial delay after the server is started to begin removing old entries. In other words, MA purging will not take place until the specified time after the server starts. Default setting is PT1H, or one hour.\n+message-archive/remove-expired-messages-delay=PT2H+\n\nThis setting sets how long MA purging will wait between passes to check for and remove old entries. Default setting is P1D which is once a day.\n+message-archive/remove-expired-messages-period=PT2D+\n\n*NOTE* that these commands are also compatible with +unified-archive+ component, just replace +message+ with +unified+.\n\n=== Configuration of number of days in VHost\n\nVHost holds a setting that determines how long a message needs to be in archive for it to be considered old and removed. This can be set independently per Vhost. This setting can be modified by either using the HTTP admin, or the update item execution in adhoc command.\n\nCommand-line utility\nSets after how many days message should be removed - by default we use 24 hours. So if entry is older than 24 hours then it will be removed, ie. entry from yesterday from 10:11 will be removed after 10:11 after next execution of purge.\nThis configuration is done by execution of Update item configuration adhoc command of vhost-man component, where you should select domain for which messages should be removed and then in field XEP-0136 - retention type select value Number of days and in field XEP-0136 - retention period (in days) enter number of days after which events should be removed from UA.\n\nIn adhoc select domain for which messages should be removed and then in field XEP-0136 - retention type select value Number of days and in field XEP-0136 - retention period (in days) enter number of days after which events should be removed from UA.\n\nIn HTTP UI select Other, then Update Item Configuration (Vhost-man), select the domain, and from there you can set XEP-0136 retention type, and set number of days at XEP-0136 retention period (in days).\n\nValue of +remove-expired-messages-delay+ and +remove-expired-messages-period+ is in format described at Duration.parse() in Java documentation.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_60_-_Components_-_D_-_Advanced_Message_Processing_-_AMP_XEP-0079.asciidoc",
"content": "[[amp0079]]\n= Advanced Message Processing - AMP XEP-0079\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-05-13 16:09\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nTigase server *5.1.0* or later offers support for link:http://xmpp.org/extensions/xep-0079.html[Advanced Message Processing], called AMP or XEP-0079.\n\nIt is enabled by default but there are several configuration options that you may tweak.\n\nConfiguration of AMP is not very complex, but as it is implemented as a component in the Tigase server it does needs a few settings to get it right.\n\nHere is a first, brief overview of the AMP configuration and later detailed explanation of each parameter.\n\n[source,bash]\n-----\n--sm-plugins=amp,-message,-msgoffline\n--amp-repo-uri=jdbc:mysql://localhost/tigasedb?user=db_usr&password=db_pwd\n--amp-security-level=STRICT\nsess-man/plugins-conf/amp/amp-jid=amp@your-domain.tld\n-----\n\n\n== First of all: plugins:\n\nEven though the whole functionality is implemented inside the component you need a way to forward messages with +AMP+ payload to that component. This is what the 'amp' plugin does. The 'amp' plugin intercepts all ++ packets even without AMP payload, redirecting some of the to the +AMP+ component and others processing in a standard way. Therefore you no longer need 'message' plugin or 'msgoffline' plugin. Those are all functions are offered by the 'amp' plugin now. Hence you have to switch 'message' and 'msgoffline' plugins off (the 'amp' plugin is loaded by default):\n\n[source,bash]\n-----\n--sm-plugins=+amp,-message,-msgoffline\n-----\n\nThe 'amp' plugin needs to know where to forward all the +AMP+ packets. By default plugin uses hostname of the given machine as this is true to the most installations. However, this is configured by the last line of the example configuration, which forwards all packets to the address 'amp@your-domain.tld':\n\n[source,bash]\n-----\nsess-man/plugins-conf/amp/amp-jid=amp@your-domain.tld\n-----\n\n== Secondly: component:\n\nBy default Tigase loads the component with the standard name 'amp'\n\n== Optional parameters:\n\nThere is also one parameter shared between the component and the plugin. Connection to the database where offline messages are stored. The AMP component has a dedicated schema for storing offline messages designed for a high traffic and high load installations. It does not use +UserRepository+ for storing messages.\n\nBy default the same physical database as for +UserRepository+ is used but you can change it and store messages in a completely separate location to reduce performance degradation of rest of the system. You can set a database connection string using following property:\n\n[source,bash]\n-----\n--amp-repo-uri=jdbc:mysql://localhost/tigasedb?user=db_usr&password=db_pwd\n-----\n\nThe link:http://xmpp.org/extensions/xep-0079.html[XEP-0079] specification has a link:http://xmpp.org/extensions/xep-0079.html#security[Section 9. - Security Considerations]. As it describes, in some cases the AMP protocol can be used to reveal user's presence information by other users who are not authorised for presence updates. There are a few possible ways to prevent this.\n\nTigase's implementation offers 3 modes to handle +AMP+ requests to prevent revealing user's status to non-authorized users:\n\n[source,bash]\n-----\n--amp-security-level=STRICT\n-----\n\nIn this mode the server performs strict checking. The +AMP+ specification is fully handled. This however involves roster loading for each offline user, hence it may impact the service performance. It may not be feasible or possible to run in this mode for services under a high load with lots of AMP messages.\n\nIn the XEP this mode is described in the following way:\n\n_Accept the relevant condition only if the sender is authorized to receive the receiver's presence, as a result of which the server MUST reply with a error condition if the sender is not so authorized; this is the RECOMMENDED behavior. This is also the default in Tigase._\n\n[source,bash]\n-----\n--amp-security-level=PERFORMANCE\n-----\n\nDummy checking is performed efficiently by just returning an error response every time there is a chance that the default action may reveal user status without looking into the user's roster. This does not affect performance but it does impact the +AMP+ compliance.\n\nIn the XEP this mode is described in the following way:\n\n_Accept the relevant condition only if the action is \"drop\", as a result of which the server MUST reply with a error condition if the action is \"alert\", \"error\", or \"notify\"; this is slightly less restrictive but still unnecessarily restricts the functionality of the system, so is NOT RECOMMENDED._\n\nIt does not do any checking. It acts like all users are authorized to receive notifications, even if it may reveal user status to unauthorized users. It does not impact the server performance and it offers full AMP compliance.\n\n[source,bash]\n-----\n--amp-security-level=NONE\n-----\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_61_-_Components_-_E_-_PubSub.asciidoc",
"content": "[[PubSubComp]]\n= PubSub Component\n:author: many authors\n:version: v1.0, September 2015\n:date: 2015-09-30 17:25\n\n:toc:\n:numbered:\n:website: http://www.tigase.org\n\n\n\n== Configuration\nTigase's Publish Subscribe component is an link:http://www.xmpp.org/extensions/xep-0060.html[XEP-0060] compliant plugin handling all publish and subscribe activity within Tigase server.\nTo enable the component the following should be in your init.properties file\n-----\n--comp-name-2 = pubsub\n--comp-class-2 = tigase.pubsub.PubSubComponent\n-----\n\n== Pubsub naming\nWithin Tigase, all pubsub component address MUST be domain-based address and not a JID style address. This was made to simplify communications structure. Tigase will automatically set component names to pubsub.domain, however any messages send to pubsub@domain will result in a +SERVICE_UNAVAILABLE+ error.\n\nPubsub nodes within Tigase can be found as a combination of JID and node where nodes will be identified akin to service discovery. For example, to address a friendly node, use the following structure:\n\n[source,xml]\n-----\n\n \n\n-----\n\n[[rosterLimit]]\n== Configure Roster Maxmimum size\nStarting with Tigase v7.1.0, administrators can configure the maximum allowable roster size per user via the init.properties file.\n-----\nsess-man/plugins-conf/jabber\\:iqa\\:roster/max_roster_size=100\n-----\nThis sets the roster limit to 100 entries per user. It can be set to any integer, however by default no limit is set.\n\n\n== AdHoc Commands\nSimilar to the HTTP API, AdHoc commands based on groovy scripts can be sent to this component to do a number of tasks. All scripts for these Ad-hoc commands are found at +sec/main/groovy/tigase/admin+ in source distrubitions, or at link:https://projects.tigase.org/projects/tigase-pubsub/repository/revisions/master/show/src/main/groovy/tigase/admin[this link]. To use them, the scripts need to be copied into the +scripts/admin/pubsub+ folder in the Tigase installation directory.\nFor all examples, the component address will be +pubsub.example.com+.\n\n=== Create a Node\nAd-hoc command node: +create-node+\nRequired role: Service Administrator\n\nCommand requires fields +node+ and +pubsub#node_type+ to be filled with proper values for execution.\n- +node+ Field containing id of node to create.\n- +pubsub#node_type+ Contains one of two possible values.\n * +leaf-node+ Node that will be published.\n * +collection+ Node that will contain other nodes.\n\nOther fields are optional fields that can be set to change configuration of newly create node to different configuration than default.\n\nExample call using TCLMT:\n-----\nbin/tclmt.sh -u admin@example.com -p admin123 remote pubsub.example.com create-node example admin@example.com leaf\n-----\n\n=== Delete a Node\nAd-hoc command node: +delete-node+\nRequired role: Service Administrator\n\nCommand requires +node+ field to be filled.\n- +node+ Field containing id of node to delete.\n\nExample call using TCLMT:\n-----\nbin/tclmt.sh -u admin@example.com -p admin123 remote pubsub.example.com delete-node example\n-----\n\n=== Subscribe to a Node\nAd-hoc command node: +subscribe-node+\nRequired role: Service Administrator\n\nCommand requires +node+ and +jids+ nodes to be filled.\n- +node+ Field containing node to subscribe to.\n- +jids+ Field containing list of JIDs to subscribe to the node.\n\nExample call using TCLMT:\n-----\nbin/tclmt.sh -u admin@example.com -p admin123 remote pubsub.example.com subscribe-node example admin@example.com,test1@example.com\n-----\n\n=== Unsubscribe to a Node\nAd-hoc command node: +unsubscribe-node+\nRequired role: Service Administrator\n\nCommand requires +node+ and +jids+ nodes to be filled.\n- +node+ Field containing node to unsubscribe to.\n- +jids+ Field containing list of JIDs to unsubscribe to the node.\n\nExample call using TCLMT:\n-----\nbin/tclmt.sh -u admin@example.com -p admin123 remote pubsub.example.com unsubscribe-node example admin@example.com,test2@example.com\n-----\n\n=== Publish an item to a Node\nAd-hoc command node: +publish-item+\nRequired role: Service Administrator\n\nCommand requires fields +node+ and +entry+ to be filled.\n- +node+ Field containing id of node to publish to.\n- +item-id+ Field may contain id of entry to publish, can be empty.\n- +entry+ Field should contain multi-line entry content that should be valid XML values for items.\n\nThis command due to it's complexity cannot be easily executed by TCLMT using default remote script which provides support for basic adhoc commands.\nExample call using TCLMT:\n-----\nbin/tclmt.sh -u admin@example.com -p admin123 remote pubsub.example.com publish-item example item-1 'Example 1'\n-----\n\nExample Groovy script to execute create-node command using JAXMPP2\n[source,java]\n-----\nimport tigase.jaxmpp.j2se.Jaxmpp\nimport tigase.jaxmpp.core.client.AsyncCallback\nimport tigase.jaxmpp.core.client.exceptions.JaxmppException\nimport tigase.jaxmpp.core.client.xmpp.stanzas.Stanza\nimport tigase.jaxmpp.core.client.SessionObject\nimport tigase.jaxmpp.j2se.ConnectionConfiguration\nimport tigase.jaxmpp.core.client.xml.Element\nimport tigase.jaxmpp.core.client.xml.DefaultElement\nimport tigase.jaxmpp.core.client.xmpp.forms.JabberDataElement\n\nJaxmpp jaxmpp = new Jaxmpp();\n\njaxmpp.with {\n getConnectionConfiguration().setConnectionType(ConnectionConfiguration.ConnectionType.socket)\n getConnectionConfiguration().setUserJID(\"admin@example.com\")\n getConnectionConfiguration().setUserPassword(\"admin123\")\n}\n\njaxmpp.login(true);\n\ndef packet = IQ.create();\npacket.setAttribute(\"to\", \"pubsub.example.com\");\n\nElement command = new DefaultElement(\"command\");\ncommand.setXMLNS(\"http://jabber.org/protocol/commands\");\ncommand.setAttribute(\"node\", \"create-node\");\npacket.addChild(command);\n\nElement x = new DefaultElement(\"x\");\nx.setXMLNS(\"jabber:x:data\");\n\ncommand.addChild(x);\n\ndef data = new JabberDataElement(x);\ndata.addTextSingleField(\"node\", \"example\");\ndata.addListSingleField(\"pubsub#node_type\", \"leaf\");\n\njaxmpp.send(packet, new AsyncCallback() {\n void onError(Stanza responseStanza, tigase.jaxmpp.core.client.XMPPException.ErrorCondition error) throws JaxmppException {\n println \"received error during processing request\";\n }\n\n void onSuccess(Stanza responseStanza) throws JaxmppException {\n x = responseStanza.getFirstChild(\"command\").getFirstChid(\"x\");\n data = new JabberDataElement(x);\n def error = data.getField(\"Error\");\n println \"command executed with result = \" + (error ? \"failure, error = \" + error.getFieldValue() : \"success\");\n }\n\n void onTimeout() {\n println \"command timed out\"\n }\n});\n\nThread.sleep(30000);\njaxmpp.disconnect();\n-----\n\n== PubSub Node Presence Protocol\n\n*Occupant Use Case*\n=== Log in to Pubsub Node\nTo log in to PubSub Node user must send presence to PubSub component with additional information about node:\n[source,xml]\n-----\n\n \n\n-----\n\nComponent will publish this information in node:\n\n[source,xml]\n-----\n\n \n \n \n \n \n \n \n\n\n \n \n \n \n \n \n \n\n-----\nAnd then will send notification with presences of all occupants to new occupant.\n\n=== Log out from PubSub Node\nTo logout from single node, user must send presence stanza with type unavailable:\n[source,xml]\n-----\n\n \n\n-----\nComponent will send events to all occupants as described:\n[source,xml]\n-----\n\n \n \n \n \n \n \n \n\n-----\nIf component receives presence stanza with type unavailable without specified node, then component will log out user from all nodes he logged before and publish events.\n\n=== Retrieving list of all Node Subscribers\nTo retrieve list of node subscribers, node configuration option +tigase#allow_view_subscribers+ must be set to true:\n[source,xml]\n-----\n\n \n \n \n \n http://jabber.org/protocol/pubsub#node_config\n \n 1\n \n \n \n\n-----\nWhen option is enabled, each subscriber may get list of subscribers the same way link:http://xmpp.org/extensions/xep-0060.html#owner-subscriptions-retrieve[as owner].\n[source,xml]\n-----\n\n \n \n \n\n-----\nThere is extension to filter returned list:\n[source,xml]\n-----\n\n \n \n \n \n \n \n \n\n-----\nIn this example will be returned all subscriptions of users from domain \"denmark.lit\".\n\n[[storeFullXMLLastPresence]]\n== Store Full XML of Last Presence\nA new feature has been implemented in v7.1.0 that allows Tigase to store a more detailed presence stanza to include timestamps and other information.\n\n=== Requirements\nEnsure that +presence-offline+ plugin is enabled in init.properties. To do this, add *+presence-offline* to the *--sm-plugins* line.\n\nThe following two lines configure options to broadcast probes to offline users.\n-----\nsess-man/plugins-conf/skip-offline=false\nsess-man/plugins-conf/skip-offline-sys=false\n-----\nWithout these lines, Tigase will not send presence probes to users that the server knows to be offline.\n\nThe full XML presence is stored under the tig_pairs table with a pkey of +last-unavailable-presence+ will look like this:\n[source,xml]\n-----\n\nLogged out\n\n-----\nAs you can see, the plugin has added a delay stamp which indicates the last time they were seen online. This may be suppressed by using the following line in your init.properties file.\n-----\nsess-man/plugins-conf/delay-stamp=false\n-----\n\nYou may also limit probe responses only to newly connected resources.\n-----\nsess-man/plugins-conf/probe-full-jid=true\n-----\n\nWhen a user logs on, they will receive the same full unavailable presence statements from contacts not logged in. Also the repository entry containing their last unavailable presence will be removed.\n\n*NOTE: This will increase traffic with users with many people on their rosters.*\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_62_-_Components_-_E_-_PubSub_-_1_-_Offline_Message_Sink.asciidoc",
"content": "[[offlineMessageSink]]\n= Offline Message Sink\n:author: Bartosz Malkowski\n:version: v1.0, October 2015\n:date: 2015-10-07 09:36\n\n:toc:\n:numbered:\n:website: http://www.tigase.org\n\n== Description\n\nMessages sent to offline users is published in PubSub node, from where that message is sent to all the node subscribers as a PubSub notification.\n\n[source,xml]\n-----\n\n \n \n \n \n Hello\n \n \n \n \n\n-----\n\n== Configuration\nThe PubSub node must be created and configured beforehand:\n\n=== Create node\n[source.xml]\n-----\n\n \n \n \n\n-----\n\nAfter that is done, you need to add SessionManager as a publisher:\n\n=== Add sess-man as publisher\n[source,xml]\n-----\n\n \n \n \n \n \n\n-----\n\nFinally, the AMP plugin must be configured as well\n\n=== init.properties configuration\n[source,bash]\n-----\nsess-man/plugins-conf/amp/msg-pubsub-jid=pubsub.coffeebean.local\nsess-man/plugins-conf/amp/msg-pubsub-node=message_sink\nsess-man/plugins-conf/amp/msg-pubsub-publisher=sess-man@coffeebean.local\n-----\n\nOf course be sure that AMP plugin is in your +--sm-plugins+ line.\n\n== Usage\nBecause these sinks use a standard PubSub component, administration of the sink node is identical to any other PubSub node. link:http://www.xmpp.org/extensions/xep-0060[XEP-0060] defines standard PubSub usage and management.\n\n=== Managing Subscriptions\n\n==== Add new Subscriber\n[source,xml]\n-----\n\n \n \n \n \n \n\n-----\n\n==== Remove Subscriber\n[source,xml]\n-----\n\n \n \n \n \n \n\n-----\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_63_-_Components_-_E_-_PubSub_-_2_-_PubSub_Schema_Changes.asciidoc",
"content": "[[PubsubSchemaChanges]]\n= PubSub Schema Changes\n:author:\n:version: v1.0 September, 2015\n:date: 2015-30-09 17:28\n\n:toc:\n:numbered:\n:website: http://www.tigase.org\n\nTigase PubSub Component is currently version 3.2.0 which is introduced in Tigase server v7.1.0\n\n[[Pubsub3.2.0Changes]]\n== PubSub 3.2.0 Changes\n\nPubSub v 3.2.0 adds a new procedure TigPubSubGetNodeMeta which supports PubSub metadata retrieval while conducting a disco#info query on nodes.\n\nYou will need to upgrade your database if you are not using v3.2.0 schema. Tigase will report being unable to load PubSub component if you do not have this schema version.\n\nThe MySQL schema can be found link:https://projects.tigase.org/projects/tigase-pubsub/repository/revisions/master/entry/database/mysql-pubsub-schema-3.2.0.sql[Here].\n\nThe Derby schema can be found link:https://projects.tigase.org/projects/tigase-pubsub/repository/changes/database/derby-pubsub-schema-3.2.0.sql[Here].\n\nThe PostGRESQL schema can be found link:https://projects.tigase.org/projects/tigase-pubsub/repository/changes/database/postgresql-pubsub-schema-3.2.0.sql[Here].\n\nThe MS SQL schema can be found link:https://projects.tigase.org/projects/tigase-pubsub/repository/changes/database/sqlserver-pubsub-schema-3.2.0.sql[Here].\n\nThe same files are also included in all distributions of v7.1.0 in +[tigaseroot]/database/+ . All changes to database schema are meant to be backward compatible.\n\nFor instructions how to manually upgrade the databases, please refer to xref:tigaseServer71[Tigase v7.1.0 Schema Updates section].\n\n[[Pubsub310change]]\n== PubSub 3.1.0 Changes\nThe PubSub Schema has been streamlined for better resource use, this change affects all users of Tigase.\nTo prepare your database for the new schema, first be sure to create a backup! Then apply the appropriate pubsub schema to your MySQL and it will add the new storage procedure.\n\nThe MySQL schema can be found link:https://projects.tigase.org/projects/tigase-pubsub/repository/revisions/master/entry/database/mysql-pubsub-schema-3.1.0.sql[Here].\n\nThe Derby schema can be found link:https://projects.tigase.org/projects/tigase-pubsub/repository/changes/database/derby-pubsub-schema-3.1.0.sql[Here].\n\nThe PostGRESQL schema can be found link:https://projects.tigase.org/projects/tigase-pubsub/repository/changes/database/postgresql-pubsub-schema-3.1.0.sql[Here].\n\nThe MS SQL schema can be found link:https://projects.tigase.org/projects/tigase-pubsub/repository/changes/database/sqlserver-pubsub-schema-3.1.0.sql[Here].\n\nThe same files are also included in all distributions of v7.1.0 in +[tigaseroot]/database/+ . All changes to database schema are meant to be backward compatible.\n\n== PubSub v3.0.0 Changes\nTo update older installations of Tigase to the PubSub Schema v3.0.0 follow these instructions. Note this should be done before upgrading to PubSub v3.1.0.\n\nStep by Step guide.\n\n=== Prepare Old Database for Upgrade\nIn +database+ directory of Tigase installation you will find SQL files which will prepare old database schema for upgrade using following this naming pattern: +-pubsub-schema-3.0.0-pre-upgrade.sql+ Where ++ can be one of the following: +mysql+, +sqlserver+, ie. for MySQL you will find the file +mysql-pubsub-schema-3.0.0-pre-upgrade.sql+. You need to execute statements from this file on your source database, which will drop old procedures and functions used to access database and also this statements will rename old tables by adding suffix _1 to each of old tables. Example:\n\nMySQL::\n +mysql -u tigase -p tigase_pubsub < database/mysql-pubsub-schema-3.0.0-pre-upgrade.sql+\n\nMS SQL::\n +sqlcmd -S %servername% -U %root_user% -P %root_pass% -d %database% -i database\\sqlserver-pubsub-schema-3.0.0-pre-upgrade.sql+\n\n=== Update Tigase PubSub Component\nFor this you need to copy the Tigase PubSub Component jar file to jars directory inside Tigase XMPP Server installation directory. It is also recommended to copy files from database directory of Tigase PubSub Component to database directory in Tigase XMPP Server installation directory.\n\nIf you happen to use one of the the distribution packaged (either installer or -dist-max flavored archive) then all required files are already available - both new schema files will be available in +database/+ directory as well as both versions of PubSub component will be present in +jars/+ directory - PubSub3 as tigase-pubsub.jar and PubSub2 as tigase-pubsub-2.2.0.jar.old (provided for compatibility reasons).\n\n=== Load New Schema\nIn the +database+ directory you will find files containing new schemas for:\n\n- MySQL - +mysql-pubsub-schema-3.0.0.sql+\n- PostgreSQL - +postgresql-pubsub-schema-3.0.0.sql+\n- MSSQL - +sqlserver-pubsub-schema-3.0.0.sql+\n- DerbyDB - +derby-pubsub-schema-3.0.0.sql+ and +pubsub-db-create-derby.sh+\n\nFor most databases, with the exception of Derby, you only need to execute statements from the proper file. For example:\n\nMySQL::\n +mysql -u tigase -p tigase_pubsub < database/mysql-pubsub-schema-3.0.0.sql+\n\nMS SQL::\n +sqlcmd -S %servername% -U %root_user% -P %root_pass% -d %database% -i database\\sqlserver-pubsub-schema-3.0.0.sql+\n\nPostgreSQL::\n +psql -h $DB_HOST -q -U ${USR_NAME} -d $DB_NAME -f database/sqlserver-pubsub-schema-3.0.0.sql+\n\nFor DerbyDB you need to execute the +pubsub-db-create-derby.sh+ script and pass proper JDBC URI to database to which you want to load schema (if database does not exist, it will be created).\n-----\ndatabase/pubsub-db-create-derby.sh\n-----\n*NOTE:* It is possible to use same database which was used before - then after upgrade you will have new tables and old tables with _1 suffix.\n\n=== Execute Migration Utility\nIn the +/database+ directory you will find the +pubsub-db-migrate.sh+ file which you need to execute and pass arguments with JDBC URIs needed to connect to source and destination database. If you used dedicated tables for PubSub you will also need to pass a class name used to access database (value of +pubsub/pubsub-repo-class+ variable from +etc/init.properties+ file).\n\nExample for dedicated table used for PubSub:\n[source,sql]\n-----\ndatabase/pubsub-db-migrate.sh -in-repo-class tigase.pubsub.repository.PubSubDAO\n-in 'jdbc:mysql://localhost/tigase_pubsub?user=tigase&password=passwd'\n-out 'jdbc:mysql://localhost/tigase_pubsub?user=tigase&password=passwd'\n-----\n\nExample for use without dedicated PubSub tables:\n[source,sql]\n-----\ndatabase/pubsub-db-migrate.sh\n-in 'jdbc:mysql://localhost/tigase?user=tigase&password=passwd'\n-out 'jdbc:mysql://localhost/tigase?user=tigase&password=passwd'\n-----\n\nExample for use with dedicated tables in a Windows environment:\n[source,sql]\n-----\ndatabase/pubsub-db-migrate.cmd -in-repo-class tigase.pubsub.repository.PubSubDAO\n-in 'jdbc:sqlserver://\\\\:;databaseName=;user=tigase;password=tigase;schema=dbo;lastUpdateCount=false'\n-out 'jdbc:sqlserver://\\\\:;databaseName=;user=tigase;password=tigase;schema=dbo;lastUpdateCount=false'\n-----\n\nDuring execution this utility will report information about migration of PubSub data to the new schema, and the same information will be store in +pubsub_db_migration.log+.\n\n=== Finish\nAfter successful migration you will have all data copied to new tables. Old tables will be renamed by adding suffix _1. After verification that everything works OK, you can delete old tables and it's content as it want be used any more.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_64_-_Components_-_F_-_Server_Monitoring.asciidoc",
"content": "[[serverMonitoring]]\n= Server Monitoring\n:author: Unknown\n:version: v1.0\n\nAll the documentation and resources related to the Tigase server monitoring.\n\nxref:setupRemoteMonitoring[Setting up Remote Monitoring in the Server]\nxref:retrievingStatisticsFromTheServer[Retrieving Statistics from the Server]\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_65_-_Components_-_F_-_Server_Monitoring_-_1_-_Setting_up_Remote_Monitoring_in_the_Server.asciidoc",
"content": "[[setUpRemoteMonitoring]]\n= Setting Up Remote Monitoring in the Server\n:author: unknown\n:version: v1.0\n:date: 2010-04-06 21:18\n\nTigase server can be remotely monitored over following protocols: *JMX/RMI*, *SNMP* and *HTTP*. Even though JMX offers the biggest control and visibility to the server states, all of the monitoring services give the same basic set of the server statistics:\n\n- Number of network connections for s2s, c2s and Bosh\n- Last second, last minute and last hour load for all main components: SM, MR, c2s, s2s, Bosh, MUC and PubSub\n- System statistics - memory usage (heap and non heap) and the server uptime in milliseconds and human readable text.\n- Users statistics - number of registered users and number of online user session.\n\nJMX/RMI and SNMP servers offer basic security and can restrict access while the HTTP server doesn't offer any access restriction mechanisms. Therefore HTTP monitoring is recommended to operate behind a firewall.\n\nThe monitoring itself causes very low overhead in terms of the resources and CPU consumption on top of the normal Tigase processing requirements so it can be left on without worrying about performance degradation.\n\n*Note.* _This works with the Tigase server from version_ *4.2.0* _or SVN revision_ *1418*.\n\n== What You Need\nUsing v7.1.0 and later, statistics binaries are built-in dist-max and no extra files are needed. If you have downloaded -dist file, you will need tigase-extras.\n\nTo ensure, two files are necessary to run monitoring:\n\n. link:https://projects.tigase.org/projects/tigase-extras/files[tigase-extras] or the link:https://projects.tigase.org/projects/tigase-server/repositoryr[current snapshot].\n. *jdmkrt.jar* file from link:https://opendmk.java.net/[OpenDMK] project version 5.1 or later. A copy of this jar file in also available in our maven repository: link:http://maven.tigase.org/openDMK/jdmkrt/1.0-b02/[jdmkrt.jar].\n\nBoth files should be in the /jars directory.\n\n\n[[monitoring_activation]]\n== Activation\n\nYou can either run the Tigase installer and use the configuration wizard to activate the monitoring or edit etc/init.properties file and add following line:\n\n[source,bash]\n-----\n--monitoring=jmx:9050,http:9080,snmp:9060\n-----\n\nAs you see there is only a single line where you put list of monitoring servers you want to activate. Each server is responsible for activation of a different protocol and takes a single parameter - port number. There are following protocols supported right now:\n\n- *jmx* - activating monitoring via JMX/RMI\n- *http* - activating monitoring over HTTP protocol\n- *snmp* - activating monitoring over SNMP protocol\n\nYou can have all protocols active at the same time or any combination of them or none.\n\n== Security\n\nBoth JMX and SNMP offer security protection to limit access to monitoring data. The security configuration is a bit different for both.\n\n[[monitoring_jmx]]\n== JMX\nAfter the server installation or in the SVN repository you can find 2 files in the *etc/* directory: *jmx.access* and *jmx.password*.\n\n- *jmx.access* is a user permission file. You can use it to specify whether the user can access the monitoring data for reading only 'readonly' or with read-write 'readwrite' access. There are example entries in the file already and the content may simply look like:\n+\n[source,bash]\n-----\nmonitor readonly\nadmin readwrite\n-----\n\n- *jmx.password* is a user password file. You can set user passwords here and the format again is very simple and the same as for jmx.access. There are example entries already provided for you convenience. Content of the file may look like the example below:\n+\n[source,bash]\n-----\nadmin admin_pass\nmonitor monitor_pass\n-----\n\nUsing above to files you can control who and how can access the JMX monitoring services.\n\n=== SNMP\nAccess to SNMP monitoring is controlled using ACL (access control lists) which can be configured in the file *snmp.acl* located in *etc/* directory. It contains lots of detailed instructions how to setup ACL and restrict access per user, host and what kind access is allowed. The simplest possible configuration may look like this:\n\n[source,bash]\n-----\nacl = {\n {\n communities = public, private\n access = read-only\n managers = public.host.com, private.host.com\n }\n {\n communities = admin\n access = read-write\n managers = localhost, admin.host.com\n }\n}\n-----\n\nYou might also need Tigase MIB definition: link:https://projects.tigase.org/projects/tigase-server/repository/changes/src/main/resources/mib/JVM-MANAGEMENT-MIB.mib[TIGASE-MANAGEMENT-MIB.mib] for the server specific statistics. The MIB contains definition for all the server statistics exposed via SNMP.\n\n=== HTTP\nAccess the server at example.com:9080 and you will be presented with an Agent View.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_66_-_Components_-_F_-_Server_Monitoring_-_2_-_Retrieving_statistics.asciidoc",
"content": "[[retrievingStatisticsFromTheServer]]\n= Retrieving statistics from the server\n:author: Daniel Wisnewski\n:version: v2.0\n:date: 2015-13-07 11:22\n\n:toc:\n:numbered:\n:website: http://www.tigase.net\n\nBy default we can retrieve server statistics using XMPP, no additional setup is necessary.\n\n== Retrieving statistics using XMPP\n\nAccessing statistics over XMPP protocol requires any XMPP client capable of executing link:http://xmpp.org/extensions/xep-0050.html[XEP-0050: Ad-Hoc Commands]. It's essential to remember, that only administrator (a user whose JID is configured as administrative) can access the statistics.\n\n== Psi XMPP Client\n\nFor the purpose of this guide http://psi-im.org/[Psi] client will be used. After successfully configuring and connecting to account with administrative privileges we need to access _Service Discovery_, either from application menu or from context menu of the particular account account:\n\nimage:images/monitoring_xmpp_1.png[caption=\"Figure 1: \", title=\"Access service discovery\", alt=\"roster-discovery\", width=\"233\"]\n\nIn the _Service Discovery_ window we need to find _Server Statistics_ component:\n\nimage:images/monitoring_xmpp_2.png[caption=\"Figure 2: \", title=\"Access statistics component in service discovery\", alt=\"discovery-stats\", width=\"558\"]\n\nWe can either access statistics for all components or select particular component after expanding the tree. To execute ad-hoc command simply double click on the particular node which will open window with statistics:\n\nimage:images/monitoring_xmpp_3.png[caption=\"Figure 3: \", title=\"Server statistics\", alt=\"server-stats\", width=\"456\"]\n\nIn this window, in addition to see the statistics, we can adjust _Stats level_ by selecting desired level from the list and confim by clicking _Finish_.\n\n\n== Retrieving statistics using JMX\n\nIn order to access statistics over JMX we need to enable support for it in Tigase - xref:monitoring_activation[Monitoring Activation]. Afterwards we can use a number of tools to get to the statistics, for example the following:\n\n== JConsole\n\nAfter opening JConsole we either select local process or provide details of the remote process, including IP, port and credentials from *etc/jmx.** files:\n\nimage:images/monitoring_jmx_jconsole_1.png[caption=\"Figure 4: JConsole\", alt=\"jconsole\", width=\"754\"]\n\nAfterwards we navigate to the MBeans tab from where we can access the `tigase.stats` MBean. It offers similar options to XMPP - either accessing statistics for all components or only for particular component as well as adjusting level for which we want to obtain statistics:\n\nimage:images/monitoring_jmx_jconsole_2.png[caption=\"Figure 5: JConsole\", alt=\"jconsole\", width=\"967\"]\n\n== StatsDumper.groovy\n\nIn order to collect statistics over period of time following groovy script can be used: link:files/StatsDumper.groovy[StatsDumper.groovy]. It's a Simple JMX client that connects to Tigase and periodically saves all statistics to files.\n\nIt takes following parameters:\n[source,bash]\n----\n$ groovy StatsDumper.groovy [hostname] [username] [password] [dir] [port] [delay(ms)] [interval(ms)] [loadhistory(bool)]\n----\n* hostname - address of the instance\n* username - JMX username\n* password - JMX username\n* dir - directory to which save the files with statistics\n* port - port on which to make the connection\n* delay(ms) - initial delay in milliseconds after which statistics should be saved\n* interval(ms) - interval between each retrieval/saving of statistics\n* loadhistory(bool) - indicates whether or not load statistics history from server (if such is enabled in Tigase)\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_67_-_Components_-_F_-_Server_Monitoring_-_3_-_EventBus.asciidoc",
"content": "[[eventBus]]\n= Eventbus\n:author: Bartosz Malkowski\n:date: 2015-04-09 8:56\n:version: v1.0 September 2015\n\n:toc:\n:numbered:\n:website: http://www.tigase.org\n\nNew for Tigase version 7.1.0, is an *eventbus* component to help with monitoring has been implemented. This allows you to set thresholds for certain predefined tasks and you or other JIDs can be sent a message when those thresholds are passed. You can even configure a mailer extension to have an E-mail sent to system administrators to let them know an event has occured!\nLets begin with setup and requirements.\n\nEventbus is based on a limited http://www.xmpp.org/extensions/xep-0060.html[PubSub] specification. Events are delivered to subscribers as a normal PubSub notification.\n\nEach component or client may subscribe for specific types of events. Only components on cluster nodes are allowed to publish events.\n\n== Setup\nEventbus is enabled by default on v7.1.0 b4001 and later, no setup needed!\n\n== How it Works\nEvents in Eventbus are identified by two elements: name of event and its namespace:\n[source, xml]\n-------\n\n 1\n\n-------\nWhere event name is `EventName` and namespace is `tigase:demo`.\n\nListeners may subscribe for a specific event or for all events with specific a namespace. Because in pubsub, only one node name exists, so we have to add a way to convert the event name and namespace to a node name:\n[source]\n-------\nnodename = eventname + \"|\" + namespace\n-------\nSo for example, to subscribe to ``, node must be: `EventName|tigase:demo`. If you wish to subscribe to all events with a specific namespace, use an asterisk (`*`) instead of the event name: +*|tigase:demo+.\n\n[NOTE]\n===============================\nIf client is subscribed to /*|tigase:demo node, then events will not be sent from node /*|tigase:demo, but from the *real* node (in this case: `EventName|tigase:demo`).\n===============================\n\n[[availableTasks]]\n== Available Tasks\nEventbus monitoring has several pre-defined tasks that can be monitored and set to trigger. What follows is the list of tasks with the options attributed to each task.\n\n- *disk-task* - Used to check disk usage. +\nAvailable Options\n . +enabled[B]+ - Enable or disable task, Boolean value.\n . +period[I]+ - Period of running check, Integer value.\n . +threshold+ - Percentage of used space on disk, Float value.\n\n- *cpu-temp-task* - Used to check CPU temperature. +\nAvailable Options\n . +enabled[B]+ - Enable or disable task, Boolean value.\n . +period[I]+ - Period of running check, Integer value.\n . +cpuTempThreshold[I]+ - Temperature threshold of CPU in °C.\n\n- *load-checker-task* - Used to check system load. +\nAvailable Options\n. +enabled[B]+ - Enable or disable task, Boolean value.\n. +period[I]+ - Period of running check, Integer value.\n. +averageLoadThreshold[L]+ - Average percent load threshold, Long value.\n\n- *memory-checker-task* - Used to check memory usage. +\nAvailable Options\n. +enabled[B]+ - Enable or disable task, Boolean value.\n. +period[I]+ - Period of running check, Integer value.\n. +maxHeapMemUsagePercentThreshold[I]+ - Alarm when percent of used Heap memory is larger than, Integer value.\n. +maxNonHeapMemUsagePercentThreshold[I]+ - Alarm when percent of used Non Heap memory is larger than, Integer value.\n\n- *logger-task* - Used to transmit log entries depending on level entered. +\n. +enabled[B]+ - Enable or disable task, Boolean value.\n. +levelThreshold+ - Minimal log level that will be the threshold. Possible values are SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST, and ALL.\n\n- *connections-task* - Used to check users disconnections. +\n*NOTE: The event will be generated only if both thresholds (amount and percentage) will be fulfilled.* +\n. +enabled[B]+ - Enable or disable task, Boolean value.\n. +period[I]+ - Period of running check in ms, Integer value.\n. +thresholdMinimal[I]+ - Minimal amount of disconnected users required to generate alarm.\n. +threshold[I]+ - Minimal percent of disconnected users required to generate alarm.\n\n== Configuration\nConfiguration of the eventbus monitor can be done one of two ways; either by lines in init.properties file, or by sending XMPP stanzas to the server. You may also send XMPP stanzas VIA HTTP REST.\nXMPP stanza configurations will override ones in init.properties, but they will only last until the server restarts.\n\n=== init.properties\nTasks can be configured in the init.properties file. See xref:availableTasks[available tasks] for the tasks that can be setup.\n\nTo enable a specific monitor task, use the following line:\n-----\nmonitor/$TASKNAME/enabled[B]=true\n-----\nWhere monitor is the component name for tigase.monitor.MonitorComponent, and $TASKNAME is one of the xref:availableTasks[available task names].\n\nThis format will be the same for other settings for tasks. For example:\n-----\nmonitor/$TASKNAME/period[I]=1000\n-----\nwhich sets the check period to 1000 milliseconds.\n\n*NOTE* Once triggers have been activated, they will become dormant. Think of these as one-shot settings.\n\n==== Subscription Limitations\nTo define list of JIDs allowed to subscribe for events:\n[source, bash]\n-----\neventbus/affiliations/allowedSubscribers=francisco@denmark.lit,bernardo@denmark.lit\n-----\nIf this is left blank, all users can subscribe.\n\n=== Configuration via XMPP\nWe can also configure the eventbus monitor component using XMPP stanzas. This allows us to set and change configurations during server runtime. This is done using a series of +iq+ stanzas send to the monitor component.\n\nWe can query each component for its current settings using the following stanza.\n[source,xml]\n-----\n\n\n\n-----\n\nThe server will return the component current settings which will make things easier if you wish to edit them. In this case, the server has returned the following to us\n[source,xml]\n-----\n\n\n\nTask Configuration\n\n\n0\n\n\n60000\n\n\n0.8\n\n\n\n\n-----\nThis tells us that the disk-task setting is not active, has a period of 60000ms, and will trigger when disk usage is over 80%.\n\nTo send new settings to the monitor component, we can send a similar stanza back to the monitor component.\n\n[source,xml]\n-----\n\n\n\n\n0\n\n\n60000\n\n\n0.8\n\n\n\n\n-----\n\nTo which a successful update will give you an XMPP success stanza to let you know everything is set correctly.\n\n(Include what the response will be from this setting!)\n\nAlternatively, you can update specific settings by editing a single field without adding anything else. For example, if we just wanted to turn the +disk-task+ on we could send the following stanza:\n\n[source,xml]\n-----\n\n\n\n\n1\n\n\n\n\n-----\n\nTo set any other values, do not forget that certain parts may need to be changed, specifically the\n** fields. +\n- Your field type will be defined by the type of variable specified in the xref:availableTasks [Available Tasks] section. +\n- +var=x task#+ will be followed by the property value taken directly from the xref:availableTasks [Available Tasks] section, minus the data type parameter.\n\n== Getting the Message\nWithout a place to send messages to, eventbus will just trigger and shut down. There are two different methods that eventbus can deliver alarm messages and relevant data; XMPP messages and using the mailer extension.\n\n=== XMPP notification\nIn order to retrieve notifications, a subscription to the +eventbus@tigase.org+ user must be made.\nKeep in mind that subscriptions are not persistent across server restarts, or triggers. +\nThe eventbus schema is very similar to most XMPP subscription requests but with a few tweaks to differentiate it if you wanted to subscribe to a certain task or all of them. Each task is considered a node, and each node has the following pattern: +eventName|eventXMLNS+. Since each monitoring task has the +tigase:monitor:event+ event XMLNS, we just need to pick the event name from the list of tasks.\nSo like the above example, our event node for the disk task will be +disk-task|tigase:monitor:event+.\nApplied to an XMPP stanza, it will look something like this:\n[source,xml]\n-----\n\n \n \n \n\n-----\nDon't forget to replace $USER_JID with the bare JID of the user you want to receive those messages. You can even have them sent to a MUC or any component with a JID.\nAvailable events are as follows:\n- disk-taskEvent for +disk-task+\n- LoggerMonitorEvent for +logger-task+\n- HeapMemoryMonitorEvent for +memory-checker-task+\n- LoadAverageMonitorEvent for +load-checker-task+\n- CPUTempMonitorEvent for +cpu-temp-task+\n- UsersDisconnected for +connections-task+\n\nAlternatively, you can also subscribe to all events within the eventbus by using a wildcard * in place of the event XMLNS like this example:\n[source,xml]\n-----\n\n \n \n \n\n-----\n\n=== Sample notification from Eventbus\n[source, xml]\n-------\n\n \n \n \n \n 1\n \n \n \n \n\n-------\n\n[[monitorMailer]]\n== Mailer Extension\nTigase Server Monitor Mailer Extension (TSMME) can send messages from the monitor component to a specified E-mail address so system administrators who are not logged into the XMPP server.\n\nFor v7.1.0 versions and later, TSMME is already included in your distribution package and no extra installation is needed.\n\nFor versions older than 7.1.0 TSMME requires two files to operate:\n\n- A compiled build of tigase mailer from link:https://projects.tigase.org/projects/tigase-server-ext-mailer/repository[its repository]. Place the compiled .jar file into /jars directory.\n\n- javax.mail.jar file which may be downloaded from link:http://java.net/projects/javamail/downloads/download/javax.mail.jar[this link]. Also place this file in the /jars directory.\n\n[source,properties]\n-----\nmonitor/mailer-smtp-host=mail.tigase.org\nmonitor/mailer-smtp-port=587\nmonitor/mailer-smtp-username=sender\nmonitor/mailer-smtp-password=********\nmonitor/mailer-from-address=sender@tigase.org\nmonitor/mailer-to-addresses=receiver@tigase.org,admin@tigase.org\n-----\n\n- +monitor/mailer-smtp-host+ - SMTP Server hostname.\n- +monitor/mailer-smtp-port+ - SMTP Server port.\n- +monitor/mailer-smtp-usernam+ - name of sender account.\n- +monitor/mailer-smtp-password+ - password of sender account.\n- +monitor/mailer-from-address+ - sender email address. It will be set in field from in email.\n- +monitor/mailer-to-addresses+ - comma separated notification receivers email addresses.\n\nIt is recommended to create a specific e-mail address in your mail server for this purpose only, as the account settings are stored in plaintext without encryption.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_68_-_Components_-_G_-_Server_to_Server_Protocol.asciidoc",
"content": "[[v5xs2sps]]\n= Server to Server Protocol Settings\n:author: Artur Hefczyc \n:version: v2.0, June 2014: Reformatted for AsciiDoc.\n:date: 2010-06-29 21:27\n:revision: v2.1\n\n:toc:\n:numbered:\n:website: http://tigase.net\n\nTigase server *5.1.0* or later offers new, rewritten from scratch, implementation for s2s communication which allows you to tweak it's configuration to get a better performance in your installation.\n\nS2S (or server to server) protocol is enabled by default with optimal settings chosen. There are however, a set of configuration parameters you can adjust the server behavior to achieve optimal performance on your installation.\n\nThis documents describes following elements of the Tigase server configuration:\n\n. Number of concurrent connections to external servers\n. The connection throughput parameters\n. Maximum waiting time for packets addressed to external servers and the connection inactivity time\n. Custom plugins selecting connection to the remote server\n\n== Number of Concurrent Connections\nNormally only one connection to the remote server is required to send XMPP stanza to that server. In some cases however, under a high load, you can get much better throughput and performance if you open multiple connections to the remote server.\n\nThis is especially true when the remote server works in a cluster mode. Ideally you want to open a connection to each of the cluster nodes on the remote server. This way you can spread the traffic evenly among cluster nodes and improve the performance for s2s connections.\n\nTigase server offers 2 different parameters to tweak the number of concurrent, s2s connections:\n\n- 'max-out-total-conns' - the property specifies the maximum outgoing connections the Tigase server opens to any remote XMPP server. This is 'per domain' limit, which means that this limit applies to each of the remote domains Tigase connects to. If it is set to '4' then Tigase opens a maximum of 4 connections to 'jabber.org' plus maximum 4 connections to 'muc.jabber.org' even if this is the same physical server behind the same IP address.\n+\nTo adjust the limit you have to add following line to the +init.properties+ file:\n+\n[source,bash]\n-----\ns2s/max-out-total-conns[I]=2\n-----\n\n- 'max-out-per-ip-conns' - the property specifies the maximum outgoing connections Tigase server opens to any remote XMPP server to its single IP address. This too, is 'per domain' limit, which means that this limit applies to each of the remote domains Tigase connects to. If it is set to '1', and the above limit is set to '4', and the remote server is visible behind 1 IP address, then Tigase opens a maximum of 1 connection to 'jabber.org' plus a maximum of 1 connection to 'muc.jabber.org' and other subdomains.\n+\nTo adjust the limit you have to add following line to the init.properties file:\n+\n[source,bash]\n-----\ns2s/max-out-per-ip-conns[I]=2\n-----\n\n== Connection Throughput\nOf course everybody wants his server to run with maximum throughput. This comes with a cost on resources, usually increased memory usage. This is especially important if you have large number of s2s connections on your installations. High throughput means lots of memory for network buffers for every single s2s connection. You may soon run out of all available memory.\n\nThere is one configuration property which allows you to adjust the network buffers for s2s connections to lower your memory usage or increase data throughput for s2s communication.\n\nMore details about are available in the init.properties guide under the link to +--net-buff-high-throughput+ property description.\n\n== Maximum Packet Waiting Time and Connection Inactivity Time\nThere are 2 timeouts you can set for the component controlling s2s communication.\n\n- 'max-packet-waiting-time' - this sets the maximum time for the packets waiting for sending to some remote server. Sometimes, due to networking problems or DNS problems it might be impossible to send message to remote server right away. Establishing a new connection may take time or there might be communication problems between servers or perhaps the remote server is restarted. Tigase will try a few times to connect to the remote server before giving up. This parameter specifies how long the packet is waiting for sending before it is returned to the sender with an error. The timeout is specified in seconds:\n+\n[source,bash]\n-----\ns2s/max-packet-waiting-time[L]=420\n-----\n\n- 'max-inactivity-time' - this parameters specifies the maximum s2s connection inactivity time before it is closed. If a connection is not in use for a long time, it doesn't make sense to keep it open and tie resources up. Tigase closes s2s connection after specified period of time and reconnects when it is necessary. The timeout is specified in seconds:\n+\n[source,bash]\n-----\ns2s/max-inactivity-time[L]=900\n-----\n\n== Custom Plugin: Selecting s2s Connection\nSometimes for very large installations you may want to set larger number of s2s connections to remote servers, especially if they work in cluster of several nodes. In such a case you can also have a control over XMPP packets distribution among s2s connections to a single remote server.\n\nThis piece of code is pluggable and you can write your own connection selector. It is enough to implement 'S2SConnectionSelector' interface and set your class name in the configuration using following parameter in +init.properties+ file:\n\n[source,bash]\n-----\ns2s/s2s-conn-selector=YourSelectorImplementation\n-----\n\nThe default selector picks connections randomly.\n"
},
{
"path": "tigase-server 7.1.0/modules/documentation/adminguide/asciidoc/text/Admin_Guide_69_-_Components_-_H_-_MUC.asciidoc",
"content": "[[tigaseMUC]]\n= Tigase MUC Component\n:author: not known\n:version: v1.0 October 2015\n:date: 2015-10-01 15:00\n\n:toc:\n:numbered:\n:website: http://www.tigase.org\n\nTigase MUC component is included in all Tigase distributions, to enable MUCs have the following lines in your +init.properties+ file:\n\n-----\n--comp-name-4 = muc\n--comp-class-4 = tigase.muc.MUCComponent\n-----\n\n== Configuration Options\n- *room-log-directory* +\nDirectory to store chat logs\n-----\nmuc/room-log-directory=/var/log/muc/\n-----\n\n- *message-filter-enabled* +\nTo disable filter and allow MUC transfer all subelements in set:\n-----\nmuc/message-filter-enabled[B]=false\n-----\n\nFor example, this allows users to send XHTML stanzas through MUC chatrooms on your server.\n\n- *presence-filter-enabled* +\nTo disable filter and allow MUC transfer all subelements in set:\n-----\nmuc/presence-filter-enabled[B]=false\n-----\n\n- *search-ghosts-every-minute* +\nTo enable pinging occupants every minute\n-----\nmuc/search-ghosts-every-minute[B]=true\n-----\n\n- *ghostbuster-enabled* +\nTo disable active searching of ghosts in MUC Rooms:\n-----\nmuc/ghostbuster-enabled[B]=false\n-----\n\n- *muc-allow-chat-states* +\nTo allow transfer of chat-states in MUC messages:\n-----\nmuc/muc-allow-chat-states[B]=true\n-----\n\n- *muc-lock-new-room* +\nTo turn off default locking newly created rooms:\n-----\nmuc/muc-lock-new-room[B]=false\n-----\nBy default new room will be locked until owner submit room configuration.\n\n- *muc-multi-item-allowed*\nTo disable joining from few resources to sinlge nickname:\n-----\nmuc/muc-multi-item-allowed[B]=false\n-----\n\n=== History Providers Parameters\n- *history-db* +\nDatabase type. By default the same what is used as User Repository in Server.\nProvided types: +derby+, +mysql+, +memory+, +pgsql+, +sqlserver+, +none+.\n-----\nmuc/history-db=none\n-----\n\n- *history-db-uri* +\nURI for database, if should be used different than default from Tigase Server:\n-----\nmuc/history-db-uri=jdbc:derby:/database/tigasedbmuc\n-----\n\n=== Public log\n- *muc-logger-class* +\nTo set custom class for MUC logger:\n-----\nmuc/muc-logger-class=com.example.CustomLogger\n-----\nClass must implment interface +tigase.muc.logger.MucLogger+.\n\n=== Modules\nEach module can be configured to use custom implementation by including it in the init.properties, the defaults are as follows:\n[source,properties]\n-----\nmuc/modules/jabber:iq:version[S]=tigase.component.modules.impl.JabberVersionModule\nmuc/modules/owner[S]=tigase.muc.modules.RoomConfigurationModule\nmuc/modules/presences[S]=tigase.muc.modules.PresenceModuleImpl\nmuc/modules/groupchat[S]=tigase.muc.modules.GroupchatMessageModule\nmuc/modules/invitations[S]=tigase.muc.modules.MediatedInvitationModule\nmuc/modules/urn:xmpp:ping[S]=tigase.component.modules.impl.XmppPingModule\nmuc/modules/unique[S]=tigase.muc.modules.UniqueRoomNameModule\nmuc/modules/disco[S]=tigase.muc.modules.DiscoveryModule\nmuc/modules/iqforwarder[S]=tigase.muc.modules.IqStanzaForwarderModule\nmuc/modules/admin[S]=tigase.muc.modules.ModeratorModule\nmuc/modules/privatemessages[S]=tigase.muc.modules.PrivateMessageModule\nmuc/modules/commands[S]=tigase.component.modules.impl.AdHocCommandModule\n-----\n\n[[mucRoomConfig]]\n=== Room Configuration options\nIn addition to the default Room configuration options defined in the MUC specification Tigase offers following as well:\n\nTigase MUC Options::\n- tigase#presence_delivery_logic - allows configuring logic determining which presence should be used by occupant in the room while using multiple-resource connections under one nickname, following options are available:\n * PREFERE_PRIORITY\n * PREFERE_LAST\n- tigase#presence_filtering - (boolean) when enabled broadcasts presence only to selected affiliation groups\n- tigase#presence_filtered_affiliations - when enabled tigase#presence_filtering is enabled one can select affiliation which should receive presences, following are possible to select from:\n * owner\n * admin\n * member\n * none\n * outcast\n- muc#roomconfig_maxusers - Allows configuring of maximum users of room.\n\n\nConfiguring default room configuration in init.properties::\n-----\nmuc/default_room_config/
![](\"${util.link(\"/avatar/\")
\n