Date: Fri, 29 Mar 2024 10:27:36 -0500 (CDT) Message-ID: <999007702.30340.1711726056013@bmc1-rhel-confprod1.managed.contegix.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_30339_1568802742.1711726056012" ------=_Part_30339_1568802742.1711726056012 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
To identify a source file that can be deployed from a remote loc= ation to another remote location without making a local copy, you must crea= te a URL using a special syntax that incorporates a protocol and a network = location.
The URL syntax is shown below. Square brackets indicate optional compone= nts.
[[prot= ocol:][//[Domain;][User][:password]@]Host[:port]]][/sharename]/Path
Omitting all components except The following list explains all components in a URL: Note The rscd protocol does not work with the Agent mounts source for=
direct use at deployment option. Note On some systems you might be required to have the nfslock and <=
em>rpcbind or portmap services running for the nfs mount to b=
e established properly. Ensure that these services are running before attem=
pting an nfs-based deploy. Note Be aware of the following: Note To ensure that a password remains encrypted throughout the Deploy Job pr=
ocess, you can enter a password as a parameter, such as /Path
specifies direct acces=
s to the file system of the local host. When you provide only /Path=
code>, files are accessed using local system calls rather than networking.<=
/p>
protocol
=E2=80=94 specifies how to put or get files and di=
rectories to or from the specified Host. For the local host, the default ap=
proach is to use direct access to the file system. For remote hosts, the fo=
llowing protocols are supported:
rscd
=E2=80=94 Use the Network Shell protocol. This is =
the default approach.file
=E2=80=94 Use the local file system.nfs
=E2=80=94 Use UNIX file sharing.smb
=E2=80=94 Use Windows file sharing. For the SMB prot=
ocol, you must provide a Windows "share name" in front of the path. No othe=
r protocols require a share name. The SMB protocol also requires you to pro=
vide all necessary connection information (domain, user name, and password)=
.
Domain
=E2=80=94 The Windows domain that provides user acc=
ounts. A domain is only necessary for the SMB protocol. When providing Wind=
ows user information, if you do not provide a domain, the user is presumed =
to be a user local to the host.User
=E2=80=94 The identity that should be used to access =
a device. A user is only necessary for the SMB protocol. The default value =
for User
is the identity of the user who invoked the Deploy Jo=
b.password
=E2=80=94 The password for the specified user. =
A password is only necessary for the SMB protocol. URLs containing password=
s are encrypted when passed between devices.??MOUNT_PWD??=
. The parameter can reference a local property on a BLPackage used t=
o deploy a software package or it can reference a server property for the h=
ost to be mounted. The value of the property contains the actual password. =
When defining the property, choose a property type of Simple and set the ty=
pe to Encrypted String.Host
=E2=80=94 The DNS host name or IP address (IPv4 or IP=
v6). The default value is localhost (127.0.0.1). If you specify an IPv6 add=
ress along with the NFS protocol or the SMB protocol, enclose the IPv6 addr=
ess in brackets.Port
=E2=80=94 The IP port number that should be used to a=
ccess the protocol service on the host. The default value is based on the s=
elected protocol, such as 4750 for rscd or 2049 for nfs.ShareName
=E2=80=94 The name under which a directory is ex=
ported via Windows file sharing. This optional component should only be spe=
cified for the SMB protocol. Internally, BMC Server Automation converts the=
directory specified with ShareName
into a UNC location and as=
sociates connection information (Domain
, User
, an=
d password
) that can be used to access the UNC location.
For NFS, BMC Server Automation consults the NFS server to determine which =
initial sub-string in the path is exported. BMC Server Automation combines =
this sub-string with the absolute path defined using the Path
=
component.Path
=E2=80=94 The path to a file or directory. Use forwar=
d slashes "/" as path delimiters.Examples
/etc/p=
asswd
# /etc/passwd on the current default host
//hp11dev/etc/passwd
# /etc/passwd on hp11dev, using the rscd protocol
nfs://hp11dev/etc/passwd
# Use an NFS mount of hp11dev export
smb://myDomain;BLuser:??MOUNT_PWD??@winXP37/REPO/HOSTS
# The HOSTS file is in a shared directory called REPO. Access the # HOSTS f=
ile=20
# using an SMB map.=20
# The user who can access the file is named BLuser in the domain called myD=
omain.=20
# The password # is a parameter referring to a local property called MOUNT_=
PWD.=20
# The host name is winXP37.