Datos de Superficie

Updating and maintaining data

After you have created a set of baseline data, you can keep that data current with changes to external data sources by rerunning relevant synchronization packages. This will import any new records that have been added to an external data source, and will capture changes to any values that are contained in existing records. You can use the "Run a synchronization

package" action in the workflow designer to set a recurring pattern for ongoing synchronization jobs. See "Run a synchronization package" under "LANDesk Service Management actions" in the ALM Designer's guide.

LANDESK ASSET LIFECYCLE MANAGER

Exporting and importing synchronization packages

The Export/Import feature in the Synchronization wizard is designed to make it easy for LANDesk Asset Lifecycle Manager customers to share synchronization packages with each other. Using this tool, you can export synchronization packages you have created, or import synchronization packages others have created. (See "Additional resources" on page 144 for information on the LANDesk Technical Community.)

To export a package from the Synchronization packages page

1. Select the package you want to export. 2. Click Export.

3. At the File Download prompt, click Save. 4. In the Save As dialog box, click Save.

The package is saved as an XML file, in the path you specified. 5. Click Close to close the Download complete message.

To import a package from the Synchronization packages page

1. Click Import.

2. On the Confirm Import dialog box, click Browse.

3. Select the XML file for the package you want to import, and click Open. 4. Click the green checkmark button.

This imports the package and opens it in the Synchronization wizard so you can examine its settings and make any necessary changes. If it finds another package with the same name, it will append a number (0, 1, 2, etc.) to the end of the package name.

You can click the (more packages...) link in the top right corner of the Synchronization wizard to go directly to the LANDesk Technical Community website, where you can download additional shareable synchronization packages.

ASSET MANAGER'S GUIDE

Synchronization wizard

Use the Synchronization wizard to create packages that you can use to import and update data from external data sources. A synchronization package specifies the data source, defines how data from that source will be mapped to specific columns in ALM asset records, and specifies whether new data will be automatically added to the destination asset or sent to a “pending” queue where the changes can be manually reviewed before being accepted. After you have created packages, you can run them at any time to import or update the data from the specified data sources.You can also set up a workflow to automatically run a

synchronization package according to a schedule you define. See "Run a synchronization package" under "LANDesk Service Management actions" in the Designer's guide.

IMPORTANT: To run a synchronization package, the user must have both the Create Instance permission and the Edit Instance permission. In the Design console, on the toolbar for the corresponding form, click

Properties > Security and set these permissions for the user or role who will be running the sync package. If either permission is missing, the sync package will fail and the log file will indicate that permissions were lacking. Note also that for any workflows that include a Run Synchronization Package action, while configuring the workflow, the "Run as" user must have these permissions granted.

For an overview of the data synchronization process, see "Synchronizing asset data" on page 61.

To create a package using the synchronization wizard

1. Click the Synchronization tab at the top of the Web console.

Only roles that have been given access will see the Synchronization tab; otherwise, it will be hidden. For more information, see "Asset Lifecycle Manager roles" on page 36.

2. Click Synchronization packages. 3. Click New.

LANDESK ASSET LIFECYCLE MANAGER

Task 1: General panel settings

Use the options on the General panel to name the package, specify the destination asset for the imported data, and specify the source from which the data will be imported.

1. Click General to open the General panel.

2. Type the name you want to give the package in the Package name field.

3. Browse to and select the asset or resource to which you want to add or update data. 4. Choose the Data source from which you will be importing or updating data.

5. Follow the instructions below pertaining to the data source you specified.

Synchronizing a CSV data source

To create a package to synchronize with a CSV file

1. In the File path field, type the exact path (UNC or local) to the CSV data source. 2. Click Test to verify that you are able to successfully connect to the specified CSV file.

Notes:

 If you are using the ALM Web console on a machine other than the Web server, you can import a file that is physically located on the Web server, or you can make sure the file is located on a network share that the user logged into ALM has rights to access.

 If you are running the Asset Lifecycle Manager Web console directly on the ALM Web server, a mapped drive or regular network share will work as expected.

ASSET MANAGER'S GUIDE

Defining and synchronizing ODBC data sources

When you select the radio button for ODBC, the settings on the General page change to allow you to specify the data source, login credentials for the ODBC source, and include a query to specify the data to be retrieved (see "Syntax for ODBC data sources" below).

To synchronize with ODBC data sources, you need to define the data sources using the

Windows ODBC Data Source Administrator utility on the server where ALM is installed. You can synchronize with any type of ODBC-compliant data source; three typical examples are a SQL Server, an Oracle database, and a Microsoft Excel spreadsheet.

For example, if you want to synchronize from an LDMS core server set up with a SQL database, you need to define that database as a data source (or, if you are using an Oracle database, you define that database as a data source). If you have asset data stored in an Excel spreadsheet, you can define that spreadsheet as a data source and refer to named regions in the spreadsheet that contain the data you want to synchronize.

