[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference pamsrc::objectbroker

Title:ObjectBroker - BEA Systems' CORBA
Notice:See note 3 for kits; note 5 for training; note 1134 for releases
Moderator:TLE::PARODId
Created:Tue Jul 11 1989
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1413
Total number of notes:6391

1393.0. "BEA Systems JOB Opportunities" by SEND::SLAVIN () Mon Apr 07 1997 17:30








********************************************************************

                             BEA Systems

                          Job Opportunities

                                  in

                   ObjectBroker Development and Q/A



                    CORBA, dCOM, ActiveX, OO, JAVA



             NT, Windows95, HP-UX, Digital Unix, SOLARIS,

                  SunOS, IBM AIX, OpenVMS, Windows16



                             BEA Systems

                   110 Spit Brook Road, ZKO02-2/R80

                   Nashua, New Hampshire 03062-2698

********************************************************************

The ObjectBroker team has been sold to BEA Systems.  We have a  number

of opportunities in the New Hampshire area.

********************************************************************



ObjectBroker has a number of new projects under  development,  and  is

expanding the product delivery team and the Q/A team.



ObjectBroker  is  BEA  Systems'  suite  of  software  for  integrating

applications  while  fostering  a  client  / server environment across

multiple platforms  and  transports.   With  ObjectBroker,  developers

focus  on  their  applications, not how the client and the server will

talk to each other.  ObjectBroker employs an object oriented model  to

shield  developers  from  the  issues  surrounding platform specifics,

networking protocols, and operating systems, without  confining  users

to  an  OO development environment.  The core product is available for

15 different platforms!



ObjectBroker includes an implementation of  the  OMG's  CORBA  (Object

Management   Group's   Common   Object  Request  Broker  Architecture)

specification.   New  ObjectBroker  versions   are   currently   under

development to support JAVA and CORBA IIOP.  Experience in OO, C, C++,

CORBA, JAVA, transports, protocols, data marshalling,  security,  DCE,

distributed  computing,  multi-platform product development, UNIX, and

Windows32 a plus.



New additions to the ObjectBroker product suite are being developed to

support  ActiveX  to  CORBA  object interactions, and to implement and

integrate Microsoft's dCOM (Distributed Component Object  Model)  with

DCE  (the  Distributed  Computing  Environment).   DCOM is Microsoft's

underlying Object Oriented middleware  that  supports  almost  all  of

Microsoft's  products.   This work covers a broad spectrum of areas in

computing, including distributed computing  using  DCE-RPC,  OO,  UNIX

operating systems programming, security, compiler design, and threads.

Knowledge and experience with C++  and  OO  analysis  and  design  are

required.   Experience  with  distributed computing, especially DCE is

strongly desired.







                                                                Page 2





ObjectBroker Product Development Positions:



We are looking for software engineers to work on the entire  suite  of

ObjectBroker   projects.    Candidates  must  have  strong  C  or  C++

programming skills  with  several  years  of  design  and  development

experience.   BS/MS  Computer  Science, strong in C or C++, minimum 3+

years product development.  Multi-platform  development,  OO  analysis

and  design,  CORBA,  JAVA,  dCOM, ActiveX, OO tools, Unix, Windows32,

distributed computing and security environments  such  as  DCE  are  a

plus.



Developers for ObjectBroker CORBA, JAVA Contact:                

        Mary Ann Slavin, ObjectBroker Engineering Manager 

        (603) 881-0143          slavin@send.enet.dec.com 



Developers for ObjectBroker dCOM, ActiveX Contact:              

        Peter Drivas, ObjectBroker Engineering Manager 

        (603) 881-6349          drivas@send.enet.dec.com 

********************************************************************

ObjectBroker Customer Q/A Team Leader Position:



The ObjectBroker product has a need for a Q/A team leader  concentrate

on   customer   problem   resolution,   product  support  and  product

maintenance.  This person will handle customer problems  from  initial

report  to  resolution,  lead  maintenance  releases,  coordinate  bug

correction with main stream development  efforts  and  testing.   They

will  triage the problems, access risk and importance.  They will work

with others on the ObjectBroker team to get problems corrected, merged

into the sources, and released to customers.



Candidates must have C or C++ programming skills with several years of

development experience.  Strong organization and communications skills

required.   BS/MS  Comp  Sci,  experience  in  C   or   C++,   product

development,  customer  interactions  needed.  Development exposure to

networking software, DMQ, PC LANs,  OLE,  DDE,  OO-tools,  distributed

computing and security environments such as DCE are a plus.



Customer Q/A Team Leader for ObjectBroker Contact:              

        Mary Ann Slavin, ObjectBroker Engineering Manager 

        (603) 881-0143          slavin@send.enet.dec.com 

********************************************************************

ObjectBroker Q/A Development Positions:



The ObjectBroker Q/A team verifies new  functionality  in  the  entire

ObjectBroker  product  suite.   The Q/A team primarily works with UNIX

and Windows32 operating systems.   For  desktop  tools  we  are  using

Visual  C++,  Visual  Test, and Visual Basic.  BS/MS Computer Science,

strong in C or C++,  minimum  3+  years  product  development  or  Q/A

experience.  Multi-platform development, OO design, CORBA, JAVA, dCOM,

ActiveX, OO tools, Unix, Windows32, distributed computing and security

environments such as DCE are a plus.



Team Leader and Developers for ObjectBroker Q/A Team Contact:           

        Frank Liva, ObjectBroker Engineering Manager 

        (603) 881-6036          liva@send.enet.dec.com 


T.RTitleUserPersonal
Name
DateLines
1393.1.0 against corporate policy?????BEAVER::MCKEATINGTue Apr 08 1997 10:3216
I did not think it was allowed to post job opportunities for external
companies in Digital notes files?

from HR006-54: PROPER USE OF DIGITAL COMPUTERS, SYSTEMS AND NETWORKS

I would have though it violated:-

o Solicitation of any kind
o Any use that would create a potential conflict of
                     interest for the employee, see Policy HR006-06,
                     Conflicts of Interest


can someone please confirm .0 is allowed?

Bob
1393.2RECV::SLAVINTue Apr 08 1997 13:202
This is not a Digital notes file anymore. This is a BEA-Digital notes file 
being accessed by both companies and residing on a BEA Systems computer.
1393.3Connected to a digital network!!!!BEAVER::MCKEATINGTue Apr 08 1997 15:389
As long as you are connected to the easynet you bide by DIGITAL rules!

it may be a "BEA-Digital notes file 
being accessed by both companies and residing on a BEA Systems computer."

but it's connected to DIGITAL's network.


Bob
1393.4Let me "refer" you!VAXCPU::michaudJeff Michaud - ObjectBrokerTue Apr 08 1997 16:5518
> As long as you are connected to the easynet you bide by DIGITAL rules!

	Bob, you forgot the smily faces! :-)

	Next you're going to be saying that because Digital is connected
	to the global Internet, and USENET, that everyone using the
	Internet must bide by Digital rules :-)

	I guess you don't realize that non-Digital jobs are allowed and
	posted in the JOBS notesfile, or that non-Digital job notices are
	being posted to USENET newsgroups which are carried inside Digital.

	In any case, complaining here, even if you are in the right
	(though w/out being privy to the agreement between the two
	companies you really don't know), is not going to change much.
	I suggest if you are not interested in the jobs, then don't
	apply.  But if you are, please let me refer you, and I'll
	split the referal bonus with you :-)
