12 docs tagged with "howto"

When modeling an application in Txture, it is crucial to accurately reflect its deployment environments and relationships.

In Txture, a Business Application is a key part of the platform's default data model.

There are two recommended options to model logical compute clusters, such as Hypervisors or Container Engines cluster in Txture.

Database clusters are relatively straightforward to model.

An ESB is represented by an asset of the asset-type "Technical Component", which is part of Txture's default data model for the Cloud Transformation use case.

Txture offers a variety of options to retrieve data from its repository.

Quite often, particularly when starting new projects, a good starting point to get some data into Txture is an existing CSV or Excel file.

Since excel sheets are a widespread form of information collection, Txture offers various ways to import information from this file format:

Using Txture's default Structure model, there is a separate Asset-Type for depicting and modeling an interface between two or more applications, databases or other technical components.

While Txture offers multiple ways to import existing data or to crowd-source data, it can still be necessary to manually enter data.

Txture’s flexible Data Model and the different modeling capabilities in its Dependency and Tree reports offer various options for representing specific architectural constructs.

Using Txture's default Structure, there is a separate Asset Type for depicting and modeling clusters, such as a VMware Cluster that uses the vSphere Hypervisor.