NOTE: If you are upgrading to ALM 5.0 from ALM 3.5 or 4.0

and you previously created ODBC sync packages that you want to use with ALM 5, you will need to create a new DSN using the 64-bit ODBC Data Source Administrator, and use exactly the same DSN name. Otherwise, you would need to recreate each sync package one-by-one.

Two examples of defining a data source are given below: setting up a SQL database, and setting up a Microsoft Excel spreadsheet. To set up an Oracle database, follow the steps for a SQL database but select the Microsoft ODBC for Oracle driver in step 3; some other settings may differ as you complete the wizard.

To define a SQL database as a data source

1. From the ALM server, click Start > Programs > Administrative Tools > Data Sources (ODBC).

2. Click the System DSN tab, then click Add.

LANDESK ASSET LIFECYCLE MANAGER

4. Type a name to identify the SQL data source (this name will appear in the ALM synchronization UI). Optionally, you can type a description for the data source. 5. Select the SQL server for the SQL database, and then click Next.

6. To verify authenticity on the SQL server, select With SQL Server authentication using a login ID and password entered by the user. Type the login ID and password for the SQL server, and then click Next.

The wizard tests the connection to the SQL server, and if successful, continues to let you select the database.

7. Select Change the default database to, and then select the name of the database. For LDMS SQL databases, select ldservice. Click Next.

8. Accept all other default settings, and then click Finish.

9. A summary of the data source is displayed. If you want to verify that the data source settings are correct, click Test Data Source. After the success message, click OK.

To define a Microsoft Excel spreadsheet as a data source

1. In the spreadsheet, name the regions of data that you want to refer to (in Excel, click

Insert > Name > Define). Each named region is treated like a table in a database, and columns within the named regions are treated like columns within a database table. 2. On the server where the spreadsheet is stored, click Start > All Programs >

Administrative Tools > Data Sources (ODBC). 3. Click the System DSN tab, then click Add.

4. Select the Microsoft Excel (.xls) driver and then click Finish. A wizard opens to help you define the data source.

5. Type a name to identify the spreadsheet as a data source (this name will appear in the ALM synchronization UI). Optionally, you can type a description for the data source. 6. If needed, select the version of Microsoft Excel that the spreadsheet was created in. 7. Click Select Workbook and browse to the location of the Excel file. Select the file and

click OK.

8. Click OK to complete the setup.

NOTE: If the ALM synchronization tool can't open a spreadsheet file, make sure that the spreadsheet is not currently open in Microsoft Excel. Open spreadsheets are locked and can't be accessed as data sources.

Syntax for ODBC data sources

When you define a package for an ODBC data source, the Table, View, or Query text box lets you specify a table name or view in that data source, or create a query that selects data from one or more parts of the data source. The query syntax you use here should follow the ODBC standards for the type of data source being referenced.

In this syntax text box, you can simply type a table or view name to synchronize data from a table or view. When you do this, all data columns in the table or view are available for synchronization. To select data more specifically, type a query in the Table, View, or Query

text box. For example, if you reference a SQL database and want to select all data from one table, you can enter a query in this form:

Select * from tablename

This query selects all data from the specified table.

As another example, you can give a column name an alias to make it easier to remember the contents of that column when synchronizing data. The syntax for this example is in this form:

ASSET MANAGER'S GUIDE

This query select the data from the specified column but labels it with the alias you specify.

LDMS queries

If you have LANDesk Management Suite (LDMS) 9.0 SP2 or later, and you have defined queries in LDMS to extract inventory data for reports, etc., you can create synchronization packages to use those queries to capture data directly and synchronize it to your

ALM database.

Note: To synchronize data from existing LDMS queries:

 You need to have set up a connection to the LDMS core you want to query (Tools >

Settings > Integration servers).

 The LDMS core needs to be LDMS 9.0 SP2 or later; if you attempt to query from an older core (LDMS 9.0 SP1 or earlier), a warning message will appear and the sync job will fail.

 To access LDMS data from a core running LDMS 8.8 SP2 through 9.0 SP1, you would need to use the AMP synchronization source as described below.

To create a synchronization package for LDMS queries

1. Create a new synchronization package, specifying the package name and the asset or resource into which you want to synchronize.

2. For the data source, select LDMS Query.

3. Specify the integration server (LDMS core) you wish to query.

4. In the LDMS query field, select the query you want to use. If the core does not meet the specified requirements, an error message will appear, indicating the problem. 5. Click Mapping and proceed to map the fields. The Source columns in the Mapping

panel should match the columns defined in the query you specified. 6. Complete the settings on the Matching, and Rules pages.

LANDESK ASSET LIFECYCLE MANAGER

Defining and synchronizing data sources with Avocent

®

Management

Platform (AMP)

