Providing a Custom Response File

You need to provide a custom response file if you want to specify any of the following information:

Your customer support identifier to associate this data with your company.
A proxy or an Oracle support hub to enable data collection and sending for a system that does not have Internet access.

How To Create and Install a Custom Response File Package

Perform the following steps to provide a custom IPS package with the custom response file.

Create the custom response file.
Create the response file using an existing Oracle Configuration Manager installation. For information about creating the custom response file, see “Creating a Response File” in Oracle Configuration Manager Installation and Administration Guide. The response file must be named ocm.rsp.
Create a custom IPS package.
Create an IPS package that contains the custom response file. If you create different custom response files for different systems, put each response file in a separate package. The path and file name are the same for each custom response file. The package names can be different. Only one Oracle Configuration Manager custom response file package can be included in any AI manifest.
1. Create the directory hierarchy.
  The custom response file must be installed as /var/ocm/.rsp/ocm.rsp on the AI client system.
```
$ mkdir -p proto/var/ocm/.rsp
$ cp ocm.rsp proto/var/ocm/.rsp
```
2. Create the package manifest.
  Create the following file named ocsresp.p5m.
```
set name=pkg.fmri value=ocsresp@1.0,5.11
set name=pkg.summary value="Oracle Configuration Manager custom response file"
set name=pkg.description value="Oracle Configuration Manager custom response file"
depend fmri=pkg:/system/ocm type=require
file var/ocm/.rsp/ocm.rsp group=root mode=0444 owner=root path=var/ocm/.rsp/ocm.rsp
```
  The depend and file lines are the only lines that are required. The summary and description lines are useful if users try to find or view this package in a repository.
3. Create the repository for the package.
  This example creates the repository in the local directory, with ocm as the publisher.
  
  Note - Create the repository in a directory that is accessible by the AI clients at installation time.
```
$ pkgrepo create customocm
# pkgrepo -s customocm add-publisher ocm
```
4. Publish the package.
```
$ pkgsend publish -d ./proto -s ./customocm ocsresp.p5m
pkg://ocm/ocsresp@1.0,5.11:20110708T174359Z
PUBLISHED
```
  Clients can install the package from the customocm repository. The ocm publisher with customocm origin is defined in the AI manifest as shown in the next step.
  See Copying and Creating Oracle Solaris 11 Package Repositories for instructions to make the new repository accessible to client systems through either NFS sharing or HTTP.
Add the package to the AI manifest.
Add the package to the software installation section of the AI manifest. Either customize an AI manifest XML file or write a derived manifests script to add these elements. See Chapter 10, Provisioning the Client System for information about customizing an AI manifest.
Use the installadm export command to retrieve the content of one or more existing AI manifests. The following example shows the XML elements you need to add. Only one Oracle Configuration Manager custom response file package can be included in any AI manifest.
```
<software type="IPS">
  <source>
    <publisher name="solaris">
      <origin name="http://pkg.oracle.com/solaris/release"/>
    </publisher>
    <publisher name="ocm">
      <origin name="file:///net/host/export/customocm"/>
    </publisher>
  </source>
  <software_data action="install">
    <name>pkg://ocm/ocsresp</name>
  </software_data>
</software>
```
Make sure the origin is a URI the clients can access during AI installation. Use zfs set sharenfs to export the repository so that clients can access the local repository.
Update the modified AI manifest in the AI install service.
Use the installadm update-manifest command to replace the AI manifest content with the content that includes the custom Oracle Configuration Manager response file package. Any criteria or default status remain with the manifest or script following the update.

Add the custom response file package property to the system configuration profile.

Since a client can use any number of system configuration profiles, you might want to put this property setting in a separate profile so that you can easily add this setting for any or all clients.

<service name='system/ocm' type='service' version='1' >
  <instance name='default' enabled='true' >
    <property_group name='reg' type='framework'>
      <propval name='response_file_pkg_name' type='astring' value='pkg:/ocsresp' />
    </property_group>
  </instance>
</service>

Add the modified system configuration profile to the AI install service.
Use the create-profile subcommand of the installadm command to add the new or customized system configuration profile to the AI install service.
In the following example, filename is the full path name of the configuration profile. The file criteria.xml specifies which clients should use this profile. If this profile contains only the response file package name setting, and if the same custom response file should be used by all clients, omit the -C or -c options.
```
# installadm create-profile -n svcname -f filename -C criteria.xml
```

Skip Navigation Links
Exit Print View
	Installing Oracle Solaris 11 Systems Oracle Solaris 11 Information Library