PowerBuilder Tips, Tricks, and Techniques

Berndt Hamboeck

Subscribe to Berndt Hamboeck: eMailAlertsEmail Alerts
Get Berndt Hamboeck: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Related Topics: Java EE Journal, Apache Web Server Journal, ERP Journal on Ulitzer

J2EE Journal: Article

Working with the Enterprise Portal

An Overview Part 1

The Agent Manager
Sybase supports administrators who want to start, stop, or restart servers and services with a preinstalled Web application in EAServer called the System Management Console. This Web console interacts with agent managers running in each installation. The agent manager allows the Web console to stop and restart managed services such as EAServer.

NOTE: An agent manager must be running on each machine that hosts Sybase software managed by the Web console.

Where to Find It
The agent runs as a Windows service and starts automatically when you boot the machine (look for the installed service Sybase EP Management Agent). You can also start and stop the agent manually by starting or stopping the service. Alternatively, you can start and stop the Agent Manager by running the batch files located in the %SYBASE%/AgentManager-3_0_0\bin subdirectory of your (already installed) EAServer installation directory (%SYBASE% is the default for the C:\Program Files directory - I personally use C:\Sybase). The command file am_start.bat starts the agent manager, and am_stop.bat stops the agent manager. The agent manager also starts or stops the CIM repository.

Sybase Web Console
The Web Console is where an EAServer or portal administrator can start, stop, and ping local and remote services (such as servers or connection caches). Simply start the Web browser, and you can connect to the Web console (the same way you would connect using Jaguar Manager) to view information or the actual status of an installed product and perform management actions on it. You can also configure access control on these actions to limit which users can perform them.

As mentioned, administrators can use the Web console that comes with EAServer to manage installations. Keep in mind that if you use different machines for your Sybase Enterprise Portal installation, as pointed out in the Sybase Enterprise Portal installation guide, they must all use the same CIM Repository. Each installation also requires a local agent manager. To configure a federation of managed installations, choose a machine to host the CIM Repository and the EAServer installation that hosts Systems Management. Make sure the Systems Management and Agent Manager options are selected for this EAServer installation. For subsequent installations, change the CIM Repository host and, if necessary, the port to the address on the systems management machine, and make sure that the Agent Manager install option is selected for EAServer.

NOTE: Each machine that hosts installations managed by the Web console must have a local agent manager running to enable shutdown and restart of managed services. Because the systems management software is itself an EAServer application, you can't use the Web console to start or restart the server that is hosting the systems management application. Similarly, you can't use the Web console to shut down or restart services that are critical to the management architecture, such as the CIM Repository.

Don't forget to start the CIM Repository when you connect to the Web console. When you start the agent manager that's in the same installation as the CIM Repository, the agent manager starts the CIM Repository if it's not already running. You can manually start and stop the service with the commands described previously.

Where to Find It
You use the Web console by starting your browser and pointing it to http://host:port/SysMgmt/mgmt, where host is either localhost or your machine name (after installing the Enterprise Portal, it's machinename.domainame) and the port is 8080 by default.

As you'll see, the Web console provides two access points for remote administration:

  • Systems Management - Enables you to do basic management functions, such as reading error logs or starting and stopping services
  • Systems Management Access Control - Enables you to limit which users can access or modify the state of managed systems using the Web console
You must log into each of these access points individually; you are prompted for a username and password after you click the plus sign icon next to either Systems Management or Systems Management Access Control.

Simply enter the information needed to connect to your EAServer (use your IIOP listener information for EAServer and the jagadmin user - the password is empty by default). Figure 4 shows what this should look like. If you get a MessageBox indicating that the username, password, or EAServer information is not correct but you're quite sure that it is, look in the Jaguar.log file in your EAServer/bin directory. It might show you that something is wrong with the database or the connection cache. If you're sure that the CIM Repository is running (for example, the CIMListVersion utility displays results), take a look at the connection cache used by the console. First try to ping it. If this fails, check the configuration and the driver (com.sybase.jdbc2.jdbc.SybConnectionPoolDataSource) of the cache (see Figure 5).

SySAM and Licensing
The CIM Repository and the SySAM must be installed on the same machine in your portal architecture. This machine (server) is called the license host because it stores the license certificates. In a multimachine environment all other machines access the license file on the license host to check out valid software licenses.

More Stories By Berndt Hamboeck

Berndt Hamboeck is a senior consultant for BHITCON (www.bhitcon.net). He's a CSI, SCAPC8, EASAC, SCJP2, and started his Sybase development using PB5. You can reach him under [email protected]

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.