Reusing a repository manager across multiple portal instances

Hi everyone
I am currently implementing a Enterprise Portal, including KM, for a customer. This customer is utilizing two portal instances, one for intranet-users, the other for extranet-users. I am not entirely sure why this approach was chosen, since it was made before I was assigned to this project.
This customer has an interesting requirement: that both portals will utilize the same file share as a KM repository. The idea is that intranetusers (i.e. salespeople etc) will create KM resources for customers. Resources belonging to a specific customer must not be accessible by other customers. Additionally, there may be documents which is only accessible by salespeople.
So far we have implemented automated creation of these resources, including setting the authorisation on folder, as well as file level. This works very well when working with a FSDB repository manager on the intranet server. The issue is that the authorisation settings are obviously not reflected on the extranet-portal, since we have not figured out a way of reusing the same repository manager on the other portal.
My question then is whether it is possible to create an FSDB repository manager on one of the portals and reuse it on the other. This would quite conveniently allows us to reuse authorisation settings across both portals.
Does anyone know whether this is possible at all?
If you need more info to answer this, do not hesitate to ask
Best regards,
Svein Gunnar Standnes

Hi Svein,
as I assume you know, if you use a CM Repository in FSDB mode folders and documents are stored in the file system, but metadata is stored in the database. Integrating a fileshare into two portals as a CM Repository in FSDB mode will lead to serious inconsistencies, as for example one document will have KM properties in one portal but no properties (or other) in the other, different version histories, and many more!
The only way to integrate in both portals a fileshare would be as a File System Repository Manager in <b>write-protect (read-only) mode</b>. If the repository is not read-only in such a scenario, concurrent updates to a file by different users on different installations can leave the content of the file in a corrupt state.
So to sum it up, in write mode I would definitely refrain from integrating the file share in two portals!
Hope this helps,
Robert

Similar Messages

How do you configure the DAM so it can be shared across multiple CQ instances?

How do you configure the DAM so it can be shared across multiple CQ instances?

You can use shared datastore http://dev.day.com/content/kb/home/Crx/CrxSystemAdministration/HowToCombineTheDatastoreToP reserveDiskSpace.html multiple CQ instance will use same file system to share asset
clustering http://dev.day.com/docs/en/crx/current/administering/cluster.html multiple node will share repository.
But you can not have something like one DAM and then have different CQ instance pointing to it (As not everything goes in to one location in file system)
Yogesh

Process Chains across multiple BW instances?

We're considering to implement a "CIF" (corporate information factory) approach for BW, using mutiple BW layers (staging, storage, analysis, across regions). It seems to make sense from a performance management perspective.
However one concern is the administration / monitoring.
Can standard BW tools (e.g. process chains, admin cockpit) customized to be used across multiple BW instances (plus ideally OLTP reporting, which we also have)? Or would we end up having to log in to each system individually? My gut / understanding tells me it is the latter one, but would appreciate any thoughts.
Thanks!

Hi Ingo,
Thanks for the information. I too have same scenario to work out.
Is there any possibility of automatic Source/server name conversion from system A to System B while copying all the Universes and Queries.
For Example: In BI we have an option to datasource server name change convention while transporting from one system to another system through out the landscape.
As you said in your reply, in life cycle manager, do we need to edit connection for each & every universe or any option for one and all universes.
Any documentation on this is appreciable...
Please provide me information.
Thanks in Advance.
Regards,
Ravi Kanth

Multiple Portal instances on the same machine

Hi Forum,
we have a requirement where in we are asked to implement multiple instances of Portal on the same machine. can you please give me some detials on Feasibility , issues and limitations of having multiple Portal instances on the same machine , different instances pointing to different tiers(Dev, Test, Production) etc
pointers will be highly appreciated..
regards,
uday

Hi Uday,
Please look at this.
Multiple Portal Instances - Virtual Hosting
Regards,
Siva
P.S: Award points if you find this useful.

