Customizing a CIP profile refers to creating a customized
installation package (CIP) with the IBM® WebSphere® Installation Factory that bundles
an installation image and maintenance packages, but can also contain
previously exported standalone application server configuration archives
(CARs), enterprise applications, user files, and scripts. After a
CIP is installed you can create a new profile using the customized
template for a repeatable, tailored profile solution. Customizing
a CIP profiles differs from the custom profile type, which is an empty
node designed to be federated into a cell.
Before you begin
The installer can use the Profile Management Tool to create CIP profiles
and automatically restore the profile customizations that are included
in the CIP. Or, the installer can use the manageprofiles command
to perform the same tasks manually from the command line.
If
you cannot use the Profile Management Tool,
use the manageprofiles command
to restore the customized profiles as described in Creating customized CIP profiles from the command line.
You
must have previously installed a CIP to create CIP profiles and restore
customizations that are included in the CIP.
If
you are restoring a customized profile that uses messaging, you must
also include a script to configure the service integration bus (SIB).
The original SIB configuration is not portable and, therefore, is
not included in the CIP.
Note: The QEJBSVR
user profile must have proper authority to the files and directories
involved to run any customized scripts which read or write from the
file system.
About this task
The series of configuration events for using a configuration
archive and other CIP customizations is shown in the following example:
- Install the application server.
- Create a default (standalone application server) profile, deploy
applications, and make other configuration changes.
- Optionally create a configuration archive of the default profile
using the wsadmin tool:
./wsadmin.sh -conntype NONE -c "\$AdminTask exportWasprofile {-archive myarchive.car}"
Avoid trouble: Be sure that
\ is in front
of
$AdminTaskgotcha
wsadmin.bat -conntype NONE -c "$AdminTask exportWasprofile {-archive myarchive.car}
Note: The first steps above are optional and are only
required if a configuration archive needs to be exported for inclusion
in a CIP. If configuration archive customization is not required,
then the steps above can be omitted.
- Use the Installation Factory to create a CIP that includes the
application server product image.
The CIP optionally includes a
refresh pack as well as a fix pack.
- Include scripts to run during install time or uninstall time.
- Optionally include the configuration archive in the CIP for a
standalone application server configuration.
- Optionally include additional files to be installed on the system.
- Distribute the CIP to installers who require the pre-configured
system for their users.
- Install the CIP.
A configuration archive is available
for an application server CIP profile only. A special profile template
enables the importation of a configuration archive file into the application
server profile. You cannot create a feature pack CIP with a configuration
archive.
Use the
Profile Management Tool to create CIP profiles
that accept configuration actions that are included in the CIP. Use
the application server CIP profile when you are restoring a configuration
archive file or other customizations. The
Profile Management Tool can also create
normal profiles that do not accept customizations.
- When you run the Profile Management Tool with
CIP customized profiles installed, the Environment Selection panel
will show environments with -- cip_uid at
the end. These are the customized profiles, and each of them will
create a regular profile and then apply the customizations through
a profile augmentation. If the customized profile that you select
contains a configuration archive, then it will be imported.
- The environments listed on the Environment Selection panel, which
do not have a -- cip_uid at
the end, are the regular profile types. If you want a regular profile
without customizations, select one of these.
Procedure
Create and augment an application server profile that does
not include a CAR file. Choose the application server
profile in the enhanced Profile Management Tool.
The Profile Management Tool uses the
appropriate profile template to create an application server that
does not require the CAR, but that still accepts other customizations.
The Profile Management Tool automatically augments
a CIP profile with any customizations that exist for the profile type.
Results
After creating the profile and restoring the customizations,
the installation should have a profile that is configured like the
profile in the model product installation that was the pattern for
the CIP. Existing customizations are used only when you create a CIP
profile with the Profile Management Tool.
What to do next
After installing your customized system,
install a Web server and plug-ins, if necessary, and start the application server to test your applications.