Upgrading Oracle Pedigree and Serialization Manager

Following are the steps for upgrading Oracle Pedigree and Serialization Manager (OPSM) from 1.1.1.0.5 to 1.2.0.0.0.

This chapter covers the following topics:

Pre-Upgrade Tasks
Upgrade Tasks
Post Upgrade Tasks
Re-Upgrade Tasks

Pre-Upgrade Tasks

Upgrade to Oracle 11gR2 (11.2.0.3.0) 64-bit bit Production Database, Enterprise Edition.
Upgrade to WebLogic 11gR1PS6 (10.3.6.0) 64-bit.
Upgrade to SOA Suite 11gR1PS6 (11.1.1.7.0) 64-bit, including Enterprise Manager and the Repository Creation Utility (RCU) 11gR1PS6.

Refer to Updating Your Schemas with Patch Set Assistant in Oracle® Fusion Middleware Patching Guide, 11g Release 1 (11.1.1.7.0), to upgrade the schemas to 11gR1PS6. If there are issues upgrading the SOAINFRA schema, follow the steps from SOA 11g: Getting "SOAINFRA schema is not valid" Error During Upgrade Process [Article ID 1467024.1] from support.oracle.com.
Download and apply the patch 16964825 from support.oracle.com.
Set the following environment variables:
- MW_HOME to your Middleware Home.
  
  For example, MW_HOME=/slot/ems2383/oracle/mwhome
- MW_ORA_HOME to your SOA HOME.
  
  For example, MW_ORA_HOME=$MW_HOME/Oracle_SOA1
- Set the PATH variable to include $ORACLE_HOME/bin.
  
  For example, export PATH=$ORACLE_HOME/bin:$PATH
Copy the pas.zip file to the location that you have set in your MW_ORA_HOME environment variable.
Unzip the pas.zip file using the following command: unzip pas.zip (If you have unzipped the pas.zip elsewhere, move it to the location that you’ve set in your MW_ORA_HOME environment variable).
Take a backup of the OPSM data. In particular, take a backup of any custom code in the package specification and body of the following database packages - PAS_SERIAL_GEN and PAS_SERIAL_VAL.
Create the tablespaces required for creating the FUSION_ATGLITE user by running the "upgradeInstall_step1_fusion_atgliteSchema_createTablespaces.sql" SQL script provided from within the MW_ORA_HOME/pas/db folder.

Important: Open the script and modify the parameters before running. This script should be run while connected to the database as the SYS user.
Import the FUSION_ATGLITE schema by navigating to the MW_ORA_HOME/pas/atglite folder, and running the impdp command. For example, in a Linux environment, the following commands can be run:

sh $ORACLE_HOME /bin/oraenv (to set the environment variables)

create directory mydir as '<MW_ORA_HOME>/pas/atglite;' (keeping the quotes, replace <MW_ORA_HOME> with the actual value and run in sqlplus as the SYS user)

cd $ORACLE_HOME/bin

impdp \”sys/<sys password>@<ORACLE_SID> as sysdba\”

DUMPFILE=mydir:fusion_atglite.dmp

LOGFILE=mydir:fusion_atglite.log

Important: Above command should be run while connected to the database as the SYS user.
Grant new roles and privileges to the database schema users/owners FUSION_ATGLITE and PAS by running the "upgradeInstall_step1_fepasSchema_alterUser.sql" SQL script provided from within the MW_ORA_HOME/pas/db folder.