Create multiple portal instances with only one database?

Can someone create multiple portal instances with only one database?
If so, how is this done, just by running the portal configuration wizard?
How are most people running with multiple developers working on portal? Do they share a portal instance, or create their own?
Thank you very much!
Phillip

i'm currently using 9ias rel 2(9.0.2) and i have install one infrastructure and two mid tier, hoping that this will create two portal, but it didn't. Can you please tell me how to do create two portal within one server.
thanks and regards;
andrew

Sharing portlets across multiple portal applications

Hello all,
I have a single enterprise application that consists of several portal web applications. Most of these portal web applications have common portlets within their codebase. Is it possible to share portlet code across multiple web applications?
Thanks

No, not possible, in the same way that sharing JSPs and Pageflows wouldn't be possible across multiple webapps. You can, however, have multiple portals within one Portal webapp, and then you could share portlets and portlet resources amongst those portals.
George

Multiple Portal Instances

We have two separate Portal Instances, Development and Production, which are also on separate servers. Can we utiize a SSO Server for both?

Please redirect your query to Product->Portal for faster and accurate response.
Thanks,
Mathew

Question about Multiple Portal Instances

WE HAVE iAS 1.0.2.2 ON W2000 SERVER AND
DB 8.1.7 ON ANOTHER W2000 SERVER.
WE HAVE A COUPLE OF PORTAL INSTANCES AND WE PLAN TO HAVE MORE IN THE FUTURE.
EACH PORTAL INSTANCE HAS ITS OWN LOGIN SERVER DAD.
EACH PORTAL INSTANCE REPRESENTS A DIFFERENT COMPANY.
WE ARE STILL IN DEVELOPMENT PHASE, TO ACCESS A PARTICULAR PORTAL INSTANCE WE USE
FOR EXAMPLE:
http://hostname/pls/DAD_INSTANCE1 http://hostname/pls/DAD_INSTANCE2
I WOULD LIKE TO KNOW WHAT IS THE BEST SOLUTION TO ACCESS EACH PORTAL INSTANCE LIKE
http://company1.com http://company2.com
I WILL APPRECIATE ANY ADVICE.
TKS!!
null

You can set up those names, company1.com and company2.com in internal DNS server, if you have one. Or, get an official domain name. Once you get them, you need to modify httpd.conf accordingly. What we do next is modify index.html so an request for company1.com is redirected to /pls/DAD, which is portal home, using onload() javascript function. Then, you can get to portal home by typing http://company1.com as url.

Multiple Portal Instances and Cookie Names

i have three portal instances (3.0.7) under the same database 8.1.7 on NT.
for example:
portal30 + portal30_sso
myportal + myportal_sso
testportal + testportal_sso
actually i cannot work on more than one portal at the same time. so, each time i want to work under a particular portal i make sure i am not logged in the other two.
if i assign a different COOKIE NAME in the
GATEWAY for each DAD it will fix my problem?
any suggestion?
tks!!

i will appreciate some answer to this posting.
tks!

Documentum Repository Manager not appearing

Hi,
I am currently trying to set up a Documentum Repository Manager. I downloaded the following components from Documentum:
1. DFC for Windows
2. iViews for Related Content - SAP EP
3. Repository Manager - SAP Portal
I have managed to deploy the components to my SAP EP (NetWeaver 20004s). I can see the documentum iViews listed in the Portal Content folder and the com.documentum.ei.eprm.manager.DCTMRepositoryManager component in the list of Repository Managers.
I created an instance of DCTMRepositoryManager by keying the neccessary configuration information. However, in KM Content, I am unable to see the configured prefix. I tried to look for the prefix in Runtime->RepositoryManagers, but to no avail.
Why would my Documentum Repository not appear? Is there any settings that I have missed? Has anyone managed to get this working in NetWeaver2004s? Any help would be appreciated.
Thank You.
Yours truly.
Message was edited by: Voon Siong Lum

