There are three types of permanent license: installed, concurrent user, and named user. An installed license unlocks the software on a single computer. If you buy an installed license for N computers, then the license allows use of the software on up to N computers. A concurrent-user license for N concurrent users allows N users to run the software concurrently.
The software may be installed on 10N computers. A named-user license authorizes a specific user to use the software on up to 5 different computers. To activate your software, click Upload a New License , and, in the dialog that appears, browse for or enter the path to the license file, and click OK. The license email that you receive from Altova will contain your license file a s an attachment.
The license file has a. Browse for or e nter the path to the license file , and click OK. You can then either: i acquire the license from your Altova product via the product's Software Activation dialog see below , or ii assign the license to the product from Altova LicenseServer.
For more information about licensing via LicenseServer, read the rest of this topic. The Software Activation dialog screenshot below can be accessed at any time by clicking the Help Software Activation command. In the dialog, click Upload a New License , and browse for and select the license file. Click OK to confirm the path to the license file and to confirm any data you entered your name in the case of multi-user licenses.
Finish by clicking Save. Select the machine on which the LicenseServer you want to use has been installed. As these broadcasts are limited to a subnet, License Server must be on the same subnet as the client machine for auto-discovery to work. If auto-discovery does not work, then type in the name of the server. The Altova LicenseServer must have a license for your Altova product in its license pool.
Click Save to acquire the license. After a machine-specific aka installed license has been acquired from a LicenseServer, it cannot be returned to the LicenseServer for a period of seven days. After that time, you can return the machine license to LicenseServer click Return License so that this license can be acquired from LicenseServer by another client.
Note that the returning of licenses applies only to machine-specific licenses, not to concurrent licenses. Check out license. You can check out a license from the license pool for a period of up to 30 days so that the license is stored on the product machine. This enables you to work offline, which is useful, for example, if you wish to work in an environment where there is no access to your Altova LicenseServer such as when your Altova product is installed on a laptop and you are traveling.
While the license is checked out, LicenseServer displays the license as being in use, and the license cannot be used by any other machine. The license automatically reverts to the checked-in state when the check-out period ends.
Alternatively, a checked-out license can be checked in at any time via the Check in button of the Software Activation dialog. To check out a license, do the following: i In the Software Activation dialog, click Check out License see screenshot above ; ii In the License Check-out dialog that appears, select the check-out period you want and click Check out. The license will be checked out.
After checking out a license, two things happen: i The Software Activation dialog will display the check-out information, including the time when the check-out period ends; ii The Check out License button in the dialog changes to a Check In button. You can check the license in again at any time by clicking Check In. Because the license automatically reverts to the checked-in status after the check-out period elapses, make sure that the check-out period you select adequately covers the period during which you will be working offline.
Note: For license check-outs to be possible, the check-out functionality must be enabled on LicenseServer. If this functionality has not been enabled, you will get an error message to this effect when you try to check out. In this event, contact your LicenseServer administrator. Copy Support Code. Click Copy Support Code to copy license details to the clipboard. This is the data that you will need to provide when requesting support via the online support form.
Altova LicenseServer provides IT administrators with a real-time overview of all Altova licenses on a network, together with the details of each license, as well as client assignments and client usage of licenses. The advantage of using LicenseServer therefore lies in administrative features it offers for large-volume Altova license management.
Altova LicenseServer is available free of cost from the Altova website. When you are ready to order a licensed version of the software product, you can use either the Purchase a Permanent License Key button in the Software Activation dialog see previous section or the Order Form command to proceed to the secure Altova Online Shop.
Opens the Altova Product Registration page in a tab of your browser. Registering your Altova software will help ensure that you are always kept up to date with the latest product information. Checks with the Altova server whether a newer version than yours is currently available and displays a message accordingly. Let's begin by creating a package that will store a new use case diagram. Note that UModel does not require that a specific diagram must reside in a specific package; however, you might want to organize diagrams into packages for better organization and consistency.
Enter the name of the new package in this example, "Use Case View" , and press Enter. Right-click the previously created "Use Case View" package. A Use Case diagram has now been added to the package in the Model Tree window, and a new Diagram window has been created as well. A default name has been provided automatically. Double-click the diagram name in the Model Tree window, change it to "Overview Account Balance", and press Enter to confirm. Right-click in the newly created diagram and select New Actor.
The actor element is inserted at the click position. Click the Use Case toolbar button and then click inside the diagram window to insert the element. A "UseCase1" element is inserted.
Note that the element, and its name, are currently selected, and that its properties are visible in the Properties window. Change the title to "get account balance", press Enter to confirm. Double-click the title if it is deselected. Note that the use case is automatically resized to adjust to the text length. When selected, model elements in a diagram display various connection handles and other items used to manipulate them.
Handles can be used to create relationships between elements, or show or hide certain compartments from the element, as shown below.
Double-click the "Actor1" text of the Actor element, change the name to "Standard User" and press Enter to confirm. Place the mouse cursor over the handle to the right of the actor.
A tooltip containing "Association" appears. Click the handle, drag the Association line to the right, and drop it on the "get account balance" use case.
An association has now been created between the actor and the use case. The association properties are also visible in the Properties window.
Click the use case and drag it to the right to reposition it. The association properties are visible on the association object. Click the use case to select it, then click the collapse icon on the left edge of the ellipse. The "extension points" compartment is now hidden. A blue dot next to an element in the Model Tree window signifies that the element is visible in the current diagram. For example, in the image below, three elements are currently visible in the diagram and thus have a blue dot in the Model Tree:.
Resizing the actor adjusts the text field, which can also be multi-line. To insert a line break into the text, press Enter while holding the Ctrl key pressed. To finish up the Use Case diagram:. Click the Use Case toolbar button and simultaneously hold down the Ctrl key. Click at two different vertical positions in the diagram to add two more use cases, then release the Ctrl key.
Name the first use case "get account balance sum" and the second, "generate monthly revenue report". Click the collapse icon of each use case to hide the extensions compartment. Click the actor and use the association handle to create an association between "Standard User" and "get account balance sum". To create an "Include" dependency between use cases creating a subcase :. An "include" dependency is created, and the include stereotype is displayed on the dotted arrow. The actor in the "generate monthly revenue report" use case is not a person, but an automated batch job run by a bank computer.
0コメント