Develop > Presentation layer > Customize IBM Sales Center > Deploy customizations to the IBM Sales Center


Post deployment provisioning mechanisms

Once the initial client image is installed, further deployment of Eclipse features that comprise WED4WL, Sales Center, and user customizations can occur. There are three provisioning mechanisms available to support this. Each mechanism requires a different infrastructure and imposes a different minimal initial client install to enable post deployment provisioning.

The choice between these methods is made based on the degree of automation, whether a user must be running the client when the install occurs, and takes into account any prior commitment to one of the infrastructure technologies. An enterprise that has deployed a management and software deployment technology way prefer to extend its existing infrastructure to also accommodate Sales Center clients rather than introducing another specific infrastructure, and one of the choices will permit that in most cases.

All three of these mechanisms use the same Eclipse update site produced by the customization build recommended in building customizations for deployment in Rational Application Developer. IBM Sales Center is provided on the DVD as an Eclipse update site, and can also be installed by these mechanisms.

After installing Windows XP on the prototype client, but before capturing the image to clone, additional software must be installed that is sufficient to enable the post-deployment technology that you intend to use. Each of the alternatives indicates in its Prerequisites section which additional software must be loaded onto a prototype client in the initial client image.


Related concepts

Deploy customizations to the IBM Sales Center

Image installation mechanisms

Accept customizations for deployment in Rational Application Developer

Production installation of the IBM Sales Center client

IBM Sales Center Quick Install


Related tasks

Use IBM Tivoli Device Management Server

Manual install with Eclipse update manager

Use IBM Tivoli Device Management Server: Create an Eclipse NativeAppBundle

Use IBM Tivoli Device Management Server: Enable Enterprise Management Agent

Use IBM Tivoli Device Management Server: Registering the NativeAppBundle with the Device Management Server

Use IBM Tivoli Device Management Server: Scheduling a software distribution job

Use IBM Tivoli Device Management Server: Uninstallation using a Bundle Control Job


+

Search Tips   |   Advanced Search