Hi Venkat,
Most of the documentation and installation files for integrating the documentum iViews and the repository manager into the Portal can be found at Documentum's website. You can access the website from http://softwaresupport.emc.com/login/login.asp.
You will need to have an account and login to the site before you can download the relevant items though.
Best of luck to you in trying to integrate documentum.
Yours truly.

Clear template cache on multiple CF instances in a single action?

I'm running several instances of Coldfusion on the same box
with template caching turned 'on' for each instance. I have it set
up where one instance will replicate file changes to the other
instances, but with caching turned on, I currently have to log in
to each CF Admin instance and click the "Clear Template Cache Now"
button for the file changes to appear. As I add more instances,
this will become an increasingly tedious process.
Does anyone have or know of a way to clear template cache
across multiple CF instances in a single action?

cfJarrod wrote:
> I'm assuming that using clearTrustedCache() will only
clear the cache for a
> single CF instance and not all instances on the server.
Is that in fact true?
Yes.
> Ideally I'd like to run a single script that will clear
the cache for all
> instances.
The Admin API is an application programming interface: you
are supposed
to write your own scripts that call its methods.
Jochem
Jochem van Dieten
Adobe Community Expert for ColdFusion

How to reuse common code across multiple work repositories

Hi Experts,
I have a ruqirements from our customer side. we have a one master repository attached with three work repositories(wk1,wk2,2k3). Customer want to place some common code into wk1 workrepository and want to reuse across multiple workrepositories(wk2,wk3).
Generally we can reuse code in same work repositories like knowmodules and interfaces.
Is it possible to use across mutiple workrepositories?
Thanks in Advance
Siri

You can't hare the same instance of the code across multiple work repositories. You have to have a seperate instance in each work repository. However you can manage it as if it was shared through ODI's versioning capability i.e. all changes to the common code are only ever made in one work repository i.e. Wk1 and then deployed to the other 2 which is as simple as getting the latest version from the Master repository. You could even set up security in Wk2 and Wk3 to make sure that your developers/users do not have permission to edit the common code in those repositories.

Tag instances - same instance being used across multiple tags

