Thanks for trying out the DCOM feature, Laird!
Useful Blogs you may want to check out:
https://blogs.oracle.com/foo/tags/dcom
The key to using DCOM is getting the Windows machines working with each
other using DCOM. Once they are configured to do that well, everything
else is usually very smooth going.
The key command for you to run is validate-dcom. It will test DCOM
between 2 machines.
asadmin tip of the day. If you want to see every DCOM command that we
have run this:
asadmin dcom
Command dcom not found.
Check the entry of command name. This command may be provided by a
package that is not installed
Closest matching local and remote command(s):
create-node-dcom
delete-node-dcom
install-node-dcom
list-nodes-dcom
ping-node-dcom
setup-local-dcom
uninstall-node-dcom
update-node-dcom
validate-dcom
Again, thanks for using DCOM and please let us know how it goes!
On 4/25/2012 1:48 PM, Laird Nelson wrote:
> On Wed, Apr 25, 2012 at 4:32 PM, Joe Di Pol <joe.dipol_at_oracle.com
> <mailto:joe.dipol_at_oracle.com>> wrote:
>
> [a bunch of useful stuff]
>
>
> What a thorough reply; thanks. I'll see if I can get create-node-dcom
> working since that would by far be the preferred mechanism. If I
> understand you right (and I'll look it up in the manpages as well,
> obviously) I would run this command on the DAS, right, and presumably
> would direct it to "look" at my Windows server? Again, thanks.
>
> Best,
> Laird
>
> --
> http://about.me/lairdnelson
>