Collaboration deployment unsuccessful

Hi,
I am unsuccessful at installing Collaboration 4.2 on Interaction. The platform is .NET on Windows Server 2003.
I get the following error inside any portlet after adding a Collaboration portlet to any page:
Collaboration encountered an error.
java.lang.NoClassDefFoundError
     at com.plumtree.collaboration.context.CollaborationContextFactory.createCollaborationContext(CollaborationContextFactory.java:68)     at com.plumtree.collaboration.webui.framework.action.CollaborationController.service(CollaborationController.java:64)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
     [etc]
Some context:
* my Collaboration database and tables are owned by the Collaboration user
* my Interaction database and tables are owned by the dbo user that created the database. I changed ownership to the Interaction user without success
* ptverify.bat runs fine
* ptconfig.exe is able to connect to the database
* I have the following line in the database.xml configuration file of Collaboration: <linked-database-alias>alidb.dbo.</linked-database-alias>. I also tried <linked-database-alias>alidb.alidbuser.</linked-database-alias>
* I installed both Interaction and Collaboration following the deployment instructions line by line. In particular I ran scripts on each db with the correct user.
I have spent hours on this. Surprisingly no one else on the web seems to encounter that same issue although I followed the deployment guide line by line.
Any suggestions greatly appreciated!
Greg

Did you ever find a resolution to this?
We have (during testing) run a good few dozen of these instances up and have from time to time come across this same error, we never resolved it but it 'disappeared' and hasn't come back, but if there is a known cause/solution to this I'd love to add it to my notes.
Cheers,
Mik.

