This section includes the following topics:
Renaming the Precise FocalPoint server
Using CLI you can rename the Precise FocalPoint server. This can be used, if due to IT requirements, you need to rename the Precise FocalPoint server.
Limitations
- If the FocalPoint server has instances or Collectors installed on it, you can’t rename it. The only exceptions to this, are the following agents:
- Alerts InformPoint
- Precise for SAP agent
- If you have a Collector other than the ones above, installed on the FocalPoint server, contact Customer Support for further assistance.
- If you have already installed updates on one of your components, verify with Customer Support whether you have to reapply these updates after performing the Move and Rename procedure.
Procedure
To rename the FocalPoint server
- Before running the rename server CLI, verify that you completed physically renaming the server (using the related server operating system tools).
- Manually stop all Precise agents on the server including on the Precise FocalPoint server. Don’t use the GUI to stop them.
- Delete the infra/host/hostname.txt file.
- Run the following command from the <Precise_root> folder on the renamed server:
Windows infra\bin\psin_cli.bat
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action rename-server
-old-name <previous_server_name>
-new-name <new_server_name>
-proxy-alias <proxy_alias>
-installation-cd-path <installation_cd_path>
UNIX ./infra/bin/psin_cli.sh
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action rename-server
-old-name <previous_server_name>
-new-name <new_server_name>
-proxy-alias <proxy_alias>
-installation-cd-path <installation_cd_path>
Table 13-1 Elements for Renaming the Precise FocalPoint server
| Element | Description |
|---|
| i3-user | See Authenticate to CLI Utility. |
| i3-encrypted-password | See Authenticate to CLI Utility. |
| action | Always rename server Mandatory: Yes |
| old-namer | The server name before the rename. Values: previous-server-name Mandatory: Yes |
| new-name | The server name after the rename. Values: new-server-name Mandatory: Yes |
| proxy-alias | The renamed node alias. Mandatory: Yes |
| installation-cd-path | Indicates the absolute path to the folder where the Precise v9.6 download was downloaded to. Values: String Mandatory: Yes |
Moving the Precise FocalPoint server
Using CLI you can move the Precise FocalPoint server. This can be used if, due to IT requirements, you need to move all Precise FocalPoints on the server to another server.
Limitations
- The instructions refer to moving all Precise components that are installed on the Precise FocalPoint server to another server. Partial moving, or moving components from a server other than the Precise FocalPoint server, is not supported. If you want to move only one FocalPoint, contact Customer Support.
- If the FocalPoint server has instances or collectors installed on it, you can’t move it. The only exceptions to this, are the following agents:
- Alerts InformPoint
- Precise for SAP agent
- If you have a Collector not from the list above installed on the FocalPoint server, contact Customer support for further assistance.
- Only the PMDB FocalPoint is handled; the PMDB is not moved during this procedure. To move the PMDB, see Moving the PMDB to another server.
- Datafiles in the Precise FocalPoint that were not loaded to the PMDB are lost.
- The server to which the Precise FocalPoint is moved should have the same characteristics as the original Precise FocalPoint server.
- Identical operating system vendors.
- Same operating system type. However, the version may be different. For example: A transition from Linux 6.2 to Linux 7.0 and vice versa is not supported, but a transition from Linux 7.0 to Linux 7.1 and vice versa is possible.
- Same bit version. Moving components from 64-bit servers to 32-bit server, or vice versa, is not supported.
- Same CPU model. Moving components from AMD CPU to ITANIUM CPU, or vice versa, is not supported.
- You cannot move the Precise framework and the product frameworks to a server that is already installed as part of your federation installation.
- If you have already installed updates on one of your components, verify with Customer Support whether you have to reapply these updates after performing the Move and Rename procedure.
Procedure
To move the FocalPoint server
- Stop all agents on all servers except for infra agents (listeners and Precise FocalPoint)
- Manually stop the Precise FocalPoint
Copy the entire <precise_root> folder from the origin server to the target server.
For UNIX, verify that the <precise_root> folder is moved to the target server with the original folder permissions. If the original folder permissions are not saved on the target server, problems may occur. |
- After the copy is completed, delete the file infra/host/hostname.txt from the new server.
- Start the Precise FocalPoint on the original server.
Run the following CLI on the new server using IN as the product-code argument value:
Windows infra\bin\psin_cli.bat
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action move-focal
-product <product_code>
-old-server <old_server_name>
-new-server <new_server_name>
-installation-cd-path <cd_path>
-proxy-alias <proxy_alias>
UNIX ./infra/bin/psin_cli.sh
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action move-focal
-product <product_code>
-old-server <old_server_name>
-new-server <new_server_name>
-installation-cd-path <cd_path>
-proxy-alias <proxy_alias>
After the move, the old server contains only the Precise Listener. You can uninstall it using setup for server CLI. The CLI might produce action items. |
- For each FocalPoint you have installed on the old server, run the same command as above on the new main Precise FocalPoint server (change the -product argument value). When running the CLI, run it according to the following order:
- SAP FocalPoint (if installed) - product code SP
- Alerts FocalPoint (if installed) - product code PF
- All other installed FocalPoints product codes
Table 13-2 Elements for Moving the Precise FocalPoints server
| Element | Description |
|---|
| i3-user | See Authenticate to CLI Utility. |
| i3-encrypted password | See Authenticate to CLI Utility. |
| action | Always move-focal Mandatory: Yes |
| product | Values:The FocalPoint product code. See Product Codes. Mandatory: Yes |
| old-server | The old server name. Values: string Mandatory: Yes |
| new-server | The new-server-name. Values: string Mandatory: Yes |
| installation-cd-path | Path to the folder where the Precise v9.6 download was downloaded to. Values: string Mandatory: Yes |
| proxy-alias | The renamed node alias. Values: string Mandatory: Yes |
Post-move adjustments and updates
After moving the FocalPoint server, you will need to make adjustments and updates for the following:
- Adjustment for Precise for SAP FocalPoint and agents on the new server
- Updating SAP on the original server
Adjustment for Precise for SAP FocalPoint and agents on the new server
To adjust the Precise for SAP framework on the new server
- Run the following commands from the <precise_root> folder (to uninstall Precise for SAP FocalPoint services):
products\sap\bin\pssp_install_fp.bat products\sap\bin\pssp_install_agents.bat IS1 - Open the products\sap\cfg\IS1\agents-config.xml file and replace the original server's Precise root folder with the new server's Precise root folder in the following elements:
- homedir
- cfgdir
- logdir
- rfgdir
- Start the agents on the new server.
Updating SAP on the original server
To update SAP on the original server
- Run the following commands from the <precise_root> folder to uninstall the Precise for SAP FocalPoint services:
products\sap\bin\pssp_uninstall_fp.bat products\sap\bin\pssp_uninstall_agents.bat IS1
Verification
After moving the Precise FocalPoint’s server, perform the following verifications in the new installation:
- Check the agent’s status in Adminpoint
- Check that the Performance Warehouse processes are running and that data is loaded
- Check that data is displayed in the various products
Moving the PMDB FocalPoint to another server
Using CLI you can move the PMDB FocalPoint to a new server.
Limitations
- The new server should be installed (with BA) before the PMDB FocalPoint is moved.
- Only the PMDB FocalPoint is handled; the PMDB is not moved during this procedure. To move the PMDB, see Moving the PMDB to another server.
Procedure
To move the PMDB FocalPoint
- Run the following command from the main Precise FocalPoint server.
Windows infra\bin\psin_cli.bat
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action move-focal
-product PW
-old-server <old_server_name>
-new-server <new_server_name>
[-installation-cd-path <cd_path>]
UNIX ./infra/bin/psin_cli.sh
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action move-focal
-product PW
-old-server <old_server_name>
-new-server <new_server_name>
[-installation-cd-path <cd_path>]
This CLI might produce action items. In case of failure, the command can be executed again. |
Table 13-3 Elements for Moving the PMDB FocalPoint to another server
| Element | Description |
|---|
| i3-user | See Authenticate to CLI Utility. |
| i3-encrypted-password | See Authenticate to CLI Utility. |
| action | Always move-focal Mandatory:Yes |
| product | Always PW Mandatory: Yes |
| old-server | The old PW server name. Values: string Mandatory: Yes |
| new-server | The new PW server name. Values: string Mandatory: Yes |
| installation-cd-path | The path to the path to the folder where the Precise v9.6 download was downloaded to. Values: string Mandatory: Yes |
Moving the PMDB to another server
Using CLI, you can move the PMDB to another server.
When moving the PMDB FocalPoint to a server other than the Precise FocalPoint server, restart the Precise Listener on the new PMDB FocalPoint server. |
Limitations
- You can only move the PMDB. No agents are involved.
- You can only move to the same DBMS type (for example, Oracle to Oracle and SQL Server to SQL Server).
However, you can move to another DBMS version.- For an SQL Server based database, you must use the same authentication mode (SQL authentication or Windows OS Authentication), and the new database should have the same collation.
- For an Oracle database, you must use the same charset.
For guidelines regarding export and import, see Examples for exporting and importing an SQL Server or Oracle based PMDB.
Procedure
To move the PMDB
- Stop all agents, including Precise Listeners and the Precise FocalPoint.
- Manually export the PMDB, and import it to the new DBMS. For an Oracle PMDB, export the PMDB tablespaces metadata also.
- Start the Precise FocalPoint.
- Run the CLI command on the main Precise FocalPoint server. The command updates the Precise registry with the related information.
Windows infra\bin\psin_cli.bat
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action move-pw-db
-parameter <parameter_name>=<parameter_value>
UNIX ./infra/bin/psin_cli.sh
-i3-user <user_name>
{-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
-action move-pw-db
-parameter <parameter_name>=<parameter_value>
For example:
For SQL Server in Windows:
infra\bin\psin_cli.bat
-i3-user admin -i3-clear-password admin
-action move-pw-db -parameter dbms-instance=NEW_DATABASE1
-parameter dbms-dba-user=sa
-parameter dbms-dba-clear-password=sa
For Oracle in UNIX:
./infra/bin/psin_cli.sh
-i3-user admin -i3-clear-password admin
-action move-pw-db -parameter dbms-
server=new_poolhp6 -parameter dbms-instance=NEW_ORCL dbms-dba-user=SYSTEM dbms-dba-clear- password=MANAGER
Table 13-4 Elements for Moving the PMDB to another server
Verification
After moving the PMDB to another server, perform the following verifications in the new installation:
- Check the agent’s status in Adminpoint
- Check that the Performance Warehouse processes are running and that data is loaded
- Check that data is displayed in the various products
Examples for exporting and importing an SQL Server or Oracle based PMDB
The following section provides examples of the export and import procedures for SQL Server and Oracle based PMDBs.
Exporting and importing an SQL Server based PMDB
To export an SQL Server based PMDB
- Open the Microsoft SQL Server Management Studio.
- Right-click on the Performance Warehouse database.
- Select the Tasks > Back Up … option.
- Configure the backup file and click OK.
- Wait for confirmation of a successful export.
To import an SQL Server based PMDB
- Copy the created backup file to the new server.
- Open the Microsoft SQL Server Management Studio on the new server.
- Right-click on Databases.
- Select Restore Database….
- In the "to database?" field, enter the previous database name.
- In the "from device" field, click on the ... (browse) button, and select the backup meda file.
- Select Add.
- Select the backup file.
- Click OK.
- Select the most recent backup.
- Click OK on the restore confirmation message.
Exporting and importing an Oracle based PMDB
When using Oracle as the PMDB repository, you can use the export and import utilities to move data. For more information, see http://wiki.oracle.com/page/Oracle+export+and+import+.
These utilities are available under the <ORACLE_HOME>/bin folder. |
To export an Oracle based PMDB
- Open a command line.
- Execute "exp" with the tablespaces’ parameter.
- Follow the instructions in the script (you can use most of default values).
- For "user to be exported", enter the PMDB user, for example: PRECISE_PMDB
If error 942 occurs while using the export utility, execute the following as system user:
@c:\oracle\ora92\rdbms\admin\catexp.sql
To import an Oracle based PMDB
- Copy the exported data to the new database.
- Open a command line in the new database.
- Execute the "imp‟ command and follow the script instructions.