Installing TrueSight Orchestration Development Studio using the wizard
Where you are in the installation process
| Step | Task |
|---|---|
| 1. | Preparing for TrueSight Orchestration installation |
| 2. | Install Remedy SSO (external) |
| 3. | Install the repository |
| 4. | Install the Configuration Distribution Peer |
| 5. | Install TrueSight Orchestration Development Studio (You are here) |
| 6. | Install TrueSight Orchestration Content |
| 7. | Install additional peers – Activity Peer |
Install additional peers – Lightweight Activity Peer | |
Install additional peers – High Availability CDP | |
| 8. | Install the Operator Control Panel |
| 9. | Install the Health and Value Dashboards |
| 10. | Complete post-installation configuration tasks |
To install Development Studio
- Navigate to the directory where the installation program files are downloaded and extracted from the zip folder and click setup.cmd to start the installation program.
- On the splash screen, select the language in which to view the installation program, and click OK.
Review the welcome page, and click Next.
Read the license agreement, agree to the terms, and click Next.
- Select Install a new Development Studio; then click Next.
Browse and select a destination directory to install the component and click Next.
Select a workspace location (local directory) to save all your work and click Next.
More about the Development Studio workspace location
- Do not specify a network drive.
- If you are installing multiple instances of
Development Studio, you must specify a unique workspace location for each instance.
Example:
Windows: C:\Documents and Settings\username\DevStudio
- Review the information and click Install.
- On the Installation Summary panel, perform one of the following actions:
- To exit the installation program, click Done.
- To review the BAO_install_log.txt file, click View Log, and then click Done to exit the installation program.
- To ensure that the installation is successful,
launch TrueSight Orchestration Development Studio
.
By default, TrueSight Orchestration uses the JRE bundled with the product. For options to work with external or open source Java, reach out to the BMC Customer Support team.
Troubleshooting Development Studio issues
If you face issues while using the Development Studio, see
Troubleshooting problems in TrueSight Orchestration Development Studio
.
Next step in the installation process
After installing the repository, CDP, and Development Studio, you can now install content to set up a basic development or demonstration environment. To install other components, see the Installing – Classic mode section.
Comments
There needs to be a document for converting from Oracle Java JRE or JDK to AdoptOpenJDK for Development Studio.
For anyone that is able to see this comment, here's what I had to do to make the switch (on Windows): Navigate to the Development Studio installation directory edit Development Studio.ini and update the path for the "-vm" option
example: change C:\Program Files\BMC Software\BAO\Studio\8.2.00\jvm\bin to C:\Program Files\AdoptOpenJDK\jdk-8.0.265.01-hotspot\bin
Also, if you have to reinstall Development Studio, or get a new computer and have to install it, make sure to update your path in the DevelopmentStudio.properties for the realops.home and ao.home entries to match whatever your installation path is.
Hi Greg,
Thanks for your comment!
Let me check with the team and update the documentation as required.
TSO Platform uses the JRE bundled with the product. In that case, one doesn't need to change the JRE path.
That is true. The caveat is if your Enterprise Security team dictates that Oracle Java must be removed. In this case, you can either upgrade to version 20.02 or newer (not always a simple and quick process), or install the AdoptOpenJDK and change the options file to point to it.
Hi Greg,
I checked with the team and BMC doesn't recommend using external JAVA for TSO.
Thanks.
I fully understand that this is not a recommended path. That said, Oracle Java is a licensed product now. The last version of Oracle Java that was bundled with TSO as of 8.2+ was Oracle Java 1.8u202 or 1.8u212. These versions are flagged as vulnerable and as such cause concern with Enterprise Security. Customers like us are not always ready and able to make the significant investment in time and resources to install/upgrade and vet the newer versions of TSO. Providing a simple means of transitioning to an open source platform like AdoptOpenJDK, which is bundled with TSO as of v20.02, gives customers a means to resolve concerns with Enterprise Security and vulnerability scanners until such time allows for the migration to version 20.02+.
Even if only on a temporary basis. Even providing a statement of something like "if you need to switch from Oracle Java to an open source platform like AdoptOpenJDK, please open a support ticket." At least it can provide a path to follow.
Hi Greg,
I appreciate your comment and have updated the documentation with the suggested changes.
Log in or register to comment.