Similar Messages

  • Cisco Prime Collaboration Deployment with BE7K and VMWare license

    Hello, I am looking for some help trying to figure out if Cisco Prime Collaboration Deployment can be used to upgrade our existing 7.1.5 cluster.  From what I have read there is a API problem with the VMWare license that comes with the BE7K.  But after reviewing the BOM/quote from my VAR it lists the foundation license which based of the release notes is supported.
    UCSS-U-VMW-FND-5-1
    UCSS Cisco UC Virt. Foundation  Five Year - 1 server
    Has anybody out there had expericne with PCD and BE7K'?
    This is from release notes of PCD
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/10_5_1/CUCM_BK_P139675A_00_pcd-rns-1051/CUCM_BK_P139675A_00_pcd-rns-1051_chapter_010.html
    Search for “Business Edition 7000” and it will state it is not supported with PCD.  It is because the licenses that the BE 6k and 7K are shipped with don’t enable certain VMware APIs that PCD needs.
    “Virtualization Software License Compatibility
    Cisco Prime Collaboration Deployment is not compatible with all license types of VMware vSphere ESXi, as some licenses do not enable required VMware APIs.
    The following are compatible with Cisco Prime Collaboration Deployment:
    Cisco UC Virtualization Foundation (appears as "Foundation Edition" in vSphere Client)
    VMware vSphere Standard Edition, Enterprise Edition, or Enterprise Plus Edition
    Evaluation mode license
    The following are not compatible with Cisco Prime Collaboration Deployment:
    Cisco UC Virtualization Hypervisor (appears as "Hypervisor Edition" in vSphere Client)-preloaded on Cisco Business Edition 6000 and Business Edition 7000
    VMware vSphere Hypervisor Edition
    Any help would be appreacted.
    JP

    Thanks Jamie for repsonding, we haven't made any purchase's yet but I wanted to ensure we are purchasing a solution that won't lead to a lot of frustration.  We only have 1000 phones so we are pretty small and the BE7K seems to be a good fit and value.
    Cheers,

  • Error to do upgrade with Prime Collaboration Deployment

    Hi all,
    We need do a upgrade from CUCM 8.0 to 10.0
    We are migratin with the Prime Collaboration Deployment, but when we add the Esxi host, an error appear.
    "Failed to mount Cisco Prime Collaboration Deployments export as NFS store to the ESXi Host"
    The UCS is a UCS 240.
    We can discover the cluster old, but don´t cant add the Esxi host.
    We deploy the new VM for the new CUCM 10.0
    Please, I need your help.
    Thanks
    Guillermo

    Most likely you don't have the right ESXi license for this, you need at least FND for PCD
    Page 11
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/ucmap/10_0_1/CUCM_BK_U9C58CB1_00_ucmap-administration-guide.pdf
    If you don't meet the ESXi license requirements, nothing to do here, either buy the necessary license, or don't use PCD.

  • Where do I download Prime Collaboration Deployment?

    Where do I download Prime Collaboration Deployment from?

    [+5] to Manish/Jaime.
    You would get PCD either through PUT [if going for upgrade/migration] or if placing a fresh order.
    In both cases, it would be e-deliveryAccess order from where u need to download PCD.
    name of downloaded file would be pcd_vApp_UCOS_10.5.2.10000-5_vmv7_v1.2.ova
    Please find attached snapshot.
    regds,
    aman

  • Access to Prime Collaboration Deployment 10.5 software/OVA?

    Cisco Forum:
    How might a person obtain a copy of Cisco's Prime Collaboration Deployment software/OVA?
    Downloading Cisco software lists lots of Prime Collaboration 10.5 offerings but not the Deployment option.  Cisco's PUT Tool offers Prime Collaboration Standard 10.X but is failing with an internal error before I can even determine what might be contained with it. 
    How might Cisco's PCD software/OVA be obtained?
    Thank you.
    Dan

    for OVA
    Cisco only supports virtualized deployments of Cisco Prime Collaboration Deployment. PCD is deployed using an OVA that contains the pre-installed PCD application. This OVA is obtained with a licensed copy of Cisco Unified Communications Manager Release 10.5(1) software. For information about how to extract and deploy the PCD_VAPP.OVA file,
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/PCD/CUCM_BK_PB8976C2_00_pcd_rns_1001/CUCM_BK_PB8976C2_00_pcd_rns_1001_chapter_01.html
    for extracting OVA
    Step 1  
    Extract the PCD_VAPP.OVA from the pcd_vApp_UCOS_10.xxxxx.iso file. A new PCD_VAPP.OVA file is created. Verify the file size; ISO and OVA files do not have the same file size.
    Step 2  
    Deploy the PCD_VAPP.OVA file in vCenter to install Cisco Prime Collaboration Deployment. If you are using vSphere client, the name of this file may be PCD_VAPP.OVA. If you are using the VMware vSphere web client to deploy the file, you must first change the name to PCD_VAPP.ova (lowercase) before deploying the file.
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/pcdadmin/10_5_1/CUCM_BK_U35347D2_00_pcd-administration-guide-1051/CUCM_BK_U35347D2_00_ucmap-administration-guide-1051_chapter_01.html#CUCM_TK_E008CD66_00

  • Deployment unsuccessful via UNIX box but Successful from windows

    Hi,
    I am able to deploy my ADF application on remote server by my ANT SCRIPT.
    But when I am trying to deploy my application through UNIX box, Its successfully making EAR File but that EAR file is smaller(in term of size) , which I am getting from Windows deployment from similar script. It not adding bc4j.xcfg file of AM and adfm.xml file also in EAR. If I am deploying this same EAR file from script on unix then its successfully deploying and when I am going to my application its showing blank page insist of contains.
    I am using same script for deployment on unix box also which I am using on Windows.
    Can anyone suggest me where I am lacking or something which I need to take care on Unix.
    Thanks in Advance
    Ramit Mathur

    Looks like your ant script is buggy...
    If your ant script does not produce the same EAR (I only mean the content, not the size) there must be something wrong either with your installation on the UNIX box or your ant script.
    If you know which files are missing thats the point to look at. As you wrote the script it should not be difficult to find the part of hte script which should copy the missing files into the resulting EAR file. May be you have a wrong path (windows like drive letters or '\' instead of '/') in your script.
    Timo

  • Cisco Prime Collaboration Deployment - Not able to mount NFS

    Hi everybody,
    We are trying to add an ESXi server to the PCD, but we are unable to succeed due to an error while mounting the NFS unit.
    We get the following message:
    "Failed to mount Cisco Prime Collaboration Deployments export as NFS store to the ESXi Host"
    In the PCD we obtain the followings logs I attach the file.
    We are using a VMware vSphere Enterprise Edition
    The ESXi, has the VMkernel port map to a different subnet that the management subnet.
    VMkernel: 10.11.202.75
    VMmanagement: 10.11.200.75
    To Add the ESXi host we are attacking the 10.11.200.75. Someone knows if the VMkernel must be in the same subnet for the NFS to mount?
    2014-11-07 14:17:26,711 WARN  [pool-1-thread-18] validation.ESXiValidation.isDSinESXiHost - Datastore PCD_NFS is NOT connected to ESXi Host 10.11.200.75
    2014-11-07 14:17:57,585 ERROR [pool-1-thread-18] custom.PreESXiHostCreate.call - failed to mount ucmap nfs 
    Thanks in advance.

    Hi everybody,
    Finally it turns it was a problem with the ASA. We apply a predefined rule in the ASA to allow NFS. We discover that the rule was not correctly defined, after creating a specific rule everything work just fine.

  • Need help: JCA deployment unsuccessful using dcmctl

    I am using the command line tool dcmctl with the deployApplication option to deploy a standalone JCA resource adapter. I am having some problems with lookup of this JCA from EJB.
    I execute the command:
    dcmctl deployApplication –f my_jca.rar –a my_jca
    The output I get:
    Application: my_jca
    Component Name: home
    Component Type: OC4J
    Instance: myinstance.mycompany.com
    At the end of it, I see the logfiles and it seems like the jca deployment went thru ok. But, when I use my ejb, I keep getting the message that my_jca not found (com.evermind.server.rmi.OrionRemoteException).
    Under what JNDI tree is this jndi name my_jca to be found? How do we lookup for this? How do I know what went wrong in my lookup. The same jca works well with all other appservers.
    Here is the ra.xml I have. DO I need to provide a vendor specific descriptor? OC4J deploys one automatically so I didn't supply one:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE connector PUBLIC "-//Sun Microsystems, Inc.//DTD Connector 1.0//EN" "http://java.sun.com/dtd/connector_1_0.dtd">
       <connector id="Connector_ID">
          <display-name>my_jca</display-name>
          <description>My JCA</description>
          <vendor-name>my company</vendor-name>
          <spec-version>1.0</spec-version>
          <eis-type>DCOM Applications</eis-type>
          <version>1.0</version>
          <license>
             <license-required>false</license-required>
          </license>
          <resourceadapter id="J2CResourceAdapter_ID">
             <managedconnectionfactory-class>com.intrinsyc.jca.JintManagedConnectionFactory</managedconnectionfactory-class>
             <connectionfactory-interface>com.intrinsyc.jca.ConnectionFactory</connectionfactory-interface>
             <connectionfactory-impl-class>com.intrinsyc.jca.JintConnectionFactory</connectionfactory-impl-class>
             <connection-interface>com.intrinsyc.jca.Connection</connection-interface>
             <connection-impl-class>com.intrinsyc.jca.JintConnection</connection-impl-class>
             <transaction-support>NoTransaction</transaction-support>
             <authentication-mechanism id="AuthenticationMechanism_1067225162993">
                <authentication-mechanism-type>BasicPassword</authentication-mechanism-type>
                <credential-interface>javax.resource.spi.security.PasswordCredential</credential-interface>
             </authentication-mechanism>
             <reauthentication-support>false</reauthentication-support>
             <security-permission id="SecurityPermission_1067117771153">
                <description>testing with all</description>
                <security-permission-spec>grant { permission java.security.AllPermission; };</security-permission-spec>
             </security-permission>
          </resourceadapter>
       </connector>

    I am using the command line tool dcmctl with the deployApplication option to deploy a standalone JCA resource adapter. I am having some problems with lookup of this JCA from EJB.
    I execute the command:
    dcmctl deployApplication –f my_jca.rar –a my_jca
    The output I get:
    Application: my_jca
    Component Name: home
    Component Type: OC4J
    Instance: myinstance.mycompany.com
    At the end of it, I see the logfiles and it seems like the jca deployment went thru ok. But, when I use my ejb, I keep getting the message that my_jca not found (com.evermind.server.rmi.OrionRemoteException).
    Under what JNDI tree is this jndi name my_jca to be found? How do we lookup for this? How do I know what went wrong in my lookup. The same jca works well with all other appservers.
    Here is the ra.xml I have. DO I need to provide a vendor specific descriptor? OC4J deploys one automatically so I didn't supply one:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE connector PUBLIC "-//Sun Microsystems, Inc.//DTD Connector 1.0//EN" "http://java.sun.com/dtd/connector_1_0.dtd">
       <connector id="Connector_ID">
          <display-name>my_jca</display-name>
          <description>My JCA</description>
          <vendor-name>my company</vendor-name>
          <spec-version>1.0</spec-version>
          <eis-type>DCOM Applications</eis-type>
          <version>1.0</version>
          <license>
             <license-required>false</license-required>
          </license>
          <resourceadapter id="J2CResourceAdapter_ID">
             <managedconnectionfactory-class>com.intrinsyc.jca.JintManagedConnectionFactory</managedconnectionfactory-class>
             <connectionfactory-interface>com.intrinsyc.jca.ConnectionFactory</connectionfactory-interface>
             <connectionfactory-impl-class>com.intrinsyc.jca.JintConnectionFactory</connectionfactory-impl-class>
             <connection-interface>com.intrinsyc.jca.Connection</connection-interface>
             <connection-impl-class>com.intrinsyc.jca.JintConnection</connection-impl-class>
             <transaction-support>NoTransaction</transaction-support>
             <authentication-mechanism id="AuthenticationMechanism_1067225162993">
                <authentication-mechanism-type>BasicPassword</authentication-mechanism-type>
                <credential-interface>javax.resource.spi.security.PasswordCredential</credential-interface>
             </authentication-mechanism>
             <reauthentication-support>false</reauthentication-support>
             <security-permission id="SecurityPermission_1067117771153">
                <description>testing with all</description>
                <security-permission-spec>grant { permission java.security.AllPermission; };</security-permission-spec>
             </security-permission>
          </resourceadapter>
       </connector>

  • Prime Collaboration Deployment 10.6 Migrating CM8.x to an existing CUCM 10.5 cluster?

    Quick and easy one hopefully:
    Can PCD assist with migrating CUCM 8.6 to an existing live CUCM 10.5 ? Suspect not but fingers crossed :)
    Rich

    Only upgrade files are available under downloads at cisco.com, fresh install ISO only comes with the 10.x media kit you need to order via PUT

  • CUCM Cluster "Partition Unalligned" Issue Resolution by PCD (Prime Collaboration Deployment)

    Dear all,
    I will test soon (asap i got bootable 9.1.2 software) to solve "partition unalligned" issue with CUCM Cluster version 9.1.2.11900-12.
    In my opinion, we can solve this issue with PCD as migrate unalligned cluster to a new cluster with same version.
    Do anybody test it before?
    What is your opinions?
    Best Regards,
    Mesut 

    Hi Aman,
    As i found out, correct answer should be "migration to 9.x unsupported by CPD" for CUCM version 9.X.
    But just imagine, you have 8 servers in a cluster at version 10.X with Partition Unalligned issue. Is PCD not a good alternative to DRS to solve this issue while migrating to a new cluster with PCD?
    Best Regards,
    Mesut 

  • Ask the Expert: Architecting your Collaboration Solution with Social and Video

    With Gebran Chahrouri
    Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about ways that Enterprise Social and Video are woven into traditional Voice solutions and Architectures  with Cisco expert Gebran Chahrouri. Extend your Cisco collaboration architecture to reach into Cloud and/or on premise Cisco WebEx Social and TelePresence offerings. Gebran will be answering any questions about architecting a current solution or devising a roadmap to take your collaboration deployment to the next level.
    Gebran Chahrouri is a principal engineer and architect for the WebEx Social product with a focus on scalability. Since joining Cisco in 1998 he has held engineering leadership and software management positions on products including Customer Contact, Cisco IPICS, and the Cisco TelePresence Exchange service. Chahrouri has nearly 30 years of experience in architecting, managing, and developing software products at Cisco, ROLM, IBM, Siemens, and Aspect. He holds a master's degree in electrical and computer engineering from the University of Michigan and has over 20 patents filed by the U.S. Patent Office.
    Remember to use the rating system to let Gebran  know if you have received an adequate response. 
    Gebran might not be able to answer each question due to the volume expected during this event. Remember that you can continue the conversation on the Collaboration, Voice and Video sub-community discussion forum shortly after the event.This event lasts through February 22, 2013. Visit this forum often to view responses to your questions and the questions of other community members.

    Hi Jason,
    Thanks for your question.
    WebEx Social combines the power of social networking, content creation, and real-time communications. Employees can quickly connect with people, communities and information they need to get work done.
    The product tour video (http://www.cisco.com/en/US/prod/collateral/ps10680/vds_cQuad_prodTour.html) featured at http://www.cisco.com/web/products/quad/index.html gives a really good overview of the product.
    If you prefer a document to read I recommend http://www.cisco.com/en/US/prod/collateral/voicesw/ps6788/vcallcon/ps556/case_study_c36-706800_ps10668_Products_Case_Study.html
    I would be happy to answer any further questions.
    - Gebran

  • Deploy EAR failure,Who can help me to deploy?

    Dear all:
              I'm running two cluster set-ups in the WLS6.1 , follow introduction my
              test condition:
              Two members on NT server and an Admin server, they reside all different
              Machine.
              I test it before package EAR , jsp and servlet call SessionBean to work
              very well,but
              I package a test EAR file , it includes a Stateful Session Bean and war
              file(only one Servlet and three JSPs)
              When I deployed EAR file, Server show a error message to below:
              > > <Error> <Management> <Error initializing module Login.war of
              application ClusterAdmin:Name=gfortuneNet,
              > > Type=Application from path
              .\config\ClusterAdmin\applications\gfortuneNet.ear: Login.war does not
              exist.>
              > > <Notice> <Management> <Application Poller not started for production
              server.>
              I check out the Administrator Console , I find "Login.war" to deploy
              unsuccessful , Following is my test code and configuration:
              ***Servlet***
              public class loginServlet extends HttpServlet implements
              java.io.Serializable {
              private static final String CONTENT_TYPE = "text/html; charset=BIG5";
              public void doPost(HttpServletRequest request, HttpServletResponse
              response) throws ServletException, IOException {
              response.setContentType(CONTENT_TYPE);
              PrintWriter out = response.getWriter();
              doGet(request,response);
              public void doGet(HttpServletRequest request, HttpServletResponse
              response) throws ServletException, IOException {
              response.setContentType(CONTENT_TYPE);
              PrintWriter out = response.getWriter();
              HttpSession session = request.getSession(false);
              try{
              Context ctx = getInitialContext();
              LoginQueryHome home = (LoginQueryHome) ctx.lookup("LoginQuery");
              LoginQuery the_ejb = home.create();
              } catch (NamingException e)
              {  e.printStackTrace();   }
              catch (RemoteException e)
              { e.printStackTrace(); }
              catch (CreateException e)
              { e.printStackTrace();}
              public static Context getInitialContext()throws NamingException
              Properties p = new Properties();
              p.put(Context.INITIAL_CONTEXT_FACTORY,
              "weblogic.jndi.WLInitialContextFactory");
              p.put(Context.PROVIDER_URL, "t3://10.168.168.32:9001"); //
              cluster1 server
              return new InitialContext(p);
              **web.xml :**
              <?xml version="1.0" ?>
              <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web
              Application 1.2//EN"
              "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd>
              <web-app>
              <servlet>
              <servlet-name>loginServlet</servlet-name>
              <servlet-class>com.servlet.loginServlet</servlet-class>
              </servlet>
              <servlet-mapping>
              <servlet-name>loginServlet</servlet-name>
              <url-pattern>/loginServlet</url-pattern>
              </servlet-mapping>
              </web-app>
              **weblogic.xml :**
              <!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web
              Application 6.0//EN"
              "http://www.bea.com/servers/wls600/dtd/weblogic-web-jar.dtd>
              <weblogic-web-app>
              <description>WebLogic Descriptor</description>
              <session-descriptor>
              <session-param>
              <param-name>
              PersistentStoreType
              </param-name>
              <param-value>
              replicated
              </param-value>
              </session-param>
              </session-descriptor>
              </weblogic-web-app>
              **application.xml:**
              <?xml version="1.0" encoding="ISO8859_1"?>
              <!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EE
              Application 1.2//EN'
              'http://java.sun.com/j2ee/dtds/application_1_2.dtd'>
              <application>
              <display-name>login</display-name>
              <description>Application description</description>
              <module>
              <ejb>Test_BookBean.jar</ejb> // This is
              Stateful Session Bean
              </module>
              <module>
              <web>
              <web-uri>Login.war</web-uri>
              <context-root>clicklit</context-root>
              </web>
              </module>
              </application>
              ***weblogic-ejb-jar.xml***
              <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD
              WebLogic 6.0.0 EJB//EN'
              'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
              <weblogic-ejb-jar>
              <weblogic-enterprise-bean>
              <ejb-name>LoginQueryBean</ejb-name>
              <stateful-session-descriptor>
              <stateful-session-clustering>
              <home-load-algorithm>RoundRobin</home-load-algorithm>
              <replication-type>InMemory</replication-type>
              </stateful-session-clustering>
              </stateful-session-descriptor>
              <reference-descriptor>
              <resource-description>
              <res-ref-name>jdbc/CORDataSource</res-ref-name>
              <jndi-name>GalaxyDataSource</jndi-name>
              </resource-description>
              </reference-descriptor>
              <jndi-name>LoginQuery</jndi-name>
              </weblogic-enterprise-bean>
              </weblogic-ejb-jar>
              Please every bea consultants tell me what's lost to build up ?
              Best Regards,
              James Huang
              

    I'm not really a servlet expert, but it appears that you've enabled
              in-memory replication for the Login servlet, but your WLS is not
              clustered.
              -- Rob
              james wrote:
              >
              > Hi! Rob Woollen:
              > First thanks for your responsion , I forget Configure the
              > HttpClusterServlet .
              > but I configure the HttpClusterServlet to web.xml lately, and only deploy
              > Login.war to WLS6.1 , finding the other error message,Can you tell me,
              > what's wrong for me?
              >
              > > > **web.xml
              > file************************************************************************
              > **
              > <?xml version="1.0" ?>
              > <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application
              > 1.2//EN" "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
              > <web-app>
              > <servlet>
              > <servlet-name>loginServlet</servlet-name>
              > <servlet-class>com.servlet.loginServlet</servlet-class>
              > </servlet>
              > <servlet>
              > <servlet-name>HttpClusterServlet</servlet-name>
              >
              > <servlet-class>weblogic.servlet.internal.HttpClusterServlet</servlet-class>
              > <init-param>
              > <param-name>defaultServers</param-name>
              >
              > <param-value>10.168.168.32:9001:9002|10.168.168.200:9001:9002|10.168.168.154
              > :9001:9002</param-value>
              > </init-param>
              > <init-param>
              > <param-name>DebugConfigInfo</param-name>
              > <param-value>OFF</param-value>
              > </init-param>
              > </servlet>
              > <servlet-mapping>
              > <servlet-name>loginServlet</servlet-name>
              > <url-pattern>/loginServlet</url-pattern>
              > </servlet-mapping>
              > <servlet-mapping>
              > <servlet-name>HttpClusterServlet</servlet-name>
              > <url-pattern>/</url-pattern>
              > </servlet-mapping>
              > <servlet-mapping>
              > <servlet-name>HttpClusterServlet</servlet-name>
              > <url-pattern>*.jsp</url-pattern>
              > </servlet-mapping>
              > <servlet-mapping>
              > <servlet-name>HttpClusterServlet</servlet-name>
              > <url-pattern>*.htm</url-pattern>
              > </servlet-mapping>
              > <servlet-mapping>
              > <servlet-name>HttpClusterServlet</servlet-name>
              > <url-pattern>*.html</url-pattern>
              > </servlet-mapping>
              > </web-app>
              >
              > > > **Error
              > message*********************************************************************
              > *****
              > <2001/9/10 ??11?35?52?> <Error> <HTTP Session> <FATAL: replicated HTTP sess
              > ions specified but clustering not enabled for webapp: /Login>
              > javax.management.MBeanException
              > at
              > weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl
              > .java:960)
              > at
              > weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl
              > .java:913)
              > at
              > weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:898)
              > at
              > weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
              > .java:618)
              > at
              > weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
              > 90)
              > at
              > weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              > nImpl.java:350)
              > at
              > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
              > at
              > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
              > at
              > weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
              > at
              > weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
              > at $Proxy69.addTarget(Unknown Source)
              > at
              > weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationM
              > anager.java:833)
              > at
              > weblogic.management.mbeans.custom.ApplicationManager.addApplication(Applicat
              > ionManager.java:930)
              > at
              > weblogic.management.mbeans.custom.ApplicationManager.addApplication(Applicat
              > ionManager.java:852)
              > at
              > weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager
              > .java:768)
              > at
              > weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager
              > .java:701)
              > at
              > weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManag
              > er.java:198)
              > at java.lang.reflect.Method.invoke(Native Method)
              > at
              > weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
              > .java:606)
              > at
              > weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
              > 90)
              > at
              > weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              > nImpl.java:350)
              > at
              > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
              > at
              > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
              > at
              > weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
              > at
              > weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
              > at $Proxy5.update(Unknown Source)
              > at
              > weblogic.management.console.webapp._domain.__upload_app._jspService(__upload
              > _app.java:150)
              > at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
              > at
              > weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              > :263)
              > at
              > weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              > :200)
              > at
              > weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
              > l.java:190)
              > at
              > weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
              > at
              > weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java
              > :35)
              > at
              > weblogic.management.console.actions.internal.ActionServlet.doAction(ActionSe
              > rvlet.java:172)
              > at
              > weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServ
              > let.java:85)
              > at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
              > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
              > at
              > weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              > :263)
              > at
              > weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              > :200)
              > at
              > weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
              > ntext.java:2390)
              > at
              > weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
              > :1959)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > <2001/9/10 ??11?35?52?> <Error> <Management> <Error deploying application
              > .\config\ClusterAdmin\applications\Login.war :
              > java.lang.reflect.UndeclaredThrowableException>
              >
              > > > Best Regards,
              > > >
              > > > James Huang 09/10/2001
              >
              > "Rob Woollen" <[email protected]> ?????
              > news:[email protected]...
              > > It looks like the server is complaining about the Login.war file not
              > > existing (or in the specified place) in the ear file.
              > >
              > > -- Rob
              > >
              > > james wrote:
              > > >
              > > > Dear all:
              > > > I'm running two cluster set-ups in the WLS6.1 , follow
              > introduction my
              > > > test condition:
              > > > Two members on NT server and an Admin server, they reside all different
              > > > Machine.
              > > > I test it before package EAR , jsp and servlet call SessionBean to work
              > > > very well,but
              > > > I package a test EAR file , it includes a Stateful Session Bean and war
              > > > file(only one Servlet and three JSPs)
              > > > When I deployed EAR file, Server show a error message to below:
              > > >
              > ****************************************************************************
              > > > *******************
              > > > > > <Error> <Management> <Error initializing module Login.war of
              > > > application ClusterAdmin:Name=gfortuneNet,
              > > > > > Type=Application from path
              > > > .\config\ClusterAdmin\applications\gfortuneNet.ear: Login.war does not
              > > > exist.>
              > > > > > <Notice> <Management> <Application Poller not started for
              > production
              > > > server.>
              > > >
              > ****************************************************************************
              > > > *******************
              > > > I check out the Administrator Console , I find "Login.war" to deploy
              > > > unsuccessful , Following is my test code and configuration:
              > > >
              > > > ***Servlet***
              > > > public class loginServlet extends HttpServlet implements
              > > > java.io.Serializable {
              > > > private static final String CONTENT_TYPE = "text/html;
              > charset=BIG5";
              > > > public void doPost(HttpServletRequest request, HttpServletResponse
              > > > response) throws ServletException, IOException {
              > > > response.setContentType(CONTENT_TYPE);
              > > > PrintWriter out = response.getWriter();
              > > > doGet(request,response);
              > > > }
              > > > public void doGet(HttpServletRequest request, HttpServletResponse
              > > > response) throws ServletException, IOException {
              > > > response.setContentType(CONTENT_TYPE);
              > > > PrintWriter out = response.getWriter();
              > > > HttpSession session = request.getSession(false);
              > > > . . . . . . . . . . . . . .
              > > > . . . . . . . . . . . . . .
              > > > try{
              > > > Context ctx = getInitialContext();
              > > > LoginQueryHome home = (LoginQueryHome) ctx.lookup("LoginQuery");
              > > > LoginQuery the_ejb = home.create();
              > > > . . . . . . . . . . . . . .
              > > > . . . . . . . . . . . . . .
              > > > } catch (NamingException e)
              > > > {  e.printStackTrace();   }
              > > > catch (RemoteException e)
              > > > { e.printStackTrace(); }
              > > > catch (CreateException e)
              > > > { e.printStackTrace();}
              > > > }
              > > > public static Context getInitialContext()throws NamingException
              > > > {
              > > > Properties p = new Properties();
              > > > p.put(Context.INITIAL_CONTEXT_FACTORY,
              > > > "weblogic.jndi.WLInitialContextFactory");
              > > > p.put(Context.PROVIDER_URL, "t3://10.168.168.32:9001");
              > //
              > > > cluster1 server
              > > > return new InitialContext(p);
              > > > }
              > > > }
              > > >
              > ****************************************************************************
              > > > ********
              > > > **web.xml :**
              > > > <?xml version="1.0" ?>
              > > > <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web
              > > > Application 1.2//EN"
              > > > "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd>
              > > > <web-app>
              > > > <servlet>
              > > > <servlet-name>loginServlet</servlet-name>
              > > >
              > <servlet-class>com.servlet.loginServlet</servlet-class>
              > > > </servlet>
              > > > <servlet-mapping>
              > > > <servlet-name>loginServlet</servlet-name>
              > > > <url-pattern>/loginServlet</url-pattern>
              > > > </servlet-mapping>
              > > > </web-app>
              > > >
              > > > **weblogic.xml :**
              > > > <!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web
              > > > Application 6.0//EN"
              > > > "http://www.bea.com/servers/wls600/dtd/weblogic-web-jar.dtd>
              > > > <weblogic-web-app>
              > > > <description>WebLogic Descriptor</description>
              > > > <session-descriptor>
              > > > <session-param>
              > > > <param-name>
              > > > PersistentStoreType
              > > > </param-name>
              > > > <param-value>
              > > > replicated
              > > > </param-value>
              > > > </session-param>
              > > > </session-descriptor>
              > > > </weblogic-web-app>
              > > >
              > ****************************************************************************
              > > > ********
              > > > **application.xml:**
              > > > <?xml version="1.0" encoding="ISO8859_1"?>
              > > > <!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD
              > J2EE
              > > > Application 1.2//EN'
              > > > 'http://java.sun.com/j2ee/dtds/application_1_2.dtd'>
              > > > <application>
              > > > <display-name>login</display-name>
              > > > <description>Application description</description>
              > > > <module>
              > > > <ejb>Test_BookBean.jar</ejb> // This is
              > > > Stateful Session Bean
              > > > </module>
              > > > <module>
              > > > <web>
              > > > <web-uri>Login.war</web-uri>
              > > > <context-root>clicklit</context-root>
              > > > </web>
              > > > </module>
              > > > </application>
              > > >
              > ****************************************************************************
              > > > ********
              > > > ***weblogic-ejb-jar.xml***
              > > > <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD
              > > > WebLogic 6.0.0 EJB//EN'
              > > >
              > 'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
              > > > <weblogic-ejb-jar>
              > > > <weblogic-enterprise-bean>
              > > > <ejb-name>LoginQueryBean</ejb-name>
              > > > <stateful-session-descriptor>
              > > > <stateful-session-clustering>
              > > >
              > <home-load-algorithm>RoundRobin</home-load-algorithm>
              > > > <replication-type>InMemory</replication-type>
              > > > </stateful-session-clustering>
              > > > </stateful-session-descriptor>
              > > > <reference-descriptor>
              > > > <resource-description>
              > > > <res-ref-name>jdbc/CORDataSource</res-ref-name>
              > > > <jndi-name>GalaxyDataSource</jndi-name>
              > > > </resource-description>
              > > > </reference-descriptor>
              > > > <jndi-name>LoginQuery</jndi-name>
              > > > </weblogic-enterprise-bean>
              > > > </weblogic-ejb-jar>
              > > >
              > > > Please every bea consultants tell me what's lost to build up ?
              > > >
              > > > Best Regards,
              > > >
              > > > James Huang
              > >
              > > --
              > >
              > > ----------------------------------------------------------------------
              > >
              > > AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server
              > >
              > > by Michael Girdley, Rob Woollen, and Sandra Emerson
              > >
              > > http://learnWebLogic.com
              AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server
              by Michael Girdley, Rob Woollen, and Sandra Emerson
              http://learnWebLogic.com
              

  • Cisco Prime Collaboration Deplyment

    Hi All,
    Can any one point me to the location to download the ova file to install the prime collaboration deployment 10.0.
    Thanks
    patcbr600

    Sorry for all of the edits, but I'm trying to correct my error.
    Ok, so this document gives the name of the OVA:
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/ucmap/10_0_1/CUCM_BK_U9C58CB1_00_ucmap-administration-guide/CUCM_BK_U9C58CB1_00_ucmap-administration-guide_chapter_01.html#CUCM_TK_I20C0932_00
    And the download page does not have it listed:
    http://software.cisco.com/download/release.html?mdfid=285031516&release=10.0&relind=AVAILABLE&catid=268439477&softwareid=284522598&rellifecycle=&reltype=latest
    Sorry, but I've got nothing.  I'll see myself out.

  • Two TCS Server Deployment- Without clustering License

    Dear Team,
    I have a TP Collaboration deployment with VCS/TMS/TCS for Different types of Endpoints.
    We have two Content Servers for recording, but the cluster license is not ordered. Do we have any other deployment options without clustering(since cluster license is missing) for two TCS servers?
    Appreciate your comments.
    Thanks ,
    Riyas

    Just run them as two stand-alone servers. We've been running three stand-alone TCS servers for years, works fine. See the admin guide relevant for the version you are running http://www.cisco.com/c/en/us/support/conferencing/telepresence-content-server/products-maintenance-guides-list.html and configure each accordingly.
    /jens
    Please rate replies and mark question(s) as "answered" if applicable.

  • Upgrade Call Manager from 8.6.2 to 10.5

    Hello All,
    We are planning to upgrade a Cisco Call Manager Publisher node from 8.6.2 to 10.5. We want to install a new publisher on a new environment, but we are struggling with some questions.
    If we install the Pub node 10.5 can we migrate the configuration from the 8.6.2 to 10.5? Do we need a special tool for this?
    If above doesn't work, we can still migrate the existing call manager towards the new servers and start the upgrade, the only problem we face there is that we have to change the publisher's IP because we want to use a new ip addressing scheme.
    Kr,
    Yannick Vranckx

    Your best bet is to use the new tool: cisco prime collaboration deployment. This fits perfectly into what you want to do here and can easily help you with all aspect of the migration including the ip address change. You can learn how to use the tool here..
    https://www.youtube.com/watch?v=JzG4kz1_hL4

Maybe you are looking for