Important: This script should be run while connected to the database as the SYS user. In addition, the database schema user/owner FUSION_ATGLITE will be created locked and password expired. After the script has run successfully, be sure to edit the FUSION_ATGLITE owner to unlock them and set a new password.
Install the XDBPM utilities by unzipping xdbpm.zip (in the MW_ORA_HOME/pas/db folder). Change to the xdbpm directory and run the xdbSupport.sql script with $PWD as parameter. For the Unix/Linux operating systems:
```
sqlplus <user>/<password>@<database> as sysdba @xdbSupport $PWD
```
Important: This script should be run while connected to the database as the SYS user.
Register the XML Schema’s used by the database objects by running the "upgradeInstall_step1_pasepcSchema_doSchemaRegistration.sql" SQL script provided within the MW_ORA_HOME/pas/db folder.
```
sqlplus <user>/<password>@<database> as sysdba @upgradeInstall_step1_pasepcSchema_doSchemaRegistration.sql $PWD
	
```
Important: This script should be run while connected to the database as the SYS user.
Upgrade the OPSM database objects (for example, tables, views, and so on) by running the "upgradeInstall_step1_fepasSchema_upgradeSchema.sql" SQL script provided within the MW_ORA_HOME/pas/db folder.
```
sqlplus <user>/<password>@<database> @ upgradeInstall_step1_fepasSchema_upgradeSchema.sql $PWD
```
Important: This script should be run while connected to the database as the PAS user.
Restore the backup of the custom code in the packages PAS_SERIAL_GEN and PAS_SERIAL_VAL.
Create synonyms for the PAS objects in the FUSION_ATGLITE schema by running the “newInstall_step2_fusionSchema_createSynonyms.sql” SQL script provided within the MW_ORA_HOME/pas/db folder.

Important: This script should be run while connected to the database as the FUSION_ATGLITE user.
Grant privileges over PAS objects to the FUSION_ATGLITE user by running the "upgradeInstall_step1_fepasSchema_grantsForFusion.sql" SQL script provided within the MW_ORA_HOME/pas/db folder.

Important: This script should be run while connected to the database as the SYS user.
Upgrade the seed data by running the "upgradeInstall_step2_fepasSchema_upgradeSeedData.sql" SQL script provided from within the MW_ORA_HOME/pas/db folder.

Important: This script should be run while connected to the database as the PAS user.
Load the seed data by running the "seed_pas_audit.sql" SQL script provided from within the MW_ORA_HOME/pas/db folder.

Important: This script should be run while connected to the database as the FUSION_ATGLITE user.
Upgrade the user data by running the "upgradeInstall_step3_fepasSchema_upgradeUserData.sql" SQL script provided from within the MW_ORA_HOME/pas/db folder.

Important: This script should be run while connected to the database as the PAS user.
Move the jar utility from your JDK home folder into the search path. This is needed because the install script uses the jar utility to extract the files and modify the connection parameters.
Replace this line: JAVA_OPTIONS="${JAVA_OPTIONS}" in the setDomainEnv.sh located in $MW_HOME/user_projects/domains/<domain_name>/bin directory with the following: JAVA_OPTIONS="${JAVA_OPTIONS} -DATGLITE=Y -Doracle.jdbc.createDescriptorUseCurrentSchemaForSchemaName=true"
Navigate to $MW_HOME/user_projects/domains/base_domain/bin, and startup the WebLogic server and the managed servers using the following command:

./startWebLogic.sh

./startManagedWebLogic.sh soa_server1

./startManagedWebLogic.sh pas_server1