1393.5A bit of courtesy wouldnt go astrayBIGUN::BAKERat home, he's a touristThu Apr 10 1997 03:2616
    I would have thought the issue was clear and some courtesy would be
    displayed to your partners.
    
    Digital has ongoing development efforts for value-added middleware product
    etc. Our ability to deliver to current plans could be seriously eroded by 
    a concerted poaching effort. The BEA/Digital partnership is not the
    only part of Digital's distributed product, or indeed service, offerings.
    
    Any criticism of the handling of this relationship seems to be met with
    the teflon frypan mentality. Nothing sticks and you end up with a lump
    on your head at the end.
    
    After all, a partnership goes two ways. I've yet to see some courtesy
    extended the other way.
    
    - John
1393.6METSYS::THOMPSONWed Apr 16 1997 10:4514
Hi,

I think the criticism of the job postings is unwarranted. 

Whatever that policy says it is now plainly overtaken by events and
needs to be re-visited. We now have BEA, EDS, Oracle, etc., employees
roaming the "Easynet". Maintaining network links to those organizations
is obviously beneficial to all concerned, it has also presumably been 
approved by CCS. 

However the security and Business implications of this don't appear to
have been thought through yet.

M 
1393.7Aren't there bigger problems to solve?NUTS2U::LITTLEATG/EOS/Object Infrastructure/meWed Apr 16 1997 19:5515
    re: .5
    
    I'd hardly say any poaching is going on.  Posting some openings whether
    for Digital positions or BEA positions presumably only helps both
    parties as we have a vested interest in seeing each other succeed.
    
    As to "criticism of handling of this relationship", I'm not sure what
    you are specifically referring to, but do remember that those of us at
    BEA had little (make that no) choice in becoming BEA employees.  If
    there are problems with the relationship, it is certainly in all
    parties best interests to get them worked out.  Making oblique
    references doesn't do that.
    
    -tl
    
