How to work with FTP (File transfer protocol) in Oracle SOA

How to work with FTP (File transfer protocol) in Oracle SOA

Tool:

WINSCP (or) FILEZILLA à using for creating username and password

1. Request to the admin

Admin  a. Create folder

1. Permission to folder(read and write)
2. access user name and password
3. IP address
4. Console FTP adapter(configuration)

Host name :

Port:

User name:

Password:

3. J developer  FTP adapter
4. get  read
5. put write
6. synchronous get syn read
7. List files  list files

FTP Adapter configuration:

1. Install filezilla (or) WINSCP

Open – filezilla    

4th option    general

Click add    users(username)  ex: filezilla243

Password : welcome1 (note: 3 characters)

Click   shared folders(left side)   Add  

Folder path(ex: D:// FTP _ Remote)  

• Read
• Write
• Delete
• Append
• Create
• Delete
• List
• Sub dirs   ok

2. :7001/console  

Deployment FTP adapter  configuration  

Out band connection pool  new  

Javax. Resource.cd  

JNDI Name(eis.FTP.Ramesh1) finish  

• Resource.cd à expand  

Eis .FTP.Ramesh1   click

Use next button multiple times and set the property value of user name, password, port, host name

Interested in mastering Oracle SOA Training?
Enroll now for FREE demo on Oracle SOA Training.

Note: In case of no pass word, FTP uses public/private key

1. Authentication type
2. Host
3. Private key file
4. User name
5. Use stop

Ex:

1. User name = filezilla user name (ex: file Zilla 243)
2. Password = filezilla Password (ex: welcome1)
3. Port = 21 (default)
4. Host name = local host /192.168.121.3 (default) 

Save   Deployment  FTP adapters   update  

Deployment port path : C:/Oracle /middle ware/Oracle SOA1/SOA/connectors/plan.XML

Next  Next   finish

A1:

i/p  invoke i/p

A2:

o/p  “success”

FTP – put adapters:

5-8  put file

6-8  direction path for o/p, file name (put.txt), append

7-8  native format

Sample txt:

123 sai  teja

143  Ramesh Reddy

Project: (FTP _get ) poll

FTP get adapters:
6-10 Directory for incoming files (physical path)
9 -10  Native format incoming file
Transform 1:
Receive i/p ? invoke i/p variable
Project:

XSD:

o/p directory size  string

file name  string

Directory  string

Modified time string

Creation time string

File size string

A1:

i/p  invoke i/p

A2:

Invoke o/p  o/p

FTP  list files Adapters:

6-8 incoming file path

Note:

We want to write the o/p in our system then we add invoke between “invoke _ FTP”  and “A2”.

MISSING LINE PG:117

Project (FTP _synchronous get)

MDS (Meta Data service)

1. File Based MDS
2. CB based MDS

File Based MDS:

C:/oracle /middle ware/ J developer/ integration /seed/apps

Note: this ”apps” folder creates our self and folder name must give apps doesn’t five other name.

Apps sub folders(XML, XSD, XSLT, WSDL)

Example:

1. XML (fault buildings.XML, fault policies .XML)
2. XSD (PO.XSD, Internal order.XSD)

Note:

If the server is not working, then we are using “file-based mds”

File Based MDS creation:

View resource palette New connection —-> SOA – MDS

Connection name(file based – MDS) , connection type (file based MDS)  browse (C:/oracle/middleware/ j developer/…./seed)select ‘seed’  text connection àok

XML,XSD,XSLT,WSDL(central repository  reused assets/artefacts)

Note: All projects WSDL keeping in OER folder(11g)

DB Based MDS:

1. Jar (java archives) XSD’s, XML’s, XSLT’s, WSDL’s
2. SOA Bundle
3. Deploy into server
4. Jar:

Create new project Select – generic project

Project name (DB based – MDS)  finish

Note: this name doesn’t show is server, only files shows in server

Right click on projectnew  click

Select Deployment + profiles

Select  JAR file ok

Deployment profile name (DB Based – jar ) ok

Click on  contributors and unmark  project o/p directory  project dependencies

Add browse (c:/oracle/middle ware /…../apps)

Ok

Click on filters ok  ok

Note : select or remove XML,XSD….

2. SOA Bundle:

Select – project(DB based – mds)  Click  New  click

Select – deployment profiles, SOA bundle  ok 

Deployment profile name/DB Based – bundle –ok 

Select – dependences, DB based _ jar  ok ok

3. Deploy into the server:

Select project (DB based _ MDS) 

Click Deploy – DB Based 

(Deploy to SOA Bundle) next next  Finish

Select project (DB Based _MDS) Click 

Deploy – DB Based – Bundle  Deploy to application server  next next 

App_ server _ Ramesh1  next  default next finish.

DB Based MDS creation:

View —-> resource palette  data base –right click  new DB connection  connection name(RCU_ MDS), Username(dev_ MDS), pass word(welcome1)

Test connection   ok

View  resource palette

Click new connection   SOA _MDS

Connection name(DB Based _MDS), connection Type(DB Based MDS), connection (RCU_MDS), select MDS Partition(SOA _ Infra ) test connection ok

Note:

MDS – Only one server

OER (11g) Oracle Enterprise Repository à multiple server (or) MDS(Total company)

BSR(10g) Business service repository à multiple server (or) MDS(Total company)

Unit Testing (in project it shows test suites)

2 types of testing

1. Auto mation testing
2. Manual testing(our doing)

• Actual value = Expected value à test case pass
• Actual value = ! Expected value à test case

• Assertion is must in real time
• Input not given to the process we are given “Dummy input”.

If the client (or)DB – select is not ready to use but, we want to test the process that time we will use “unit testing”.

Project: CC validation

• It automatically creates tests, inside test suites

Double click on valid _1234 .XML

Case 1:

Double click on CCvalidation _client

Generate sample à click

Change:

1234-1234-1234-1234

20,000

Ok

Case 1: we are giving dummy input to the process

Case 2: Data not send to the DB _select, but it gives dummy o/p