HowToEpipOM: All available jobs through epichannel

$ epichannel -help
-------------------------------------------------------------------------------
EpiChannel -help
EpiChannel Version 7.1.1.0.1293
-------------------------------------------------------------------------------
EpiChannel executes extraction jobs locally or remotely, runs MomentumBuilder,
AggregateBuilder, Scrutiny, RandomPerm, and CreateCurrentViews.

-------------------------------- Example Usage --------------------------------
Run a job:
EpiChannel -l -b -s
-u -d -p
-J
Run a job:
EpiChannel -i -j

Run MomBuilder in ForceRebuild mode:
EpiChannel -i -mom -fb

Run Scrutiny and check the Outbound Marketing Server, the Mart, and AggBuilder
EpiChannel -i -scr AppServer Mart AggBuilder

List completed, running, and pending EpiChannel tasks:
EpiChannel -i -ls -all

Run a job on the remote server:
EpiChannel -i -j -r

Attach to the job with ID 3579 and print its log files as it runs:
EpiChannel -i -a 3579

Kill the job with ID 3579:
EpiChannel -i -k 3579

Run a job; Override the mail configuration specified in the instance storage:
EpiChannel -i -j -mh mail.mydomain.com
-ma martin@mydomain.com -ms it_worked@mydomain.com
-mw something_wrong@mydomain.com -mf it_failed@mydomain.com

Usage Notes:
All command line parameters are case insensitive.
All command line parameters can begin with /, -, or --.
Command line parameters can appear in any order.
-------------------------------- Return Codes ---------------------------------
(0) EPICHANNEL_SUCCESS EpiChannel executed successfully
(1) EPICHANNEL_FAILURE EpiChannel failed as a result of a user or an
environmental error
(2) EPICHANNEL_USERCANCEL EpiChannel failed because it was canceled with
the --kill command.
(3) EPICHANNEL_RUNTIMEEXCEPTION
EpiChannel failed because of an internal error.
Send all log files to [906] Customer
Support.
-------------------------------------------------------------------------------
-h, -?, /?, --help Display this list of command-line options.
-------------------------------------------------------------------------------
-j, --Job Run the specified extraction job.
-t, --TrialRun Simulate execution of the SQL on the source and
destination databases without making any changes
to the data.
--LogRows Log the contents of the first rows of
every extraction statement.
-#, --MaxSelects
The maximum number of rows to fetch in any SQL
statement.
-f, --ForceRestart Ignore previous execution history and start
executing job from the beginning.
-------------------------------------------------------------------------------
-mom, --MomBuild Run MomentumBuilder. Generate or update the
accelerators required for generating lists and
campaigns.
-npt, --NumParallelThreads
The number of concurrent accelerator creation
queries issued.
-f, --ForceRestart Ignore previous execution history and build all
accelerators requested by the metadata
-fb, --ForceRebuild Rebuild accelerators from scratch. Do not
attempt to incrementally update.
--NoMirror Run MomBuilder against the currently active
datamart partition.
-------------------------------------------------------------------------------
-agg, --AggBuild Run AggregateBuilder. Build aggregate tables to
improve query response time.
-------------------------------------------------------------------------------
-scr, --Scrutiny ...
Run the specified internal consistancy checks on
the EpiCenter. consists of one or
more of the options below separated by spaces.
All Run all Scrutiny checks.
Meta Run Scrutiny checks on the metadata.
Mart:Next Run Scrutiny checks on the EpiMart (in the next
space).
Mart:Current Run Scrutiny checks on the EpiMart (in the
current space).
Mart:Prev Run Scrutiny checks on the EpiMart (in the
previous space).
Op Run Scrutiny checks on the EpiOp.
AppServer Run Scrutiny checks required by the Outbound
Marketing Server.
EpiChannel Run Scrutiny checks required for EpiChannel
extraction.
AggBuilder Run Scrutiny checks required by
AggregateBuilder.
MomBuilder Run Scrutiny checks required by MomentumBuilder.
SchemaGen Run Scrutiny checks required for adaptive schema
generation.
Warning Run Scrutiny checks for warnings in addition to
errors.
-------------------------------------------------------------------------------
-rnd, --RandPerm Build a random sampling table used for sampling
of demographic dimensions and for populating
random lists.
-------------------------------------------------------------------------------
-ccv, --CreateCurrentViews Rebuild external reporting views which select
the currently active versions of the base tables.
-------------------------------------------------------------------------------
-dae, --Daemon Spawn a daemon process that checks the metadata
for remote requests to execute EpiChannel, and
acts on those requests.
-------------------------------------------------------------------------------
-stop, --StopDaemon Request a running daemon to kill all the remote
jobs it has spawned and exit.
-------------------------------------------------------------------------------
-ls, --List List currently running and pending EpiChannel
executions.
--All Show completed instances as well.
-------------------------------------------------------------------------------
-a, --Attach Attach to and print the logs from the specified
execution instance of EpiChannel. The instance
can be currently running or completed. Get
by executing the --List command.
-------------------------------------------------------------------------------
-k, --Kill Kill the specified running instance of
EpiChannel. Get by executing the
--List command.
------------------------------- General Options -------------------------------
-b, --DBVendor The name of the vendor of the dbms on which the
SQLServer EpiMeta database resides.
Oracle
-s, --Server The name of the server where the EpiMeta
database resides.
-u, --UserName The username of the EpiMeta database. Pass ""
to request the use of operating system level
authentication.
-d, --DBName The database name of the EpiMeta database.
This parameter is not required on Oracle.
-p, --Password The password for the user of the EpiMeta database
-pt, --Port The port to use to connect to the EpiMeta
database. If not supplied, database type default
is used.
-disableDBLog Disable logging to the Epiop database
-int, --Interactive Run EpiChannel in interactive mode. This is
incompatible with the --RemoteLaunch option and
the --Noninteractive option.
-nonint, --Noninteractive Disable use of interactive mode for job steps
whose debug level is set to interactive. This
option is incompatible with the --Interactive
option.
-r, --RemoteLaunch Request that the remote daemon process launch an
EpiChannel instance with the specified command
line (excluding --RemoteLaunch and its options).
-dt, --Detach Dont attach to the remotely spawned process and
dont print its log files. Send the request to
the Daemon process and exit immediately.
-dwc, --DieWithClient Request that the remotely spawned EpiChannel
execution instance kill itself if the connection
with this client is lost.
-i, --InstanceName The name of an EpiCenter instance stored
locally. Connection information and other
EpiChannel options are taken from this local set
of defaults. Options specified via command line
parameters override options specified inside the
local instance storage.
--InstallRootDir
The directory in which this version of [906]
Outbound Marketing is installed.
-l, --LoggingDir
The directory where logging files will be
created.
--DisableDBLog Disables logging to the EpiOp data store. This
option should only be necessary if DB-Logging is
causing short jobs that would otherwise run
in only a few minutes to run for a long time.
-sch, --Scheduler Directs EpiChannel to fail if a previously
failed job failed on a job step that had OnError
action set to ManualRepeat. This should be used
whenever EpiChannel is being called from an
automated scheduler.
-ma, --MailAdmin The e-mail address of the administrator for your
application, which is used as the return address
for automatic e-mail notification of job status.
-mh, --MailHost The hostname of the SMTP host computer through
which e-mail is to be sent.
-ms, --MailSuccess
The address to which an e-mail containing
EpiChannel log files is to be sent on successful
completion of an extraction job. Multiple
addresses can be separated by commas (without
spaces).
-mw, --MailWarning
The address to which an e-mail containing a
warning message is to be sent when a warning is
generated during execution of an extraction job.
Multiple addresses can be separated by commas
(without spaces).
-mf, --MailFailure
The address to which an e-mail containing
EpiChannel log files is to be sent on failure of
an extraction job. Multiple addresses can be
separated by commas (without spaces).
-------------------------------------------------------------------------------
EpiChannel| |Completed|
| | |

