Summary

Synopsis

Discussion

If required you would first of all need to configure the user with the ?View and Manage Configurations? permission. You would do this by checking the role assigned to the user under the ?Administer Operations -> Manage Users ->Username? tab , Note the assigned role and then check that this has the permission under ?Administer Operations -> Manage Roles ->Role? tab. Note it is not necessary to do this for the ?admin? user.

You may want to change the Export and Import Settings under ?Administer Operations -> System Configuration -> Export And Import Settings? tab to control how many records per file are used.

Imports and Exports are processed as background jobs you should therefore configure an alert to control this process under the ?Administer Operations -> Define Alerts -> Export and Import Background Jobs [1] - > Configure? tab. Assuming you want to process the command immediately you should select a suitably short interval (30 seconds?), Set to Active and if necessary restrict to a suitable user role, again this is not necessary for the admin user.

With these settings you are now ready to export or import, so for the particular instances you requested ?

Export Feature
?Package Products?, Select ?Features? from the ?Search In? dropdown box and click on the ?spy glass?.
To export all features select ?Export & All Items?. This will submit the background job which will perform the export

Export Feature Bundle
As above but select ?Feature Bundles? from the drop down box

Export License Model
?Package Products -> Manage License Models? click on ?spy glass? then export as above

Export Product
?Package Products?, Select ?All Products? from the ?Search In? dropdown box and click on the ?spy glass? the export as above.

Import
The exported files can be imported by selecting the appropriate file as part of the following instructions (taken from the FNO Help Guide) ?

1. Click Administer Operations, and select Import from the navigation bar.
2. On the Import Business Objects page, under Would you like to submit the import job and
come back for the results?, select one of the following:
Yes: A large file, over 2 MB in size, should be processed asynchronously. The job is submitted
for processing and assigned a record number, and you can check the job status on the status
page.
No: A smaller file, under 2 MB, can be processed synchronously. (It will not be placed in a
processing queue but processed immediately.)
3. Under File Name, click Browse. Browse to the.jar file you wish to import.
4. Under Do you want the process to continue if some records fail to import?, select one of
the following:
Continue: the import process will continue even if errors are encountered.
Stop: the import process will stop upon encountering an error.
5. Under Should duplicate records be updated or generate an error?, select one of the
following:
Update: If the entity already exists in the database, the record is updated with the information
in the import file.
Generate Error: If the entity already exists in the database, it is not updated and an error
message is generated.
6. Click Import. The file is imported into FLEXnet Operations.

More details can be found in the FNO help guide (fno_help_guide.pdf) but hopefully this will serve as a quick guide.