CIM(Configuration and Installation Manger) Setup. Step -2 ServerInstance-Configuration. (ATG 10.2)

ATG Requires Database to startup. Its not the CRS(Commerce Reference Store) that we are setting along with CIM requires DB as there are Products information needs to be persisted. Its ATG Platform that requires database. Check the Sql directory in DAS, DSS, DPS,DCS Modules.

After Setting up ATG related Schemas through ATG CIM in step1 we Now do the next step.
If Not Please DO the Step-1 (CIM(Configuration and Installation Manger) Setup. Step -1 DataBases Setup. (ATG 10.2)).

===================================================================

C:\ATG10.2_New\ATG10.2\home\bin>cim.bat
Application Server: jboss
The following installed ATG components are being used to launch:
  ATGPlatform version 10.2 installed at C:\ATG10.2_New\ATG10.2


Nucleus running


     Oracle ATG Web Commerce Configuration Installation Manager



=======CIM MAIN MENU===============================================
enter [h]elp, [q]uit to exit


Choose the task you want to perform:


  [1]  Database Configuration - Done
 *[2]  Server Instance Configuration
  [3]  Application Assembly & Deployment
  [R]  Set the Administrator Password - Done
  [P]  Product Selection - Done (ATG Content Administration & Oracle ATG
Commerce Reference Store & ATG-Endeca Integration & ATG Site Administration)
  [A]  Select Application Server - Done (JBoss)
  [C]  Custom CIM Plugin Launcher

 >

-------SERVER INSTANCE TYPE SELECTION-------------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit


0 Instances Configured


  [S]  Publishing Server - 0 Instances Configured
  [R]  Production Server - 0 Instances Configured
  [D]  Done

 > s
  (Searching for products... done.)

-------SERVER INSTANCE DATASOURCE VALIDATION FOR MANAGEMENT---------------------
enter [h]elp, [m]ain menu, [q]uit to exit



-------SERVER INSTANCE TYPE CONFIGURATION---------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit



 *[P]  Publishing Server General Configuration - REQUIRED
  [I]  Instance Management - REQUIRED
  [C]  Modify Calculated Module List - OPTIONAL
  [S]  Scenario Manager - OPTIONAL
  [D]  Deploy CRS Endeca Application - OPTIONAL
  [O]  Configure Another Server Instance Type

 >

   Enter Production Lock Server Hostname > localhost

   Enter Production Lock Server Port [[9012]] > 9015

   Enter CAS Hostname [[localhost]] >

   Enter CAS Port [[8500]] >

   Enter EAC Hostname [[localhost]] >

   Enter EAC Port [[8888]] >

   Enter Endeca Base Application Name [[ATG]] > CRS

   Enter the Fully-qualified Workbench Hostname, Including Domain
 > localhost

   Enter Workbench Port Number [[8006]] >

   Enter Local Preview Hostname [[localhost]] >

   Enter Local Preview Host Port [[8080]] >

   Enter Default MDEX Host Name [[localhost]] >

   Enter Default MDEX Port Number [[15000]] >

-------SERVER INSTANCE TYPE CONFIGURATION---------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit



  [P]  Publishing Server General Configuration - DONE
 *[I]  Instance Management - REQUIRED
  [C]  Modify Calculated Module List - OPTIONAL
  [S]  Scenario Manager - OPTIONAL
  [D]  Deploy CRS Endeca Application - OPTIONAL
  [O]  Configure Another Server Instance Type

 >

-------INSTANCE MANAGEMENT------------------------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit


Select a server instance to Edit, Add a new server instance, or remove a
server instance



 *[A]  Add Server Instance
  [R]  Remove Server Instance
  [D]  Done

 >

  Select Type of Server Instance To Create

 *[1]  Publishing with a Server Lock Manager : Minimum 1 Required
  [2]  Publishing

Select one >

-------NAME FOR NEW SERVER INSTANCE---------------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit



   Enter Server Instance Name :  [[atg_publishing_lockserver]]
 > amca

