Installation of WCS v5.1.64.0

Has anyone installed WCS v5.1.64.0 on Ubuntu v8.04 Server?
Thanks in advance

Do you have change to install WCS with Ubuntu?

Similar Messages

  • Multible installations of WCS detected - when trying to upgrade WCS

    Does anyone have an idea of how to work around this problem ?
    When i try to upgrade a WCS (from 7.0.172 to 7.0.230) it tells me that i cannot upgrade because it has detected multible installations of WCS.
    When i search through "add / remove programs" and "program files" there are no other installations.
    How does the WCS installations detect other installations and how do i work around this ?

    Thank you for your response.
    I have searched all of the drive (this server only has C:\) and i still cannot find anything.
    I have started to search through the registration datatbase, but no luck so far.
    I have even tried to uninstall the 7.0.172 i was upgrading from.
    It even gives the same error message when trying to reinstall 7.0.172.
    /Thomas

  • Custom DB password in WCS 7.0.220.0

    Hi there,
    we are desperately trying to set a custom password of our WCS database in order to use it for direct SQL queries (Cumbersome over Web surface).
    To my knowledge there is a way to reset it however this password would be randomly generated and not available in plain text.
    Until version 6 there was a feature to directly set a password via the dbadmin command.
    Anyone know a way? Thanks!
    Regards,
    Patrick

    Hi all,
    I hope not too many have followed my approach yet as it comprises a problem. That is leaving the dbopts.db
    file (that contains the encrypted password for the 'dba' user) in the directory /WCS7.0.230.0/webnms/db/eval_kit/standalone unmodified which will no longer allow to start the database server if the WCS service is re-started due to invalid credentials or mismatch between database user record and the password in dbopts.db file.
    You would find similar messages as shown below in the logfile solmsg.out
    [root@WCS standalone]$ more solmsg.out
    23.07 14:36:52 User 'DBA' was disconnected abnormally, user id 39, machine id WCS.
    23.07 14:36:52 User 'DBA' was disconnected abnormally, user id 53, machine id WCS.
    23.07 14:36:52 Memory allocation size has fallen below 1483MB. Current size: 1483647331 bytes. Number of allocations: 12465.
    23.07 14:36:56 User 'DBA' tried to connect from WCS with an illegal username or password.
    23.07 14:38:04 User 'DBA' tried to connect from WCS with an illegal username or password.
    23.07 14:46:17 User 'DBA' tried to connect from WCS with an illegal username or password.
    23.07 14:49:52 User 'DBA' tried to connect from WCS with an illegal username or password.
    23.07 15:03:56 Server shut down by either ALT+F4 or kill command
    Mon Jul 23 15:09:36 2012
    Version: 04.50.0184
    Operating system: Linux 2.6.18 ix86 MT
    Solid BoostEngine - v.04.50.0184 (Linux 2.6.18 ix86 MT)
    (C) Copyright Solid Information Technology Ltd 1993-2010
    Using license file /data/WCS/WCS7.0.220.0/webnms/db/eval_kit/standalone/solid.lic
    License for Solid BoostEngine 4.x, Standard Edition
    Development license
    Serial number: 416000266
         4 processors
         100 concurrent connections
         25 threads
         SmartFlow option
         HotStandBy option
         1 master databases
         5 replica databases
         Accelerator option
         Diskless replica option
    Licensed to:
         Cisco Systems
         WCS WNBU
    Current working directory changed to /data/WCS/WCS7.0.220.0/webnms/db/eval_kit/standalone
    Using configuration file /data/WCS/WCS7.0.220.0/webnms/db/eval_kit/standalone/solid.ini
    Starting roll-forward recovery, please wait ...
    Recovery of 2242 transactions successfully completed
    23.07 15:09:57 Listening of 'TCP/IP localhost 1315' started.
    23.07 15:09:58 Solid BoostEngine started at Mon Jul 23 15:09:58 2012
    23.07 15:09:58 Database started.
    23.07 15:09:58 Memory allocation size has exceeded 1102MB. Current size: 1102911836 bytes. Number of allocations: 738.
    23.07 15:09:58 User 'DBA' tried to connect from WCS with an illegal username or password.
    23.07 15:14:58 User 'DBA' tried to connect from WCS with an illegal username or password.
    23.07 15:19:58 User 'DBA' tried to connect from WCS with an illegal username or password.
    23.07 15:24:58 User 'DBA' tried to connect from WCS with an illegal username or password.
    23.07 15:29:58 User 'DBA' tried to connect from WCS with an illegal username or password.
    23.07 15:34:58 User 'DBA' tried to connect from WCS with an illegal username or password.
    In order to avoid that problem please follow the steps below:
    Please note, that the first two steps are only necessary if you did already change the 'dba' user password with the SQL statement ''ALTER USER dba IDENTIFIED BY ") and only replacing the dbopts.db file does not resolve the issue of mismatching credentials.
    1)
    Uninstall the WCS 7.0.220.0 installation
    2)
    Conduct a fresh installation of WCS 7.0.220.0 (or successor version 7.0.230.0).
    Restore from an existing database backup (http://www.cisco.com/en/US/docs/wireless/wcs/7.0/configuration/guide/7_0main.html#wp1077207).
    3)
    Stop the WCS 7.0.220.0 (or 7.0.230.0) service
    Update (2012/07/25, 08:18 UTC):
    If the database server cannot be stopped by using the /opt/WCS7.0.30.0/StopWCS script, navigate to the /WCS7.0.230.0/webnms/db/bin directory and connect to the database server with the command "./solcon 'tcp localhost 1315' dba ". Issue the command "shutdown" in order to stop the database service. You will be automatically disconnected from the database server. Stopping the WCS service by using the /opt/WCS7.0.30.0/StopWCS script will now work and you can proceed with the next step.
    4)
    Conduct a fresh installation of WCS 6.0.202.0.
    Start the WCS 6.0.202.0 service.
    Run the dbadmin.sh utility and change the database password for the user 'dba' (./dbadmin.sh password ).
    This will update both the corresponding user record in the database itself as well as the dbopts.db file.
    5)
    Stop the WCS 6.0.202.0 service.
    Start the WCS 7.0.220.0 (or 7.0.230.0) service.
    6)
    Run the SQL statement as described in my previous post.
    7)
    Make a backup of the dbopts.db file of the v7 installation and replace it with the one of the v6 installation.
    [root@WCSstandalone]# pwd
    /data/WCS/WCS7.0.230.0/webnms/db/eval_kit/standalone
    [root@WCS standalone]# cp dbopts.db dbopts.db.backup-v7
    [root@WCS standalone]# rm -rf dbopts.db
    [root@WCS standalone]# cp /data/WCS/WCS6.0.202.0/webnms/db/eval_kit/standalone/dbopts.db .
    8)
    Restart (Stop and start) the WCS 7.0.220.0 (or 7.0.230.0) service.
    By doing so, the WCS will continue working without any problems and direct database access is possible.
    [root@WCS bin]# /opt/WCS7.0.230.0/WCSStatus
    Health Monitor is running.
    WCS is running.
    Database server is running
    Apache server is running
    [root@WCS bin]# ./solsql -e "select * from SYS_USERS" 'tcp localhost 1315' dba
    Solid SQL Editor (teletype) v.04.50.0188
    (C) Copyright Solid Information Technology Ltd 1993-2010
    Connected to 'tcp localhost 1315'.
           ID NAME               TYPE                    PRIV PASSW           PRIORITY   PRIVATE LOGIN_CATALOG    
            1 DBA                USER                       1       NULL         0 WEBNMSDB         
    1 rows fetched.
    SOLID SQL Editor exiting.
    Please apologize my delayed update to this post!
    HTH
    Stephan

  • WLC upgrade to 7.0.98.0, WCS & Location Appliance to upgrade - Building maps location

    Hi,
    We recently upgraded about 24 WLCs (4402s and 5508s) from 6.x to 7.0.98.0. In order to support these WLCs through WCS, we also need to upgrade the WCS to 7.0.164 which is currently running at 6.0.132.0 (Linux OS). Same is the case with Wireless Location Appliance 2700 to be upgraded as well. Wireless Management system has number of building maps with AP locations.
    Prior to upgrade the WCS / Location appliance we need to take the backup of these building maps, already stored to export after the upgrade. Kindly let us know the directory where all these maps are being stored, as during upgrade we will loose all the stored data / maps.
    Thanks for your kind assistance.
    Regards.
    Shuja

    Hi Shuja:
    Who says you're going to lose all your maps and stored data during a WCS upgrade?  The installer for WCS 7.0.164.0 will see the 6.0.132.0 installation and upgrade it in place, modifying the existing data to work in the new 7.0 format.  The installer for WCS 7.0.164.0 will even ask you if you want to make a backup of this data before the upgrade process even starts, although it would be a good idea to pull a backup of everything before you start.  (One can never have too many backups, right?)  The backup application in your existing install should be at /opt/WCS6.0.132.0/backup .  Run that application and it will prompt you for a location to put the .nmsbackup file.
    The .nmsbackup file that results from a WCS backup is what gives WCS its portability across platforms (physical/virtual) and operating systems (Windows/Linux).  It's essentially the lifeboat of WCS, containing the database, the maps, the licenses and other supporting files.
    Performing Maintenance Operations chapter of the WCS Configuration Guide:
    http://tools.cisco.com/squish/08725
    Sincerely,
    Rollin Kibbe
    Network Management Systems Team

  • WebCenter Sites (WCS) Community Application infrastructure questions

    Essentially, we are looking to perform the most basic, bare-bones installation of WCS Community. After reading through the Community installation guide, I have gathered that the following infrastructure will be necessary, and I am hoping you can either confirm or correct me if I am wrong. We will be deploying on WebLogic. Figure 3 on page 11 of the Community install guide diagrams the most basic infrastructure as I understand it to be, which is:
    1. Two separate physical servers, one for the Production Stack, and one for the Management Stack.
    2. Deployment of a Production Delivery instance of WCS on the Production Stack (the Co-Resident Satellite Server that comes out-of-the-box with WCS install is not enough).
    3. Deployment of a Management instance of Community on the Management Stack (but on a separate WebLogic managed server instance than the WCS Management deployment).
    4. Deployment of a Production instance of Community on the Production Stack (but on a separate WebLogic managed server instance than the WCS Delivery deployment).
    I understand that all 4 deployments need to happen on separate WebLogic application (managed) server instances. But to dig a little deeper, I guess my main question is, do the Production and Management Stacks need to be on separate virtual machines (we are using VMs to house WebLogic), or can we have 4 WebLogic managed servers on the same VM and house all 4 deployments on the same WebLogic domain?
    Thanks, and your advice will be greatly appreciated,
    Somen

    Hi Somen -
    Sorry for the delay in responding.
    There's no need to install WebLogic on separate domains, just be careful that they don't collide. If you get creative, you'll also see that you can actually configure CoS on far fewer WL instances than those called out in the spec. Support issues may ensue, however. But for dev purposes, no need to torture yourself with 4 app servers unless you want to.
    Tony

  • WCS very sluggish

    I'm working on a new installation of WCS (7.0.172) and it is extremely slow. I haven't got my permanent license (should be in by tommorow), so maybe it has something to do with the evaluation licenses. The server itself (Windows Server 2003 R2, 32 bit) is running very fast. (Single processor, 4GB of RAM). Memory utilization is fairly low. I have added an MSE to the system, the maps for 2 floors, and one controller, but other than that is it brand new. Any ideas? When I go to the server diags all of the pages there are quick.

    No idea.
    It could be the server itself being slow for some reason (check the process manager when WCS is being used to see any cpu usage) or it could be that snmp traffic is slow on the network because of high retransmissions or broadcast storm or whatever else.

  • WCS 5.2.130 apache stopped

    Hi,
    I've an installation of WCS 5.2.130 with a win2003 server ( with 8G RAM and 3.4GHz proc ).
    I found several time the APACHE SERVER and WCS stopped while DATABASE and HEALTH MONITOR are running
    I've seen a bug related a logon/logout from the phisical console, but it's not this the situation.
    The workaround is to logon ( via remote desktop ) into the server and sto/restart the WCS.
    Any idea / suggest ?
    Many thanks in advance
    Luigi

    What does eventviewer indicate?
    Also, do you have iis running as well?
    there may be a conflict.
    Given the fact that is on windows, do you have automatic updates enabled and/or are there local or domain policies that could affect system users that are used for services?
    Another workaround would be to create a script that monitors the service and restarts it if the service is down. It has been a while since I messed with windows, but there are many ways to do this

  • Update WCS installation

    Hello,
    I have WCS running at the version 6.0.132; would like to upgrade to latest version 6 available; downloaded software and started installation. At the point where installation should find the previous version, the messages says that there is none to find. The current installation is on D drive and installation wizard goes by default to C drive. If you follow the installation wizard there is step where you can choose installation directory but not sure why wizard did not find existing installation.
    I would like to keep existing database and just perform upgrade - what your suggestions would be in this case?
    Thanks.

    you can backup the DB and then restore back after upgrade.. That is, get the backup.. uninstall the previous... install the latest and then restore the DB
    http://www.cisco.com/en/US/docs/wireless/wcs/6.0/configuration/guide/6_0main.html#wp1077130
    Regards
    Surendra

  • Recommendations in WCS Installation (Windows 2003)

    Hi,
    Two questions about Requisites to install WCS..
    1) Should I install WCS in a Windows 2003 Workgroup or in a Windows 2003 Member Server.
    2) In the procedure Configuring WCS to run as a Domain User, can I use any user in AD or that user must have admin rights...
    What the main objective from this procedure?
    Thanks a Lot,
    Andre Lomonaco

    hi Hasan,
    Thanks for replying back so quickly.
    Both these pointers didnt help.
    The first one just shows how to install GUI on Windows. That's the second step. I am first trying to find out how to do basic telnet on Vision in Windows 2003.
    I remember in 11.5.10. In production system, had to bring MSCA Functionality through applying a patch.
    My question is : In Vision environment, Do I need to install a patch to get the functionality ? I am not sure at this moment as I can see part of responsibilities already there.
    May be I just need to configure the Vision MSCA Environment.
    Appreciate if you/ OR Someone could confirm on this. My guess is that it is already installed and it just needs to be configured.
    But I just wanted to be doubly sure before changing any configuration.
    Thanks,
    Dhiraj

  • Does WCS come with the 5508 WLC?

    Forum
    I am providing a quote to a client for a wireless installation.  I have two 5508 boxes and about 40 AP's on the quote, as well as associated SmartNet.
    I was reading how the Cisco Unified Wireless Network is comprised of:
    Controllers
    Access Points
    The Cisco Wireless Control System (WCS)
    Cisco Mobility Services Engine
    My questions are:
    1.  Does WCS come installed on the Controller?  Is this something that the customer receives simply by virtue of the fact that they are purchasing the Controller?  Or is this a separate piece of software with a cost?
    2.  What exactly is the Cisco Mobility Services Engine?  What does it do that the Controller will not?  How would I sell one to a customer?
    Thank You
    Kevin

    WCS is a Windows 2003 application (so not "on the controller") that is completely separate and has to be purchased separately with different levels of licensing for different feature sets.
    WCS is most useful when having several WLCs to manage and is offered when you buy a lot of stuff I think.
    WCS alone brings better reporting features (graphs, pdf reports, ...) and maps to visualize everything.
    MSE is a kind of "calculation appliance" that you link to your WCS to locate all clients and rogues in real-time on the map. Only that. But it's a cool enough feature :-) Without MSE you can only view one client at a time (when entering its mac address in the search field) on WCS maps.
    Nicolas

  • Issue while installing WCS using omii.ini: Database ping failed

    Hi,
    I am trying to install WCS on local linux VM. I am following the document 'Oracle WebCenter Sites: Installing on Oracle WebLogic Application Server".
    Following are the things I have been able to do successfully:
    Install Oracle DB, create a database and then create a user for this database
    Install WebLogic server, create domain, create admin server, managed server, and finally create a datasource. THe datasource connection to the DB created in step 1 above is successfull.
    I downloaded the WCS installer from Oracle Website 'WebCenterSites_11.1.1.6_bp1'. I am installing using silent installer using omii.ini file.
    During installation, on receiving the prompt to install CS and CAS applications, I installed them successfully via WebLogic console.
    I tested the URL 'http://localhost:7001/cs/HelloCS' and it showed me the Oracle WCS 11g page.
    Now, when I go back to the wcs installation terminal and hit Enter, it gives following error:
    [2013-07-11 01:32:21.861][CS.INSTALL][INFO] 1. If your platform requires you to manually deploy the Sites application, deploy Sites now. Otherwise, continue with step 2 2. Restart your application server. 3. Test the URL http:////HelloCS to see if application is deployed successfully 4. If the test is successful, press ENTER. URL http://localhost:7001/cs/HelloCS [2013-07-11 01:41:16.841][CS.INSTALL][INFO] CSSetupEngine.testConnectionAction:  Testing user configuration and database connectivity. [2013-07-11 01:41:17.118][CS.INSTALL][INFO] CSSetupEngine.postURL:  PostURL success for http://localhost:7001/cs/HelloCS [2013-07-11 01:41:17.118][CS.INSTALL][INFO] CSSetupEngine.testConnectionAction:  Web Server and Application Server Configuration test finished successfully. [2013-07-11 01:41:17.118][CS.INSTALL][INFO] CSSetupEngine.testConnectionAction:  Attempting to Ping the Database. [2013-07-11 01:41:17.459][CS.INSTALL][ERROR] CSSetupEngine.doPing:  Database Ping Failed. Make sure your application server and web server are running. Response received = HTTP/1.1 200 OK HOST_SERVICE: FutureTenseContentServer:11.1.1.6.1 Transfer-Encoding: chunked Date: Wed, 10 Jul 2013 20:11:17 GMT Set-Cookie: JSESSIONID=vpMNRd1Fwb1NJyb5NH1pXx5dfmPhzzyJL2S3yYry3FwQqL8hFVJ6!1994306862; path=/; HttpOnly Content-Type: text/html; charset=UTF-8 X-Powered-By: Servlet/2.5 JSP/2.1 [2013-07-11 01:41:17.459][CS.INSTALL][ERROR] CSSetupEngine.doPing:  Database Ping Failed. Make sure your application server and web server are running. Response received = HTTP/1.1 200 OK HOST_SERVICE: FutureTenseContentServer:11.1.1.6.1 Transfer-Encoding: chunked Date: Wed, 10 Jul 2013 20:11:17 GMT Set-Cookie: JSESSIONID=vpMNRd1Fwb1NJyb5NH1pXx5dfmPhzzyJL2S3yYry3FwQqL8hFVJ6!1994306862; path=/; HttpOnly Content-Type: text/html; charset=UTF-8 X-Powered-By: Servlet/2.5 JSP/2.1 [2013-07-11 01:41:17.460][CS.INSTALL][ERROR] CSSetupEngine.testConnectionAction: Database Ping was attempted with WCSDataSource as the DSN. The URL that was passed in = http://localhost:7001/cs/CatalogManager. Please Check your connection and property files settings. [2013-07-11 01:41:17.460][CS.INSTALL][ERROR] CSSetupEngine.testConnectionAction:  Install was unable to ping the database. Installation has halted. [2013-07-11 01:41:17.461][CS.INSTALL][ERROR] Worker.run. Install failed.                Please check log file.                          Click Yes to modify your install choices      and re-try install.                             Click No to terminate application. 
    It looks like DB ping is getting failed.
    But I am not sure how to resolve this error.
    Please help. I am pasting the content of my bea_omii.ini file that I have used. (Please view as HTML, as formatting is getting lost on this page.)
    Do let me know if any other information is required from my end.
    bea_omii.ini:
    #ContentServer install properties #Thu Apr 17 12:03:27 IST 2008 # Content Server Information # Specify the directory where you want to install Content Server i.e on windows C\:/csinstall on unix /opt/csinstall CSInstallDirectory=/home/oracle/WCS # Path to the Shared Directory i.e on windows C\:/csinstall/Shared on unix /opt/csinstall/Shared CSInstallSharedDirectory=/home/oracle/WCS/Shared # For delivery installation set Development to false Development=true # CSInstallType single/upgrade/cluster default is single only needed for upgrade or cluster #CSInstallType=single # This is to select APPSERVER Note: PORTALSERVER is not supported CSInstallPlatformType=APPSERVER # Set the application/portal server you want to install # Possible options are: wls92 for ( weblogic server), websphere60 (for webshpere), tomcat5 (for tomcat) CSInstallAppServerType=wls92 # Set the path to the server directory ex. For weblogic, on windows CSInstallAppServerPath=C\:\\bea\\wlserver_10.3 # on unix CSInstallAppServerPath=/u01/software/bea/wlserver_10.3 CSInstallAppServerPath=/home/oracle/Oracle/Middleware/wlserver_10.3 # [WEBLOGIC ONLY] Set the path to the weblogic domain i.e. on windows CSInstallWLDomainPath=C\:/bea/user_projects/domains/base_domain # on unix CSInstallWLDomainPath=/u01/software/bea/user_projects/domains/base_domain CSInstallWLDomainPath=/home/oracle/Oracle/Middleware/user_projects/domains/WCSDomain # [WEBLOGIC ONLY] Set the weblogic domain name i.e. base_domain name from path C\:/bea/user_projects/domains/base_domain CSInstallAdminDomainName=WCSDomain # Option for manual deployment (Should always be set to true) CSInstallbManual=true #Manual deployment needs to set the path where installer has to explode the war CSManualDeployPath=/home/oracle/WCS/deployment # Set the context path for your web application for example /cs/ sCgiPath=/cs/ # Set the database type Possible options #CSInstallDatabaseType=  [SQL Server, DB2, Oracle10]  CSInstallDatabaseType=Oracle10 # Set the data source name CSInstallDBDSN=WCSDataSource # By default it is installed as a primary cluster member. To install as cluster member make CSInstallType=cluster. CSInstallType=single #WEM installation IsWEMInstall=TRUE #hostname where cs is installed CASHostName=localhost # port number of cs installation CASPortNumber=7003 #Server HostName of internally accessible CAS CASHostNameLocal=localhost #Server PortNumber of internally accessible CAS CASPortNumberLocal=7003 #Server HostName where CAS is actually deployed CASHostNameActual=localhost # Select the default logger name (possible values com.fatwire.cs.core.logging.StandardLog, com.fatwire.cs.core.logging.TraditionalLog # com.fatwire.cs.core.logging.StandardTraditionalLog , org.apache.commons.logging.impl.Log4JLogger LoggerName=org.apache.commons.logging.impl.Log4JLogger # Set the host name where the application will be running CSInstallWebServerAddress=localhost # Set the port number where the application will be running CSInstallWebServerPort=7001 # Set this property to true if you are installing Spark CSInstallSpark=false # Sample Sites Information # Set this true if you want to install Avisports sample site. Avisports=true # CS-Direct and CS-Direct Advantage properties. Please don't touch them ContentCentre=true CatalogCentre=true # Set this true if you want to install CS Engage otherwise false MarketingStudio=true # Set this to true if you want to install Commerce Connectors CommerceConnector=true # Set this to true to install Structure and Navigation for FS2 this is only installed if this is development mode FSCore=true # Set this to true to install Engage Extensions for Structure and Navigation. This depends on Development and FSCore FSEngageCore=true # Set this to true to install Store Schema. This depends on Development and FSCore FSStoreSchema=true # Set this to true to install Engage Extensions for Store Schema. This depends on Development, CommereceConnector and FSEngageCore FSEngageStoreSchema=true # Set this to true to install Document Schema. This depends on Development and FSCore FSDocSchema=true # Set this to true to install Sample Visitors. This depends on Development and FSCore FSLocalUser=true # Set this to true to install Pretty URL Package. This depends on Development and FSCore FSPrettyURL=true # Set this to true to install Store Demo Data. This depends on Development and FSStoreSchema FSStoreDemoData=true # Set this to true to install Document Demo Data. This depends on Development and FSDocSchema FSDocDemoData=true # Set this to true to install Engage Store Data. This depends on Development,FSStoreDemoData,FSEngageStoreSchema and FSStoreSchema FSEngageStoreDemoData=true # If you want to install First Site II Site View set it true otherwise false. This depends on Development and FSStoreSchema FSSiteView=true # Set this to true to install Analytics. This depends on Development,FSCore,FSEngageCore,FSStoreSchema,CommerceConnector and CatalogCentre FSAnalytics=true # Set this to true to install Legacy (core) asset types (Article, Linkset). This depends on Development and ContentCentre CCSampleAssets=true # Set this to true to install Burlington Financial asset types. This depends on Development and ContentCentre CCSampleAssetsBF=true # Set this to true to install Engage and Analytics extensions for Burlington Financial. This depends on Development,MarketingStudio and ContentCentre MSSampleAssetsBF=true # Set this to true to install HelloAssetWorld asset types. This depends on Development and ContentCentre CCSampleAssetsHW=true # Set this to true to install GE Lighting asset types. This depends on Development and ContentCentre CatCSampleAssets=true # Set this to true to install Hello World sample site.  This depends on Development and ContentCentre CCSampleSiteHW=true # Set this to true to install Burlington Financial sample site. This depends on CCSampleAssets and CCSampleAssetsBF CCSampleSiteBF=true # Set this to true to install Burlington Financial Extensions sample site. MSSampleSiteBF=true # Set this to true to install GE Lighting sample site. MSSampleSiteGE=true # Spark sample site components # Set this to true to install Document Management sample asset types DMSampleAssets=false # Set this to true to install Content Management sample asset types WCMSampleAssets=false # Set this to true to install Base Components SparkSampleSite=false # Set this to true to install Sample Data SparkSampleData=false # Set this to true to install Sample Portlets. Set this true if this is a portal server SparkSamplePortlets=false

    Thanks for your reply Yct.
    I got the ping issue resolved today, there was an issue in the data source. Finally I was able to complete the installation successfully.
    But there is one more issue now. After completing the installation, I am trying to access the URL to get to the WCS login page, but with no success.
    Below, I am mentioning few URLs that I tried, and the outcome:
    http://localhost:7001/cs/HelloCS ,           This URL gives me a page with some static content messages like 'Welcome to Oracle WebCenter Sites 11gR1'. Then there are some text lines in blue color. I think this page is working as expected.
    http://localhost:7001/cs/login , this URL automatically gets redirected to the URL 'http://localhost:7003/cas/login?service=http%3A%2F%2Flocalhost%3A7001%2Fcs%2Fwem%2Ffatwire%2Fwem%2FWelcome' and I get an error message 'Firefox can't establish a connection to the server at localhost:7003.'
    http://localhost:7001/cas/login, this takes me to login page, where when I enter fwadmin@xceladmin credentials, I am taken to JASIG Central Authentication Service page, which is again static, and I can't do anything on this page
    http://localhost:7001/cs/Satellite?c=Page&cid=1327351719456&pagename=avisports%2FPage%2FHomeLayout1 , this takes me to the Avisports site, which is functional
    http://localhost:7001/cs/Satellite?c=Page&childpagename=FirstSiteII%2FFSIILayout&cid=1124747609916&pagename=FSIIWrapper, this takes me to he FirstSit page, which is again functional
    Issue: I am not getting the main login page, where I would get 3 sites(Avisports/FirstsiteII) in the dropdown.
    Looks like there is something wrong going on.
    Following I am pasting my omii.ini file, if it helps:
    #ContentServer install properties
    #Thu Apr 17 12:03:27 IST 2008
    # Content Server Information
    # Specify the directory where you want to install Content Server i.e on windows C\:/csinstall on unix /opt/csinstall
    CSInstallDirectory=/home/oracle/WCS
    # Path to the Shared Directory i.e on windows C\:/csinstall/Shared on unix /opt/csinstall/Shared
    CSInstallSharedDirectory=/home/oracle/WCS/Shared
    # For delivery installation set Development to false
    Development=true
    # CSInstallType single/upgrade/cluster default is single only needed for upgrade or cluster
    #CSInstallType=single
    # This is to select APPSERVER Note: PORTALSERVER is not supported
    CSInstallPlatformType=APPSERVER
    # Set the application/portal server you want to install
    # Possible options are: wls92 for ( weblogic server), websphere60 (for webshpere), tomcat5 (for tomcat)
    CSInstallAppServerType=wls92
    # Set the path to the server directory ex. For weblogic, on windows CSInstallAppServerPath=C\:\\bea\\wlserver_10.3
    # on unix CSInstallAppServerPath=/u01/software/bea/wlserver_10.3
    CSInstallAppServerPath=/home/oracle/Oracle/Middleware/wlserver_10.3
    # [WEBLOGIC ONLY] Set the path to the weblogic domain i.e. on windows CSInstallWLDomainPath=C\:/bea/user_projects/domains/base_domain
    # on unix CSInstallWLDomainPath=/u01/software/bea/user_projects/domains/base_domain
    CSInstallWLDomainPath=/home/oracle/Oracle/Middleware/user_projects/domains/WCSDomain
    # [WEBLOGIC ONLY] Set the weblogic domain name i.e. base_domain name from path C\:/bea/user_projects/domains/base_domain
    CSInstallAdminDomainName=WCSDomain
    # Option for manual deployment (Should always be set to true)
    CSInstallbManual=true
    #Manual deployment needs to set the path where installer has to explode the war
    CSManualDeployPath=/home/oracle/WCS/deployment
    # Set the context path for your web application for example /cs/
    sCgiPath=/cs/
    # Set the database type Possible options
    #CSInstallDatabaseType=  [SQL Server, DB2, Oracle10] 
    CSInstallDatabaseType=Oracle10
    # Set the data source name
    CSInstallDBDSN=WCSDataSource
    # By default it is installed as a primary cluster member. To install as cluster member make CSInstallType=cluster.
    CSInstallType=single
    #WEM installation
    IsWEMInstall=TRUE
    #hostname where cs is installed
    CASHostName=localhost
    # port number of cs installation
    CASPortNumber=7003
    #Server HostName of internally accessible CAS
    CASHostNameLocal=localhost
    #Server PortNumber of internally accessible CAS
    CASPortNumberLocal=7003
    #Server HostName where CAS is actually deployed
    CASHostNameActual=localhost
    # Select the default logger name (possible values com.fatwire.cs.core.logging.StandardLog, com.fatwire.cs.core.logging.TraditionalLog
    # com.fatwire.cs.core.logging.StandardTraditionalLog , org.apache.commons.logging.impl.Log4JLogger
    LoggerName=org.apache.commons.logging.impl.Log4JLogger
    # Set the host name where the application will be running
    CSInstallWebServerAddress=localhost
    # Set the port number where the application will be running
    CSInstallWebServerPort=7001
    # Set this property to true if you are installing Spark
    CSInstallSpark=false
    # Sample Sites Information
    # Set this true if you want to install Avisports sample site.
    Avisports=true
    # CS-Direct and CS-Direct Advantage properties. Please don't touch them
    ContentCentre=true
    CatalogCentre=true
    # Set this true if you want to install CS Engage otherwise false
    MarketingStudio=true
    # Set this to true if you want to install Commerce Connectors
    CommerceConnector=true
    # Set this to true to install Structure and Navigation for FS2 this is only installed if this is development mode
    FSCore=true
    # Set this to true to install Engage Extensions for Structure and Navigation. This depends on Development and FSCore
    FSEngageCore=true
    # Set this to true to install Store Schema. This depends on Development and FSCore
    FSStoreSchema=true
    # Set this to true to install Engage Extensions for Store Schema. This depends on Development, CommereceConnector and FSEngageCore
    FSEngageStoreSchema=true
    # Set this to true to install Document Schema. This depends on Development and FSCore
    FSDocSchema=true
    # Set this to true to install Sample Visitors. This depends on Development and FSCore
    FSLocalUser=true
    # Set this to true to install Pretty URL Package. This depends on Development and FSCore
    FSPrettyURL=true
    # Set this to true to install Store Demo Data. This depends on Development and FSStoreSchema
    FSStoreDemoData=true
    # Set this to true to install Document Demo Data. This depends on Development and FSDocSchema
    FSDocDemoData=true
    # Set this to true to install Engage Store Data. This depends on Development,FSStoreDemoData,FSEngageStoreSchema and FSStoreSchema
    FSEngageStoreDemoData=true
    # If you want to install First Site II Site View set it true otherwise false. This depends on Development and FSStoreSchema
    FSSiteView=true
    # Set this to true to install Analytics. This depends on Development,FSCore,FSEngageCore,FSStoreSchema,CommerceConnector and CatalogCentre
    FSAnalytics=true
    # Set this to true to install Legacy (core) asset types (Article, Linkset). This depends on Development and ContentCentre
    CCSampleAssets=true
    # Set this to true to install Burlington Financial asset types. This depends on Development and ContentCentre
    CCSampleAssetsBF=true
    # Set this to true to install Engage and Analytics extensions for Burlington Financial. This depends on Development,MarketingStudio and ContentCentre
    MSSampleAssetsBF=true
    # Set this to true to install HelloAssetWorld asset types. This depends on Development and ContentCentre
    CCSampleAssetsHW=true
    # Set this to true to install GE Lighting asset types. This depends on Development and ContentCentre
    CatCSampleAssets=true
    # Set this to true to install Hello World sample site.  This depends on Development and ContentCentre
    CCSampleSiteHW=true
    # Set this to true to install Burlington Financial sample site. This depends on CCSampleAssets and CCSampleAssetsBF
    CCSampleSiteBF=true
    # Set this to true to install Burlington Financial Extensions sample site.
    MSSampleSiteBF=true
    # Set this to true to install GE Lighting sample site.
    MSSampleSiteGE=true
    # Spark sample site components
    # Set this to true to install Document Management sample asset types
    DMSampleAssets=false
    # Set this to true to install Content Management sample asset types
    WCMSampleAssets=false
    # Set this to true to install Base Components
    SparkSampleSite=false
    # Set this to true to install Sample Data
    SparkSampleData=false
    # Set this to true to install Sample Portlets. Set this true if this is a portal server
    SparkSamplePortlets=false

  • Does WCS run on Windows 2008 R2 server?

    Can anybody share his/her experience with running WCS on Windows 2008 R2 server?
    Is it possible and did you experience any problems with it? (during installation or during normal usage)
    Is it supported by Cisco already?
    Our distributor is a little bit vague about that, that's is why I am asking it here.

    From WCS 7 release notes :
    Operating Systems Requirements
    The following operating systems are supported:
    •Windows 2003/SP2 and Windows 2003 R2/SP2 32-bit installations with all critical and security Windows updates installed.
    Windows 2003/SP2 64-bit installations are not supported. A 32-bit  operating system running on a 64-bit capable hardware is supported.
    Windows 2003 32-bit installations provide support for up to 64 GB of RAM  if Physical Address Extension (PAE) is enabled. See the Windows  documentation for instructions on enabling this mode.
    •Red Hat Linux Enterprise Server 5.X 32-bit operating system installations.
    Red Hat Linux Enterprise Server 5.X 64-bit operating system  installations are not supported. A 32-bit operating system running on a  64-bit capable hardware is supported.
    •Windows  2003 and Red Hat Linux version support on VMware ESX version 3.0.1 and  above with either local storage or SAN over fiber channel.
    Individual operating systems running WCS in VMware must follow the specifications for the size of WCS that you intend to use.
    No Windows 2008 ! I know lots of people have been crying for it and it should be coming in next releases but no promises as of now :-(
    Nicolas

  • Upgrade WCS 7.0 to PI 1.2 via NCS 1.1

    Hello all,
    we have started to do the upgrade from WCS 7.0 to PI12. In order to do that we first need to upgrade to NCS 1.1. We have ordered the following from Cisco:
    R-W-PI12-M-K9
    WCS 7.0 to Cisco Prime   Infrastructure 1.2 Migration
    N/A
    14 days
    No
    N/A
    1
    1.995,00 
    1.995,00 
    0
    1.995,00 
    R-PI12-BASE-K9
    Prime Infrastructure 1.2 Base   License and Software
    N/A
    14 days
    Yes
    N/A
    1
    0,00 
    0,00 
    0
    0,00 
    L-PI12-LF-500-LIC
    Prime Infrastructure 1.2 -   Lifecycle - 500 Device Lic PAK
    N/A
    14 days
    Yes
    N/A
    1
    0,00 
    0,00 
    0
    0,00 
    L-PILMS42-500-M
    Prime Infrastructure LMS 4.2 -   500 Device Upgrade Lic
    N/A
    14 days
    Yes
    N/A
    1
    0,00 
    0,00 
    0
    0,00 
    L-PI12-LF-100-LIC
    Prime Infrastructure 1.2 -   Lifecycle - 100 Device Lic PAK
    N/A
    14 days
    Yes
    N/A
    3
    0,00 
    0,00 
    0
    0,00 
    L-PILMS42-100-M
    Prime Infrastructure LMS 4.2 -   100 Device Upgrade Lic
    N/A
    14 days
    Yes
    N/A
    3
    0,00 
    0,00 
    0
    0,00 
    L-W-PI12-500-M
    WCS to Prime Infrastructure 1.2   Migration 500 Device
    N/A
    14 days
    No
    N/A
    1
    0,00 
    0,00 
    0
    0,00 
    L-W-PI12-100-M
    WCS to Prime Infrastructure 1.2   Migration 100 Device
    N/A
    14 days
    No
    N/A
    3
    0,00 
    0,00 
    0
    0,00 
    I have done the upload of the XML File from our WCS 7.0 installation to get the License File. But on the NCS 1.1 installation the following License is needed first (Cisco Prime Network Control System 1.1 Config Guide):
    NoteBefore adding the licenses that are migrated from your WCS installation, apply the L-WCS-NCS1-M-K9 license. The licenses migrated from WCS are generated as “ADD” licenses, and you cannot apply them unless you apply the L-WCS-NCS1-M-K9 license.
    L-WCS-NCS1-M-K9 is the Product Number to do the upgrade from WCS 7.0 to NCS 1.0, R-WCS-PI11-M-K9 is the product number to dothe upgrade from WCS 7.0 to NCS/PI 1.1.
    If I try to install just the License File I get from Cisco using the XML file from our WCS 7.0 installation, I get the error "Unable to add any license without an NCS (L-NCS-1.0-K9) license.".
    But how do a get this license if I ordered R-W-PI12-M-K9 (WCS 7.0 to PI1.2 Upgrade License)? What is the step to get the right License?
    Many thanks in advance for any help on that issue.
    Best regards,
    Hans

    Hello Joe,
    no. The information in the deployment Guide (the link i proveded before) is wrong.
    You still need to follow the upgrade path WCS 7.0 -> NCS 1.1 (here you have to use for example 1.1.1.24, because 1.1.2.12 cannot be upgraded to PI 1.2), then you can upgrade NCS 1.1 to PI 1.2 (if you upgraded the WCS to NCS 1.1.1.24 you need to install a patch ncs_patch-1.1.1.24-upgrade-12.gz, for other 1.1 releases you need a different patch).
    The major problem was the licensing. Because with the order of the Upgrade Licenses from WCS 7.0 to PI 1.2 I got "normal licenses", for PI 1.2, a Base License and Lifecycle Licenses (the number of Lifecycle Licenses matches the number from the order).
    Because we ordered the WCS 7.0 to PI 1.2 Upgrade Licenses I also ordered the NCS Appliance with the PI 1.2 (before I thought a direct upgrade from WCS 7.0 to PI 1.2 should be possibel, why not, if you can order the licenses with the description Upgrade License WCS 7.0 to PI 1.2 :-)). So I had to downgrade the NCS Appliance to NCS 1.1. After the downgrade the NCS Appliance came up without any licenses. So the major porblem was that I could not use the PI 1.2 licenses (they are not installable on NCS 1.1). So I got a demo/temporary license from Cisco for NCS 1.1 to do just the migration. After the final upgrade to PI 1.2 I installed the base and the lifecycle licenses and now everything is fine.
    Best regards,
    Hans

  • I am new to OWC , installed all the required software's and trying to install OWC sites in weblogic server and in the middle of the installation it is creating all the required tables and throwing below exception

    [2013-06-12 21:52:15,554 IST] [INFO ] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.install] READURL successful ReadURL for element OpenMarket/Xcelerate/Installation/AddACL?name=xceleditor&command=addacl&COMMANDNAME=READURL&USERNAME=ContentServer&permission=63&PASSWORD=<user password>&
    [2013-06-12 21:52:15,566 IST] [INFO ] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.install] READURL successful ReadURL for element OpenMarket/Xcelerate/Installation/AddACL?name=xceladmin&command=addacl&COMMANDNAME=READURL&USERNAME=ContentServer&permission=127&PASSWORD=<user password>&
    [2013-06-12 21:52:15,578 IST] [INFO ] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.install] READURL successful ReadURL for element OpenMarket/Xcelerate/Installation/AddACL?name=xcelpublish&command=addacl&COMMANDNAME=READURL&USERNAME=ContentServer&permission=63&PASSWORD=<user password>&
    [2013-06-12 21:52:15,590 IST] [INFO ] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.install] READURL successful ReadURL for element OpenMarket/Xcelerate/Installation/AddACL?name=Visitor&command=addacl&COMMANDNAME=READURL&USERNAME=ContentServer&permission=63&PASSWORD=<user password>&
    [2013-06-12 21:52:15,602 IST] [INFO ] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.install] READURL successful ReadURL for element OpenMarket/Xcelerate/Installation/AddACL?name=VisitorAdmin&command=addacl&COMMANDNAME=READURL&USERNAME=ContentServer&permission=127&PASSWORD=<user password>&
    [2013-06-12 21:52:15,614 IST] [INFO ] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.install] READURL successful ReadURL for element OpenMarket/Xcelerate/Installation/AddACL?name=RemoteClient&command=addacl&COMMANDNAME=READURL&USERNAME=ContentServer&permission=127&PASSWORD=<user password>&
    [2013-06-12 21:52:15,627 IST] [INFO ] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.install] READURL successful ReadURL for element OpenMarket/Xcelerate/Installation/AddACL?name=WSUser&command=addacl&COMMANDNAME=READURL&USERNAME=ContentServer&permission=1&PASSWORD=<user password>&
    [2013-06-12 21:52:15,639 IST] [INFO ] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.install] READURL successful ReadURL for element OpenMarket/Xcelerate/Installation/AddACL?name=WSEditor&command=addacl&COMMANDNAME=READURL&USERNAME=ContentServer&permission=63&PASSWORD=<user password>&
    [2013-06-12 21:52:15,652 IST] [INFO ] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.install] READURL successful ReadURL for element OpenMarket/Xcelerate/Installation/AddACL?name=WSAdmin&command=addacl&COMMANDNAME=READURL&USERNAME=ContentServer&permission=127&PASSWORD=<user password>&
    [2013-06-12 21:52:15,663 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.xcelerate] Error: com.openmarket.xcelerate.commands.EventManagerDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'CSEvents'
    [2013-06-12 21:52:15,664 IST] [INFO ] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.xml] Installation Error in Basic/Install: errno -22 from EVENTMANAGER.INSTALL: Error: com.openmarket.xcelerate.commands.EventManagerDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'CSEvents'
    [2013-06-12 21:52:15,666 IST] [INFO ] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.install] READURL successful ReadURL for element OpenMarket/Xcelerate/Installation/Basic/Install?editacl=xceleditor&adminacl=xceladmin&COMMANDNAME=READURL&upgrade-log=C:/owcSites/oracle/webcenter/sites/logs/sites.log&USERNAME=ContentServer&upgradefrom=0.0.0.0.0&PASSWORD=<user password>&
    [2013-06-12 21:52:15,681 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.xcelerate] Error: com.openmarket.xcelerate.commands.ObjectPublishManagerDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'ObjectPublish'
    [2013-06-12 21:52:15,682 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.xcelerate] Error: com.openmarket.xcelerate.commands.DistributionListDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'DistributionList'
    [2013-06-12 21:52:15,682 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.xcelerate] Error: com.openmarket.xcelerate.commands.ApprovedAssetsDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'ApprovedAssets'
    [2013-06-12 21:52:15,683 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.xcelerate] Error: com.openmarket.xcelerate.commands.AssetExportTargetManagerDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'AssetExportData'
    [2013-06-12 21:52:15,684 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.xcelerate] Error: com.openmarket.xcelerate.commands.AssetDefaultTemplateManagerDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'AssetDefaultTemplate'
    [2013-06-12 21:52:15,684 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.xcelerate] Error: com.openmarket.xcelerate.commands.AssetPublishListDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'AssetPublishList'
    [2013-06-12 21:52:15,685 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.framework] error: errno -22 on attempt to create table
    [2013-06-12 21:52:15,686 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.xcelerate] Error: com.openmarket.xcelerate.commands.SessionTableDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'PubSession'
    [2013-06-12 21:52:15,687 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.xcelerate] Error: com.openmarket.xcelerate.commands.PubTargetManagerDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'PubTarget'
    [2013-06-12 21:52:15,688 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.framework] error: errno -22 on attempt to create table
    [2013-06-12 21:52:15,698 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.xcelerate] Error: com.openmarket.xcelerate.commands.EmbeddedReferenceTableDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'EmbeddedReference'
    [2013-06-12 21:52:15,699 IST] [INFO ] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.xml] Xcelerate Installation Error in Publish/Install: errno -22 from APPROVEDASSETS.INSTALL: Error: com.openmarket.xcelerate.commands.ApprovedAssetsDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'ApprovedAssets' errno -22 from ASSETTARGETMANAGER.INSTALL: Error: com.openmarket.xcelerate.commands.AssetExportTargetManagerDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'AssetExportData' errno -22 from ASSETTEMPLATEMANAGER.INSTALL: Error: com.openmarket.xcelerate.commands.AssetDefaultTemplateManagerDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'AssetDefaultTemplate' errno -22 from ASSETPUBLISHLIST.INSTALL: Error: com.openmarket.xcelerate.commands.AssetPublishListDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'AssetPublishList' errno -22 from DELIVERYTYPE.INSTALL: Error: com.openmarket.xcelerate.commands.AssetPublishListDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'AssetPublishList' errno -22 from SESSIONMANAGER.INSTALL: Error: com.openmarket.xcelerate.commands.SessionTableDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'PubSession' errno -22 from PUBTARGETMANAGER.INSTALL errno -22 from PUBCONTEXT.INSTALL errno -22 from EMBEDDEDREFERENCETABLE.INSTALL: Error: com.openmarket.xcelerate.commands.EmbeddedReferenceTableDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'EmbeddedReference'
    [2013-06-12 21:52:15,699 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.install] READURLProblem in CallElement. Error number=-22
    Can some one help me in identifying the issue.

    Hello,
    errno -22 means " Table already exists."
    This could occur if:
    - The install had failed before during the 2nd stage (i.e. some tables were created previously) and you did not drop the schema before re-install.
    - The database user you are using has access to more than 1 WCS schemas and thought the tables exist already.
    Suggestions:
    1. Make sure the db user is set up as per the Configuring Supporting Software document ( http://docs.oracle.com/cd/E29495_01/doc.1111/webcenter_sites_11gr1_bp1_configuring_supporting_software.pdf )
    2. If the second stage of the install fails, you must drop the database tables, undeploy the WebCenter Sites application, delete the WebCenter Sites file structure, and re-install WebCenter Sites. ( http://docs.oracle.com/cd/E29495_01/doc.1111/webcenter_sites_11gr1_bp1_install_on_weblogic.pdf )
    Regards,
    Yu-Chun

  • Two different WCS instances, pointing to the same database

    Hi,
    for some unknown reason that came from the architecture fellows, I need to install 02 instances of WCS pointing to the same database server. I mean, both instances would need to "share" the database. They don't want a cluster schema because they need to have the option to deploy the app in one instance and, if wverything is ok, deploy to the remaining instance.
    Do you know if such architecture is possible? I did the installation of one instance(instance A), but when trying to install the instance B referring to A's database, I get a ton of errors.
    Any advice is much appreciated.
    Regards,
    Vinicius
    Edited by: 1000164 on Apr 15, 2013 8:18 PM

    Hi,
    This is not the way Sites has been designed. Each instance should have their own schema and repository unless the two instances work as a Sites cluster.
    So what you're trying to achieve is not possible using your approach. What I could suggest is to install two separate instances on its own, create the necessary data model, asset configurations, templates, etc. in one instance and replicate it to the other instance by publishing it to the other instance using real-time publish. If you use LDAP or any other supported directory server you would be able to use a singe directory for both sites instances.
    Regards,
    Rodney

Maybe you are looking for