ECM Connector 2.0

Hello-

I have a few questions regarding the ECM connector which I haven't been able to find in the documentation.

1. Is it possible to select an "initial-directory" and a "ceiling-directory" in which we can start the user off in one folder and limit that user from other folders in MediaBin. The idea is to create a folder off the root in MediaBin called "WebAssets". This folder would be the only folder users of TeamSite would have access to in MediaBin.

2. Is it possible to turn off the Media Bin "Import" button in TeamSite? There are some users that should not be given the option to import assets from MediaBin. Would it be possible to disable the ECM "import" button and revert to the pre-ECM "import" button using the TeamSite GUI Toolkit and keep the ECM connector installed?

3. Does authentication between the user of TeamSite and the credentials of assets in MediaBin only work if LDAP is used? The user that is logged into TeamSite should only have access to the assets that have rights to in MediaBin.

Thanks
Anew

Find more posts tagged with

Comments

msnider

Yes, the MediaBin server must be configured to use LDAP in order to use the "Login as TeamSite user" option. In addition, the MediaBin web service must be configured correctly to use TrustedClient authentication. The web service's ReadMe file should explain what changes need to be made.

Once you've configured the ECM Connector to use TrustedClient authentication, the user privileges you've assigned in MediaBin should be reflected within the ECM Connector browser thus allowing you to restrict access to specific folders for each individual user.

The above describes how to filter the MediaBin folder structure based on user permissions. I'm not sure if that covers your definition of an "initial" folder. I believe the ECM Connector attempts to locate the last folder\asset picked and that value is stored in a properties file. However, you may want to cross post to the TeamSite forum to see if that is truly the case and to see if there is a way to conditionally disable the Import button.

Hope this helps,
Mark

cliff1

Anew,

Very insightful questions. Here are the anwsers:

1. This is currently not an option (a feature request already exists). However, if you limit the permissions in MB, can can get some of the control you desire. If you are using a guest account, make sure the guest user can only access the desired folders/files. For trusted login, the assuption is the TeamSite user is also a MB user, so they should have access to the same set of files -- after all, they can log directly into MB and export the file and then import it into TS.

2. There is no way to "enable" the MB connection and then "disable" the direct import feature. I'll file a feature request.

3. See Mark's reply. If you are using the "Login with a MediaBin guest account" option, no LDAP is needed.

Nicholas

Anew,

Very insightful questions. Here are the anwsers:

1. This is currently not an option (a feature request already exists). However, if you limit the permissions in MB, can can get some of the control you desire. If you are using a guest account, make sure the guest user can only access the desired folders/files. For trusted login, the assuption is the TeamSite user is also a MB user, so they should have access to the same set of files -- after all, they can log directly into MB and export the file and then import it into TS.

2. There is no way to "enable" the MB connection and then "disable" the direct import feature. I'll file a feature request.

3. See Mark's reply. If you are using the "Login with a MediaBin guest account" option, no LDAP is needed.

I would like to know if this feature request is already filed? that when import asset from TeamSite-Import then there should be option to import a whole directory rather one asset at a time.

I think, I reaised this question sometime ago but not sure so please confirm if it is filed already.

Thanks Nicholas
Thanks Nicholas

cliff1

Feature Request # 63342 is "Should be able to use the ECM Connector to import a group of associated media files with a single import action.". This is talking about importing a group of MB files that have been related in MediaBin -- they do not need to be in the same directory. Do you specifically want to import a directory?

The problem with either scenario is coming up with the semantics that everyone will agree is correct for a group of files. Error handling is perhaps the stickiest issue. Could you send me an e-mail offline and I will try to arrage a call between you, me and the Product Manager. The next two weeks don't look good, but early December looks OK.

cliff.mcbride@interwoven.com

suj

While Iwov is implementing the feature request for getting associated files in mediabin, anyone who needs this can use web services to identify the related assets (You may have this as a subroutine in TPL or a perl module). I did this for ECM 1.0. ECM 2.0 may need a different approach in getting the mediabin details.

Something like this:-Not much error handling though.

package ****::Utilities;

###############################################################################
=pod

=head1 NAME
Utilities.pm

=head1 SYNOPSIS

Methods available:
****::Utilities::getAssociatedAssets();

=head1 DESCRIPTION
This module contains commonly used functions

=head1 COPYRIGHT
E 2006 of ****.