-------JBOSS PORT BINDING-------------------------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit


Running multiple instances on the same machine requires each instance to use a
unique port binding.


 *[U]  Use Default Port Binding
  [C]  Choose Custom Port Binding

 >

   Enter HTTP Port [[8080]] >

   Enter HTTPS Port [[8443]] >

   Enter Site HTTP Port [[8080]] >

   Enter RMI Port [[8860]] >

   Enter DRP Port [[8850]] >

   Enter File Deployment Port [[8810]] >

   Enter File Synchronization Deploy Server Port [[8815]] >

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\dynamo\Configuration.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\dynamo\Initial.properties

   Enter Lock Server Port [[9010]] >

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\dynamo\service\ServerLockManager.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\dynamo\service\ClientLockManager.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\dynamo\service\jdbc\
JTDataSource_production.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\dynamo\service\jdbc\
DirectJTDataSource_staging.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\dynamo\service\preview\Localhost.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\dynamo\service\jdbc\
SwitchingDataSourceB.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\dynamo\service\jdbc\
DirectJTDataSource_production.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\commerce\endeca\index\
CategoryToDimensionOutputConfig_staging.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\userprofiling\
PersonalizationRepository_production.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\seo\SEORepository_production.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\store\stores\
StoreTextRepository_production.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\endeca\assembler\
AssemblerApplicationConfiguration.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\dynamo\service\jdbc\
DirectJTDataSource.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\commerce\locations\
LocationRepository_production.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\dynamo\service\jdbc\
SwitchingDataSourceA.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\dynamo\service\
ClientLockManager_production.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\commerce\search\
ProductCatalogOutputConfig.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\endeca\ApplicationConfiguration.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\commerce\catalog\
ProductCatalog_production.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\endeca\index\
IndexingApplicationConfiguration.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\multisite\
SiteRepository_production.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\dynamo\service\jdbc\JTDataSource.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\moduleList.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\commerce\pricing\priceLists\
PriceLists_production.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\commerce\search\
ProductCatalogOutputConfig_staging.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\commerce\endeca\index\
CategoryToDimensionOutputConfig.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\dynamo\service\jdbc\
JTDataSource_staging.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\amca\localconfig\atg\dynamo\service\ClusterName.properties

-------SERVER INSTANCE CONFIGURATION--------------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit



-------INSTANCE MANAGEMENT------------------------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit


Select a server instance to Edit, Add a new server instance, or remove a
server instance


  [P]  amca - Publishing with a Server Lock Manager

  [A]  Add Server Instance
  [R]  Remove Server Instance
 *[D]  Done

 >

-------SERVER INSTANCE TYPE CONFIGURATION---------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit



  [P]  Publishing Server General Configuration - DONE
  [I]  Instance Management - 1 Instance Configured
  [C]  Modify Calculated Module List - OPTIONAL
  [S]  Scenario Manager - OPTIONAL
  [D]  Deploy CRS Endeca Application - OPTIONAL
 *[O]  Configure Another Server Instance Type

 >

-------SERVER INSTANCE TYPE SELECTION-------------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit


1 Instance Configured


  [S]  Publishing Server - 1 Instance Configured - DONE
  *[R]  Production Server - 0 Instances Configured
  [D]  Done

 > r

-------SERVER INSTANCE DATASOURCE VALIDATION FOR PRODUCTION---------------------
enter [h]elp, [m]ain menu, [q]uit to exit



-------SERVER INSTANCE TYPE CONFIGURATION---------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit



 *[P]  Production Server General Configuration - REQUIRED
  [I]  Instance Management - REQUIRED
  [C]  Modify Calculated Module List - OPTIONAL
  [S]  Scenario Manager - OPTIONAL
  [D]  Deploy CRS Endeca Application - OPTIONAL
  [O]  Configure Another Server Instance Type

 >

   Enter CAS Hostname [[localhost]] >

   Enter CAS Port [[8500]] >

   Enter EAC Hostname [[localhost]] >

   Enter EAC Port [[8888]] >

   Enter Endeca Base Application Name [[CRS]] >

   Enter the Fully-qualified Workbench Hostname, Including Domain
 > localhost

   Enter Workbench Port Number [[8006]] >

   Enter Default MDEX Host Name [[localhost]] >

   Enter Default MDEX Port Number [[15000]] >