1393.8They may take my source code, but they will never take my FREEDOM :-)BEAVER::MCKEATINGThu Apr 17 1997 09:3953
RE .6 

"I think the criticism of the job postings is unwarranted. 

Whatever that policy says it is now plainly overtaken by events and
needs to be re-visited. We now have BEA, EDS, Oracle, etc., employees
roaming the "Easynet".

Hm..so you admit I may be correct in the current DIGITAL positioning?, and .0
violates the rules as they stand?

So the policy should be changed. The let's ignore the rules they are out 
of date attitude does not help the corporation. 


I am certainly in favour of making sure our partners have the correct level of 
access to our information and the same applies the other way. Can we roam the 
BEA,EDS, Oracle networks? Please provide me a pointer other than the public
www pages and the odd notes gateway.

BEA job postings are available for all to see on the BEA www pages. 


re .7    "I'd hardly say any poaching is going on."

So why bother put the announcement here? If they did not think it was going to 
attract attention then there would be no point adding it.


RE "    As to "criticism of handling of this relationship""

check notes 5141 in the Digital conference and 2775 in the DECmessageQ notes 
file. 

    "if there are problems with the relationship, it is certainly in all
    parties best interests to get them worked out."

The problems are not related to engineering. But to the total lack of thought
given to digitals existing customer relationships and the NSIS relationship as
var,service,training, and consulting delivery of these products. The view so 
far is the 'partnership' is not happening in this area. 


The above is a classic example of pitfalls that occur when we have third 
parties roaming our network. How can we have DIGITAL discussions regarding this
relationship without the effected party seeing them? restricted conferences? 
DIGITAL is now a key customer of these products. I would love to have access to
my customers network to see what is going on.


hope this helps a little,

Bob (Like my Murphys, i'm not.......)
1393.9This is all just noise...CAMPY::ADEYPC Server...now there's an oxymoron!Thu Apr 17 1997 13:107
    Note 1393.8 by BEAVER::MCKEATING
    
    As recent history has shown (the DCU Board of Directors elections a few
    years ago), policies really are merely guidelines to be interpreted as
    management wishes!
    
    Ken....
1393.10REQUE::BOWERPeter Bower, ObjectBrokerThu Apr 17 1997 14:2016
    
> The above is a classic example of pitfalls that occur when we have third 
> parties roaming our network. How can we have DIGITAL discussions regarding this
> relationship without the effected party seeing them? restricted conferences? 
> DIGITAL is now a key customer of these products. I would love to have access to
> my customers network to see what is going on.

    No one from BEA is roaming the network. All of us have explicit
    instructions to not access any notes conference, any vtx servers, any
    internal web pages, any internal mailing lists, and any other place
    with Digital internal information. We use the network for mail and 
    getting out to the internet.
    
    As soon as our network line is put into ZKO, we will be off the
    Digital network.
1393.11I see nothing in the contract to prevent BEA from posting in it's own notesfiles job noticesVAXCPU::michaudJeff Michaud - ObjectBrokerFri Apr 18 1997 01:2382
> I am certainly in favour of making sure our partners have the correct level of
> access to our information and the same applies the other way. Can we roam the 
> BEA,EDS, Oracle networks? Please provide me a pointer other than the public
> www pages and the odd notes gateway.

	The contract between Digital and BEA grants to BEA employees access
	to Digital's network as long as BEA leases space to us.  It does not
	grant to Digital employees access to BEA's network (btw, we don't
	even have access to BEA's internal network yet so we don't have
	anything you don't have :-).  Here's the section of the contract
	that grants that:

   "10.5.     SHARED EQUIPMENT AND FACILITIES.  If Digital sublets or otherwise
              provides office space to any Transferred Employees pursuant to
              Section 10.3 of this Agreement, such Transferred Employees shall
              have full access to the computing resources (E.G., hardware,
              software, network privileges, and communications) which were used
              by such employees while employed by Digital in connection with
              their duties involving the Middleware Assets.  Such access to
              computing resources shall be provided without further charge to
              BEA.  The parties agree to cooperate promptly to resolve any
              security or confidentiality concerns which may arise as a result
              of the sharing of computing resources contemplated in this
              Section 10.5, provided that any such
              solutions shall be designed to ensure that the Transferred
              Employees shall be able to perform their jobs effectively,
              efficiently, and without undue delay."

	BTW, you do realize that by reading this notesfile that you are
	indeed roaming through BEA's network as Maryann said in .2.

> BEA job postings are available for all to see on the BEA www pages. 
> re .7    "I'd hardly say any poaching is going on."
> So why bother put the announcement here? If they did not think it was going to
> attract attention then there would be no point adding it.

	You've been using the WWW to view non-Digital job postings!?  Tsk tsk.

	But seriously, is there really much difference between posting
	the URL for the job postings on the BEA Web server, vs. posting
	the web page(s) the URL points to?

> The above is a classic example of pitfalls that occur when we have third
> parties roaming our network.

	????  I don't see the example, because as Peter said, we are
	not "roaming" the Digital network and posting our job openings
	in Digital notesfiles.  It was only posted in BEA notesfiles,
	which you have choosen to roam.  If a BEA employee had posted
	the job notices in a Digital notesfile (such as the JOBS notesfile)
	then you may have a point, depending on the contract between
	Digital and BEA (which is included as one of the document attachments
	in BEA's SB-2 SEC submission before going public, which you can
	find from the SEC web site (assuming Digital allows you to roam
	the Internet :-).

	Searching for "solicit" within the Digital/BEA contract, I only
	found two occurances.  From my interpretation of these sections
	(and assuming another part of the agreement contradicts or modifies
	the following sections), BEA only agreed to not solicit Digital
	employees who work on Middleware until the closing date of the
	sale, which I believe occurred March 26th.  Digital on the other
	hand can't solicit us, so you better not post any Digital job
	notices in here :-).  If you read the contract differently (contracts
	can often be interpreted in more than one way, else we'd never
	have had the TV series "Paper Chase" :-) let me know.  Otherwise,
	my offer still stand, let me be the one to refer you for one of
	the job openings in .0, and I'll split the referal bonus with you!

   "10.7.     NON-SOLICITATION.  BEA shall not hire or attempt to hire any
              Digital employees who work on the Middleware Assets in the United
              States prior to the Closing Date without the written consent of
              Digital.  Digital agrees not to re-hire or directly or indirectly
              attempt to re-hire, for a period of 12 months from the Closing
              Date, any of the Terminated Employees."

"9.   BEA EMPLOYEES

    BEA reserves the right to determine the assignment of BEA employees.
    Digital agrees, during the period of the services and for one year
    thereafter, not to directly or indirectly solicit any BEA employee
    providing those services for employment by Digital."
1393.12What a ridiculous debateNUTS2U::LITTLEATG/EOS/Object Infrastructure/meSat Apr 26 1997 06:1511
    re: .8
    
    Gimme a break.  The original comment said "concerted poaching effort". 
    Posting a listing of job opportunities for engineering resources that
    will help build a product that both Digital and BEA will sell and
    profit from is hardly a "concerted poaching effort" or particularly
    detrimental to any parties involved.  Would you prefer people to leave
    Digital and go to a competitor?
    
    -tl