HowToEpiphany:- Added new user,but can not access using thin client

You have added a new user in OM.
But when the user is trying to access epiphany using thin client login error is coming.

Check:-
Check the credentials of that user in OM again.
If its a NT LM access check for the domain.
If its LDAP access check the details.

And then refresh the OM.

HowToEpiphany:- Can not start OM Service.

You trying to start the service but can not and its says like "Error-1053 The service did not respond to the start or control request in a timely fashion".

If windows can not start a service for 3 minutes it will throw error.
Wait and refresh the service.It may get start a bit later.

If it is not starting then
Check the administrative tools-->event viewer logs
Try to find out the error and resolve this.
Possible error may be:-
1/ Scrutiny error.
2/ Database connectivity.
3/ Another instance of weblogic/websphere is running. etc.

HowToEpiphany:- Can not connect from epiphany thin client

You may get error like:-
Message from the ISAPI plugin:

No backend server available for connection: timed out after 20 seconds.

Build date/time: Jun 21 2002
Change Number: 191629

Check:-
1/ SSA Global OM server is running.
2/ Weblogic/Websphere is running.

HowToEpiphany: Installing SSA Outbound Marketing In Windows

1. Prepare your database:
a.

2. Prepare your window for OM:-
3. Installing a web server
a. Install IIS.After rebooting Windows, verify that service w3svc (World Wide Web Publishing Service) is set to Automatic. If it is not, set it to automatic using the (right-click) Properties dialog box. IIS does not work properly unless this service is running.
b. Setting web site protection:-
i. Navigate to (Windows) Start > Programs > Administrative Tools >Internet Services Manager.
ii. For each Web site created for use with a different Outbound Marketing instance, right-click and select Properties.
iii. Open the Home Directory tab and set Application Protection to High. If this setting is changed to High (Isolated) from another value, ensure that the change is propagated to all child scripts.
iv. Click OK to save your settings.
v. Stop and restart IIS after completing the above steps for all Web sites intended for use with Outbound Marketing instances



