- Configuration
- Notifications
- Other
- Activate log tracker for a user
- Add SSL certificate
- Add Monitor Task
- Add Monitor Timer Task
- Add New Item - ext
- Add New Item - Vhost
- Change user inter-domain communication permission
- Connections Time
- DNS Query
- Default room config
- Delete Monitor Task
- Fix User’s Roster
- Fix User’s Roster on Tigase Cluster
- Get User Roster
- Get any file
- Get Configuration File
- Get init.properties File
- Load Errors
- New command script - Monitor
- New command script - MUC
- OAUth credentials
- Pre-Bind BOSH user session
- Reload component repository
- Scripts
- Statistics
- Users
This is an advanced window for settings and management for the XMPP server.
From 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.
This section gives you a drop-down menu for components - List will provide a list of active running components with the following format component name :: componentInfo{Title=Server, Server version/revision (submission date), Class=component class} For example: amp :: componentInfo{Title=Tigase XMPP Server, Version=7.1.0-SNAPSHOT-b3990/574c329f (2015-08-28/10:32:06), Class=tigase.server.amp.AmpComponent}
- 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.
- 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.
- Remove allows you to remove components from a dropdown list. Components will be removed upon confirmation, however settings will be reverted on server restart.
This 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.
This 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. Logging will cease once the server restarts.
Here 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.
You 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.
This section allows you to add monitor scripts in Groovy while using a delay setting which will delay the start of the script.
Provides 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.
You 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.
Allows you to set the default configuration for new MUC rooms. This will not be able to modify current in use and persistent rooms.
This 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.
You 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.
This does the same as the Fix User’s Roster, but can apply to users in clustered servers.
As 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.
Enables 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: logs/tigase.log.0
If 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.
Will output the current init.properties file, this includes any modifications made during the current server session.
Will display any errors the server encounters in loading and running. Can be useful if you need to address any issues.
Allows 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.
Allows 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.
Uses OAuth to set new credentials and enable or disable a registration requirement with a signed form.
Allows 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.
This will show if you have any external components and will reload them in case of any stuck threads.
This section provides a list of command scripts for all active components. Each component has the following options - Get list available commands will list script commands for the component divided by either Scripts or Groups. - 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. - 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.
You will be unable to edit or run commands from this section.
These 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.
Provides 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.
Provides 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.
This 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.
This section returns the number of active users per specific vhost.
Here 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.
Allows 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.
Provides a text window for admins to input the bare JID of the user they wish to remove from the server.
This section allows admins to get information about a specific user including current connections as well as offline and online messages awaiting delivery.
Provides 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.