Info: Performing the steps described in this article requires direct server access. Depending upon how your system is hosted and the level of access you have to that system, coordination may be required with your Partner or WoodWing Support team. When Studio Server is running in WoodWing Cloud, these steps are managed by WoodWing. For a full overview of the steps that need to be done by WoodWing and how to request them, see WoodWing Cloud - Change management.
Installing additional Studio Servers can be beneficial when having to set up environments using different languages, terminologies, and so on.
In essence, setting up additional servers is very much the same as setting up the very first instance of Studio Server on a system, but with a few minor differences.
Step 1. Perform the steps as explained in Installing Studio Server, 'step 5: Installing Studio Server', but with the following differences:
- For step 2: when copying the StudioServer folder to the web root folder, make sure to give the folder a name that is different than any StudioServer folders that are already present.
- For step 5: point the
INETROOTvalues of the config.php file to the new Studio Server folder.
Step 2. <![CDATA[ ]]>In Studio Server, click Server Plug-ins to access the Server Plug-ins page and thereby initiating all Server plug-ins.
Step 3. In Studio Server, access the Health Check page (Advanced > Health Check) and run the appropriate tests.
Note: The database can also reside on one of the machines used as the application server. When using MSSQL or Oracle as the database you need to install the database client libraries on the same system as where the application server resides.
Do you have corrections or additional information about this article? Leave a comment! Do you have a question about what is described in this article? Please contact Support.
Please sign in to leave a comment.