-------SERVER INSTANCE TYPE CONFIGURATION---------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit



  [P]  Production Server General Configuration - DONE
 *[I]  Instance Management - REQUIRED
  [C]  Modify Calculated Module List - OPTIONAL
  [S]  Scenario Manager - OPTIONAL
  [D]  Deploy CRS Endeca Application - OPTIONAL
  [O]  Configure Another Server Instance Type

 >

-------INSTANCE MANAGEMENT------------------------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit


Select a server instance to Edit, Add a new server instance, or remove a
server instance



 *[A]  Add Server Instance
  [R]  Remove Server Instance
  [D]  Done

 >

-------NAME FOR NEW SERVER INSTANCE---------------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit



   Enter Server Instance Name :  [[atg_production]] > prodps1

-------JBOSS PORT BINDING-------------------------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit


Running multiple instances on the same machine requires each instance to use a
unique port binding.


 *[U]  Use Default Port Binding
  [C]  Choose Custom Port Binding

 > c

-------CHOOSE CUSTOM JBOSS PORT BINDING-----------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit



  Select a port binding

 *[1]  Default : HTTP port is 8080
  [2]  ports-01 : HTTP port is 8180
  [3]  ports-02 : HTTP port is 8280
  [4]  ports-03 : HTTP port is 8380

Select one > 2

   Enter HTTP Port [[8180]] >

   Enter HTTPS Port [[8543]] >

   Enter Site HTTP Port [[8180]] >

   Enter RMI Port [[8861]] >

   Enter DRP Port [[8851]] >

   Enter File Deployment Port [[8811]] >

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\prodps1\localconfig\atg\dynamo\Configuration.properties

   Enter Lock Server Hostname [[localhost]] >

   Enter Lock Server Port [[9015]] >

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\prodps1\localconfig\atg\dynamo\service\
ClientLockManager.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\prodps1\localconfig\atg\dynamo\service\
ClientLockManager_production.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\prodps1\localconfig\atg\commerce\locations\
LocationRepository.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\prodps1\localconfig\atg\dynamo\service\jdbc\
SwitchingDataSourceB.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\prodps1\localconfig\atg\endeca\
ApplicationConfiguration.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\prodps1\localconfig\atg\dynamo\service\jdbc\
DirectJTDataSource_production.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\prodps1\localconfig\atg\commerce\catalog\
ProductCatalog.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\prodps1\localconfig\atg\endeca\index\
IndexingApplicationConfiguration.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\prodps1\localconfig\atg\dynamo\service\jdbc\
DirectJTDataSource.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\prodps1\localconfig\moduleList.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\prodps1\localconfig\atg\dynamo\service\jdbc\
JTDataSource.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\prodps1\localconfig\atg\commerce\pricing\priceLists\
PriceLists.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\prodps1\localconfig\atg\userprofiling\
PersonalizationRepository.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\prodps1\localconfig\atg\endeca\assembler\
AssemblerApplicationConfiguration.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\prodps1\localconfig\atg\epub\DeploymentAgent.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\prodps1\localconfig\atg\epub\file\ConfigFileSystem.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\prodps1\localconfig\atg\dynamo\service\jdbc\
DirectJTDataSource.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\prodps1\localconfig\atg\seo\SEORepository.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\prodps1\localconfig\atg\dynamo\service\jdbc\
SwitchingDataSourceA.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\prodps1\localconfig\atg\dynamo\service\ClusterName.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\prodps1\localconfig\atg\store\stores\
StoreTextRepository.properties

  >> Properties File successfully created at C:\ATG10.2_New\ATG10.2\home\..\
home\servers\prodps1\localconfig\atg\multisite\SiteRepository.properties

-------SERVER INSTANCE CONFIGURATION--------------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit



