SSRegistration

The Registration of Sun Studio product

The main goal of this project is registration of each instance Sun Studio product with Sun Online Account.

The registration process generally contains 3 steps:

  • create of Service Tags (ST) information for this instance of Sun Studio
  • register this information in the Sun Inventory using SOA (if user confirmed)
  • register this information in local ST Repository (if installed)


To provide registration of Sun Studio we should:

  • create infrastructure in SysNet
  • create registration library
  • update Sun Studio (installer, components, packages or any) to register product after installation


Development Plan

All development is splitted into 2 phases. The limited registration is included int Express 07/08 and full support of registration should be in "X" release of Sun Studio.

Phase 1 (The Express Support)

  • The adding of Service Tags for Sun Studio Express in SWORDfish database
  • The creation Web interface in Connected System Network (test repository)
  • The documentation should be located on the Wiki
  • The script which is able to register Sun Studio in local service tags and global environment
  • The simple installer which allow user to unpack and register Sun Studio

After this phase we should have an release of Sun Studio which could be registered during installation. Also we should have a well defined process to communicate with SysNet for next releases.

The registration workflow for express release

The Sun Studio is distributed as a shell script which unpack the Sun Studion binaries and register this instance.

Step 0 (Initiating)

User downloads Sun Studio express and run installation. The installer script unpack binaries in th current directory and initiate installation.

Step 1 (ST creation and local registration) This step is done only once without any user confirmation. The registration component create Service Tags for this instance of product. The unique product_urn is generated for this purpose. The ST information is saved in Sun Studio directory to share the product ID between users. If ST are installed on the system product should be registered also there.

This step should be completed always.

Step 2 (SOA registration) After completion of Step 1 the register utility checks Sun Inventory accessibility for Online registration. If there is no connection to Sun Inventory this step should be silently skipped. Otherwise all data for registration is send to SysNet and user is promted about confirmation of registration. The browser with landing page should be shown to complete registration with SOA. File:SSRegistration/login SSRegistration.png

Aftter completion the product should be marked as registred. File:SSRegistration/thank SSRegistration.png

Afte this step installation and registration are finished.

Notes :

  • If Sun Studio is installed and uninstalled several times each copy is considered as a new product
  • There is no uninstallation process and all information about gears should be removed by user manually (probably we create script for this)
  • If user did not register and he has local ST he could register later with SysNet Registration Client
  • User could interrupt registration by closing browser, we could not determine this
  • The NB is not registered


Phase 1 (full support) Jul - Oct

  • The product SS "X" should be registered in Connected Services (see 1)
  • The registration should be included in all installers and IPS for Sun Studio distribution
  • The uninstalation should unregister product (if product is uninstalled with installer or IPS)
  • The registration should be included in Sun Studio components (IDE, probably C/C++ compiler)
  • The registration of Sun Studio & NetBeans bundle should be supported

After this step we should have full support of registration unregistration.


The registration workflow for full release

The registration could be initiated at next points :

  • By the installer after installation is successfully completed
  • By the Sun Studio components when they are run
  • Manually from IDE
  • By the script HTML page which could be run by user manually(???)

Step 0 (Initial check)

If registration is not initiated by installer firstly it is needed to verify that this copy is not registered yet otherwise exit.

Step 1 (ST creation) This step is done only once without any user confirmation. (Usually it should be done during installation). The registration component should create Service Tags for this instance of product. The unique product_urn should be generated for this purpose. The ST information should be saved in Sun Studio directory to share the product ID between users. If ST are installed on the system product should be registered their.

Step 2 (SOA registration)

The browser with landing page should be shown to complete registration with SOA. Aftter completion the product should be marked as registered.

Step 3 (Unregistration)

The product should be unregistered when Sun Studio is uninstalled.

Notes :

  • If Sun Studio is installed and uninstalled several times each copy is considered as a new product
  • If Sun Studio is not installed but copied and the ST are not installed on the system the ST creation is done for each user
  • The registration process is initiated by Sun Studio components from time to time if Sun Studio is not registered
  • The NB is registered if it is coubundled with Sun Studio


TBD

Testing

Test scenarios for the Express release are here

Teams, mail aliases, product workspace

The spde-installer-iteam@sun.com alias of installer team should be used to discuss all registration related issues.

The Registration is supported by:

Jesse Grodnik Mngr
Igor Nikiforov Dev
Leonid Mesnik Dev
Stepan Doubrava X Des
Alexandr Alexandrov QA


Poduct Data

Sun Studio Express 07/08 (TBD)

servicetag.ss.urn=
servicetag.ss.name=
servicetag.ss.version=
servicetag.ss.parent.urn=
servicetag.ss.parent.name=

Links

ServiceTags Web

The ST Registration Specs

sowRDFish

Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo