Archive for July, 2008

Senior J2EE Developer | Full-time | Jersey City, NJ


Summary

IdeaReboot Inc is looking for a highly motivated Senior J2EE Developer with strong server side programming and workflow automation experience. The primary responsibility includes defining, designing, and implementing a dynamic workflow solution based on JBPM.

Continue reading ‘Senior J2EE Developer | Full-time | Jersey City, NJ’

JMS - Ensuring Reliability | Part - 2


Continuing from Part 1 which talked about Message Acknowledgment and means of ensuring basic reliability with JMS, here we talk about Persistence, Expiration, Priority and Temporary Queues/Topics.

What are the two delivery modes for messages to specify their Persistence? And, how do you specify them?
The two delivery modes are fields of the DeliveryMode interface and are as follows.

  1. The PERSISTENT delivery mode, which is the default, instructs the JMS provider to take extra care to ensure that a message is not lost in transit in case of a JMS provider failure. A message sent with this delivery mode is logged to stable storage when it is sent.
  2. The NON_PERSISTENT delivery mode does not require the JMS provider to store the message or otherwise guarantee that it is not lost if the provider fails.

Continue reading ‘JMS - Ensuring Reliability | Part - 2′

JMS - Ensuring Reliability | Part - 1


Until a JMS message has been acknowledged, it is not considered to be successfully consumed. The successful consumption of a message ordinarily takes place in three stages.
1. The client receives the message.
2. The client processes the message.
3. The message is acknowledged. Acknowledgment is initiated either by the JMS provider or by the client, depending on the session acknowledgment mode.

What are the basic mechanisms for impacting the reliability of message delivery?
  • ACKNOWLEDGMENT- by specifying various levels of control over message acknowledgment
  • PERSISTENCE - by specifying that messages are persistent, that they must not be lost in the event of a provider failure
  • PRIORITY - by setting various priority levels for messages, which can affect the order in which the messages are delivered
  • EXPIRATION - by specifying an expiration time for messages, so that they will not be delivered if they are obsolete
  • TEMPORARY DESTINATION - by creating temporary destinations that last only for the duration of the connection in which they are created

Continue reading ‘JMS - Ensuring Reliability | Part - 1′

JMS Introduction


Messaging enables distributed communication that is loosely coupled. A component sends a message to a destination, and the recipient can retrieve the message from the destination. However, the sender and the receiver do not have to be available at the same time in order to communicate. In fact, the sender does not need to know anything about the receiver; nor does the receiver need to know anything about the sender. The sender and the receiver need to know only what message format and what destination to use. In this respect, messaging differs from tightly coupled technologies, such as Remote Method Invocation (RMI), which require an application to know a remote application’s methods.

A JMS application is composed of the following parts.

  • A JMS provider is a messaging system that implements the JMS interfaces and provides administrative and control features. An implementation of the JEE platform usually includes a JMS provider.
  • JMS clients are the programs written in the Java that produce and consume messages.
  • JMS Destinations are Queue for a point-to-point messaging and Topic for pub/sub messaging.
  • Messages are the objects that communicate information between JMS clients and destinations.
  • Administered objects are pre-configured JMS objects created by a server administrator for the use of messaging clients. The two kinds of administered objects are destinations and connection factories

Continue reading ‘JMS Introduction’

JMS - Message Driven Bean


A Message Driven Bean or MDB is a JMS message consumer that usually implements some message processing and/or routing logic. The bean registers interest (via deployment descriptor) in a Queue or Topic of its choice, implements MessageListener and MessageDrivenBean interface, and awaits arrival of asynchronous messages.

Does an MDB have a home or a component interface?
Messages are delivered asynchronously to a bean by the messaging service provider (e.g. IBM MQ) or an application server (e.g. JbossMQ). The bean cannot be invoked by a client and hence does not require a home or a component interface.An MDB does not have any client-visible identity or a conversational state - all the instances of the bean are treated equivalent for servicing receipt of a message. Typically, a server creates a pool of MDB instances and keep them in method-ready state. On arrival of a message, one of the instances is assigned to the client. After the onMessage() method execution, the bean is returned to the pool of available beans. The J2EE (now JEE) container essentially controls the lifecycle of such a bean. The component pooling of MDB results in more scalable applications.

Continue reading ‘JMS - Message Driven Bean’

Oracle Identity Federation Engineer | San Jose, CA


Summary
IdeaReboot Inc is looking for one of its Networking Clients, an Oracle Identity Federation Engineer to manage all account provisioning within our Client’s enterprise. The product will be applied to both internal and external systems. This is a very heterogeneous environment; so we require someone with Oracle Identity Management & Identity Federation installation, support & maintenance experience.You will work with a worldwide cross-functional team, and assist the project manager and tech lead to drive projects to completion. You will collaborate with dispersed teams, both geographically and technologically, so you must have the skills to understand and respect cultural differences. The ideal OIM / OIF engineer demonstrates the desired blend of technology and communication skills necessary to succeed in this position. Continue reading ‘Oracle Identity Federation Engineer | San Jose, CA’

Sr. Perl Developer | Contract Position | San Jose, CA


Summary
IdeaReboot Inc is looking for one of its industry leading Networking client, a seasoned Perl Developer to join and exciting enterprise scale IT Infrastructure SOA project. The platform has being built as a general platform and, as such, needs to have provisioning capabilities with it. You will work with the tools development team to build out the provisioning tools. As a Sr. Perl Developer, you will be part of the tools team in building deployment capabilities. You will also assist in integrating the platform’s deployment capabilities with the provisioning source of truth framework. Continue reading ‘Sr. Perl Developer | Contract Position | San Jose, CA’

QA Engineer | Palo Alto | CA


Summary
IdeaReboot Inc is looking for QA Engineer to be part of a fast growing VDI (Virtual Desktop Infrastructure) team and work on the VDM (Virtual Desktop Manager) product. The VDI group focuses on bringing security, manageability and mobility benefits of virtualization to enterprise desktops. As a QA Engineer you will be working on new products in the VDI group and play a key role in developing the test harness and test plans. Excellent QA skills required. Ability to define the test cases based on marketing and engineering requirements. You must have experience performing black box as well as white box testing. Continue reading ‘QA Engineer | Palo Alto | CA’

Java QA Engineer | San Jose, CA


eBay Java QA Engineer - Hot JobsSummary & Expectation

IdeaReboot Inc is looking for its direct client, an industry leading Ecommerce Company is looking for a Java QA Engineer. As part of the QA team, you will play a key role in the testing and administration of complex, multi-tiered distributed software applications. The position will consist of 80% manual testing and 20% automation. You will collaborate with other engineers, administrators, and managers to successfully: Continue reading ‘Java QA Engineer | San Jose, CA’

Silk/Python QA Engineer | Palo Alto


Summary
IdeaReboot Inc is looking for experienced Python and/or SilkTest automation engineer with strong background in UI test automation using Squish open source test automation tool. You will be developing python (preferred) or Silk code inside Squish to automate testing of a Linux based UI for an enterprise software product. Continue reading ‘Silk/Python QA Engineer | Palo Alto’