Author: rdickens
Date: 2013-02-13 15:34:04 -0500 (Wed, 13 Feb 2013)
New Revision: 9146
Modified:
epp/docs/branches/6.0/Admin_Guide/en-US/chapter-3-Command_Line_Interface.xml
Log:
Changed several instances of '<screen>' with '<command>' as
appropriate
Modified: epp/docs/branches/6.0/Admin_Guide/en-US/chapter-3-Command_Line_Interface.xml
===================================================================
---
epp/docs/branches/6.0/Admin_Guide/en-US/chapter-3-Command_Line_Interface.xml 2013-02-13
06:54:53 UTC (rev 9145)
+++
epp/docs/branches/6.0/Admin_Guide/en-US/chapter-3-Command_Line_Interface.xml 2013-02-13
20:34:04 UTC (rev 9146)
@@ -29,11 +29,15 @@
<para>After deploying the CLI web application you can connect to the CLI over
SSH as follows</para>
<example>
<title>SSH Syntax</title>
- <screen>ssh -p <port>
<user>@<host></screen>
+ <para>
+ <command>ssh -p <port> <user>
@<host></command>
+ </para>
</example>
<example>
<title>SSH Example</title>
- <screen>ssh -p 2000 root@localhost</screen>
+ <para>
+ <command>ssh -p 2000 root@localhost</command>
+ </para>
</example>
<remark>Added full path for clarity.</remark>
<para>
@@ -147,7 +151,7 @@
<title>cat</title>
<para>
The
- <code>cat</code>
+ <command>cat</command>
command executes the
<code>read-config-as-xml</code>
operation on a managed resource and outputs the XML data to the shell. The
managed resource must support the
@@ -295,7 +299,7 @@
<title>import</title>
<para>
The
- <code>import</code>
+ <command>import</command>
command executes the
<code>import-resource</code>
operation on a managed resource.
@@ -353,7 +357,9 @@
</para>
<example>
<title>Syntax</title>
- <screen>$ scp -P <port>
<user>@<host>:{portal-container}:{path}
<file></screen>
+ <para>
+ <command>$ scp -P <port>
<user>@<host>:{portal-container}:{path}
<file></command>
+ </para>
</example>
<para>
The
@@ -367,12 +373,16 @@
<para>So to export 'foo/bar' resource assuming the CLI is
deployed to 'example.org'.</para>
<example>
<title>Export of foo/bar resource</title>
- <screen>$ scp -P 2000
'root@example.org:portal:/foo/bar' bar.zip</screen>
+ <para>
+ <command>$ scp -P 2000
'root@example.org:portal:/foo/bar' bar.zip</command>
+ </para>
</example>
<para>Attributes like 'filter' can be added to the path
of the SCP command just as you would add query parameters to a URL.</para>
<example>
<title>Export of foo/bar resource with filter</title>
- <screen>$ scp -P 2000
'root@example.org:portal:/foo/bar?filter=bar:baz,foo-bar'
foo.zip</screen>
+ <para>
+ <command>$ scp -P 2000
'root@example.org:portal:/foo/bar?filter=bar:baz,foo-bar'
foo.zip</command>
+ </para>
</example>
</section>
<section id="sid-8094332_GateInManagement-Import">
@@ -384,7 +394,9 @@
</para>
<example>
<title>Syntax</title>
- <screen>$ scp -P <port> <file>
<user>@<host>:{portal-container}:{path}</screen>
+ <para>
+ <command>$ scp -P <port> <file>
<user>@<host>:{portal-container}:{path}</command>
+ </para>
</example>
<para>
The
@@ -397,7 +409,9 @@
</para>
<example>
<title>Import foo.zip to foo resource</title>
- <screen>$ scp -P 2000 foo.zip
'root@example.org:portal:/foo'</screen>
+ <para>
+ <command>$ scp -P 2000 foo.zip
'root@example.org:portal:/foo'</command>
+ </para>
</example>
<para>More specific examples of the SCP command can be found below
pertaining to that particular management extension.</para>
</section>
Show replies by date