Create the following ATGLITE JDBC datasources in the WebLogic Server Admin Console (e.g. http://<server hostname>:<admin server port>/console):


Name	JNDI Name	User
ApplicationDB	jdbc/ApplicationDBDS	FUSION_ATGLITE user with the OPSM database connection properties
AppMasterDB	jdbc/AppMasterDBDS	FUSION_ATGLITE user with the OPSM database connection properties
mds-ApplicationMDSDB	jdbc/mds/mds-ApplicationMDSDBDS	OPSM MDS user with the OPSM MDS database connection properties

For the above:

Database type should be Oracle.
The database driver should be Oracles Driver (Thin) for Instance connections: Versions: 9.0.1 and later.
Uncheck Supports Global Transactions under the Transaction Options.
Target the datasources to the application server and SOA server. For example, pas_server1 and soa_server1.
After creating the datasources, modify the following properties under the Connection Pool tab: Initial Capacity = 20, Minimum Capacity = 20, and Maximum Capacity = 4096 (same as the pasDB datasource settings).

Change the Staging Mode property under the server Configuration tab and Deployment sub-tab of the application server and SOA server (for example, pas_server1 and soa_server1) to nostage. Backup the files under the folder present in the Staging Directory Name property and remove the files from that directory for both the application server and SOA server (for example, pas_server1 and soa_server1).
Ensure the Listen Address and Listen Port properties of the servers is populated with the host address and the corresponding port for that server, under the server Configuration tab and General sub-tab.
Backup the user_projects directory under the middleware home. This is needed because the upgrade script modifies the domain and if the upgrade fails for any reason, you will need this backup to restore the original domain.
In the Weblogic Admin Console, navigate to Services, then Data Sources, then select the pasDB data source. On the Configuration tab and Connection Pool sub-tab, change the user for the pasDB data source to FUSION_ATGLITE and change the password corresponding to that user.
In the Enterprise Manager, undeploy all OPSM applications. Under the Fusion Middleware domain, expand WebLogic Domain then select your domain (for example, base_domain). On the right side, at the top of the page, from the WebLogic Domain drop down, select Application Deployment, then select Undeploy. Select PasSerializationManager, PasSerialsService_SerialsServices, PasTransactionsService_TransactionsServices and then click Next. Click Undeploy.
In the Enterprise Manager, undeploy all composites. Under the Navigation Tree, go to Farm_<domain> node (<domain> refers to the actual name of your domain), then SOA node, then soa-infra node, then default node, then select the Deployment button, and select Undeploy All From This Partition. If after undeploying the composites, if some composites still show as deployed, then bounce the soa_server1.
Populate the values in pas_install.properties to ensure that a description of every property is available before the property is referred to. The appropriate parameters are described in the comments of the pas_install.properties file. The pas_install.properties file is located in the MW_ORA_HOME/pas/scripts directory.

Configure an Access Control List File for Web Service E-mail Notifications (Optional)

If you want the system to send notification e-mails if errors are detected on transactions or transactions that are locked as "In Progress" during the processing of the Transaction Service, Serial Service, and Product Service web services then you must configure an access control list (ACL) file. To configure an ACL file you will need to:

Create an ACL file.
Assign the ACL file to the outgoing SMTP network host for your e-mail server.
Grant permission to use the ACL file.

Before you can use PL/SQL network utility packages such as UTL_SMTP, you must configure an ACL file that enables fine-grained access to external network services.

To Configure an ACL File for Web Service E-mail Notifications:

Log into the database as the "sys" user.

Create an ACL file.

Example for creating an ACL file:

begin

   dbms_network_acl_admin.create_acl (
   acl => 'utl_smtp.xml',
   description => 'Enables mail to be sent',
   principal => 'PAS',is_grant => true,
   privilege => 'connect',
   start_date => TO_DATE('2007-12-27','yyyy-mm-dd'),
   end_date => TO_DATE('2022-12-27','yyyy-mm-dd')
    );

   commit;
  end;
   /


Name	Parameter
acl	The name of the access control list XML file, generated relative to the "/sys/acls" directory in the XML DB Repository.
description	A description of the ACL.
principal	Principal (database user or role) to whom the privilege is granted or denied. Case sensitive.
is_grant	Privilege is granted or not (denied).
privilege	Network privilege to be granted or denied - "connect \| resolve" (case sensitive). A database user needs the connect privilege to an external network host computer if they are connecting using the UTL_TCP, UTL_HTTP, UTL_SMTP, and UTL_MAIL utility packages. To resolve a host name that was given a host IP address, or the IP address that was given a host name, with the UTL_INADDR package, grant the database user the resolve privilege.
start_date	Default value NULL. When entered, the ACL will only be active on or after the entered date. Date formats are: yyyy-mm-dd (2013-09-01) dd-mm-yyyy (01-09-2013) mm-dd-yyyy (09-01-2013) You can enter date in any format if the valid date format is provided.
end_date	An optional end date for the ACL. Date formats are: yyyy-mm-dd (2013-09-01) dd-mm-yyyy (01-09-2013) mm-dd-yyyy (09-01-2013) You can enter date in any format if the valid date format is provided.

Assign the ACL to the outgoing SMTP network host for your e-mail server.

Example for assigning ACL to outgoing SMTP network:

begin
   dbms_network_acl_admin.assign_acl (
   acl => 'utl_smtp.xml',
   host => 'your smtp host name',
   lower_port => your smtp port);
   commit;
  end;
/


Name	Parameter
acl	The name of the access control list XML file.
host	The hostname, domain, IP address, or subnet to be assigned. Hostnames are case sensitive, and wildcards are allowed for IP addresses and domains.
lower_port	Defaults to NULL. Specifies the lower port range for the "connect" privilege.
upper_port	Defaults to NULL. If the lower_port is entered, and the upper_port is NULL, it is assumed the upper_port matches the lower_port.

Grant permission to use the ACL file.

Example for adding the privilege:

begin

   dbms_network_acl_admin.add_privilege (
   acl => 'utl_smtp.xml',
   principal => 'PAS',
   is_grant => TRUE,
   privilege => 'connect',
   start_date => TO_DATE('2007-12-27','yyyy-mm-dd'),
   end_date => TO_DATE('2022-12-27','yyyy-mm-dd')
    );

   commit;
  end;
   /


Name	Parameter
acl	The name of the access control list XML file.
principal	Principal (database user or role) to whom the privilege is granted or denied. Case sensitive.
is_grant	Network privilege to be granted or denied - "connect \| resolve" (case sensitive). A database user needs the connect privilege to an external network host computer if they are connecting using the UTL_TCP, UTL_HTTP, UTL_SMTP, and UTL_MAIL utility packages. To resolve a host name that was given a host IP address, or the IP address that was given a host name, with the UTL_INADDR package, grant the database user the resolve privilege.
privilege	Network privilege to be granted or denied.
position	Position (1-based) of the access control entry (ACE). If a non-NULL value is given, the privilege will be added in a new ACE at the given position and there should not be another ACE for the principal with the same is_grant (grant or deny). If a NULL value is given, the privilege will be added to the ACE matching the principal and the is_grant if one exists, or to the end of the ACL if the matching ACE does not exist.
start_date	Start date of the access control entry (ACE). When entered, the ACE will be valid only on and after the entered date. The start_date will be ignored if the privilege is added to an existing ACE. Date formats are: yyyy-mm-dd (2013-09-01) dd-mm-yyyy (01-09-2013) mm-dd-yyyy (09-01-2013) You can enter date in any format if the valid date format is provided .
end_date	End date of the access control entry (ACE). When entered, the ACE will expire after the entered date. The end_date must be greater than or equal to the start_date. The end_date will be ignored if the privilege is added to an existing ACE. Date formats are: yyyy-mm-dd (2013-09-01) dd-mm-yyyy (01-09-2013) mm-dd-yyyy (09-01-2013) You can enter date in any format if the valid date format is provided .

Upgrade Tasks

Make sure that the admin server and the managed servers (for example, soa_server1 and pas_server1) are not running.
Navigate to the PAS script directory.

For example, cd MW_ORA_HOME/pas/scripts
Execute the upgrade script to upgrade Oracle Pedigree and Serialization Manager.

For Unix-based installs, use the "pasMasterUpgrade.py" script. Run the installation script using the following command: $MW_ORA_HOME/common/bin/wlst.sh ./pasMasterUpgrade.py

Ensure that the terminal on which you are running the upgrade has sufficient scroll-back lines (for example, 2000) to capture all the output from the install activities. This enables you to review all of the upgrade activities later.

Important: The upgrade script attempts to start the Admin Server. It tests in a loop if the server is up before it continues. If you installed your WebLogic Server in Production Mode, the Admin server requires a userid and password to start which the script does not set for security reasons. In this case, you must start a new terminal window to start the Admin Server. After the script detects the server has started, it will continue.

After the Admin Server has been started, the upgrade script will prompt you to start up the managed servers (for example, soa_server1 and pas_server1). To do so, make sure the environment variables are set as described in the Pre-Upgrade Tasks section, then navigate to MW_HOME/user_projects/domains/base_domain/bin. Using separate terminal windows, startup the PAS and SOA managed servers. Keeping in mind your actual managed server names may be different, use the following commands as examples:

For Unix-based installs:
- sh startManagedWebLogic.sh soa_server1
- sh startManagedWebLogic.sh pas_server1
After the managed servers are started, press enter in the first terminal where pasMasterUpgrade.py is run to continue processing the install script.
The OPSM installation output is captured in the scroll buffer of the terminal on which you run the installation. Scroll through the buffer to check for errors. The following warnings, if seen, can be ignored:
- WARNING: Failed to create ConnectionDBean for {http://xmlns.oracle.com/oracle/apps/fnd/applcore/flex/deployment/service/model/}FlexDeploymentService
- WARNING: Failed to create ConnectionDBean for AtkHelpPortalService
After the upgrade script has completed successfully, you must restart the Admin Server and managed servers (for example, soa_server1 and pas_server1) for changes made by the upgrade script to take effect.

Post Upgrade Tasks

Verify Servers are Running

Refer to the Post Installation Tasks section to verify that the servers are running.

Configure Security for the Application and Services

Refer to the Oracle Pedigree and Serialization Manager Security Guide to configure security for the new web services and SOA composite:

QueryService
CaptureService
ProductServiceAMService
PasCaptureComposite

In the Oracle Pedigree and Serialization Manager Security Guide:

The Setting Up Global Policy Attachments section applies to ProductServiceAMService. If global policy sets are set up such that the same Policy Sets apply to all services, no additional setup is needed for this service.

The Setting Up Direct Policy Attachments section applies to the QueryService and CaptureService. Note the change in URL for the SerialsServiceAMService from opsmservices-serials/SerialsServiceAMService to opsmservices-transactions/SerialsServiceAMService.

The Setting Up Global Policy Attachments for Composites section applies to PasCaptureComposite. Review and make the necessary changes for PasCaptureComposite.

Enter Digital Signature Information (Optional)

Enable digital signatures.

Refer to the Setting Up Keys and Passwords for Digital Signature section in the Oracle Pedigree and Serialization Manager Security Guide for the setup related to digital signatures.
Enter location contact information.

Additional set up may be required for Location Contacts if you are using Digital Signatures. Refer to Maintaining Locations and Understanding Pedigree sections in the Oracle Pedigree and Serialization Manager Process Guide.

Re-Upgrade Tasks

In the event that an upgrade fails, follow the procedure below to perform a new upgrade. Keep in mind that your actual managed server names may differ from those used in the sample commands listed below.

Make sure that the environment variables are set as described in Pre-Upgrade Tasks, and that you are in the DOMAIN_HOME (typically MW_HOME/user_projects/domains/base_domain).
Stop the SOA Server.

Go to DOMAIN_HOME/bin and issue the following command at the prompt:

For Unix-based installs:

sh stopManagedWebLogic.sh soa_server1 t3://<servername>:<adminport>

For example:

sh stopManagedWebLogic.sh soa_server1 t3://host.oracle.com:7001
Stop the PAS Server.

Go to DOMAIN_HOME/bin and issue the following command at the prompt:

For Unix-based installs:

sh stopManagedWebLogic.sh pas_server1 t3://<servername>:<adminport>

For example:

sh stopManagedWebLogic.sh pas_server1 t3://host.oracle.com:7001
Stop the Admin Server.

Go to DOMAIN_HOME/bin and issue the following command at the prompt:

For Unix-based installs:

sh stopWebLogic.sh
Perform cleanup tasks:
1. Clean up the MW_HOME/user_projects directory and restore from the backup taken before the initial installation.
2. Delete the pas directory under MW_ORA_HOME.
Perform step 5 from Pre-Upgrade Tasks.
Perform step 7 from Pre-Upgrade Tasks.
Perform a new upgrade.

Follow the steps for a new upgrade starting with step 1 under the section Upgrade Tasks.