Hi
          I am using BEA WebLogic Server 6.1 SP2
          Problem:
          Tag instances - same instance being used across multiple tags
          The problem is that when I use the same jsp tag several times in a page,
          The tag is being instantiated only one time, as a result the class
          attributes
          retain their values when activating the tags.
          Example:
          A code that demonstrates the problem (not sure that it is compiled)
          public FooTag extends TagSupport {
          private boolean isValid = true;
          private String name;
          public setName(String x){
          name = x;
          public int doStartTag() throws JspException
          if (name.equals("x"){
          isValid = false;
          return SKIP_BODY;
          public int doEndTag() {
          if (isValid){
          return EVAL_PAGE;
          <table>
          <tr>
          <td><mpower:FOOTAG name="x"/>
          
          A FOOTAG implmented in FooTag </td>
          </tr>
          <tr>
          <td><mpower:FOOTAG name="y"/>
          
          A FOOTAG implmented in FooTag </td>
          </tr>
          </table>
          P.S.
          I am using the same tags library with Tomcat and iPlanet Application severs,
          I did not get this problem there !!


          What should I do to reinitialize the tag? We have the same problem on custom tag.
          We have TabSet tag, which contains a set of Tab tag. In Weblogic 5.1, everything
          works ok, however when we run it in weblogic 6.1, Tab object seems like share the
          same instance, say if I have 2 Tabs in the TabSet, it ends up shows 2 same tabs with
          the apperance of the last tab added to the tabset on the web browser. We do implement
          release() method to call super.release() of TagSupport class.
          Any help is very appreciated.
          Thanks,
          Kimberly
          "Simon Spruzen" <[email protected]> wrote:
          >
          >This is allowed. You must implement public void release() on your tag, and
          >WLS will
          >call it before this method if WLS elects to reuse the tag instance. Your
          >release
          >method just reinitialises the tag as required.
          >
          >simon.
          >
          >"Eyal H" <[email protected]> wrote:
          >>Hi
          >>
          >>I am using BEA WebLogic Server 6.1 SP2
          >>
          >>Problem:
          >>
          >>Tag instances - same instance being used across multiple tags
          >>
          >>The problem is that when I use the same jsp tag several times in a page,
          >>
          >>The tag is being instantiated only one time, as a result the class
          >>
          >>attributes
          >>
          >>retain their values when activating the tags.
          >>
          >>Example:
          >>
          >>A code that demonstrates the problem (not sure that it is compiled)
          >>
          >>public FooTag extends TagSupport {
          >>
          >>private boolean isValid = true;
          >>
          >>private String name;
          >>
          >>public setName(String x){
          >>
          >>name = x;
          >>
          >>}
          >>
          >>public int doStartTag() throws JspException
          >>
          >>if (name.equals("x"){
          >>
          >>isValid = false;
          >>
          >>}
          >>
          >>return SKIP_BODY;
          >>
          >>}
          >>
          >>public int doEndTag() {
          >>
          >>if (isValid){
          >>
          >>......
          >>
          >>}
          >>
          >>return EVAL_PAGE;
          >>
          >>}
          >>
          >>}
          >>
          >>
          >>
          >>
          >>
          >><table>
          >>
          >><tr>
          >>
          >><td><mpower:FOOTAG name="x"/>
          >>
          >>
          >>
          >>A FOOTAG implmented in FooTag </td>
          >>
          >></tr>
          >>
          >><tr>
          >>
          >><td><mpower:FOOTAG name="y"/>
          >>
          >>
          >>
          >>A FOOTAG implmented in FooTag </td>
          >>
          >></tr>
          >>
          >></table>
          >>
          >>
          >>
          >>P.S.
          >>
          >>I am using the same tags library with Tomcat and iPlanet Application severs,
          >>
          >>I did not get this problem there !!
          >>
          >>
          >>
          >

Multiple portal server instances

Hello,
I have one solaris box with JES 2005Q4 installed. I need to set up portal application development environment for multiple developers. I'm thinking about having multiple portal server instances. Is this configuration possible? Should I create multiple directory server and access manager instances as well or is it possible use one with multiple configuration instances?

Installing multiple instances of portal is only possible if you are installing in a Solaris 10 Whole-Root Zone. Create a new zone for each developer and then install all of the necessary JES components in each zone. This includes Directory, Access Manager, Application Server, and Portal.

How to deploy across multiple mid-tier instances

I was hoping someone may be able to point me in the right direction. We have two portal/webcache mid-tier instances on release 10G AS 9.0.4.2. On the ias_admin home page I tried to create a cluster and add the two instances to a cluster but it won't let me do it for a portal type install. If that is the case, how do people handle deploying such things as portlet providers and data sources across multiple mid-tier instances? Here is the concern from our Portal admin:
As discussed, the inability to cluster the mid-tiers will cause issues in production as we try and keep deployed portlet providers with their required configurations and datasources in synch. While deploying and configuring 1-2 mid-tiers for a given portlet manually is do-able, the chance for out of synch components or configuration settings is amplified for each additional mid-tier. If we manually deploy 5 mid-tiers and accidently mistype the datasource for example, we'll have a random error that will occur once requests are attempted to be serviced by that mid-tier. This will make troubleshooting difficult. We really need some way to deploy and configure settings one time and have these items propagated to all the other mid-tiers.
What is the best way to handle this scenario?
Regards and thanks for any info,
Chris Schumacher
Embry-Riddle Aeronautical University

Jar files are not stored on the file system
Temporary files are held in bpel/domain/default/tmp folder, whereas jar files in the dehydration store for clustered deployment.
If you configure BPEL (not AS) cluster - files will be propagated to all nodes.
MJ

Reusing a repository manager across multiple portal instances

Similar Messages

Maybe you are looking for