Importing Entities

To import a set of entities into FlexNet Operations, perform the following steps.

To import a set of entities into FlexNet Operations

1. Click Administer > Import Data Objects.
2. In the Import Settings tab, under Upload Type, select either Unicode of Data Import Template or Jar file. If you select Unicode of Data Import Template, skip to Step 6, otherwise go to Step 3.
3. If you are importing a JAR file larger than 2 MB in size, select the Run job in background? check box.
• If Run job in background? is selected (default setting), FlexNet Operations processes the import job asynchronously. FlexNet Operations submits the job for processing and assigns the job a record number. (You can check the status of the import job on the status page. See Import/Export Job Status for more information.)
• If Run job in background? is not selected, FlexNet Operations processes the import immediately.

See Configuring Alert Behavior for more information on configuring background jobs.

4. For Error handling, select one of the following options:
• Continue with errors—The import process continues even if errors are encountered.
• Stop import job—The import process stops upon encountering an error.
5. For Duplicate record handling, select one of the following options:
• Update record—If the entity already exists in the database, the record is updated with the information in the import file.
• Skip and Generate Error—If the entity already exists in the database, it is not updated and an error message is generated.
6. For File Name, click Choose File. Browse to the Unicode .txt or .jar file containing the data you want to import.

Note:When importing a large number of Web Register Keys, it is recommended that you limit each job to a maximum of 1,000 keys to optimize performance. If necessary, split the task into multiple jobs to stay within the recommended limit.

7. Click Import. The file is imported into FlexNet Operations.

Import Order

If copying data from one instance of FlexNet Operations to another, dependencies such as Transaction Keys, License Technologies, and License Models must be imported first. Use the Selected Items with their Dependencies (if available) or Selected items to download JAR files from their respective entity pages and upload them before uploading a Product Packing or Entitlement Management Unicode text file.

Note:See Exporting an Entity or Set of Entities as a JAR File and Downloading a Data Import Template for more information.

The following lists the order each type of entity should be uploaded.

Upload Order of Entities

Entity Type

Upload Order

Dependencies

Dependencies must be uploaded in the following order:

1. License Generator
2. License Technology
3. License Model
4. Hosts
5. Accounts
6. Users
7. Product Lines
8. Custom Attributes
9. Custom Host Attributes
10. Custom License Attributes

Product Entities

Product entities must be uploaded in the following order:

1. Features
2. Products
3. Maintenance Products
4. Part Number or Product Relationship

Entitlement Entities

Entitlement entities must be uploaded in the following order:

1. Simple and Bulk Entitlements
2. Maintenance Line Item
3. Web Reg Keys

Note:Not all entities have an export option. For any entity page that does not include an Export option, data must be manually entered into the new instance of FlexNet Operations

Fulfillment Import Limitations

If updates on import are allowed, the following limitations apply:

• Existing on-hold fulfillments can be updated only to active by import.
• Existing active fulfillments can be updated only to obsolete by import.
• Existing obsolete fulfillments cannot be updated by import.

See Also

Importing and Exporting Entities Overview

System Configuration

Exporting Entities

Using Data Import Templates

Import/Export Job Status