This topic walks you through the process of installing TrueSight Server Automation on Microsoft Windows, using the unified product installer and component installers.
Introduction
This topic is intended for system administrators preparing to install the TrueSight Server Automation product. The goal of this topic is to demonstrate how to use the unified product installer to install all essential components of the TrueSight Server Automation product in a Windows environment.
The unified product installer simplifies and improves the installation experience by providing a centralized UI for installing the default Application Server node. It installs a setup that consists of the following components:
- Microsoft SQL database: The unified product installer creates a TrueSight Server Automation schema on your database server.
- Default Application Server: This is the primary server that is installed in a TrueSight Server Automation environment. The unified product installer configures the default Application Server to connect to your database server. It also installs an RSCD agent on the default Application server. The default Application Server is also referred to as a default Application server node, because it hosts more than one component.
- File Server: You can choose to install the file server on the same machine as the default Application server (called as the local file server) or install it on a separate machine (called as a separate file server.) In the case of a separate file server, you can choose to manually install the RSCD agent or have it installed by the unified product installer.
- Console and PXE/TFTP server: The unified product installer installs the PXE/TFTP server and the optional console on the default Application Server.
What does this walkthrough show?
In this walkthrough, we will:
- Use the unified product installer to install a small TrueSight Server Automation environment (Application Server, console, file server, PXE/TFTP).
- Use the quick start page to import servers to the new environment and to add agents to those servers.
- Use individual component installers to manually install additional components such as additional Application Servers, a separate PXE/TFTP server, and a separate console server, to complete a production-level environment.
The TrueSight Server Automation environment will have the following characteristics:
| | |
|---|
| | This TrueSight Server Automation environment consists of two Application Servers: - A default Application server installed by the unified product installer on a Windows 2012 (x64) system.
- An additional Application Server installed on a Windows 2012 (x64) system to improve the performance of TrueSight Server Automation.
|
| | This TrueSight Server Automation environment consists of two instances of the TrueSight Server Automation console: - Optional console that you can install by the unified product installer on the default Application Server node.
- Optional console that you can manually installed on a separate machine (recommended for high performance environments)
|
| | The default Application Server connects to an existing Microsoft SQL server database. Note: Although the TrueSight Server Automation schema is created by the unified product installer, you must have access to an existing database that has been set up on a Microsoft SQL Server. For a description of that process, see Walkthrough: Setting up a SQL Server database. |
| | This TrueSight Server Automation environment uses a separate Windows file server machine that is installed by the unified product installer. |
| | This TrueSight Server Automation environment consists of two PXE/TFTP servers: - The PXE/TFTP server installed by the unified product installer on the default Application Server node
- A PXE/TFTP server that is manually installed on a separate machine (recommended for high performance environments).
|
What do I need to do before I get started?
Perform the following prerequisite steps before executing this walkthrough scenario:
- Download the unified product installer files to a temporary location. The TSSA<version>-WIN64.zip and TSSA<version>-RSCDAgents.zip files required in the this walkthrough can be downloaded from the Electronic Product Distribution (EPD) website. For instructions on downloading the files, see Downloading-the-installation-files .
- You must be able to access an existing database that has been set up on Microsoft SQL Server. For a description of that process, see Walkthrough: Setting up a SQL Server database .
If you want the unified product installer to automatically install the RSCD agent on your Windows file server, you must download the Microsoft Sysinternals Suite from the Microsoft tech support site and copy the PsExec file to the %PATH% variable on the default Application Server node (typically C:\Windows\System32\). By doing so, you configure the default Application Server machine as a PsExec server.
Note
- A PsExec server is not required if you choose to manually install RSCD agents on your Windows servers. For more information, see Setting-up-a-PsExec-server.
- The default Application Server can also be configured as a PsExec server, to install agents automatically, while adding additional Windows Application servers or Windows target servers.
- Uninstall any existing version of the RSCD Agent.
Update the Windows Terminal Services Server Settings for temporary folders. (In Windows Server 2008 R2 and later versions, Terminal Services is renamed to Remote Desktop Services).
Click here for steps about updating the Windows Terminal Services
To update the Windows Terminal Services (or Remote Desktop Services) configuration perform either of the following steps:
Server settings method- On the computer where you are installing the TrueSight Server Automation Console, select Start > Run.
- For Open, enter gpedit.msc, and then click OK.
- Navigate to the Temporary folders policies:
Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services >Remote Desktop Session Host > Temporary folders
or:
Computer Configuration > Administrative Templates > Windows Components > Terminal Services > Terminal Server > Temporary folders - Set the Properties of Do not delete temp folder upon exit to Enabled and then click OK.
- Set the Properties of Do not use temporary folders per session to Enabled and then click OK.
- Restart the computer.
If the settings do not take effect, use the Registry Editor (regedit):
Registry editor method- Click Start > Run and enter regedit.
- Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server.
- Set the DeleteTempDirsOnExit and the PerSessionTempDir values to 0.
- Restart the computer.
Note: The installation program uses temporary folders to preserve the install log. Usually, you can perform this update only one time; you do not need to update the configuration every time you install. However, if your Server Settings are different from those needed for installation, after you finish installing the console you can change the settings back to their previous settings.
How to install the default Application Server and separate file server using the unified installer
We start the installation process by using the unified product installer to:
- Install the default Application Server node
- Install the separate file server
- Configure the database
- Install the the PXE/TFTP server and an optional console on the default Application Server
This example uses TrueSight Server Automation version 8.9.03.
| | |
|---|
| Run the unified product installer on the machine on which you want to install the default Application server node. - Extract the TSSA<version>-WIN64.zip and TSSA<version>-RSCDAgents.zip files that you downloaded from the EPD to obtain the rscd folder and the TSSA<version>-WIN64\Disk1 folder.
- Copy the rscd folder from within the RSCDAgents extracted package to the following path in the TSSA<version>-WIN64 folder: ..\TSSA<version>-WIN64\Disk1\files\installers\
Run the setup.exe file that is In the TSSA<version>-WIN64\Disk1 folder as an Administrator to start the unified product installer wizard.
Otherwise, the installation might fail when you cannot update files in the C:\Windows\rsc folder. Important TrueSight Server Automation installation with UPI fails on international platforms because the result of disk space check is provided in foreign languages. To prevent this issue, you can skip the disk space check using the following option: setup.exe -J SKIP_DISK_SPACE_CHECK=true For information about the supported international languages, see Language-information. - Select the language in which you want to run the installer and click OK.
| |
| Read through the basic information about the unified product installer and the types of nodes that are installed in the environment. Click Next. | |
| Read the End User License Agreement (EULA) and select I agree to the terms of the license agreement. Click Next. | |
| Read the TrueSight Server Automation copyright information and select I agree to the terms of the license agreement. Click Next. | |
| The unified product installer pre-analyzes your environment: - Checks whether the platform on which you are trying to install the product is supported. If the platform check is successful, Microsoft Visual C++ 2015 Redistributable Update 3 is installed automatically.
- If the platform check fails, the installation program aborts installation with an error message and an error message is added to the log file.
| |
| Enter the database server details. - Enter the Host name or IPv4 address of the server that runs the database. Note that if your server is on an IPv6 address system you can only enter the host name of the server.
- Enter the Port that the database listens on. The default port is1433 for an SQL Database.
- Enter the Name of the database instance that you created. (See Walkthrough: Setting up a SQL Server database )
- Enter the Login Name and Login Password that you created for the database. (See Walkthrough: Setting up a SQL Server database )
- Click Next.
Click here if you want to use a connection string to connect to the database server
The Advanced option is only selected if you want to provide a custom connection string to your database. Note that all other fields are disabled when this option is selected.Type the database connection string in the field adjacent to the Advanced check box. An example of a connection string for an SQL database server is as follows: jdbc:sqlserver://<DBSERVER>:<PORT>;DatabaseName=<DBNAME>;SelectMethod=cursor Replace the variables in the above connection string, as follows: <DBSERVER> is the name or IP address of the database server
<PORT> is the port used to communicate with the database
<DBNAME> is the database name used to identify the SQL database | |
| Enter the passwords and confirm them in the Password Configuration Panel. The Password Configuration Panel includes the RBACAdmin password, BLAdmin password, and Certificate password, each accompanied by a description message. Note: All of these password fields are mandatory and initially blank by default. RBACAdmin Password
TrueSight Server Automation creates a built-in user called RBACAdmin during the installation process.
Click here for more information.
The RBACAdmin user is only assigned the RBACAdmins role.
To activate the default user, it must be assigned a password and granted access to servers in your network. You can use the RBAC Manager folder to perform these actions, but to start the console the first time, you must define a password for the RBACAdmin user.
For more information, see RBACAdmin-and-BLAdmin-users. BLAdmin Password
TrueSight Server Automation creates a built-in user called BLAdmin during the installation process.
Click here for more information.
The BLAdmin user is only assigned the BLAdmins role.
To activate the default user, it must be assigned a password and granted access to servers in your network. You can use the RBAC Manager folder to perform these actions, but to start the console the first time, you must define a password for the BLAdmin user. For more information, see RBACAdmin-and-BLAdmin-users. Certificate Password
The Application Server installation program needs a certificate password to generate a self-signed X.509 certificate.
Click here for more information.
Communication between TrueSight Server Automation and servers being provisioned uses the Transport Layer Security (TLS) protocol and X.509 certificates.The password must be at least 6 characters. For more information about certificates and the TLS protocol, see Authentication.
Click Next. | |
| A summary of the database parameters, default installation location, Application Server base port, and file server parameters is displayed. The name of the local super user for RSCD Agent mapping is also listed.
| |
| Click Customize Configuration. The Installation Directory tab displays the path where TrueSight Server Automation is installed. The default path is C:\Program Files\BMC Software\BladeLogic\ for Windows. You can customize the Installation Directory based on your requirements. | |
| Click the File Server tab and enter the file server details. - To install the file server on a separate machine, select the Install file server on a separate host option.
- Enter the Host name or IPv4 address of the file server. Note that if your server is on an IPv6 address system, you can only enter the host name of the server.
- Enter the directory on the file server where data is stored.
- (Applicable if you haven't selected the option in step 1) Enter the name of the local super user to which the RSCD Agent should map incoming connections during the installation. The super user should be local Administrator or Administrator-equivalent local user. The default super user on the first node is Administrator.
- (Applicable if you have selected the option in step 1) On the Application Server Agent Mapping tab, enter the name of the local super user to which the RSCD Agent should map incoming connections during the installation. The super user should be local Administrator or Administrator-equivalent local user. The default super user on the first node is Administrator.
Note: If the file server is on a separate machine and if it runs on Windows, ensure that you have configured the default Application Server as a PsExec server. | |
| Click the Ports tab at the top of the screen. Enter the Application Server Base port. Application Server ports are normally configured from a base port, with 9800 being the default base port. Arbitrary port assignments can be made in all cases. For more information, see Application Server ports. | |
| As an option, click the Console tab. Select Install TrueSight Server Automation Console. Note BMC does not recommend installing the console on the same machine as the Application Server. When you upgrade the Application Server, the console is not automatically upgraded. You must manually upgrade it yourself. | |
| Click Update Configuration to apply all the configuration changes that you entered on the various tabs. | |
| Click Install to proceed with the installation. The unified product installer performs the following setup operations: - Creates a TrueSight Server Automation schema in the database
- Installs the default application server
- Installs the optional console, if selected.
- Installs a PXE/TFTP server
- Installs the Network Shell
- Connects the default Application Server machine to the database
- Installs the separate file server and the RSCD agent
- Installs out-of-the-box compliance content
- Installs pre-packaged sample content (blcontent) and imports various zipkits with pre-defined content for specific tasks
| |
| If you encountered any errors while installing, click View Log to view a detailed report of the installation. Tip: BMC recommends that you save a copy of the log, before you contact technical support for further assistance. If all operations are completed successfully, click Done to exit the wizard. | |
How to add additional Application Servers
To meet the demands of a larger data center, you can deploy additional Application Servers. The additional Application Server is used for improving the performance of TrueSight Server Automation. The method described here for adding additional Application Servers is relevant only if you installed your default Application Server node using the unified product installer.
Note
This example uses TrueSight Server Automation version 8.7; however, the process is applicable to all versions 8.6 and later.
From TrueSight Server Automation 8.9.02 and later, Microsoft Visual C++ 2015 Redistributable Update 3 is installed automatically for all Microsoft Windows RSCD agent versions, provided the platform on which you are trying to install the product is supported.
| | |
|---|
| | |
|---|
| Perform the following: - Minimize the quick start page
- Right-click Servers, and click Add Server to add a PsExec server to the TrueSight Server Automation environment.
Note: If you did not copy the PsExec file to %PATH% (typically C:\Windows\System32\) of the PsExec server, you see an error in this step. - Enter the host name or IP address of the PsExec server
- Click Finish.
The PsExec Server is added to the TrueSight Server Automation environment.
| |
|---|
| Select the Configuration menu and then click Add BSA Application Server Machine. | |
|---|
| Enter the following details. - Host name or IPv4 address of the Application Server. Note that if your Application Server is on an !Pv6 address system you can only enter the host name of the server.
- User name of an account with Administrator privileges on the additional Application Server machine.
- Password of the account with Administrator privileges on the additional Application Server machine.
- Confirm the password of the account with Administrator privileges on the additional Application Server machine.
- Select the PsExec server from your environment.
| |
|---|
| Click the Advanced Options tab at the top and enter the following details. - Path to the location where you want to install the additional Application Server. The default path used is C:\Program Files\BMC Software\BladeLogic\
- Application Server ports are normally configured from a base port, with 9800 being the default base port. Arbitrary port assignments can be made in all cases. For more information, see Application Server ports.
- Enter the location you want to use as the temporary staging directory during the installation.
| |
|---|
| - Click the Validation tab at the top.
- Checks whether the platform on which you are trying to install the product is supported. If the platform check is successful, Microsoft Visual C++ 2015 Redistributable Update 3 is installed automatically.
- If the platform check fails, the installation program aborts installation with an error message displayed in the Status field. Also, an error message is added to the log file.
- Click Add node.
| |
|---|
| The additional Application Server is installed. Click OK. | |
|---|
How to add servers and install agents from the quick start page
The next step in setting up the TrueSight Server Automation environment is to import servers and add agents to those servers. An easy way to do this is by using the quick start page.
Failed to execute the [excerpt-include] macro. Cause: [Error number 2 in 0: No wiki with id [confluencePage:page] could be found]. Click on this message for details.
org.xwiki.rendering.macro.MacroExecutionException: Failed to get document for reference [confluencePage:page:Walkthrough. Adding multiple target servers to the environment]
at com.xwiki.macros.excerptinclude.internal.macro.ExcerptIncludeMacro.internalExecute(ExcerptIncludeMacro.java:130)
at productHelper.macros.BmcExcerptIncludeMacro.internalExecute(BmcExcerptIncludeMacro.java:27)
at productHelper.macros.BmcExcerptIncludeMacro.internalExecute(BmcExcerptIncludeMacro.java:18)
at com.xwiki.macros.AbstractProMacro.execute(AbstractProMacro.java:116)
at org.xwiki.rendering.internal.transformation.macro.MacroTransformation.transform(MacroTransformation.java:441)
at org.xwiki.rendering.internal.transformation.DefaultRenderingContext.transformInContext(DefaultRenderingContext.java:183)
at org.xwiki.rendering.internal.transformation.DefaultTransformationManager.performTransformations(DefaultTransformationManager.java:88)
at org.xwiki.display.internal.DocumentContentAsyncExecutor.executeInCurrentExecutionContext(DocumentContentAsyncExecutor.java:396)
at org.xwiki.display.internal.DocumentContentAsyncExecutor.execute(DocumentContentAsyncExecutor.java:269)
at org.xwiki.display.internal.DocumentContentAsyncRenderer.execute(DocumentContentAsyncRenderer.java:112)
at org.xwiki.rendering.async.internal.block.AbstractBlockAsyncRenderer.render(AbstractBlockAsyncRenderer.java:157)
at org.xwiki.rendering.async.internal.block.AbstractBlockAsyncRenderer.render(AbstractBlockAsyncRenderer.java:54)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.syncRender(DefaultAsyncRendererExecutor.java:290)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.render(DefaultAsyncRendererExecutor.java:267)
at org.xwiki.rendering.async.internal.block.DefaultBlockAsyncRendererExecutor.execute(DefaultBlockAsyncRendererExecutor.java:125)
at org.xwiki.display.internal.DocumentContentDisplayer.display(DocumentContentDisplayer.java:67)
at org.xwiki.display.internal.DocumentContentDisplayer.display(DocumentContentDisplayer.java:43)
at org.xwiki.display.internal.DefaultDocumentDisplayer.display(DefaultDocumentDisplayer.java:96)
at org.xwiki.display.internal.DefaultDocumentDisplayer.display(DefaultDocumentDisplayer.java:39)
at org.xwiki.sheet.internal.SheetDocumentDisplayer.display(SheetDocumentDisplayer.java:123)
at org.xwiki.sheet.internal.SheetDocumentDisplayer.display(SheetDocumentDisplayer.java:52)
at org.xwiki.display.internal.ConfiguredDocumentDisplayer.display(ConfiguredDocumentDisplayer.java:68)
at org.xwiki.display.internal.ConfiguredDocumentDisplayer.display(ConfiguredDocumentDisplayer.java:42)
at com.xpn.xwiki.doc.XWikiDocument.display(XWikiDocument.java:1412)
at com.xpn.xwiki.doc.XWikiDocument.getRenderedContent(XWikiDocument.java:1548)
at com.xpn.xwiki.doc.XWikiDocument.displayDocument(XWikiDocument.java:1498)
at com.xpn.xwiki.doc.XWikiDocument.displayDocument(XWikiDocument.java:1467)
at com.xpn.xwiki.api.Document.displayDocument(Document.java:788)
at jdk.internal.reflect.GeneratedMethodAccessor545.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:569)
at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke(UberspectImpl.java:571)
at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:554)
at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:221)
at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:368)
at org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:704)
at org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:75)
at org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:242)
at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:147)
at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:439)
at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:190)
at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:147)
at org.xwiki.velocity.internal.directive.TryCatchDirective.render(TryCatchDirective.java:86)
at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:304)
at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:439)
at org.apache.velocity.Template.merge(Template.java:358)
at org.apache.velocity.Template.merge(Template.java:262)
at org.xwiki.velocity.internal.InternalVelocityEngine.evaluate(InternalVelocityEngine.java:225)
at com.xpn.xwiki.internal.template.VelocityTemplateEvaluator.evaluateContent(VelocityTemplateEvaluator.java:105)
at com.xpn.xwiki.internal.template.TemplateAsyncRenderer.evaluateContent(TemplateAsyncRenderer.java:219)
at com.xpn.xwiki.internal.template.TemplateAsyncRenderer.renderVelocity(TemplateAsyncRenderer.java:174)
at com.xpn.xwiki.internal.template.TemplateAsyncRenderer.render(TemplateAsyncRenderer.java:135)
at com.xpn.xwiki.internal.template.TemplateAsyncRenderer.render(TemplateAsyncRenderer.java:54)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.lambda$syncRender$0(DefaultAsyncRendererExecutor.java:284)
at com.xpn.xwiki.internal.security.authorization.DefaultAuthorExecutor.call(DefaultAuthorExecutor.java:98)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.syncRender(DefaultAsyncRendererExecutor.java:284)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.render(DefaultAsyncRendererExecutor.java:267)
at org.xwiki.rendering.async.internal.block.DefaultBlockAsyncRendererExecutor.render(DefaultBlockAsyncRendererExecutor.java:154)
at com.xpn.xwiki.internal.template.InternalTemplateManager.render(InternalTemplateManager.java:906)
at com.xpn.xwiki.internal.template.InternalTemplateManager.renderFromSkin(InternalTemplateManager.java:868)
at com.xpn.xwiki.internal.template.InternalTemplateManager.render(InternalTemplateManager.java:855)
at com.xpn.xwiki.internal.template.InternalTemplateManager.renderNoException(InternalTemplateManager.java:810)
at com.xpn.xwiki.internal.template.InternalTemplateManager.renderNoException(InternalTemplateManager.java:802)
at com.xpn.xwiki.internal.template.DefaultTemplateManager.renderNoException(DefaultTemplateManager.java:79)
at com.xpn.xwiki.internal.template.DefaultTemplateManager.renderNoException(DefaultTemplateManager.java:73)
at org.xwiki.template.script.TemplateScriptService.render(TemplateScriptService.java:54)
at jdk.internal.reflect.GeneratedMethodAccessor6142.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:569)
at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke(UberspectImpl.java:571)
at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:554)
at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:221)
at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:368)
at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:492)
at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:147)
at org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:218)
at org.apache.velocity.runtime.directive.RuntimeMacro.render(RuntimeMacro.java:331)
at org.apache.velocity.runtime.directive.RuntimeMacro.render(RuntimeMacro.java:261)
at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:304)
at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:439)
at org.apache.velocity.Template.merge(Template.java:358)
at org.apache.velocity.Template.merge(Template.java:262)
at org.xwiki.velocity.internal.InternalVelocityEngine.evaluate(InternalVelocityEngine.java:225)
at com.xpn.xwiki.internal.template.VelocityTemplateEvaluator.evaluateContent(VelocityTemplateEvaluator.java:105)
at com.xpn.xwiki.internal.template.TemplateAsyncRenderer.evaluateContent(TemplateAsyncRenderer.java:219)
at com.xpn.xwiki.internal.template.TemplateAsyncRenderer.renderVelocity(TemplateAsyncRenderer.java:174)
at com.xpn.xwiki.internal.template.TemplateAsyncRenderer.render(TemplateAsyncRenderer.java:135)
at com.xpn.xwiki.internal.template.TemplateAsyncRenderer.render(TemplateAsyncRenderer.java:54)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.lambda$syncRender$0(DefaultAsyncRendererExecutor.java:284)
at com.xpn.xwiki.internal.security.authorization.DefaultAuthorExecutor.call(DefaultAuthorExecutor.java:98)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.syncRender(DefaultAsyncRendererExecutor.java:284)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.render(DefaultAsyncRendererExecutor.java:267)
at org.xwiki.rendering.async.internal.block.DefaultBlockAsyncRendererExecutor.render(DefaultBlockAsyncRendererExecutor.java:154)
at com.xpn.xwiki.internal.template.InternalTemplateManager.render(InternalTemplateManager.java:906)
at com.xpn.xwiki.internal.template.InternalTemplateManager.renderFromSkin(InternalTemplateManager.java:868)
at com.xpn.xwiki.internal.template.InternalTemplateManager.render(InternalTemplateManager.java:855)
at com.xpn.xwiki.internal.template.InternalTemplateManager.renderNoException(InternalTemplateManager.java:810)
at com.xpn.xwiki.internal.template.InternalTemplateManager.renderNoException(InternalTemplateManager.java:802)
at com.xpn.xwiki.internal.template.DefaultTemplateManager.renderNoException(DefaultTemplateManager.java:79)
at com.xpn.xwiki.internal.template.DefaultTemplateManager.renderNoException(DefaultTemplateManager.java:73)
at org.xwiki.template.script.TemplateScriptService.render(TemplateScriptService.java:54)
at jdk.internal.reflect.GeneratedMethodAccessor6142.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:569)
at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke(UberspectImpl.java:571)
at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:554)
at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:221)
at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:368)
at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:492)
at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:147)
at org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:218)
at org.apache.velocity.runtime.directive.RuntimeMacro.render(RuntimeMacro.java:331)
at org.apache.velocity.runtime.directive.RuntimeMacro.render(RuntimeMacro.java:261)
at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:304)
at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:147)
at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:171)
at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:147)
at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:439)
at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:190)
at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:147)
at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:439)
at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:190)
at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:439)
at org.apache.velocity.Template.merge(Template.java:358)
at org.apache.velocity.Template.merge(Template.java:262)
at org.xwiki.velocity.internal.InternalVelocityEngine.evaluate(InternalVelocityEngine.java:225)
at com.xpn.xwiki.internal.template.VelocityTemplateEvaluator.evaluateContent(VelocityTemplateEvaluator.java:105)
at com.xpn.xwiki.internal.template.TemplateAsyncRenderer.evaluateContent(TemplateAsyncRenderer.java:219)
at com.xpn.xwiki.internal.template.TemplateAsyncRenderer.renderVelocity(TemplateAsyncRenderer.java:174)
at com.xpn.xwiki.internal.template.TemplateAsyncRenderer.render(TemplateAsyncRenderer.java:135)
at com.xpn.xwiki.internal.template.TemplateAsyncRenderer.render(TemplateAsyncRenderer.java:54)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.lambda$syncRender$0(DefaultAsyncRendererExecutor.java:284)
at com.xpn.xwiki.internal.security.authorization.DefaultAuthorExecutor.call(DefaultAuthorExecutor.java:98)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.syncRender(DefaultAsyncRendererExecutor.java:284)
at org.xwiki.rendering.async.internal.DefaultAsyncRendererExecutor.render(DefaultAsyncRendererExecutor.java:267)
at org.xwiki.rendering.async.internal.block.DefaultBlockAsyncRendererExecutor.render(DefaultBlockAsyncRendererExecutor.java:154)
at com.xpn.xwiki.internal.template.InternalTemplateManager.render(InternalTemplateManager.java:906)
at com.xpn.xwiki.internal.template.InternalTemplateManager.renderFromSkin(InternalTemplateManager.java:868)
at com.xpn.xwiki.internal.template.InternalTemplateManager.renderFromSkin(InternalTemplateManager.java:848)
at com.xpn.xwiki.internal.template.InternalTemplateManager.render(InternalTemplateManager.java:834)
at com.xpn.xwiki.internal.template.DefaultTemplateManager.render(DefaultTemplateManager.java:91)
at com.xpn.xwiki.internal.template.DefaultTemplateManager.render(DefaultTemplateManager.java:85)
at com.xpn.xwiki.XWiki.evaluateTemplate(XWiki.java:2564)
at com.xpn.xwiki.web.Utils.parseTemplate(Utils.java:180)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:651)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:339)
at com.xpn.xwiki.web.LegacyActionServlet.service(LegacyActionServlet.java:108)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:227)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:122)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.xwiki.wysiwyg.filter.ConversionFilter.doFilter(ConversionFilter.java:61)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.xwiki.resource.servlet.RoutingFilter.doFilter(RoutingFilter.java:132)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.xwiki.container.servlet.filters.internal.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:208)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.xwiki.container.servlet.filters.internal.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:117)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:710)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:457)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:384)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:312)
at com.xpn.xwiki.web.XWikiAction.redirectSpaceURLs(XWikiAction.java:1171)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:509)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:339)
at com.xpn.xwiki.web.LegacyActionServlet.service(LegacyActionServlet.java:108)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:227)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:122)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.xwiki.wysiwyg.filter.ConversionFilter.doFilter(ConversionFilter.java:61)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.xwiki.container.servlet.filters.internal.SetHTTPHeaderFilter.doFilter(SetHTTPHeaderFilter.java:63)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.xwiki.resource.servlet.RoutingFilter.doFilter(RoutingFilter.java:132)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.xwiki.container.servlet.filters.internal.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:208)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.xwiki.container.servlet.filters.internal.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:117)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:542)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:143)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:687)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78)
at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:764)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:354)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:382)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:888)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1684)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: com.xpn.xwiki.XWikiException: Error number 3202 in 3: Exception while reading document [confluencePage:page:Walkthrough. Adding multiple target servers to the environment()]
at com.xpn.xwiki.store.XWikiHibernateStore.loadXWikiDoc(XWikiHibernateStore.java:1233)
at com.xpn.xwiki.store.XWikiCacheStore.loadXWikiDoc(XWikiCacheStore.java:399)
at com.xpn.xwiki.XWiki.getDocument(XWiki.java:2195)
at com.xpn.xwiki.XWiki.getDocument(XWiki.java:2257)
at com.xwiki.macros.excerptinclude.internal.macro.ExcerptIncludeMacro.internalExecute(ExcerptIncludeMacro.java:128)
... 217 more
Caused by: com.xpn.xwiki.XWikiException: Error number 2 in 0: No wiki with id [confluencePage:page] could be found
at com.xpn.xwiki.internal.store.hibernate.HibernateStore.beginTransaction(HibernateStore.java:854)
at com.xpn.xwiki.store.XWikiHibernateBaseStore.beginTransaction(XWikiHibernateBaseStore.java:576)
at com.xpn.xwiki.store.XWikiHibernateStore.loadXWikiDoc(XWikiHibernateStore.java:1082)
... 221 more
How to complete the install for a production environment
The unified product installer installs the console and the PXE/TFTP server on the default application server node to provide you with a ready-to-use test environment. However, for high-performance production environments, BMC recommends that you install and use additional instances of the console and the PXE/TFTP server on separate machines.
The individual component installers required for installing the console and the PXE/TFTP manually can be found at the following locations in the TSSA<version>-WIN64 folder. If you are installing either of the components on Linux operating systems you need to download the TSSA<version>-LIN64.zip package from EPD and extract the required individual component installers for Linux from that package.
| | | |
|---|
| | \TSSA<version>-WIN64\Disk 1\files\installers\rcp | TSSACONSOLE<version>-WIN64 |
| \TSSA<version>-WIN64\Disk 1\files\installers\pxe_64 | PXE<version>-WIN32 Note: Although you have different installers for 32-bit and 64-bit Windows for most components, for installing a a PXE/TFTP server you only have a 32-bit installer that you must use in both cases. |
| | /TSSA<version>-LIN64/Disk 1/files/installers/rcp | TSSACONSOLE<version>-WIN64 |
| /TSSA<version>-LIN64/Disk 1/files/installers/appserver_64 | |
In this walkthrough we will install additional instances of the console and the PXE/TFTP on Windows servers.
Manually installing an additional instance of the console
This example uses TrueSight Server Automation version 8.9.03.
| | |
|---|
| Navigate to the directory containing the installation files that you copied from the Application Server and run the installation program for the console (for example, ..\TSSA<version>-WIN64\Disk1\files\installers\rcp). Different installers are provided for 32-bit and 64-bit Windows. In this example, we are running the TSSACONSOLE89-SP3-WIN64 file on the Windows machine on which you plan to install the console. Select a language to use for the installation and click OK. The installer extracts the installation files, and the Introduction window opens. | |
|---|
| Ensure that you have closed all applications before you proceed. Click Next. The Review License Agreement window opens. | |
|---|
| Read the End User License Agreement (EULA) and select I agree to the terms of the license agreement if you wish to proceed. Click Next. The Directory Selection window opens. | |
|---|
| The default installation location for the console is C:\Program Files\BMC Software\BladeLogic. Click Next to use the default location. Alternatively, you can click Browse to change the installation location. | |
|---|
| A window opens in which you can select components to install. By default, all components are selected. The Network Shell is automatically installed when you install the console. Note: If you clear the TrueSight Server Automation Console Upgrade Service check box, the TrueSight Server Automation Console Upgrade Service is not installed. This service is required for automatically upgrading the TrueSight Server Automation Console when you upgrade the Application Server. Click Next. | |
|---|
| The window displays your selections. Click Install. The installer pre-analyzes your environment: - Checks whether the platform on which you are trying to install the product is supported. If the platform check is successful, Microsoft Visual C++ 2015 Redistributable Update 3 is installed automatically.
- If the platform check fails, the installation program aborts installation with an error message. Also, the error message is added to the log file.
The window displays installation progress, then displays a message when installation is complete. The console and Network Shell are installed on your machine. | |
|---|
| If all operations are completed successfully, click Done to exit the wizard. If you encountered any errors while installing, you can click View Log to view a detailed report of the installation. Tip: BMC recommends that you save a copy of the log, before you contact technical support for further assistance. | |
|---|
| Start the console. To configure the console so that it connects to the default Application Server, click Options. | |
|---|
| Click the Authentication Profiles tab and click Add. TrueSight Server Automation clients use authentication profiles to facilitate single sign-on feature. You must create an Authentication profile before you start using the Console. For more information about why we use Authentication Profiles, see System-capabilities-related-to-security. | |
|---|
| Enter the following information. - Assign a name to the authentication profile. For example, you could assign a name such as QATeam or DevTeam.
- Enter the name or IP address (IPv4 or IPv6) of the default Application Server to which the client should connect.
- Enter an Authentication Port number to which the client should connect. The same port is used for all TrueSight Server Automation authentication mechanisms. The default Port is 9840. For more information about Console ports, see TrueSight-Server-Automation-ports.
Select any one authentication mechanism for the authentication profile: - Secure Remote Password.
- AD/Kerberos Single Sign-on.
- Domain Authentication.
- LDAP.
- RSA SecurID Authentication.
- Public Key Infrastructure Authentication.
In this walkthrough we will use the Secure Remote Password mechanism. For information about implementing the other authentication mechanisms, see Implementing-authentication. - Click OK.
| |
|---|
| You can now log on the the Console using the BLAdmin user that is created while installing the default Application Server node, see step 10. Click Connect. The quick start page is the first page that is displayed once you log on the the Console. It introduces you to the main use cases of TrueSight Server Automation and allows you to execute them from a centralized UI immediately after installing the TrueSight Server Automation set up. For information about using the quick start page, see Quick-start-page. For general information about the UI of the Console, see Navigating-the-interface. | |
|---|
Manually installing an additional instance of the PXE/TFTP server
| Step | Example screen |
|---|
1 | Install the remote PXE/TFTP server - Navigate to the directory containing installation files.
- Run the PXE<version>-WIN32 installer file on the Windows machine you plan to install the PXE/TFT server.
- Click Run.
- Select the language in which you want to run the installer and click Next.
| |
|---|
2 | The PXE/TFTP installation wizard introduces you to the installation process.Click Next. | |
|---|
3 | Read the End User License Agreement (EULA) and click Yes to proceed.The Customer Information window opens. | |
|---|
4 | Enter your name and the name of your organization, and then click Next.The Choose Destination Location window opens. | |
|---|
5 | The default installation location for the PXE is C:\Program Files\BMC Software\BladeLogic\PXE.Alternatively, you can click Browse to change the installation location. Click Next to use the default location.The Network Configuration window opens. | |
|---|
6 | Confirm that the host name and IP address of the computer on which you are installing the PXE server are correct. | |
|---|
7 | Specify where the DHCP is located. If a DHCP server is running on: - The computer on which you are installing the PXE server, select Locally (On this server).
Another server or network device, select Externally (On another server). If the DHCP server is located on another host computer, the installation program automatically configures this server to function as a DHCP proxy. Note: You must configure the DHCP server differently, depending on whether it is installed on the same computer as the PXE server. For more information on configuring the DHCP server, see Configuring-a-DHCP-server-on-Windows and Configuring-a-DHCP-server-on-Linux. BMC recommends that you install the PXE server and the DHCP server on different host computers.
Click Next.The TFTP Root window opens. | |
|---|
8 | Do one of the following: - Accept the default TFTP root directory, which is C:\Program Files\BMC Software\BladeLogic\PXE\tftproot.
- Choose another directory, click Browse.
The TFTP server must reside on the same server as the PXE server. The TFTP server downloads the boot image during the provisioning process. The TFTP root directory is the location from which the files are read.Click Next.The Selected Components window opens. | |
|---|
| Review the current settings to confirm that you have specified the correct installation configuration, and then click Next. | |
|---|
9 | A progress bar indicates the progress of the installation until the Post-Configuration Options window opens.The PXE/TFTP server is installed. | |
|---|
10 | You can configure the PXE server as part of the installation by selecting the Configure the PXE server option and clicking Next.(See Configuring-the-PXE-and-TFTP-servers for more information about this option.)Alternatively, you can configure the PXE/TFTP server at a later time by using the PXE/TFTP Server configuration tool. | |
|---|
11 | Click Finish to exit the wizard. | |
|---|
Manually installing an agent on the PXE/TFTP server
For successful provisioning, the RSCD agent must be installed on the same host computer as the PXE server. You can install the agent before or after you install the PXE server.
| | |
|---|
|
- Extract the TSSA<version>-RSCDAgents.zip file that you downloaded from EPD to obtain the rscd folder. The folder contains separate installers for 32-bit and 64-bit Windows systems.
Navigate to the windows_64 folder, which is inside the rscd folder and run the following command: NEW IN 23.4 Otherwise, if you want to use SYSTEM User Only mapping, run the following command: RSCD<version>-WIN64.msi MAP_TO_SYSTEM_USER_ONLY=1 For more information on SYSTEM User Only Mapping, see Impersonation-and-privilege-mapping. - Click Run.
The installation wizard is displayed. - Click Next.
| |
|---|
|
- Accept the license agreement, and click Next.
- Configure the following Smart Agent parameters to connect to the Smart Hub for sending work requests, and click Next.
- Enable Smart Agent: Specify whether you want to enable the Smart Agent service. The service is enabled by default, which indicates that the Smart Agent is started automatically after installation.
- Smart Hub hostname: The name of the host where the Smart Hub is installed.
- Smart Hub port: The listener port of the Smart Hub. The default port is 443.
- Enroll as: The server is enrolled in the Application Server using this value. Specify one of the following identifiers to be used for the enrollment:
- <HOSTNAME>: Indicates the server host name. This is the default identifier.
- <SMARTHUB_PEER_IP>: Indicates the IP address of the server. A server might have multiple IP addresses. The IP address that is used for connecting to the Smart Hub is represented by this field.
- <SMARTHUB_PEER_FQDN>: Indicates the fully qualified domain name for the <SMARTHUB_PEER_IP>.
- <UUID>: Indicates a random UUID value. Use it to enroll the target server in the AWS public cloud data center.
- Enroll interval time (mins): The interval at which the server enrollment request is sent to the Smart Hub. The default interval is 15 minutes. Specify the interval in the range 1 - 360 minutes.
- Heartbeat interval time (mins): The interval at which the agent sends heartbeats to the Smart Hub for status updates. The default interval is 5 minutes. Specify the interval in the range 1 - 360 minutes.
- Access key: The access key that is configured for the Smart Hub. This key is used for authenticating with the Smart Hub. To obtain the access key, see Configuring the Smart Hub.
- Smart Hub polling interval time (sec): The interval (in seconds) at which the Smart Hub is polled for work requests. The default is 300 seconds.
- Tunnel feature: Specify whether you want to enable or disable (default) the Tunnel feature.
| |
|---|
| Select one of the following options, and click Next:
- Typical: Installs the agent with the default settings.
- Custom: Allows you to customize the default settings.
| |
|---|
| Click Install to begin the RSCD agent installation.
| |
|---|
| The installer checks whether Microsoft Visual C++ 2015 Redistributable is installed on the server. If this is not installed, the installation program aborts installation with an error message. | |
|---|
| Select one of the following options for the BladeLogicRSCD user password, and click Next:
- Use random password: Installs the agent with a random password generated by the installer.
- Use specified password: Installs the agent with the password specified by you.
You can change the password later by using the command or agentctl utility. For more information, see Changing-the-BladeLogicRSCD-account-password. Important If you chose to use the SYSTEM User Only mapping in step 1, the Password for BladeLogicRSCD user section does not appear on the Security preferences panel.
 | |
|---|
| You can select the Show the Windows Installer log option to view a detailed report of the installation process. Click Finish to exit the wizard. | |
|---|
Where to go from here
- During installation, default security settings are applied to the Application Server and file server. BMC recommends that you adjust the security level on the Application Server host computer and the file server host computer after completing the installation. For more information, see Security-planning.
- If you wish to manually install additional components to your environment, see Installing-individual-components.
