Question 1. How Can Personal Computers On The Network Receive Permits?
Depending on deployment, the following apply:
Normal connected-to-the-server use : The entitled number of permits are stored on a server at the customer premises. When a user starts a product with access management enabled, a permit is requested from the server. Based on availability, either a permit is provided or the request is rejected (because a permit is not available). When the user closes the product, the permit is returned to the server.
Borrowing from a server : While there is a network connection from the client computer to the server, it is also possible to borrow a permit. Permits can be borrowed for a minimum of a day and for any period up to five years. While borrowed, the permit is stored on the local computer, and is only available for use on that computer.
The local permit is used instead of attempting to gain a permit from the server. This means that the computer can disconnect from the network and still use the protected product. While the permit is borrowed, it is not available for use from the pool of permits on the server. This borrowed permit is usable until the day count reaches zero. When the day count reaches zero, the permit is not usable on the computer that borrowed it. The permit is made available on the server again.
Borrowing remotely : If there is no network connection, it is possible to use tools on the product distribution media to borrow a permit remotely. When borrowed, the experience is the same as for borrowing from a network. Note that for this process to work, there must be a method for exchanging text files (for example, by email or USB stick).
Question 2. How Can I Deploy Permits To Computers That Are Not Connected To The Network, And Is It Possible To Limit Time Of Usage?
The approximate process for borrowing remotely is as follows:
On the remote computer:
- Run a command-line tool (supplied on the distribution media)
- Send the resulting text file to an administrator that has access to the server.
On the network that is connected to the permit server:
- The administrator runs another tool. This tool uses the file that is generated by the remote computer to borrow the required permits for the number of days required.
- The administrator sends the resulting text file to the user of the remote computer.
On the remote computer:
- Run another command-line tool to apply the permits.
Question 3. Is It Possible To Hand Over Permits On A Usb Flash Drive?
Yes. Remote borrowing is possible, and borrowed licenses can be transferred on a USB flash drive.
Question 4. What Is The Upgrade Path For Customers That Use Software License Management (slm)?
The old software license management and new product access management are not compatible with each other. To take advantage of product access management, customers must uninstall any existing licensing mechanism before installation. Any SLM permits become redundant and product access management permits must be requested.
Question 5. Can The Permits Be Maintained On Different Servers?
Yes. You can maintain permits on multiple servers. A basic scenario would be to use two servers on your network to ensure that some permits are always available. You might have half of the total number of permits on each server. Under default operation, the client broadcasts a request to all servers on the network, and uses the first one to respond. It is possible to configure the client to go to a specific server, and also to configure a search order. In this situation, configure half your clients to connect to server 1 first, and half to connect to server 2 first. This configuration balances your usage over the two servers and also gives a level of backup in the event of server failure.
Question 6. Is It Possible To Place A Time Limit On The Allocation Of A Permit?
It depends on the deployment:
Normal connected-to-the-server use : When a user starts the product, the computer requests a permit from the server. While the permit is allocated, that permit cannot be used by anyone else until it is returned to the pool. When the user closes the product, the permit is made available for use on another computer again.
Borrowing from a server & Borrowing remotely: In the ‘borrowing’ scenario, a permit is allocated to the computer for a time period, ranging from one day up to five years. The advice is always to set a sensible ‘borrowing’ period. For example, if the user is working remotely for seven days, set the period for seven days.
Question 7. What Is The Smallest Time Period That A Permit Can Be Allocated For?
Permits can be borrowed for a minimum of one day.
Question 8. What Happens To A Permit If The Computer That Contains That Permit Is Stolen? Is It Possible To Retrieve The Permit?
There is no specific way to “pull” a permit back to the server. Where ‘connected-to-the-server’ use applies, the permit is returned as soon as the program is closed. In the ‘borrowing’ scenario, the recommendation is to implement sensible borrowing times.
For example:if the user is working remotely for 10 days, then set the borrowing time for 10 days. If the computer is stolen after seven days, on the 10th day the permit would be automatically returned. Alternatively, you can request a replacement permit file from IBM, which would then supersede your original permit file.
Question 9. Can I Manage Permits Myself?
No. IBM provides a permit file that is structured according to your needs as defined in the request form. You are not able to configure the permit file after it is delivered. If the structure changes over time, come back to IBM and request a replacement permit file.
Question 10. Is It Possible To Limit The Number Of Permits Available For Checkout?
Yes. Through some implementation setup, permits can be limited. In your design,
identify at least two servers:
- The first server holds most of the permits that will be allocated/available.
- The second server holds a small set of permits that are not allocated and not advertised.
If a user wants access to a product, and there are no permits available from the first server, provide access to the second server and use those permits.
Question 11. Is It Possible To Report On Concurrent Usage?
Each transaction that is carried out by the server is logged in the following format:
0 1 MTY1NQ== Fri Mar 12 14:42:55 2010 1268404975 ANB.main v8 0 1 0 Administrator TestBed_Shwcase 188.8.131.520 1 – – – – – – 0 – – – MA== 655259 MTI2OTA2MDIzNA==This log file can be exported as a CSV file. By looking at the highlighted entry, you can see how many permits are in use at that moment. See the IBM i2 Product Access Management Administration Guide for more information.
Question 12. Are The Product Access Management Capabilities Deployable And Supported In Virtual Environments?
The virtual environments that are supported for each of the products that use access management are listed in the relevant system requirements documents.
Question 13. We Have Hundreds Of Desktops That Require Product Access Management Capabilities. Can ‘push’ Tools Be Used (for Example, Sms)?
Like the rest of our products that use Microsoft Installer, silent installs across a network are possible. The parameters that are used are described in the IBM i2 Product Access Management Administration Guide.
Question 14. Is Product Access Management A Proprietary Ibm Solution?
No, product access management is based on third-party technology from SafeNet inc.
Question 15. What Operating Systems Are Supported By The Sentinel Rms License Server That Enables Product Access Management Capabilities?
Sentinel RMS license server includes support for the following operating systems:
- 32-bit versions of Windows Server 2000, 2003, and 2008
- 64-bit versions of Windows Server 2003, 2008, and 2008 R2.
Question 16. Can Ibm I2 Intelligence Analysis Portfolio Products At Version 8.9 Be Installed Alongside Older Versions Of Those Products?
No. 8.9 products are not compatible with earlier versions.
Question 17. Is It Possible For An Administrator To Control When Permits Are Required?
Yes. When a product is installed with product access management configured, a permit is always required, and the administrator controls access to permits.
Question 18. When Permit Files Are Requested, What Information About My Network Is Accessible By Ibm?
The lock codes that are used to identify each server are generated using the server’s MAC address and disk ID. The information is encrypted with an SHA-256 algorithm. It is not possible to work back to the original information that generated the code.
Question 19. Is It Possible To Run More Than 1 Sentinel Rms License Server Per Machine?
No, you can only run 1 Sentinel RMS license server per machine. You should be able to use permits from multiple software vendors on the same server (the only aspect to be watch out for is the version of the server software).
Question 20. What Might Prevent My Client Broadcast From Finding The Sentinel Rms License Server?
The Sentinel RMS license server must exist in the same subnet as the client broadcasting.
IBM Lotus Notes Interview Questions
IBM Lotus Notes Tutorial
IBM Cognos Interview Questions
IBM Cognos Tutorial
IBM Informix Interview Questions
IBM DB2 Interview Questions
IBM DB2 Tutorial
IBM Mainframe Interview Questions
IBM Lotus Notes Interview Questions
IBM Mainframe Tutorial
IBM Maximo Asset Management Interview Questions
IBM Lotus Domino Interview Questions
IBM Cognos Interview Questions
IBM BPM Interview Questions