![]() |
![]() |
![]() |
|||||
Getting Started with TaigaFrom Rex community wiki
What is Taiga 0.1.3?
Frequently Asked Questions About Taiga
Getting Taiga 0.1.3BinariesWe only provide binaries for the windows environment. Check below how to build from source if you are running linux.
Building from sourceOur sources for the Taiga project are located at http://github.com/realXtend/taiga Using source packet
Using git
Quick Build InstuctionsAfter you have Taiga 0.1.3 and modrex source we can start building. For more details read <taiga_source_location>/BUILDING.txt WindowsYou will need .NET 3.5 to build Taiga in windows. open up a cmd.exe command prompt cd <taiga_source_location> runprebuild.bat // You have now created the OpenSim.sln project file for Visual Studio 2008. compile.bat // Will build OpenSim with the default debug configuration. // If you want to build release configuration, open up the solution file in Visual Studio // and select Release from the top toolbar and build. LinuxYou will need Mono >= 2.4.2 and Nant >= 0.85 to build Taiga in linux. cd <taiga_source_location> cp addon-modules/ModreX/ModularRex/bin/* bin/ ./runprebuild.sh nant cp -a addon-modules/ModreX/ModularRex/ScriptEngines bin/ cp -a addon-modules/ModreX/ModularRex/addon-modules bin/ rm bin/Mono.Security.dll Configuring with Taiga Config WizardWe have implemented a simple configuration wizard, which can be found here. We hope that this tool will ease the pain of having to go through numerous .xml and .ini files in order to get your servers running. You can start the wizard with configure.bat. In the first view enter your Taiga 0.1.2 opensim folder location, this should be prefilled if it finds ../opensim/opensim.exe. After this you proceed and fill in the needed information to all pages. When you get to the last page you can export the configs to your opensim location by clicking Finish. Note that if you are using MySQL the default databases are opensim, grid and taigawebdav. The databases are also configurable with the wizard. You will have to create the set databases before you run start.bat. Notes: If you are in a 64-bit environment you wont most likely be able to use SQLite as youd db. Please let use know about bugs or improvement ideas you might have for the configuration tool. Known issuesPROBLEM: The wizard still has some bugs and one of them is that every value in opensim/Regions/Regions.ini is surrounded with " " quotes. If you have problems starting up or loggin into your Taiga this might be the cause. The bug will be fixed to the next config creator release. FIX: After you have exported the configs from config wizard and before you start the servers go and edit the Regions.ini manually. Remove the surrounding " " from UUIDs, IPs, ports and region names. This should do it. If you already started the servers before doing this, the databases might already be trashed with incorrect values. Should help to sweep the regions table from the grid database and restarting the servers. RESOLVED IN TAIGA 0.1.3 Configuring ManuallyFor running servers we need to configure 3 + n or 5 + n servers depending on are we supporting legacy login and how many sims are we running. The pictures below illustrates different configurations that can be used. Legacy servers are optional, and are probably going to be dropped out at some point. User server is where client viewers login with OpenID or legacy realXtend login protocol. User server then authenticates and figures out where viewer is trying to log to. Robust server provides grid services, so thats where sims register themselves and user server can query where regions are located from robust server. During login process user server sends enable client message to sim where viewer is trying to login to. Viewer, user server and sim then exchange session id's and when login is succesfull viewer enter the sim. During legacy login client is authenticated through authentication server, and authentication server provides avatarstorage address. OpenSim configuration filesOpenSim configuration includes configuring 3 files in our case, this of course depends how many sims you are running and how many regions they contain, but in the simplest case where we just configure 1 sim for Naali login, we need to configure 3 files. OpenSim.ini that resides in bin, Regions.ini that resides under Regions folder in bin and modrex.ini that resides in bin\addon-modules\ModreX\config folder. For installing MySql server etc, see the Taiga server documentation OpenSim.iniIn OpenSim.ini you need to pay attention to following ini items: [Startup]
clientstack_plugin must be set to ModularRex so that when client logs in sim creates NaaliClientView that deals with realxtend features: for example broadcasts avatar addresses to other clients in sim so avatar appearances show up correctly.
For database connections you need to choose one of available database providers. sqlite or mysql are recommended. storage_plugin deals with regions database connections.
physics parameter defines physics engine to be used and basicphysics is one that is known to work without exeptions at the time of writing. Be sure that this is only declared once, when included modrex.ini declares this for the second time exeptions may occur. [Network]
These specify port where client connects to and default location for client (The user server sends these to Naali, after it asks them from robust server)
These urls are the corresponding grid, user, asset, inventory and messaging server addresses. In our configuration grid, asset and inventory services are located at robust server and therefore they have the same ip. [AssetService]
Defines asset loader for opensim and again uri pointing to robust server [InventoryService]
Again setting the inventory service to point to robust service [GridService]
Setting the grid service to point robust server [AuthorizationService]
Setting the authorization service to point to user server [Modules]
These connectors connect the opensim to robust server services, the first part before the colon (:) gives the dll name and the latter part the connector name in the dll. Asset, inventory and grid service connectors for connecting to robust service all reside inside ModCableBeach.dll. Include-modules must point to plase where modrex.ini is located. See our OpenSim.ini example Regions.iniRegions.ini has simple syntax, you just give your region name in square brackets and give region values like normal ini file values like: [My Sim name] RegionUUID = b25f33f2-7d10-4c18-bd2f-130ad19440d7 Location = 1000,1000 InternalAddress = 0.0.0.0 InternalPort = 9001 AllowAlternatePorts = False ExternalHostName = SYSTEMIP MasterAvatarFirstName = Test MasterAvatarLastName = User MasterAvatarSandboxPassword = test You can have more than one region defined in the same file, RegionUUID, sim name, location and port must be unique to each region. Usually these are asked in the region startup and sim creates this file for you. Modrex.ini [Startup]
This must be disabled, so when enabling rex event queue could be enabled [realXtend]
Enabling realXtend UDP ports and realXtend avatars
Enabling python and rex event queue
This does probably have not effect since clientstack_plugin is set to ModularRex and port 9000 used for Naali connections, but to be on the safe side is set here
This is connection string for modrex, depending on your choise of database set your database driver, database user name and password here.
ClientView should be set to naali for the realXtend Naali viewer. See our modrex.ini example and more information about configuring ModreX Robust server configurationFor robust server you only need to configure OpenSim.Server.ini [Startup]
Startup section and ServiceConnectors parameter tells what dlls Robust server loads at startup as comma (,) separated list of dll and service to load value pairs, like ModCableBeach.dll:CableBeachServerConnector, where ModCableBeach.dll is dll name and CableBeachServerConnector is the service loaded from dll. In the above example all connector services that Naali needs are listed. [Network]
Port of the Robust server. [CableBeachService]
Our robust service url and port
This is set to point to UserServer
UserService is also located at UserServer
These values need to be specified WebDAV property provider, you need to set up your database access, with correct user id and password, or use DummyPropertyProvider. DummyPropertyProvider wont store WebDAV properties, so when using DummyPropertyProvider inventory properties will be lost on server startup. [AssetService]
As an example, the above configuration precisely mimicks the legacy asset server. It is read by the asset IN connector (defined above) and it then loads the OUT connector (a local database module). That, in turn, reads the asset loader and database connection information. Above values are tested with Naali, you need to set your corresponding database access connectionstrings with correct user id and password, you probably can also use other storage providers. [InventoryService]
Same values as for asset service, in addition inventory service also needs UserServerURI for authenticating inventory requests. [GridService]
This section specifies Robust services grid database connection, again you need to specify here your database connection string. Above example sets up mysql storage provider for grid regions. See our OpenSim.Server.ini example Messaging Server configurationFor messaging server you only need to configure MessagingServer_Config.xml The xml file has Config element that has these attributes:
Here we setup user server and grid server (robust server address) for messaging server and setup database connection credentials and set database table name (grid), set database provider dll and dll for region comms provider, below is link for example file: User Server configurationFor user server you only need to configure UserServer_Config.xml These attributes are set in the Config xml element:
Obviously we set here startup message and grid + inventory servers to point to robust server and also authentication server to point to user server. The default word is used on those parameters because with openId inventory and authentication services can be somewhere else. Again we set database connection string and provider. Example file describes the xml file in more detail: See our UserServer_Config.xml example Setting up MySqlGetting MySQL
Creating needed databases to MySQLOpen your Windows command prompt and do the following. One line is one command in the command prompt, press enter after every line as we proceed. mysql -u root -p Enter password: <insert_your_root_password_here>
CREATE DATABASE opensim; CREATE DATABASE grid; CREATE DATABASE taigawebdav; CREATE DATABASE os_modrex;
RunningAfter you are done configuring we are ready to start the servers. When a server starts its suggested at least for the first runs to check that the server is started properly and no errors occurred. You should also give time for every server to boot up successfully before starting the next server. If you have problems with OpenSim.32BitLaunch.exe running on a 32-bit operating system you can use OpenSim.exe instead. WindowsWe have made a batch file for starting the all servers in the right sequence. This is only located in the binary release. cd <taiga_location> start.bat If you build Taiga 0.1 from source heres the rundown on how to start your servers. cd <taiga_source_location>\bin call OpenSim.Server.exe call OpenSim.Grid.UserServer.exe call OpenSim.Grid.MessagingServer.exe call OpenSim.32BitLaunch.exe LinuxYou will need to open up new terminals for every server. All executables are located in <taiga_source_location>/bin mono OpenSim.Server.exe mono OpenSim.Grid.UserServer.exe mono OpenSim.Grid.MessagingServer.exe mono OpenSim.32BitLaunch.exe Changelog and HistoryVersion 0.1.3 (26.8.2010)
Version 0.1.2 (19.5.2010)
Version 0.1.1 (3.5.2010)
Version 0.1 (1.4.2010)
|
|||||||
![]() |
![]() |
![]() |