-------INSTANCE MANAGEMENT------------------------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit


Select a server instance to Edit, Add a new server instance, or remove a
server instance


  [P]  prodps1 - Production

  [A]  Add Server Instance
  [R]  Remove Server Instance
 *[D]  Done

 >
-------SERVER INSTANCE TYPE CONFIGURATION---------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit



  [P]  Production Server General Configuration - DONE
  [I]  Instance Management - 2 Instances Configured
  [C]  Modify Calculated Module List - OPTIONAL
  [S]  Scenario Manager - OPTIONAL
  [D]  Deploy CRS Endeca Application - OPTIONAL
 *[O]  Configure Another Server Instance Type

 >-------SERVER INSTANCE TYPE SELECTION-------------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit


2 Instances Configured


  [S]  Publishing Server - 1 Instance Configured - DONE
  [R]  Production Server - 2 Instances Configured - DONE
  [D]  Done

 >

=======CIM MAIN MENU=============================================
enter [h]elp, [q]uit to exit


Choose the task you want to perform:


  [1]  Database Configuration - Done
  [2]  Server Instance Configuration - Done
 *[3]  Application Assembly & Deployment
  [R]  Set the Administrator Password - Done
  [P]  Product Selection - Done (ATG Content Administration & Oracle ATG
Commerce Reference Store & ATG-Endeca Integration & ATG Site Administration)
  [A]  Select Application Server - Done (JBoss)
  [C]  Custom CIM Plugin Launcher

 > q



    Thank you for using

    Oracle ATG Web Commerce Configuration Installation Manager

    Copyright (C) 1994-2013, Oracle and/or its affiliates All rights reserved


Nucleus shutting down
Nucleus shutdown complete

C:\ATG10.2_New\ATG10.2\home\bin>

Comments

Post a Comment

Popular posts from this blog

ATG Database Tables

Most Important Tables that is required when analysing ATG related things are been listed below with all the description. The below list of tables is been divided based on the schemas in which they reside. The schemas that have been classified is based in Switching Database Architecture. For nonSwitching it a bit different which you will get to know when you reach the end. Schemas are : Production Schema Catalog Schema(SwitchA/CatA/SwitchB/CatB) Publishing Schema Production Schema :       User: DPS_USER - Has all the User details, whoever registers their account in ATG will have its entry its here. DPS_CREDIT_CARD - Contains all the User profile save cards info. This is been linked to DPS_USER table with linking table(DPS_USR_CREDITCARD). DPS_CONTACT_INFO - All the User saved addresses will be saved here like firstname, lastname, Address1, City, State, Phone Number. This table is linked with DPS_USER table using DPS_USER_ADDRESS. DCS_USER - Thi...
Read more

ATG BCC Users Roles

Each and Every person Who ever Login's to the ATG System Should have Users created in ProfileRepositoy. Their accesses to perform different Actions/Activities depends on the kind of Roles assigned to that User. Below are the Different roles that User Should Possess for Accessing BCC. User Role Description EPub-User Business User Who Creates and manages Assets. He Cannot Review them or Deploy them. EPub-Manager User Who Reviews and Approves the Assets created by ‘EPub-User’ and can deploy the same on Staging and Production. He can also create New Assets and Move them between the Targets. EPub-Admin Users Can Create new Users and grant Access to different users. Can create new users. Can assign new Responsibilities/remove responsibilities  to/from existing User. He is Same as Epub-user in case of Assests creation. He can just create/manage but cannot move them between targets. EPub-Super-Admin Has all the permissions. of the Above three...
Read more

Resetting the Dynamo Admin password

Facing difficulty in Logging in to dynamo admin or Forgot Password for the same. NO PROBLEM. Please Follow below Steps to reset it. 1) Delete all the rows from table das_account . 2) Restart the server instance. This Creates all the rows in das_account with default Values. 3) LOGIN to dyn/admin with default credentials admin/admin . 4) After Login DYN ADMIN ask to reset the password. Reset to the desired Value. Hope this Helps.
Read more