4. Install Oracle client if your OM datamart is not in this machine.
5. Installing the J2EE Application Server
a. Run the installer and follow the prompts displayed in the installer window. Accept the installation defaults or select options to comply with the standards for your enterprise. At a minimum, you must install the WebLogic server Server component. Node Manager is required and is part of the installation, but you do not need to install it as a Windows Service.
b. Install the WebLogic license. Change the name of your new downloaded license file from license.bea to license_new.bea. Run UpdateLicense.cmd license_new.bea. This peration merges the new license with current license, and saves the results in the file license.bea. The new merged file license.bea will be used by Weblogic.
6. Creating a WebLogic Domain
Note: Perform this procedure after installing BEA WebLogic and before
installing Outbound Marketing. To upgrade to the current release of
Outbound Marketing from any previous version, complete this procedure
before using the Outbound Marketing Instance Manager.
a. Start the BEA WebLogic Configuration Wizard through one of the following methods:
Windows Start menu:
Start > All Programs > BEA Products > Tools > Configuration Wizard
Windows command line:
\ wlserver_10.0\common\bin\config.cmd
Unix command line:
/wlserver_10.0/common/bin/config.sh
b. On the Welcome screen, select Create a new WebLogic domain, and click Next.
c. On the Domain Source screen, accept the default (selects Generate a domain configured automatically to support the following BEA Products:), and click Next.
d. Enter an administrative user name and password in the Configure Administrative Username and Password screen, and click Next. Store this information for logging on to the Administrative Console.
e. On the Configure Server Start Mode and JDK screen, do the following and click Next.
i. In the WebLogic Configuration Startup Mode pane, select Development Mode.
ii. Select the Java SDK to use.
In the JDK Selection pane, select BEA Supplied JDKs, and then the installed version of the SUN SDK.
f. On the Customize Environment and Services Settings screen, accept the default and click Next.
g. On the Create WebLogic Domain screen, enter a unique Domain Name. (The default is base_domain.) Do not modify the path information in the Domain Location field.
h. Click Create to complete the process and create the new domain. The new domain is used as a template domain and is not modified by Outbound Marketing.

7. Installing outbound marketing manager:-

The standard software installation (collectively called the Outbound Marketing)
on Windows includes:
- Outbound Marketing Server, an application server that coordinates user requests for data and reports, returns results in HTML format, and supports navigation between EpiCenter Web pages.
- Outbound Marketing Manager, a graphical administrative utility for configuring and managing the data mart and applications. Because the Outbound Marketing Manager runs on Windows, the Oracle configuration scripts are only present in the Windows package.
- EpiChannel, an extraction facility for downloading data from source systems into the data mart.
- Remote Web Server, a link to the installed Web server.
- Other Outbound Marketing components and utilities including language-specific files.
Note:
- Outbound Marketing software does not have to be installed on the same computer as the data mart (EpiCenter). However, for DB2, you must catalog the DB2 server on the DB2 client machine, including all of the machines in a cluster prior to installation.The installer automatically installs, or offers to install, the following required third-party software components if they are not already present:
- ODBC and JDBC drivers
- After installing Outbound Marketing software on the server host, install the Outbound Marketing Manager administrative utility on other computers to provide remote access for administrative tasks.

a. Log in under an account that has administrator privileges on the local host.
b. Get the AS_win32_nas.zip file for the installation. The zip file is available from the Infor Download Center.
c. Unzip the file to C:\\Install (the default directory), or a directory of your choice.
d. Exit all open Windows applications.
e. Make sure you have installed and configured your J2EE application server, Web server, and database management server before continuing.
Note: For the WebSphere Network Deployment application server, be sure the deployment manager and node agents are running before beginning the installation.
f. Verify that you have the Java 1.5 runtime environment installed. If necessary download and install Java 1.5 before continuing.
g. Verify that the World Wide Web Publishing Service is running. If the service is not running, navigate to Start > Programs > Administrative Tools > Services to start the service.
h. Double-click ominstall.exe in the directory specified in step c
i. A message window prompts you to set JAVA_HOME to Java 1.5 JRE/ JDK, if you have not already set JAVA_HOME.Click OK to close the OM installer. Install Java 1.5 JRE/JDK and set JAVA_HOME. Re-start the OM installer .
Note: If sunjce_provider.jar does not exist at /jre/lib/ext when JAVA_HOME points to a JDK directory, or at /lib/ext when JAVA_HOME points to a JRE directory, then you will see the following error message if you try to install OM:

ERROR: C:\java\jdk1.5.0_11/jre/lib/ext/sunjce_provider.jar does not exist. Download the file from Sun and try again. Click the OK button in the error window to stop and exit the OM installer. Then, download sunjce_provider.jar from the Sun website, install the file, and try running the OM installer again.
j. Install Microsoft Data Access Components (MDAC) 2.8, if prompted. The installation files and license are included.
i. Follow the screen prompts to install MDAC.
ii. Reboot when prompted.
iii. Restart ominstall.exe. The InstallAnywhere wizard displays the Welcome screen.
Tip: Click Cancel at any time during the installation process to terminate and uninstall any components installed to that point.
k. Click Next. The InstallAnywhere wizard displays Destination Folder screen.