=head1 AUTHOR
****.

=head1 REVISION
Desc Ver 0.1 : 05th June 2006 : ****: Base version

=head1 METHODS

=cut
###############################################################################
# Include strict pragma
use strict;
no warnings;

use TeamSite::Config;

###############################################################################
=pod
=head2 getAssociatedAssets()
This method will return associated assets for an asset from MediaBin

=over

=item ARG
Parameter 1 - assetID

=item RETURNS
List of assscoiated asset IDs
None

=back
=cut
###############################################################################

sub getAssociatedAssets($) {

my ($assetID) = @_;

use SOAP::Lite ;#( +trace => all, maptype => {} );
(my $iwhome = TeamSite::Config::iwgethome()) =~ tr|\\|/|;

my %connectorDetails = getMediaBinConnectorDetails("$iwhome/httpd/webapps/content_center/WEB-INF/conf/sample_connector/connector.xml");

# Provide Authentication details
my $decryptedPassword = `java -classpath $iwhome/httpd/webapps/content_center/WEB-INF/lib/customer.jar:$iwhome/httpd/webapps/content_center/WEB-INF/lib/jce-jdk13-124.jar:$iwhome/httpd/webapps/content_center/WEB-INF/lib/sample_connector.jar DecryptString $connectorDetails{password}`;
chomp($decryptedPassword);
BEGIN {
sub SOAP::Transport::HTTP::Client::get_basic_credentials {
return "$connectorDetails{domain}\\$connectorDetails{user}" => "$decryptedPassword";
}
}

# Create the SOAP object
my $soap = SOAP::Lite
-> proxy("$connectorDetails{wsdl_url}")
-> on_action( sub { join '/', 'http://www.mediabin.com', $_[1] } )
-> uri("$connectorDetails{wsdl_url}")
;

# Get all the available association IDs

my $method = SOAP: Smiley Very Happy

ata->name('GetAssociations')
->attr({xmlns => 'http://www.mediabin.com'});

my $result = $soap->call($method);

my @nodes = $result->valueof('//MBAssociation');
my @associationIDs;

foreach my $node (@nodes)
{

push @associationIDs, SOAP: Smiley Very Happy

ata->name(string => $node->{'mID'});
}

# Set the parameters for the method

my @params = (SOAP: Smiley Very Happy

ata->name(assetID => $assetID), SOAP: Smiley Very Happy

ata->name(associationIDs => \SOAP: Smiley Very Happy

ata->value(@associationIDs)));

$method = SOAP: Smiley Very Happy

ata->name('GetAssetAssociations')
->attr({xmlns => 'http://www.mediabin.com'});

$result = $soap->call($method => @params);

@nodes = $result->valueof('//GetAssetAssociationsResult/MBMetadata/mValues/anyType');

return @nodes;

}

###############################################################################
=pod
=head2 getMediaBinConnectorDetails()
This method will return connection details for MediaBin

=over

=item ARG
Parameter 1 - config file path

=item RETURNS
Hash of connection details as key-value pair
None

=back
=cut
###############################################################################

sub getMediaBinConnectorDetails($) {

use XML::XPath;

my ($config_file) = @_;

my $xp = XML::XPath->new(filename => "$config_file");
my $nodeset = $xp->find('//config/section[@id="mediabin"]/item'); # find all mediabin item elements
my %connectorDetailsHash;
foreach my $node ($nodeset->get_nodelist) {

my $xp = XML::XPath->new( context => $node );

$connectorDetailsHash{$node->findvalue('@name')} = $node->findvalue('@value');
}

return %connectorDetailsHash;

}

1

TestReport.rptdesign

cliff1

Excellent point! There will always be things that are not productized, or situations where the productized version does not meet your exact needs. MediaBin has excellent web-services that can be leveraged from just about any programming language, so you can augment the ECM Connector functionality with your own custom code.

When using ECM Connector 2.0 and custom code, the biggest issue is having to implement your own solution for getting the MediaBin connection information. The iwhome/local/config/ecmconnector.cfg may change (or go away) over time, so its not good to depend on this file (thus the big warning at the top of the file). Also, the passwords in this file are encrypted, so they are not usable by your custom code. I'm trying to think of a secure solution (that's supportable) in ECM 2.0 for allowing customers to leverage the config information, but no lightbulbs yet.

-Cliff