IBM Support

Steps to install the Common File System using UNC paths

Question & Answer


Question

How to install the Common File System using UNC paths?

Answer

For both the simple distributed and fully distributed modes of installation, the WebSphere Partner Gateway components require access to a common file system. You enter a path to the common file system root when you install the database and the components. Each computer in a distributed deployment has to have access to the same file system, which is typically done by mapping a drive on the local computers to point to the shared file location.

Many a times, Universal Naming Convention (UNC) path is used for the access to the common file system.

When you use a UNC path to access the file system on another machine, you must first create the common file system by running the installer on the machine that you choose to host the common file system. Then share the common file root directory that was created. After sharing the common file root directory, you can access and use this share with a UNC file name when you install WebSphere Partner Gateway components on remote machines. Do not attempt to create the common file system by running the installer on a remote machine.

However if you need to run the installer to create a common file system from a remote machine you would need to refer to the common file system using a different drive letter (in the case of Windows) or different network path (in the case of UNIX).

After installation if you do not need the drive letter/network path for common you can update the database with the UNC path for the comon file system.
Given below are the steps to update the database:

DB2:

1) Take a backup of the table.
db2 EXPORT TO <path of file> OF DEL MESSAGES <path for log file> SELECT * FROM lg_media
eg. db2 EXPORT TO \tmp\lg_media OF DEL MESSAGES \tmp\msg.out SELECT * FROM lg_media

2) Update the table lg_media with the UNC path

    a) db2 update lg_media set uri='file://<UNC path>/msg_store' where mediaid=2
    eg: db2 update lg_media set uri='file:////mach1.in.ibm.com/c$/common/msg_store' where mediaid=2
    b) db2 update lg_media set uri='file://<UNC path>/non-rep' where mediaid=1
    eg: db2 update lg_media set uri='file:////mach1.in.ibm.com/c$/common/non_rep' where mediaid=1

3) Do a db2 commit.

4) Restart all the servers.

Oracle

1) Take a backup of the table.
    a) Open a command prompt
    b) exp <db name>/<db passwd> file=<pathoffile.dmp> log=<pathoflog.log> tables=lg_media rows=yes

    eg. exp bcgapps/bcgapps file=C:\lg_media.txt log=C:\lg_media.log tables=lg_media rows=yes

2) Update the table lg_media with the UNC path
    a) update lg_media set uri='file://<UNC path>/msg_store' where mediaid=2
    eg: update lg_media set uri='file:////mach1.in.ibm.com/c$/common/msg_store' where mediaid=2
    b) update lg_media set uri='file://<UNC path>/non-rep' where mediaid=1
    eg: update lg_media set uri='file:////mach1.in.ibm.com/c$/common/non_rep' where mediaid=1

3) Do a commit.

4) Restart all the servers.
[{"Product":{"code":"SSDKKW","label":"WebSphere Partner Gateway Advanced Edition"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Not Applicable","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"6.1","Edition":"Advanced;Enterprise","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

More support for:
WebSphere Partner Gateway Advanced Edition

Software version:
6.1

Operating system(s):
AIX, HP-UX, Linux, Solaris, Windows

Document number:
357241

Modified date:
16 June 2018

UID

swg21284597