You can use the pkg set-publisher command to change a publisher URI.
Changing a Publisher Origin URI
To change the origin URI for a publisher, add the new URI and remove the old URI. Use the -g
option to add a new origin URI. Use the -G option to remove the old origin URI.
# pkg set-publisher -g http://pkg.example.com/support \
-G http://pkg.example.com/release example.com
Note: You can use either the install or update subcommand to update a package.
The install subcommand installs the package if the package is not already installed in the image. If
you want to be sure to update only packages that are already installed, and not install any new
packages, then use the update subcommand.
Reference: Oracle Solaris 11 Express Image Packaging System Guide, Managing Package
Publishers

This example shows how to display the default root crontab file.
$ suPassword:
# crontab -l
# ident "@(#)root 1.19 98/07/06 SMI" /* SVr4.0 1.1.3.1 */
#
# The root crontab should be used to perform accounting data collection.
#
#
1 0 3 * * * /usr/sbin/logadm
1 5 3 * * 0 /usr/lib/fs/nfs/nfsfind
3 0 3 * * * [ -x /usr/lib/gss/gsscred_clean ] && /usr/lib/gss/gsscred_clean
# 10 3 * * * /usr/lib/krb5/kprop_script ___slave_kdcs___

Explanation/Reference:
Explanation:
A: Each client uses one and only one AI manifest to complete its installation. The AI manifest is selected for a client according to the following algorithm:
* If no custom AI manifests are defined for this install service, the default AI manifest is used. The default AI manifest is not associated with any client criteria etc.
D: When you create a new install service, install_service_image_path/auto_install/manifest/default.xml is the initial default AI manifest for that install service.
E: Each client can use any number of system configuration profiles. If a client system does not use any configuration profile, then an interactive tool opens on that client at first boot after that client installation to complete the configuration of that client.

*Updating all of the packages on your installed system - To update all of the packages on your system that have available updates,use the pkg update command,as follows:
# pkg update Running this command updates packages that you might not otherwise consider updating,for example,kernel components and other low-level system packages.
*Adding or updating individual packages - To add individual software packages,use the pkg install command. Any dependent packages are also updated at the same time.
*install package updates that deliver fixes- A pkg update operation might include bug fixes,so the operation is similar to applying a specific patch or patches in previous Oracle Solaris releases.
Note: The IPS interfaces first check for updates for currently installed packages before retrieving them via the network. By default,interfaces check repository catalogs in the following locations:
*The default installation repository at pkg.oracle.com/solaris/release.
*The support repository in My Oracle Support. This repository is restricted to users with Oracle Solaris 11 Express support contracts,and it contains packages with the latest bug fixes. For this reason,a support contract must be purchased for production deployments.

Which Solaris release you are running on your system can be determined using the following command:
cat /etc/release
This will tell you which release you are running and when it was released. The more recent your system,the more info is contained in this file.
Example: # cat /etc/release Oracle Solaris 10 8/11 s10s_u10wos_17b SPARC Copyright (c) 1983,2011,Oracle and/or its affiliates. All rights reserved. Assembled 23 August 2011