If you have LANDesk Management Suite 8.8 through 9.0 SP1, and you installed Avocent Management Platform (AMP) on a server on your network, you can synchronize data from your Management Suite database by using AMP queries. These are referred to in the interface as "configuration items". Avocent Management Platform enables you to capture data from LDMS 8.8 or 9.0 SP1. It includes several predefined configuration items, such as "Devices,"

"Servers," and "Network Switches." In addition, you can define configuration items to query for any type of asset in the database. When you have defined custom configuration items in Avocent Management Platform, they will be displayed in the list of configuration items in the ALM interface.

Note: In order to synchronize with LANDesk Management Suite using the Avocent Management Platform:

 Your LANDesk Management Suite installation must be version 8.8 (SP2 or later) or 9.0, and must use either Oracle or SQL 2005 or later. Although LDMS 8.7 supports SQL 2000, an installation using SQL 2000 will not integrate with ALM.

 Avocent Management Platform must be installed on a server on your network. AMP can be installed on the Management Suite core, or on another machine, as long as AMP is set to point to the Management Suite core. During installation, select the Use the LANDesk Management Suite database option on the “Integrate with LANDesk Management Suite” page, and point to the current LDMS database. If this option is not specified during installation, you will not be able to access the configuration items when defining data sources for synchronization.

 When "Use the LANDesk Management Suite database" is selected during the installation of Avocent Management Platform, the Installation program will prompt for the LDMS database credentials. This needs to be the same database username and password that was used when installing the LDMS database.

To create a synchronization package for Avocent Management Platform

1. Create a new synchronization package. 2. Select AMP as the data source.

3. Type the name of your Avocent Management Platform server in the Core name text box.

4. Enter the user name and password for Avocent Management Platform (these credentials were defined during AMP installation).

5. Click Test to make sure the connection to AMP can be successfully opened.

6. Click Browse. A list of currently available configuration items from your installation of Avocent Management Platform is displayed (including both default and custom items). Select the configuration item you want to use for this synchronization package. When you select the item, the dialog closes automatically and the configuration item is displayed in the text box.

ASSET MANAGER'S GUIDE

7. When the four text boxes are complete, you can begin mapping data from this data source.

Note: In step 6, if the list of configuration items does not display, there is an error in the credentials or core server name. Check this information and correct it, then click Browse

again.

Synchronizing Active Directory data

You can synchronize user, asset, organization, vendor, and other data from Active Directory into your Asset Lifecycle Manager database. You can synchronize from an entire domain or from a specific OU, and you can use wildcards to filter the data to be added. Synchronizing from Active Directory speeds up the process of populating your ALM data repository and delivers an added benefit of helping you discover and correct inconsistencies that may exist between various data sources in your organization.

As with other synchronization sources, the order in which you synchronize different AD objects will affect how useful the synchronized data is. For example, by synchronizing Company, Department, and Location attributes first, these objects can then be included when you synchronize your User Profile data. By putting some thought into the order in which you synchronize data, you can more efficiently create relationships between assets and resources.

To create an Active Directory synchronization package

1. Create a new synchronization package and assign a package name. 2. Select Active Directory as the data source.

3. Specify the Active Directory connection, as configured in Tools > Settings >

Users/groups in the Design console (see "Configuring users/groups" in the Designer's guide).

4. (Optional) Specify the Organizational unit (OU).

LANDESK ASSET LIFECYCLE MANAGER

6. Specify the Object class and the Primary and Secondary attribute to search on, or keep the default settings.

The default object class is set to "user". You can also synchronize with the "computer" object class. To synchronize with an object class other than "user" or "computer", contact LANDesk Technical Support for assistance.

7. When the text boxes are filled in, click Mapping and proceed to map the fields.

VMWare hosts and virtual machines

If you use VMWare hosts and virtual machines in your environment, you may want to synchronize the data from these sources into your asset repository. The Virtual machine synchronization type enables you to synchronize virtual machine and host machine

information from your VMware ESX server into your ALM database so you can manage these virtual and host machines as you would other assets.

Before you can define synchronization packages for this data type, you need to have set up an integration server for VMWare in the ALM Design console (see "Using third-party connectors with Asset Lifecycle Manager" in the Designer's guide). You will need to specify the integration server in step 3 below.

To create a synchronization package for VM hosts or virtual machines

1. Create a new synchronization package and assign a package name. 2. Select Virtual machine as the Data source.

When you specify Virtual machine as the data source, the Computer object is automatically selected in the Asset or resource field, and will overwrite any other selection.

ASSET MANAGER'S GUIDE

4. Specify whether you want to import Host or Virtual machine information. 5. Select the destination Computer type you want your virtual or host assets to be

imported as. For example, if you import Virtual machine information, you may want to

In document La Cuenca Ene: Estratigrafía, dominios estructurales y su prospectiva como potencial hidrocarburífero (página 34-37)